11. 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.
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 (Ch. 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 Zach didn’t show up” readiness — the scoreboard of Ch. 13. |
| 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. |
Chapter closeout
Decision ledger
Key Decisions
- GLoops is the primary interface for operational truth.
- Ralph renders executive understanding.
Open Questions
- Which surface first removes a recurring
/goalprompt?
Related Chapters
- Product Mockups
- Capability Cards
- Role Replacement Dashboard