omp-flow-check

OMP-Flow Check

Required Inputs

Fail closed unless all are available:

• task Bundle root, review role, bounded objective, and work entry Concept;
• explicit Review Concept output path;
• native reviewer actor ID and review dispatch receipt;
• completed implementation predecessor receipt from a different actor;
• work Concept and predecessor-linked handoff, plus any applicable linked design or decisions;
• real implementation diff;

Review Order

Only Main/coordinator may dispatch, correlate operations/receipts, obtain or record human calibration, and choose a workflow transition. Those coordinator actions are inapplicable to an already-dispatched Reviewer: it must not dispatch or self-redispatch, govern, calibrate, transition, or selectively reinterpret coordinator clauses. The Reviewer still owns the complete bounded independent Review and assigned Review Concept: compare actual code and verification with the intended work/Design consequence, and report evidence contradicting the Design or its principal-problem framing through that output rather than let a handoff or superficial green check substitute for the practice result.

1. Resolve the completed predecessor operation and use its output path as the required handoff. Read the work Concept and handoff, verify they identify each other, then inspect the real diff and changed files.
2. Check scope and acceptance criteria against the work Concept and approved design.
3. Inspect correctness, edge cases, error behavior, security, maintainability, and test adequacy proportional to risk.
4. Verify applicable linked decisions, interfaces, and source constraints.
5. Run independent focused tests and broaden checks for shared behavior or contracts.
6. Write the Review Concept at the supplied output path, link it to the work and handoff, lead with severity-ordered findings, give every finding all applicable HARD_BLOCKER, PRINCIPAL_BLOCKER, WORK_FAIL, and ADVISORY labels, and record exact commands/results.