Product Surfaces
Story moment
The product is the proof
A surface earns its place when it shows what stopped being manual. Activity is noise; burden removed is signal.
Executive Summary
What this chapter establishes
The product surfaces turn the operating model from markdown into how the company is experienced, with concrete day-across-the-surfaces scenarios showing what the finished system feels like.
Humans must interact with the organization through products, not prompts. Each surface below is owned by the product the boundary assigns; each entry includes a description of its intended executive view (these descriptions are deliberate future implementation targets — no image assets are produced here).
11.1 The Action Queue — the primary human surface
Section titled “11.1 The Action Queue — the primary human surface”The Action Queue contains only items requiring human judgment — never routine work the system can do. Owner: Ralph (the executive render) over a GLoops projection (the reserved-decision items).
Each item must include: what decision is needed · why it matters · evidence · recommended option · consequences · expiration/urgency · affected organization · affected capability. Item types: approve a bounded operational mutation · answer a product clarification · approve production authority · decide priority · accept/reject a proposed comment · resolve a constitutional escalation · provide a credential/secret · approve a merge or deployment.
Intended screen — Action Queue. A single prioritized list; each card leads with the decision in one sentence, a recommended option pre-selected, the evidence one click away, the consequence of inaction, and an expiry. Empty state is the goal state: “Nothing needs you right now.”
11.2 The Capability Portfolio — what exists and what’s running
Section titled “11.2 The Capability Portfolio — what exists and what’s running”Owner: GLoops. Each capability renders as a Capability Card (see The Canonical Hierarchy §4.1): role responsibility replaced · organizations consuming it · current realization · Reference Realization · health · autonomy grade · evidence · receipts · active Work Orders · blocked states · next improvement · burden reduction.
Intended screen — Capability Portfolio. A grid of Capability Cards, filterable by family and grade, each showing its autonomy rung as a 6-segment meter and its current bottleneck in red. Sort by “largest burden remaining.”
11.3 The Organization Portfolio — onboarded organizations
Section titled “11.3 The Organization Portfolio — onboarded organizations”Owner: Ralph (executive projection over GLoops truth). Per organization: autonomy level · intelligence level · current bottlenecks · capabilities active/missing · receipts · executive actions · health · Reference Realization status.
Intended screen — Organization Portfolio. One row per organization with an autonomy dial, its single highest bottleneck called out, and a “what would continue without the human” readiness score.
11.4 Executive Updates — what changed since you last looked
Section titled “11.4 Executive Updates — what changed since you last looked”Owner: Ralph. Not a restatement of the system — a delta: new bottleneck · capability operationalized · action needed · receipt produced · role replacement changed · risk emerged · organization improved.
Intended screen — Executive Update. A short, dated changelog addressed to the executive, each line linking to the receipt or decision behind it. Replaces the long periodic markdown report.
11.5 Ralph — the Executive Operating Room
Section titled “11.5 Ralph — the Executive Operating Room”Owner: Ralph. Ralph answers: What deserves my attention? What is the current organizational bottleneck? What does the organization believe? Where is there dissent? What decision is needed? What happens if I do nothing? Ralph is not chat and not dashboarding — it is executive presence, judgment, and synthesis.
Intended screen — Ralph Executive Room. A live room with named perspectives (CEO, CTO, Chief of Staff, Head of Product, Head of Operations) that brief, agree, and dissent on the record; an agenda that routes to the right perspective by remit; and a decision panel that terminates in a recorded executive decision.
11.6 Supporting surfaces
Section titled “11.6 Supporting surfaces”| Surface | Owner | Intended view |
|---|---|---|
| Role Replacement Dashboard | Portfolio Steward (in GLoops/Ralph) | Per role: current %, target %, evidence, Role ROI, “if the CEO didn’t show up” readiness — the scoreboard of the Role Replacement Program. |
| Receipt Explorer | GLoops | Searchable stream of immutable receipts; each opens its evidence, reasoning, and the action’s original→final diff. |
| Knowledge Graph | GLoops (GBrain) | Cross-linked decisions, contradictions surfaced, precedent for any open question. |
| Operational Health | GLoops / Portfolio | The Portfolio Health instrument: manual_orchestration_remaining → 0, autonomous-operation count, and human_judgment_remaining as a floor, not a target. |
In practice — a day across the surfaces
Section titled “In practice — a day across the surfaces”(▣ These scenarios describe the Target State; today most steps still require the executive — see each surface’s grade in CURRENT_STATE.md. Walkthroughs are implementation targets, not maturity claims.)
Morning in GLoops. The executive opens the Capability Portfolio. Overnight, three Ready issues were discovered, classified, and clarified; two clarifying questions were posted automatically; one needs executive judgment and waits in the Action Queue. The executive reads the one card — recommended answer pre-filled, evidence attached — edits a word, approves. The capability learns from the edit. GitHub was never opened directly.
Morning in Ralph. The executive 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 is needed; the brief has options, a recommendation, and the consequence of doing nothing. The executive 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. The executive opens a Capability Card and watches its autonomy meter — currently rung 2 (Proposal). The rolling readiness assessment climbs 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 that matters: 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
- GLoops is the primary interface for operational truth.
- Ralph renders executive understanding.
- Walkthroughs are implementation targets, not maturity claims.
Open Questions
- Which surface first removes a recurring
/goalprompt? - Which walkthrough scenario should become the first end-to-end product demo?
Related
- Product Mockups
- Capability Cards
- Role Replacement Dashboard
- Action Queue
- Ralph Executive Room