Expand description
Durable session-scoped review findings for sticky reply / multi-scenario review.
§First principles
Review exists to independently verify claim↔record, persist findings beside the session transcript, and drive real correction — not to paint a local “resolved” badge.
Lifecycle (host-enforced):
pending → addressed (main agent) → accepted (reviewer) |
pending ← reopen from addressed | waived from pending.
Only pending findings whose registered ReviewScenario opts into
injects_into_main are prefixed into the next main-agent prompt.
§Core vs extension
- Core: lifecycle,
SessionReviewStoreV1snapshot field, inject fence,ReviewSubjectV1, scenario registry APIs. - Extensions:
ReviewScenarioimplementations (hosts / Use packages) own rubrics and evidence collection. Core never matches on scenario business rules beyond registry lookup.
Distinct from [crate::research] review contracts: those bind research
artifacts and digests.
Structs§
- Reply
Transcript Scenario - Host scenario for Desktop / CLI sticky reply review (rubrics stay in the host).
- Review
Finding Draft - Draft finding produced by a scenario before Core assigns session identity.
- Review
Scenario Registry - Process-local registry of review scenarios for one session runtime.
- Session
Review Anchor V1 - Durable pointer into the session transcript (no message body copy).
- Session
Review Finding V1 - One durable session review observation (multi-scenario envelope).
- Session
Review Store V1 - One session’s durable review findings (sticky reply / science review).
Enums§
- Review
Subject V1 - Bound review target. Scenarios choose a subject; Core does not invent rubrics.
- Review
Trigger Policy - When a scenario may be armed by the host runtime.
- Session
Review Error - Validation failures for session-scoped reply / science review findings.
- Session
Review Severity V1 - Product-neutral severity for host routing / annotation chrome.
- Session
Review Status V1 - Durable finding lifecycle for sticky reply / multi-scenario review.
Constants§
- SCENARIO_
REPLY_ TRANSCRIPT - Well-known built-in scenario id for transcript sticky / science reply review.
- SESSION_
REVIEW_ FINDING_ SCHEMA_ V1 - SESSION_
REVIEW_ MAX_ FINDINGS - SESSION_
REVIEW_ MAX_ ID_ BYTES - SESSION_
REVIEW_ MAX_ MESSAGE_ BYTES - Maximum JSON payload for one finding or store document.
- SESSION_
REVIEW_ MAX_ TEXT_ BYTES - SESSION_
REVIEW_ STORE_ SCHEMA_ V1
Traits§
- Review
Scenario - Host-supplied review scenario. Rubrics live here — not in Core.
Functions§
- admit_
finding_ drafts - Admit scenario drafts into the durable session review store.
- register_
default_ scenarios - Register the built-in reply.transcript scenario (idempotent replace).