12. Product Walkthroughs
Executive Summary
What this chapter establishes
The walkthroughs describe the intended operator and executive experience without claiming it exists today.
The manual should read like a product operating manual. Here is how the operator experiences the platform. (▣ These walkthroughs describe the Target State; today most steps still require Zach — see each surface’s grade in CURRENT_STATE.md.)
Morning in GLoops. Zach opens the Capability Portfolio. Overnight, three Ready issues were discovered, classified, and clarified; two clarifying questions were posted automatically; one needs his judgment and waits in the Action Queue. He reads the one card — recommended answer pre-filled, evidence attached — edits a word, approves. The capability learns from the edit. He never opened GitHub.
Morning in Ralph. Zach opens the Executive Room. The Chief of Staff briefs three deltas since yesterday; the CTO and Head of Product disagree on whether to ship a borderline change, and the dissent is on the record. One decision needs him; the brief has options, a recommendation, and the consequence of doing nothing. He decides. Ralph routes the decision; GLoops executes it.
Handling an Action Queue item. An item reads: “Approve production authority for the merge-readiness capability on Induct.” It states why it matters, shows the receipt history, recommends not yet (one gate unproven), and will expire in 48 hours. This is a reserved decision — exactly the kind that should reach a human. He defers; the dependent stream pauses; every other stream keeps moving.
Watching an autonomous capability. Zach opens a Capability Card and watches its autonomy meter — currently rung 2 (Proposal). He sees the rolling readiness assessment climbing on real receipts. When it reaches the bar, promotion to rung 4 will surface as an Action Queue item — never an automatic jump.
Reviewing receipts. In the Receipt Explorer he opens last night’s PR-review receipts. Each shows who decided, the original and final action, the reasoning summary, and the frozen evidence. Nothing is mutable; nothing is asserted without proof.
Approving work / understanding health. Portfolio Health shows manual_orchestration_remaining ticking toward zero and human_judgment_remaining holding steady (it is a floor — collapsing it would be a boundary violation). The single number Zach cares about: the SDLC Orchestrator role’s replacement percentage, and whether it moved this week.
Part V — The Transformation
Section titled “Part V — The Transformation”Chapter closeout
Decision ledger
Key Decisions
- Walkthroughs are implementation targets, not maturity claims.
Open Questions
- Which walkthrough should become the first end-to-end product demo?
Related Chapters
- Product Mockups
- Action Queue
- Ralph Executive Room