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.

```text 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

1. Editor-in-Chief agent:
2. Read Initiative from Editorial Work view
3. Create Workstream "Editorial — Test Article", Stage: assign
4. 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.

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

1. Product Manager agent:
2. Read Initiative from Product Work view
3. Create Workstream "Product — Test SaaS", Stage: discover
4. Advance: discover → explore → score → build-gate
5. Set Estate: Portfolio-org

6. Set Active Role: Engineering Lead ✓ Estate visible in Workstream properties ✓ Engineering Lead can read estate from Software Work view

7. Engineering Lead agent:

8. Read Initiative + estate from Software Work view
9. Create Workstream "Software — Test SaaS", Stage: frame
10. Estate is Portfolio-org → plan independent website, Konstant-Ventures org
11. Advance: frame → design → implement → verify → promote → deploy
12. Set Active Role: Platform Engineer (for Operate)

13. Create new Workstream "Editorial — Test SaaS release", Active Role: Editor-in-Chief ✓ Platform Engineer sees Operate workstream ✓ Editor-in-Chief sees Editorial workstream

14. Platform Engineer agent:

15. Read from Operate Work view
16. Create Workstream "Operate — Test SaaS", Stage: run
17. 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

1. Portfolio Manager agent:
2. Review all workstreams
3. 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.

```text 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

1. Portfolio Manager agent:
2. Read the Services workstream note
3. Create new Product Workstream "Product — Client X Tool"
4. 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