01
Commit the rule
Fix the evaluation logic and the relevant window before incoming feed values can affect the result.
Hive primitive
Receipted Feeds and Triggers
Record what a feed delivered, evaluate it against logic fixed before the window opens, and export evidence another reviewer can check.
Public overview
Production routes disabled
Fixed before the window
A feed event becomes a bounded evidence record. The primitive separates the feed delivery, the rule that evaluates it, the resulting evidence state, and any later correction. Each part has a defined place in the record.
02
Record delivery
Record the committed representation of what the feed delivered for the named window.
03
Evaluate evidence
Apply the fixed logic and produce one explicit evidence state for the available record.
04
Preserve the trail
Append corrections and export the evidence without erasing the earlier record.
Three evidence states
No forced certainty. An outcome describes whether the committed record supports the fixed rule. It does not turn incomplete evidence into a pass or failure.
The evidence supports the fixed rule.
The required recorded conditions evaluate as true for the stated window.
The evidence does not support the fixed rule.
At least one required recorded condition evaluates as false.
The evidence cannot support a definite result.
Required evidence is missing, incomplete, or invalid for the stated evaluation.
Independent review
Export evidence that can be checked outside the workflow.
The exported evidence keeps the key relationships together so an independent reviewer can inspect the commitment, delivery record, fixed rule reference, outcome, and correction chain.
- 01The committed evaluation logic and window reference.
- 02The committed feed delivery record used for evaluation.
- 03The resulting satisfied, not satisfied, or indeterminate state.
- 04The append-only links between an original entry and any correction.
Illustrative applications
For high-consequence feed workflows.
Clinical systems
Record deliveries and fixed evaluation conditions without treating the receipt as a clinical decision.
Model providers
Preserve the inputs and rule references used for an evaluation window.
Insurers and assurance teams
Review independently checkable evidence without turning the primitive into a coverage or claims decision.
Enterprise data platforms
Maintain a durable record across delivery, evaluation, correction, and export steps.
Release posture
Production routes stay disabled until every gate passes.
This page describes the primitive. It is not evidence that production mint or trigger routes are enabled.
Routes disabled- 01The public conformance profile is approved for release.
- 02Satisfied, not satisfied, and indeterminate test vectors pass.
- 03Append-only correction and export checks pass.
- 04An independent evidence verification rehearsal passes.
- 05The production release review approves route enablement.
Start with the boundary
Map the feed, window, rule, and evidence state before integration.
Use a conformance review to define what will be recorded, what remains outside the receipt, and which release gates must pass.