Interactive demo
One real Context Run, step by step
This walks through one real Context Run over a synthetic scenario from scenarios/equility-transaction-categorization — no sign-in, no customer data. Every value below is read from a committed Context Package; nothing is fabricated.
Request
What was asked: the task, who is asking, what it's scoped to, and how it arrived.
- Task
- assess_transaction_categorization
- Actor
- reviewer
- Scope
- transaction:T-1004
- Via
- sdk
Context required
What the bundle declares this task needs before it can be assessed — one requirement per row, with its own declared severities.
| Requirement | Kind | Detail | Min | Severity |
|---|---|---|---|---|
| vendor_resolved | path | transaction_vendor | 1 | missing=block, uncertain=block |
| precedent_or_rule | any_of | transaction_vendor → precedent_for_vendor OR transaction_vendor → rule_for_vendor | — | missing=warn |
| supporting_document_when_material | path | document_for_transaction (when transaction.amount ≥ materiality_policy.threshold) | 1 | missing=block |
| category_agreement | agree | rule.category == prior_categorization.category == transaction.proposed_category | — | conflicting=block |
| recent_business_context | path | transaction_vendor → note_for_vendor | 0 | uncertain=warn |
Sources examined
What was actually selected to satisfy those requirements, and how much was excluded and why.
| Record | Source | Selection basis / requirement |
|---|---|---|
| business_note:N-04 | equility_records | declared_key · recent_business_context |
| prior_categorization:PC-04 | equility_records | declared_key · precedent_or_rule |
| rule:R-04 | equility_records | declared_key · precedent_or_rule |
| transaction:T-1004 | equility_records | declared_key · requested scope |
| vendor:V-004 | equility_records | declared_key · vendor_resolved |
excluded: none total excluded 0 candidates considered 5
Findings
Structural facts about the context: what kind, which rule, what was expected vs. observed, and why it carries the severity it does.
| Severity | Kind | Rule | Subject | Severity source | Expected | Observed | Evidence |
|---|---|---|---|---|---|---|---|
| block | CONFLICTING | conflicting.agreement_unsettled | transaction:T-1004/category_agreement | requirement:category_agreement | a single agreed value | transaction.proposed_category=Equipment Rental | transaction:T-1004.proposed_category@f044f460c4a2e1ecfe5921d17e24d635739aa308027a0a4a4635f946a297b877 |
Verdict
The maximum severity over every finding above — READY, WARN, or BLOCK.
Evidence + trace
Every finding cites the exact record, field, and version it came from (see the Evidence column above); this is the full sequence of steps Tensor took to get there, in milliseconds.
Replay
Change one piece of context and watch BLOCK become READY.
The one record changed
- Record
- rule:R-04.category
- Before
- Equipment
- After
- Equipment Rental