Skip to content

Gatekeeper end-to-end test

Test plan for verifying that all 6 gatekeeper agents can hand off an Initiative through a complete lifecycle. Requires Notion databases set up per guides/notion-setup.md.

Prerequisites

  • [ ] Notion databases created (Initiatives, Workstreams, Deliverables)
  • [ ] Notion integration created, token in Bitwarden as CONDUCTOR_NOTION_READ_TOKEN
  • [ ] All 6 gatekeeper views created in Workstreams database
  • [ ] Agent CLIs installed (opencode, codex) per guides/agent-cli-orchestration.md

Test 1: Path C — Content (simplest, 2 gatekeepers)

The shortest path. Tests Portfolio → Editorial handoff.

1. Portfolio Manager agent:
   - Create Initiative "Test Article" in Notion, Path C, P2
   - Set Active Role: Editor-in-Chief
   ✓ Initiative visible in Editorial Work view

2. Editor-in-Chief agent:
   - Read Initiative from Editorial Work view
   - Create Workstream "Editorial — Test Article", Stage: assign
   - Assign desk, author, deadline
   ✓ Workstream visible in Portfolio Work view

Result: 2 gatekeepers, 1 handoff. Information flows through Notion.

Test 2: Path A — Commercial (full gate, 4 gatekeepers)

The most complex path. Tests all handoffs and the estate decision.

1. Portfolio Manager agent:
   - Create Initiative "Test SaaS", Path A, P1
   - Set Active Role: Product Manager
   ✓ Active Role changed, WIP slot checked

2. Product Manager agent:
   - Read Initiative from Product Work view
   - Create Workstream "Product — Test SaaS", Stage: discover
   - Advance: discover → explore → score → build-gate
   - Set Estate: Portfolio-org
   - Set Active Role: Engineering Lead
   ✓ Estate visible in Workstream properties
   ✓ Engineering Lead can read estate from Software Work view

3. Engineering Lead agent:
   - Read Initiative + estate from Software Work view
   - Create Workstream "Software — Test SaaS", Stage: frame
   - Estate is Portfolio-org → plan independent website, Konstant-Ventures org
   - Advance: frame → design → implement → verify → promote → deploy
   - Set Active Role: Platform Engineer (for Operate)
   - Create new Workstream "Editorial — Test SaaS release", Active Role: Editor-in-Chief
   ✓ Platform Engineer sees Operate workstream
   ✓ Editor-in-Chief sees Editorial workstream

4. Platform Engineer agent:
   - Read from Operate Work view
   - Create Workstream "Operate — Test SaaS", Stage: run
   - Write evidence: "Health checks passing, monitoring configured"
   ✓ Stage visible to Portfolio Manager at Review

4b. Editor-in-Chief agent:
   - Read from Editorial Work view
   - Create Workstream "Editorial — Test SaaS", Stage: assign
   - Write release piece
   - Advance: assign → report → draft → edit → fact-check → publish
   ✓ Published URL recorded in evidence

5. Portfolio Manager agent:
   - Review all workstreams
   - All 3 active (Software: document, Operate: run, Editorial: publish)
   ✓ Review complete, next review date set

Test 3: Cross-line loop (Services → Software)

Tests the via-Portfolio re-routing pattern.

1. Engagement Manager agent:
   - Create Workstream "Services — Client X", Stage: deliver
   - Client needs billable software → note on Workstream
   - Set Active Role: Portfolio Manager
   ✓ Portfolio Manager sees the re-routing request

2. Portfolio Manager agent:
   - Read the Services workstream note
   - Create new Product Workstream "Product — Client X Tool"
   - Set Active Role: Product Manager
   ✓ Product Manager sees the new evaluation

Success criteria

  • [ ] Initiative flows through all gatekeepers without manual intervention
  • [ ] Each gatekeeper reads from the correct Notion view
  • [ ] Estate decision (Product) reaches Engineering Lead without re-entry
  • [ ] Handoff via Active Role field is instantaneous (no waiting, no manual sync)
  • [ ] Google Calendar events appear for Due Dates
  • [ ] No gatekeeper writes to a database they shouldn't