Verification

Verification & Quality Assurance

The T3op project adheres to strict evidence-based verification gates prior to mission sign-off.

flowchart TD
    G1[Gate 1: Wiki Published & HTTPS Live] --> G2[Gate 2: Adapter & Desktop Stripping Audit]
    G2 --> G3[Gate 3: Subprocess OMP Adapter Stream Turn]
    G3 --> G4[Gate 4: Headless Chrome Browser Walk]
    G4 --> G5[Gate 5: Cryptographic Evidence Ledger]

Verification Gates

Gate 1: Documentation Precondition

• Requirement: https://wiki.t3op.loca.zone must be published and serving 200 OK via Nginx reverse proxy before application modifications commence.
• Proof: Successful HTTP status check and TLS certificate validation.

Gate 2: Adapter & Desktop Stripping

• Requirement: No non-OMP agent adapters (Codex, Claude Code, or third-party APIs) or Electron/Tauri desktop wrappers remain in the active codebase.
• Proof: Grep sweep across codebase confirming zero occurrences of stripped SDK imports or desktop runtime dependencies.

Gate 3: Live OMP Backend Round-Trip

• Requirement: The web interface must successfully trigger and stream a real turn from the host omp installation (18.2.6 at ~/.local/bin/omp).
• Proof: Server event log and transcript JSON capturing message deltas and completed turn status.

Gate 4: Headless Chrome Browser Walk

• Requirement: Automated browser execution via /usr/bin/google-chrome --headless=new.
  • Capture UI screenshot to evidence/2026-09-20-d132-t3op-345b3634/t3op-ui.png.
  • Capture browser console logs to evidence/2026-09-20-d132-t3op-345b3634/console.log verifying 0 console errors.
• Proof: Screenshot artifact and error-free console transcript.

Gate 5: Cryptographic Evidence Ledger

• Requirement: Full audit manifest in evidence/2026-09-20-d132-t3op-345b3634/result.json containing SHA-256 checksums of all deliverables, commits, and logs.
• Proof: sha256sum -c validation pass.