Plan

Engineering Plan: D-132

The D-132 mission is structured into four sequential phases, strictly gated to ensure documentation, stability, and verifiable evidence at every step.

gantt
    title D-132 Execution Phases
    dateFormat  YYYY-MM-DD
    section Phase 1
    Wiki & Upstream Survey :active, p1, 2026-09-20, 1d
    section Phase 2
    Fork & Strip Adapters  :p2, 2026-09-20, 1d
    section Phase 3
    Serve & Route App      :p3, 2026-09-20, 1d
    section Phase 4
    Receipt & Signal       :p4, 2026-09-20, 1d

Phase 1: Wiki First & Upstream Survey (Gates App Work)

• 1.1.1 Started Receipt: Write evidence/2026-09-20-d132-t3op-345b3634/started.json (decision, run, started_at, seat).
• 1.1.2 Model Verification: Confirm Gemini roles active (Gemini 3.8 Flash light, Gemini 3.1 Pro heavy).
• 1.2.1 Upstream Identification: Locate upstream pingdotgg/t3code on GitHub, pin commit sha (0ff87f251dafb32703d5f531e7b248ad0a581ee2), record licence in docs/UPSTREAM.md.
• 1.3.1 Workspace Survey: Confirm absence of /home/loca/dev/t3cd, document supersession, and verify loopback port allocation (7531).
• 1.4.1 Wiki Scaffold: Stand up /home/loca/dev/wikis/t3op/, build via build.sh t3op, configure nginx and certbot for wiki.t3op.loca.zone.
• 1.5.1 Publish Core Pages: Overview, Upstream & Licence, Architecture, Plan, Progress Log, Verification.
• 1.6.1 Gate Clearance: Verify wiki live status (200 OK) before commencing application changes.

Phase 2: Fork & Strip

• 2.1.1 Upstream Vendoring: Copy/vendor pinned commit into app/ with clean provenance attribution.
• 2.2.1 Strip Non-OMP Adapters: Remove Codex, Claude Code, and all external provider APIs; remove Electron/Tauri desktop wrappers.
• 2.3.1 OMP Backend Adapter: Implement streaming omp driver executing ~/.local/bin/omp with JSON event normalization.
• 2.4.1 Local Persistence: Store all user sessions in data/sessions/; verify no remote CDN references.

Phase 3: Serve & Route

• 3.1.1 Production Build & Unit: Build web assets, record build hash, create and enable systemd user unit t3op.service on loopback port 7531.
• 3.2.1 Ingress Routing: Deploy deploy/t3op.loca.zone.nginx.conf, enable site, issue Let’s Encrypt TLS certificate via certbot.
• 3.3.1 Headless Chrome Verification: Capture UI screenshot, execute full conversational turn with tool execution, verify zero console errors.

Phase 4: Receipt & Signal

• 4.1.1 Final Receipt Ledger: Write evidence/2026-09-20-d132-t3op-345b3634/result.json with full integrity checksums.
• 4.2.1 Wiki Final Sync: Synchronize progress logs and verification pages with finalized hashes and receipts.
• 4.3.1 Signal Transmission: Emit T3OP_D132_COMPLETE and notify tmux wait-for -S t3op-d132-complete-9c0d0197279024ebc077640596bbe9f9.