jigor 0.1.0__py3-none-win_amd64.whl

jigor-0.1.0.dist-info/METADATA

@@ -0,0 +1,278 @@
+Metadata-Version: 2.4
+Name: jigor
+Version: 0.1.0
+Classifier: Environment :: Console
+Classifier: Programming Language :: Rust
+Classifier: Topic :: Text Processing
+License-File: LICENSE
+Summary: System One decision gateway — local von/laya ONNX backends plus the remote jev Decisions API (OpenRouter); one wire protocol across models.
+Keywords: system-one,decisions,onnx,gateway
+Author-email: Iurii Zatsepin <support@zatsepin.dev>
+Description-Content-Type: text/markdown; charset=UTF-8; variant=GFM
+Project-URL: Documentation, https://github.com/Partysun/jigor#readme
+Project-URL: Homepage, https://github.com/Partysun/jigor
+Project-URL: Repository, https://github.com/Partysun/jigor
+
+# jigor — System One decision gateway (Rust lib)
+
+System One decision models in Rust, one wire protocol across backends: `von`
+and `laya` run locally as ONNX (via `ort`); `jev` runs remote on OpenRouter's
+Decisions API.
+
+## Models
+
+- HF `sevenreasons/von-onnx-fp16` (`model.onnx` 759M, `tokenizer/tokenizer.json` 3.5M)
+- HF `Mattepiu/laya-onnx` (`laya.onnx` fp32 — matches the python reference
+  bit-for-bit; `int8/laya_int8.onnx` via `LAYA_ONNX_FILE`)
+- OpenRouter Decisions (`typesafe/jev-1.13` today) — any model there speaking
+  the same System One wire works; add it to `known_providers()` and nothing
+  else changes.
+
+## Usage as lib
+
+One dependency, one entry per backend — `noul`/`choice`/`score` questions
+in, typed answers out. Identical on von, laya and any OpenRouter model.
+
+```toml
+[dependencies]
+jigor = { path = "../jigor" }                             # local checkout
+# jigor = { git = "https://github.com/Partysun/jigor" }   # from GitHub
+# jigor = "0.1.0"                                         # once published
+serde_json = { version = "1.0" }                          # Value, json!
+```
+
+```rust
+use jigor::{Answer, Question, Backend, Result, VonBackend, choice, noul, score};
+use serde_json::json;
+
+fn main() -> Result<()> {
+    let mut von = VonBackend::new()?;   // VonBackend::new, LayaBackend::new,
+                                        // OpenRouterBackend::for_model(...):
+                                        // the same answers() call on all three
+    let questions = vec![
+        noul("churn", "Is the customer likely to churn?"),
+        choice(
+            "want",
+            "What does the customer want?",
+            &["refund", "order status", "technical help"],
+        ),
+        score("urgency", "How urgent is this?", &["calm", "annoyed", "angry"]),
+    ];
+    let asks = von.answers(
+        &json!("Customer: I was charged twice for order #4471."),
+        &questions,
+        None,
+    )?;
+
+    match asks.get("churn").unwrap() {
+        Answer::Noul { probability } => println!("churn: {:.4}", *probability),
+        _ => {},
+    }
+    Ok(())
+}
+```
+
+Only have a model id? `jigor::ask` resolves aliases and the provider for you:
+
+```rust
+let asks = jigor::ask("jev", &state, &questions, None)?;  // OpenRouter jev
+let asks = jigor::ask("laya", &state, &questions, None)?; // local laya
+// Asks { model, backend, answers }
+```
+
+Errors are one type — `jigor::Error` (carried by
+`jigor::Result<T>`): `UnknownModel`/`MissingApiKey`/`Remote` for
+routing and OpenRouter responses, `Wire`/`MissingAnswer`/`MissingAnswers`
+for malformed question/answer payloads, `Serialization` for JSON text,
+`External`/`Internal` for everything else. No foreign error type ever
+leaks out of the library.
+
+```rust
+use jigor::{Error, Result};
+
+match von.answers(&state, &questions, None) {
+    Ok(asks) => { /* typed answers */ }
+    Err(Error::Remote { status, message }) => { /* upstream 4xx/5xx */ }
+    Err(e) => println!("{e}"),
+}
+```
+
+## Production: library vs installed CLI/server
+
+One workspace, two crates (`crates/jigor` + `crates/jigor-cli`), one pip
+distribution — the same code, three ways to consume it:
+
+- **Library** — `jigor = { version = "0.1.0" }` in your crate (see
+  `Usage as lib`). Only the library target is compiled: the CLI/server code
+  and its dependencies (hyper, tokio, ...) never enter consumer builds.
+- **CLI + server (cargo)** — `cargo install jigor-cli` installs the `jigor`
+  binary: `jigor serve`, `jigor ask`, `jigor models`.
+- **CLI + server (npm)** — `npm install --global jigor` (prebuilt binary,
+  per-platform packages: linux x64/arm64, macos universal2 — Intel + Apple
+  Silicon, windows x64).
+- **CLI + server (pip)** — `pip install jigor` (maturin wheel) installs the
+  same `jigor` console script.
+
+The local ONNX models (`von`, `laya`) download to `~/.cache/huggingface` on
+first use; set `OPENROUTER_API_KEY` for the remote `jev` backend. Both crates
+are published together (`make publish`) from the shared version in
+`Cargo.toml`; the wheel and the npm binary packages are published by the
+release pipelines (`.woodpecker/wheel-*.yml`, `.woodpecker/npm-*.yml`).
+
+## Run examples (lib crate, no bin)
+
+```bash
+cargo run -p jigor --example decide            # same as Python main.py
+cargo run -p jigor --release --example bench   # bench
+cargo run -p jigor --example decide --offline
+```
+
+Expected `decide`:
+
+```
+infrastructure
+0.428
+{'infrastructure': 0.6203, 'billing': 0.1873, 'feature_request': 0.1924}
+judge: 0.3586
+rate score: 1.02 conf: 0.707 probs: {"1": 0.8109, "2": 0.1036, "0": 0.0855}
+fan-out intent: payment_failure 0.539
+```
+
+Set `JIGOR_DEVICE=cuda` to try CUDA EP
+(`ort` `cuda` feature, fallback to CPU if unavailable).
+
+## Run as executable: `jigor`
+
+```bash
+cargo build -p jigor-cli --release
+./target/release/jigor serve --host 0.0.0.0 --port 8000   # HTTP gateway
+jigor models                                              # provider x model pairs
+```
+
+The gateway mirrors the library: noul/choice/score questions in, typed
+answers out — `von`/`laya` locally, anything else routed to the OpenRouter
+backend selected by the `model` field:
+
+```bash
+jigor ask <<'JSON'   # same wire over stdin, no HTTP layer
+{
+  "state": { "error": "Disk volume /var/log at 98% capacity." },
+  "questions": {
+    "requires_intervention": {
+      "type": "noul",
+      "instructions": "Does this disk space condition require operational intervention?"
+    }
+  }
+}
+JSON
+# {"model":"von-1.0.0","backend":"local","answers":{...}}
+
+# pin the provider, or use the "jev" alias for typesafe/jev-1.13 on OpenRouter:
+jigor ask --provider openrouter --model jev < request.json
+jigor ask --model jev < request.json          # provider inferred from the id
+```
+
+```bash
+curl -X POST http://localhost:8000/v1/systemone \
+  -H "Content-Type: application/json" \
+  -d '{
+    "model": "von-1.0.0",
+    "state": { "error": "Disk volume /var/log at 98% capacity." },
+    "questions": {
+      "requires_intervention": {
+        "type": "noul",
+        "instructions": "Does this disk space condition require operational intervention?"
+      }
+    }
+  }'
+# {"model":"von-1.0.0","backend":"local","answers":{"requires_intervention":{"type":"noul","noul":0.2739}}}
+```
+
+Route by provider + model pair — `typesafe/jev-1.13` (alias `jev`) goes to
+OpenRouter, `von-1.0.0` (alias `von`) stays local; unknown pairs are rejected.
+
+Also: `GET /healthz` returns `{"status":"ok"}`.
+
+## Tweet Tester (example: using the lib)
+
+`examples/tweet.rs` is a complete Tweet Tester written _only_ against the lib
+API — it demonstrates how to build a Jev-style tool on top of
+`noul`/`choice`/`score` questions through one `answers` interface. All
+tweet-specific code lives in the example (the lib itself stays generic):
+
+- the 61-question viral-score bank (question set `v1.1`, 8 families
+  EMO/CNV/SHR/TIM/CRF/IDN/FMT/ANTI);
+- a transparent 0-100 aggregation (`0.65 * content mean + 0.35 * clean
+anti-signal`) — scoring semantics: 50 = your account's normal post, above
+  50 beats it, below 50 does worse;
+- per-family "fired % of N questions" radar stats, top helped/hurt, and
+  engagement `counters` (a wire JSON shape mirroring the viral-score API).
+
+```bash
+cargo run -p jigor --example tweet -- "We just crossed 10,000 paying customers. Thank you."
+cargo run -p jigor --example tweet -- --json "We just crossed 10,000 paying customers."
+# {"score":53,"beats_own_normal":0.53,
+#  "families":{"EMOTION":{"label":"Emotion","fired":0.11,"total":9},...},
+#  "counters":{"likes":{"multiple":1.1,"p75":2.1,"p90":4.6,"breakout_share":0.1,"probability":0.5,"confidence":"normal","own_median":null,"expected":null},...},
+#  "helped":[{"id":"k_concrete_numbers","family":"CRAFT","label":"Numbers that carry weight","answer":"Yes","detail":"Stronger than your usual post","effect":0.95}],
+#  "hurt":[...],"answers":[...61 items...],"engine":{"model":"von-1.0.0","question_set":"v1.1",...}}
+```
+
+The example resolves the backend by model, exactly like `jigor ask`: `--model
+von` (default, local ONNX), `--model jev` (OpenRouter) or any other alias.
+The 61-question bank, score, radar and counters are identical across
+backends, so you can compare the same tweet side by side:
+
+```bash
+cargo run -p jigor --example tweet -- --model von "We just crossed 10,000 paying customers. Thank you."
+cargo run -p jigor --example tweet -- --model jev "We just crossed 10,000 paying customers. Thank you."
+cargo run -p jigor --example tweet -- --model jev --json "Hot take." > jev.json
+```
+
+For the milestone tweet the outputs line up: von gives 53/100 (conservative,
+CRAFT 35%), jev gives 63/100 (CRAFT 73%). Scores across backends are not
+calibrated to each other, but the shape is directly comparable.
+
+Family `fired` is the "X% of its questions fired" radar value. The engagement
+`counters` (multiples, p75/p90, probabilities) and the `effect` coefficients
+are transparent placeholders for a fitted engagement model — tune the
+weights in the example's `counter_json`/`counter_multiple` once you have
+paired data. Von is a general decision model, so scores are a signal, not a
+forecast; fitting an engagement model on the same answers is the calibration
+step.
+
+Question builders: `choice` takes plain option strings (each is both key and
+description), `choice_pairs` takes `(key, description)` pairs, `score` takes
+ordered level texts, `noul` a plain instruction — and all three kinds mix
+freely in one `answers` call.
+
+## Auto-tagger (example: using the lib)
+
+`examples/tagger.rs` shows a `choice` workflow: given a note and a list of
+existing tags, one question — "Which tag best matches the content of this
+note?" — picks the best tag (or the `None of these fit well` fallback) with a
+probability distribution. Also runs on either backend via `--model`/`--provider`.
+
+```bash
+cargo run -p jigor --example tagger -- --title "Hiring notes" --tags "work, ideas, personal" "Budget approved for two engineers."
+# Best tag: work  (confidence 0.440)
+#   work 60%  ·  ideas 16%  ·  personal 13%  ·  None of these fit well 10%
+cargo run -p jigor --example tagger -- --model jev --tags "bugs, docs, ship" "Fixed the retry loop that dropped webhook events."
+cargo run -p jigor --example tagger -- --json --tags "a, b" "note text"   # wire JSON out
+```
+
+## Integration tests
+
+Requires [hurl](https://hurl.dev) and the local ONNX model (downloaded on
+first run). Wire fixtures live in `tests/fixtures/` (the OpenRouter Decisions
+request/response payloads are the reference for the wire format).
+
+```bash
+make test        # unit tests + hurl suite + CLI tests
+bash tests/hurl/run.sh   # jigor serve: /v1/systemone (health, noul, choice,
+                         # score, fan-out, error paths, backend routing)
+bash tests/cli/ask.sh    # jigor ask / jigor models over stdin fixtures
+# or against a running server:
+hurl --test --variable BASE_URL=http://localhost:8000 tests/hurl/*.hurl
+```
+

jigor-0.1.0.dist-info/RECORD

@@ -0,0 +1,6 @@
+jigor-0.1.0.data/scripts/jigor.exe,sha256=giM-GoubE4LUvxQFyWKr52fTX42eEo72aH5JF17b6Ng,25150976
+jigor-0.1.0.dist-info/METADATA,sha256=6Wzhoh_ct04TNB9RfE8vPWVlkGDS_gvqjefU5grYPUs,11882
+jigor-0.1.0.dist-info/WHEEL,sha256=8Aej0W0a6Cz6apA3IzJrTnxLRVLAt-w0Oh8SA3Con_c,94
+jigor-0.1.0.dist-info/licenses/LICENSE,sha256=fPOWp7LCFa6Y_N9_kc8FhumetfRCVfXtvHRHNOQhqjs,11574
+jigor-0.1.0.dist-info/sboms/jigor-cli.cyclonedx.json,sha256=mxcaWseC9P4NOH9emfiskmpPPNXDwoHZ0QVTBfNygoI,197734
+jigor-0.1.0.dist-info/RECORD,,

jigor-0.1.0.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: maturin (1.15.0)
+Root-Is-Purelib: false
+Tag: py3-none-win_amd64

jigor-0.1.0.dist-info/licenses/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [2026] [Iurii Zatsepin (https://zatsepin.dev)]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.