Docs
Docs
One page, the whole map: what you can use today, the wire every lane speaks, what a receipt holds, and where the deep reads live.
Start today
The free engine
Reflex answers typed questions on your machine, in microseconds, and abstains — says “not sure” — when the evidence is thin. Install commands, the playground and the agent skill live on its site.
live reflex.gist.rs →The hosted API
A keyed /v1/decide lane that speaks the same decision wire,
metered per answer, with a receipt on each answer. It ships with the
access plane; nothing is collectable until it opens.
The program
v2 plans a downloadable rethink program with leasable
specialists — the distributed phase. Designed, not built; there is no
download to link yet, so this page links none.
The decision wire
Every lane in the family speaks one shape. A request carries a state (the situation, in one block of text) and typed questions. Each question declares its answer space:
- choice — pick one option from a list you provide;
- score — a rubric level, lowest first;
- noul — a typed yes/no.
An answer carries the chosen outcome, a probability per option, and one calibrated confidence readout. Abstention is a first-class answer: an empty outcome means “not sure” — the probabilities still ride along, so your code branches on them instead of catching an error. The response also names the lane that served (the free floor, a trained encoder, or a hybrid) and discloses its calibration posture, so you always know what produced the numbers.
Full reference, captured live from the shipped binary: the
API page on reflex.gist.rs.
The wire contract itself is public in the katgpt-rs repository — the
feature
catalog's decision_wire section. For agents, the
reflex-integration skill walks
the whole pattern: install, ask, abstain-branch, fit thresholds from your
own labeled data.
What a receipt contains
Every answered decision carries a receipt: the build fingerprint of the binary that answered, a hash (a short digest that changes if the bytes change) of the input, a hash of the canonical decision, and the lane id. It is a hash record, not a signature — it shows what was answered; it is not a claim of authority.
Because the free floor is deterministic — the same release, the same input, the same answer — anyone can re-run a receipt and compare the hashes. That is the check the trust section walks through step by step.
Decision stats are separate, and off by default. If you opt in, your machine sends counts only — how many decisions, how many abstentions, per suite — never the text of your questions or answers. The lane runs on our test network today; the privacy page holds the full posture.
The docs map
- resources.md — “Rethink — the encoder tier”: what each rung is, in plain words.
- model_classes.md — the deep dive: encoder, autoregressive, and what trains.
- dev_flow.md — how a change travels from an idea to a measured, seated lane.
- The trust section — every piece marked live, on the test network, or planned.
- Privacy · Terms · security.txt
Not here yet
The rethink-integration skill, the API-key auth guide, and the rate-limit and error-code table all ship with the hosted tier. They describe a surface that does not serve yet, so this page links nothing for them. When the lane opens, they land here first.