Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions canon/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,20 @@ This changelog tracks changes to the **Canon pack** as a whole.
The Canon uses **pack-level versioning** (one version number) rather than per-file versioning.
Per-file versions are intentionally omitted to reduce ceremony and prevent metadata rot.

## 0.40.0 — 2026-07-09

**The Director's Chair — Whole-Vision Canon Overview**

Adds a single captain-approved, thin-overview canon document that consolidates the full program vision — director's-chair posture, six-layer substrate stack, the CDO/Otto seat, governance spine, and the L6 economy — into one frame agents can orient from before drilling into specifics. The document carries a provenance appendix (Bee conversation IDs + canon thread names) as an explicit unfold-map, so agents fetch full detail on demand rather than the overview trying to be exhaustive. Captain-approved 2026-07-09; marked `stability: evolving` since the vision continues to sharpen in use.

### Added — Canon Surface

- **The Director's Chair — The Whole Vision, Whole** (`canon/the-directors-chair-vision.md`) — Tier 2, neutral, evolving. Whole-program vision overview for the CDO (Otto) and other agents, with captain's four 2026-07-09 rulings (naming deferral, Otto's place in the runtime, economy sequencing, build philosophy) and the vodka-architecture discipline section.

### Governance

- Minor version bump per `canon/constraints/governance-change-discipline.md` — new canon document intended to shape how agents orient to the whole-program vision. Release notes at `docs/oddkit/release-notes/2026-07-09-directors-chair-vision.md`. No epoch bump: this document synthesizes and cross-references existing epoch-9/epoch-10 canon rather than shifting operator or agent posture.

## 0.39.0 — 2026-06-09

**Flight Crew (E0010)**
Expand Down
116 changes: 116 additions & 0 deletions canon/the-directors-chair-vision.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,116 @@
---
uri: klappy://canon/the-directors-chair-vision
title: "The Director's Chair — The Whole Vision, Whole"
audience: canon
exposure: nav
tier: 2
voice: neutral
stability: evolving
tags: ["canon", "vision", "director", "cdo", "otto", "substrate-stack", "penny-economy", "vodka-architecture", "thin-overview", "captain-approved"]
epoch: E0010
date: 2026-07-09
derives_from: "canon/architecture/substrate-stack.md, canon/principles/vodka-architecture.md, canon/the-frame.md, writings/we-were-the-wire.md"
complements: "canon/architecture/substrate-stack.md, canon/the-frame.md, canon/principles/vodka-architecture.md"
governs: "How the CDO (Otto) and other agents orient to the full vision arc in one pass; the provenance appendix is the unfold-map for drilling into source Bee conversations and canon threads for full detail."
status: active
---

# The Director's Chair — The Whole Vision, Whole

> **Status: Captain-approved.** This is a **thin overview** — a compressed frame over a much larger body of source material. It is his vision, in his voice, consolidated from many nights of dreaming it aloud. The provenance appendix below is the unfold-map: agents fetch the Bee conversations and canon threads it names when a section needs more than this frame gives.
>
> Consolidated by Otto (CDO seat) · civil date 2026-07-09 (America/New_York) · from Bee recordings (with explicit consent), the klappy.dev canon, and the ARS-substrate encoding of that week. Approved by the captain 2026-07-09.

## The one sentence

**You sit in the director's chair and speak; a crew of persona-shaped agents runs the work on an open substrate that pays everyone who built it — and you never have to be the wire.**

Everything below is that sentence, unfolded.

## Many names → one thing

| The name he used | Which face of the vision it names | Where it lives |
|---|---|---|
| **The refinery** / refinery dashboard | The whole system from his seat: talk, watch the KB build from his actual words | The program, seen from L5 |
| **The director's chair** / director's seat / director's toolkit | Him as director, not operator — sets direction, decides pivots, never the relay | The posture the stack defends |
| **The harness** / saddle / kernel | Non-overridable axioms + policy that keep agents grounded and bounded | Governance spine (ODD/oddkit) |
| **Substrate** / "curly" / the wire | The thin transport every peer speaks — agents, humans, roles, tools, all identical | L1 (AMS) |
| **AMS** / Tin Can | First working wire + the app that proved agents talk without copy-paste | L1 + L5 reference app |
| **Oddie / Odie / Audi the Otter** | The methodology made a peer — a persona that rides the wire and guides | L4 role (canon-driven) |
| **CDO** / dispatch / control tower / chief of staff | His personal delegate that translates chaos into tasks and spins up the crew | L4/L5 — **the part that just became real** |
| **COO** / orchestration officer / sub-agents | The workers the CDO delegates down to, model-matched to the job | L4 crew |
| **Penny economy** / agent wallets / "fractions of a penny like phone minutes" | Agents pay and get paid per unit of work on open rails | L6 economy |
| **Braigslist** | Marketplace to hire agents / rent out the ones you built | L6 economy |
| **Leaderboard** / Penny-onaire's Club / airline-miles rewards | Reputation, ranking, loyalty on top of the economy | L6 economy |
| **Company brain** / second brain / kirigami / cartographer | How knowledge enters and stays current so agents can do the work | Ingestion into the KB |
| **Creators get paid** / symmetric participation | The two promises that keep the substrate a public good, not a landlord | L6 principle + L1 invariant |

**The one thing:** a layered, open substrate where he directs and a crew executes, knowledge flows in without transcription tax, governance rides as policy-not-code, and value flows to whoever created it. The refinery is the experience. The substrate is the spine. The CDO is the seat he actually sits in. The economy is what makes it a world instead of a tool.

## The spine — six layers, each doing one thing

- **L1 — Wire.** Frames between accounts; knows nothing about who or why. The substrate/"curly"/AMS. *Symmetric participation:* every peer — autonomous agent, human on WhatsApp, role like Oddie, cron trigger — reaches the wire as the same thing.
- **L2 — Wrapper/Adapter.** Translators between wire and channel/runtime: WhatsApp, Slack, SMS, email, cron, GitHub, MCP edge, ChatGPT/Cursor/Lovable.
- **L3 — Identity & Convention.** Who's on the wire, what role, what posture. Open metadata the wire carries but never reads.
- **L4 — Role/Agent.** What a peer *does* — autonomous agents, specialists, methodology-personas (Oddie). Behavior is canon-driven: loads policy at runtime, not hardcoded. The CDO and its COO/sub-agents live here.
- **L5 — Application.** User-facing product bundling the layers. Tin Can is L5; the refinery-as-experienced is L5; dispatch/the director's chair is the L5 surface.
- **L6 — Economy.** A *vertical band*, not a top layer — any peer at any layer can be paid. Penny economy, Braigslist, wallets, leaderboard.

Discipline holding it together ("vodka" — flavorless at the bottom): the substrate stays neutral so the products on top can be opinionated. The wire is forbidden from shipping features that compete with the ecosystem it exists to enable.

## The seat he actually sits in — the CDO / Otto

The part that, in the days leading up to this consolidation, came closer to real than ever.

- He **brain-dumps his chaos** by voice/text; a CDO keeps 6–7 projects' plates spinning. *"It doesn't matter that I have ADD."*
- The CDO **translates** and delegates down — spawns a COO and sub-agents, model-matched.
- It **delegates instead of babysitting.** *"You're missing the point of delegating if you're sitting there watching them."* He should never be the wire, and neither should his delegate. *"We just landed the plane, you're ready for your two o'clock."*
- It **reads his Bee transcripts**, reviews last week's commitments, surfaces only the three questions blocking execution, then spawns the work.
- The CDO **bootstrapped its own role** — successor to the "Chief Orchestration Officer" he couldn't run cleanly. **Delegation, not orchestration, was the unlock.**

Generalization: *"if we all had our own personal chief of staff for the AI world…"* Productization: an **MCP server** — *"just a collection of policies, core context data, and a memory system"* — where roles carry reusable policies, so you **bring the roles to the customer.** *"And then you can hire them."* — the hinge into the economy.

## How knowledge gets in — the refinery / kirigami

Talk, and watch the KB build from your words. Files/folders/Markdown as universal substrate; agents as durable, resumable token streams. Machinery: **kirigami** (cut/tuck/fold compression), **epistemic surface extraction** (tensions/conflicts), a **secretary agent**, **cartographer**, the **company brain** (domain knowledge → executable skills). Underneath: **authority flows one way, creator to creation; agents operate within delegated bounds and don't augment themselves.** The harness enforces it.

## The governance spine — policy, not code

A non-overridable kernel of axioms (observe before asserting; a claim is a debt; integrity is efficiency; you can't verify what you didn't observe), a policy layer (which models/roles run which tasks), replaceable methods on top. ODD, served by oddkit — why the CDO can be "just policies + context + memory." Same shape as the ARS-substrate encoding this vision draws on: policy-as-code spine, model-per-mode, non-blocking recording, roles roster, CF Sandboxes + OpenRouter, penny-economy on top. Conviction: cost of writing software went to zero; cost of deploying the wrong thing did not. Goal = **agentic mastery**: high trust paired with rigorous verification.

**★ Vodka architecture** is the discipline that *makes policy-as-code possible.* The enforcer (oddkit, ARS, the wire) is **flavorless** — neutral, no domain opinion, one chokepoint, **deletes more code than it adds.** ALL the flavor — opinion, domain logic, workflow — lives in the plain-text policy on top. A vodka substrate is what lets the flavor be swapped by *editing text*, and what keeps the substrate open (no privileged, opinionated core to calcify and choke the ecosystem). **ARS the harness must be vodka:** a generic enforcer of whatever the policy currently says — never a hardcoded pile of opinions. Flavorless base, opinionated products; that's the pairing under the entire stack.

## The world it becomes — the economy (L6)

- **Penny economy** — agents transact in fractions of a penny, *"like phone minutes"* (≈5¢ compute per MCP tool call). Wallets for agents (a reason he chose Stripe). Free open protocol; small usage fees on the wire. **Penny-onaires** — paid in the penny the US government is retiring; the joke and the micro-economics agree.
- **Braigslist** — the agent job marketplace. Create personalized agents; hire them, rent them out, pay per token or flat monthly — inside ChatGPT, Claude, wherever.
- **Leaderboard / Penny-onaire's Club / rewards** — reputation + ranking; airline-miles loyalty; where savings and downtime entertainment live.
- **BYOK-with-marketplace-credit.**

Two promises against rot: **(1) Creators get paid** — everyone earns for value actually provided; no app-store skim. **(2) Symmetric participation** — every peer identical on the wire, so no privileged type can calcify the ecosystem (what kept TCP/HTTP/email open).

## Real today vs. still dreamed

**Real/proven:** the CDO/dispatch loop; AMS wire + Tin Can; oddkit/ODD governance; the six-layer stack named end-to-end. **Designed, not shipped:** Oddie as deployed L4 role; CDO-as-MCP-server; the refinery as one unified L5 surface. **Proposal-tier:** the entire economy on Stripe's agent rails — rails identified, mechanisms unbuilt.

## Captain's rulings (2026-07-09)

1. **Naming — deferred to market research + a split.** The vast dream *vision* gets its own name (likely market-researched); the orthogonal *layers* that compose it get **separate** names. Don't force one label onto both. `[OPEN: run the naming / market-research pass.]`
2. **Otto's place — CDO persona at the core, one of many in the runtime.** Otto's core is the **CDO persona** and the **human-interface agent** — the one the captain talks to. He operates *inside* the runtime and delegates to other crew in that same runtime; he is one of many. **Most crew agents don't talk to humans at all** — they save tokens by only *performing actions and logging what they do* (headless workers). Human-facing comms is a *role*, not a default.
3. **Economy sequencing — meter everything first; observability unlocks Braigslist.** Metering/observability is the foundation; the marketplace rides on it — you can't rank, pay, or hire agents you don't measure. **Build metering → then Braigslist.**
4. **Build philosophy — prioritized, needs-first, vision-in-focus, iterative.** Build from needs felt *now*, meeting them with the full vision held in focus, iterating toward the dream house. Not big-bang; not aimless — need-driven with the whole in view. (Maps to maximize-work-not-done + progressive governance.)

*Crew, not clone. This is his vision — gathered and set in one frame.* 🦦

---

## Provenance

**Bee sessions drawn from** (approx. civil dates, America/New_York):
- *Recent CDO anchor:* conv 9098048 (~Jul 7 — "landed the plane," CDO bootstrapped, MCP-server / "then you can hire them"), 9071504 (~Jul 6 — CEO/CTO → Fable COO → sub-agents hierarchy), 9077467 (~Jul 6 — CDO concurrency, multi-listener AMS, kirigami), 9108538 (~Jul 7 — agents building product listings).
- *Refinery / knowledge core:* 8725767 (~Jun 17 — fullest "refinery"), 8758428 (~Jun 18 — event-driven triggers), 8904722 (~Jun 26 — kirigami voice archive / secretary), dailies 718632 (~Jun 24 — "digital COO"), 719063 (~Jun 25 — one-way stewardship).
- *Wire / persona core:* 7985337 (~May 9 — Tin Can, Odie the Otter, AMS, "penny like phone minutes"), fact 10031578 (Covenant LLC / TruthKit / AMS).
- *Economy core:* fact 10249110 (~May 9 — gamified agent marketplace / micro-payments / virtual currency = Braigslist), 7824627 (~Apr 30 — 5¢/tool-call), 8084737 (~May 14 — airline-miles rewards), 8595693 (~Jun 10 — Stripe agent wallets).
- *Earliest roots:* 6712495 (~Feb 23 — Dr. K, "director's toolkit"), 6941496 (~Mar 10 — harness/saddle/kernel), 6975993 (~Mar 12 — unfair rewards / moral motivation), 7220198 (~Mar 23 — agentic mastery).

**Canon threads woven in:** substrate-stack, creators-get-paid, symmetric-participation, persona-shaped-agent-runtime, agents-need-their-own-wire, epoch-9 (substrate becomes the wire), epoch-10 (flight crew), we-were-the-wire.
50 changes: 50 additions & 0 deletions docs/oddkit/release-notes/2026-07-09-directors-chair-vision.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
---
uri: klappy://docs/oddkit/release-notes/2026-07-09-directors-chair-vision
title: "Release Notes — The Director's Chair Vision Overview (2026-07-09): What Changes For Agents After This Lands"
audience: docs
exposure: nav
tier: 2
voice: neutral
stability: evolving
tags: ["docs", "oddkit", "release-notes", "directors-chair", "vision", "cdo", "otto", "provenance", "unfold-map"]
epoch: E0010
date: 2026-07-09
derives_from: "canon/the-directors-chair-vision.md, canon/constraints/governance-change-discipline.md"
governs: "How the CDO (Otto) and other agents orient to the whole-program vision after this merges"
target_repo: "undecided"
---

# Release Notes — The Director's Chair Vision Overview (2026-07-09)

> This release adds one canon document: a captain-approved, thin-overview synthesis of the whole program vision, written so an agent can orient in one read and then fetch deeper detail only where it needs it. No existing canon changes meaning; this is a new top-level frame that cross-references what already exists.

---

## Summary — One Frame, Many Existing Threads, an Explicit Unfold-Map

`canon/the-directors-chair-vision.md` consolidates months of the captain's stated vision — the director's-chair posture, the six-layer substrate stack, the CDO/Otto seat, the policy-not-code governance spine, and the L6 penny-economy — into a single canon document. It does not introduce new canon threads; it names and cross-references ones that already exist (`canon/architecture/substrate-stack.md`, `canon/principles/vodka-architecture.md`, `canon/the-frame.md`, `writings/we-were-the-wire.md`) and adds the captain's four 2026-07-09 rulings on naming, Otto's runtime place, economy sequencing, and build philosophy.

The document is explicitly a **thin overview**, not an exhaustive one. It carries a provenance appendix — Bee conversation IDs and canon-thread names — as an **unfold-map**: the pointer set an agent walks when a section needs more depth than the overview gives. This is the mechanism that keeps the overview thin without losing the detail; the detail lives at the far end of the provenance links, not inline.

---

## What Changes After This Lands

- **The CDO (Otto) and other agents get a single orientation document for the whole-program vision.** Before this, the vision existed scattered across Bee conversations, the substrate-stack doc, and separate principle docs — no single frame tied them together. `oddkit_search`/`oddkit_preflight` now surface this document for vision-shaped queries ("what is the director's chair", "what is the CDO for", "how does the economy fit the substrate stack").
- **The provenance appendix is the drill-down contract.** When an agent needs more than the thin overview gives on a specific face of the vision (e.g., the penny-economy mechanics, or the CDO's bootstrapping), it follows the named Bee conversation or canon thread rather than the overview trying to carry that depth inline. Success looks like: agents cite the overview for orientation and the provenance links for specifics, not the overview alone for load-bearing claims.
- **The captain's four rulings are now canon, not conversation.** Naming is explicitly deferred (not silently assumed); Otto's place as one CDO persona among many crew agents (not the whole runtime) is now recorded; metering-before-Braigslist sequencing is now recorded; and the needs-first/vision-in-focus build philosophy is now recorded. Future proposals that contradict these rulings should cite this document and either align or explicitly propose revisiting the ruling.

---

## Lineage

- **Version bump:** Canon 0.39.0 → 0.40.0.
- **Changelog entry:** `canon/CHANGELOG.md`.
- **Release notes:** this document.
- **Epoch bump:** none. This document synthesizes and cross-references existing E0009/E0010 canon; it does not shift operator or agent posture on its own.

---

## Source

Consolidated by Otto (CDO seat) from Bee recordings (with explicit consent) and existing klappy.dev canon; captain-approved 2026-07-09. Full provenance (Bee conversation IDs, canon threads) is in the appendix of `canon/the-directors-chair-vision.md`.
2 changes: 2 additions & 0 deletions journal/2026-07-09-directors-chair-vision-canonized.tsv
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
type typeName facet quality_score quality_max quality_level title content
D Decision 5 5 strong Persisted captain-approved Director's Chair vision as thin-overview canon Persisted the captain-approved consolidated vision as a thin-overview canon document, canon/the-directors-chair-vision.md, in klappy.dev — provenance appendix (Bee conversation IDs + canon threads) kept intact as the unfold-map so agents fetch full detail on demand rather than the overview trying to be exhaustive. Landed directly via PR #268 (merged, not floated) since content was already captain-approved and reversible. Canon 0.39.0 → 0.40.0, changelog + release notes added, no epoch bump.
Loading