Stipryn™ fixes the required proof level before transmission, while the party bearing the consequence still controls the request.
Proof level is usually settled by whoever receives the request, after it arrives, on their terms. That is the wrong end of the exchange. The party who carries the consequence of a weak answer is the party composing the request, and by the time it has been sent their leverage is gone.
A request goes out. Somewhere downstream a decision gets made about how much evidence will come back with the answer. The composing party finds out what grade of proof they got when they read the response, which is after every decision that mattered has already been taken.
The receiver sets the evidentiary bar. The sender absorbs the risk if that bar was set low.
If the requirement was never fixed anywhere, there is nothing to point at later. A dispute becomes one recollection against another.
Treating every request as needing maximum proof is expensive and slow. Most requests do not need it. Some parts of some requests do.
Three steps, all of them completed before the request is transmitted.
The request is examined as composed. Stipryn™ reads it to identify the regions that carry evidentiary weight. The request is not altered in any way.
Regions of the request are anchored, so a requirement can attach to a specific part rather than to the whole. A figure that will be relied on can demand more than surrounding context.
Each anchored region is mapped to a required proof level, and that requirement is bound before the request leaves the composing party. The demand is fixed while they still control what is being asked.
The request is never modified. Stipryn™ produces a separate, bound requirement that travels alongside what was composed. The words that were written are the words that are sent. Nothing is rewritten, expanded, reordered, or injected, and the composing party keeps full control of their own request.
One request can carry several requirements at once, because not every part of it carries the same consequence.
| Anchored region | Why it is graded | Bound before sending |
|---|---|---|
| A figure that will be relied on | It will be entered into a downstream system or a filing, so its basis has to be checkable. | Yes |
| A claim about an external fact | It can be checked against a source, so the requirement can demand that the source be identified. | Yes |
| Framing or background text | It shapes the answer but is not relied on directly, so it can carry a lower requirement. | Yes |
The grading is set by the composing party as part of the act of composing. Stipryn™ records what was required, so the requirement is available later as evidence of what was asked for.
Stipryn™ is one of four families filed on July 31, 2026, alongside Foretoken™, Multi-Source Divergence Detection (MSDD), and Bonded Performance Attestation (BPA). It is a pre-submission primitive, so it operates earlier than the receipt work that covers what came back.
Commits to a streamed run before the first token and seals it at the close. Read
Fixes the required proof level before a request is transmitted.
Binds asserted and separately observed values without merging them. Read
Binds a declared performance budget and the actual distribution to the same response. Read
This is filed work and is not yet a public endpoint. The receipt discipline underneath it is live now: canonicalize, hash, sign, verify, and check it yourself in the browser.
Stipryn™. Patent pending, filed July 31, 2026. Pre-submission proof-level binding: analyzes a request without mutating it, anchors regions, and binds a required proof level before transmission. Hive Civilization Inc.