Phase 08 · Verification

openlogos verify reads test-results.jsonl, cross-references it against your requirements and test case documents, and produces a structured verification report. Every requirement traces to a test case, every test case to a result.

Prerequisites

All test code must use the OpenLogos reporter to write results:

import { reporter } from 'openlogos';

reporter.pass('UT-S01-01');
reporter.fail('UT-S01-02', 'Expected 409, got 200');

logos/resources/verify/test-results.jsonl must exist and contain results for all test IDs defined in Phase 06.

Running verification

cd my-project && openlogos verify

Output

logos/resources/verify/verification-report.md — a structured report showing:

Total requirements: N
Requirements with full coverage: N
Requirements with gaps: N (listed by ID)
Failed test cases (listed with error messages)
Overall verdict: PASS or FAIL

Interpreting the report

A PASS verdict means every acceptance criterion has at least one passing test case. This is the gate for openlogos launch.

A FAIL verdict lists exactly which requirements lack coverage and which tests failed — no guessing required.

Next step

Run openlogos launch to activate change management, then read about Change Proposals for managing future iterations.