Review boundaries
Review Boundaries
Section titled “Review Boundaries”Agent instruction protocol: 1.0.
Behavioral compliance depends on the connected agent or integration. The Day Shift CLI exposes repository policy and evidence, but it cannot force an unsupported agent to obey them.
Review reports what current evidence supports. It does not perform the action it recommends.
Boundary map
Section titled “Boundary map”| Evidence or action | Default posture | What it does not imply |
|---|---|---|
| Orientation, discovery, inventory, gap, next-action, smoke, links, readiness review, artifact review | Read-only | Selection, repair, authorization, acceptance, or closeout |
| Readiness authorization | Explicit write | Attempt opening or implementation permission beyond the selected contract |
| Validation execution, manual record, or imported evidence | Explicit selected transition | Acceptance, disposition, or task close |
| Implementation completion | Explicit write | Review acceptance, attempt close, task close, or parent completion |
| Review disposition | Explicit write bound to current review evidence | Task close or reconciliation acceptance |
| Receipt-bound apply | Explicit write with exact preconditions | A second source of authority or permission to reuse stale evidence |
| Reconciliation build | Explicit write | Final judgment, acceptance, metadata synchronization, or follow-up creation |
| Metadata synchronization | Explicit reviewed write | Repair of bodies, traceability, or unrelated artifacts |
Reading findings
Section titled “Reading findings”- Blocking findings stop the proposed transition until the owning evidence is repaired or explicitly routed.
- Warnings require review or explicit acceptance; they are not hidden permission to write.
- Administrative drift can be reported without changing metadata when the active posture is read-only.
- Suggested commands are callable guidance only. Recheck authorization, selection, revisions, effects, and confirmation before invocation.
A clean review remains read-only. A receipt proves that an applied mutation occurred; it does not replace the authorization and preconditions that allowed that mutation.
Freshness and replay
Section titled “Freshness and replay”Bind every mutation to the exact current artifact pair and review receipt it consumes. If either revision changes, stop and refresh the supported preview or review. Preserve stale evidence as history rather than editing it into a current-looking result.
Handoff
Section titled “Handoff”Use Task instructions for the task transition sequence. Use Stop and escalate when findings require authority the current request does not grant. Return to Current work when review changes the active-artifact handoff, or restart with Agent orientation when policy context changes.