canon: Substrate Stack architecture + Constitutional Triangle (magical-first-run, symmetric-participation, creators-get-paid)#183
Merged
Conversation
…re canon Adds canon/architecture/ as a new directory housing structural maps and layered models — distinct from canon/principles/ (reasoning orientations), canon/decisions/ (specific committed choices), and canon/patterns/ (repeatable design templates applied at one layer). The Klappy Substrate Stack is the inaugural architecture document: a 6-layer model (L1 Wire, L2 Wrapper-Adapter, L3 Identity-Convention, L4 Role-Agent, L5 Application, L6 Economy cross-cutting) that functions as the canonical lookup for 'where does X live?' questions across the program. Each layer has one concern, narrow neighbor interfaces, and can be replaced without disturbing the others. Includes layer-assignment table for existing work (AMS broker → L1, MCP wrapper and channel adapters → L2, ams.convention.v1 → L3, Oddie and other agents → L4, TinCan portal → L5, penny economy and Stripe rails → L6) and an enforcement section listing what the stack forbids (wire opinions about peer type; wrapper application semantics; first- party application-layer features inside the substrate, per AMS D0020). Stability: evolving. Iteration from contact with reality. Companion principles (magical-first-run, symmetric-participation, creators-get-paid) land in a follow-up commit on this branch and cite this architecture document as their structural reference. Provenance: operator-Claude conversation 2026-05-09. Session journaled at agent-messaging-service journal/2026-05-09-substrate-stack-and- constitutional-triangle.tsv (PR #73).
…metric-participation, creators-get-paid) Three klappy.dev tier-1 principles that together with canon/architecture/ substrate-stack.md form the program's constitutional commitments at the substrate layer (L1), the application layer (L5), and the cross-cutting economy layer (L6). Each principle cites its governing layer in canon/architecture/substrate- stack.md and cross-references AMS-tier mechanism canon (D0020 substrate- not-application positioning, D0021 Stripe integration surface, D0006 dream-house-wire-edge-wrappers, D0017 selective subscription, D0018 multi-stream per account per conversation) where relevant. magical-first-run (L5): Any user-facing application on the substrate must be reachable, useful, and intelligible to a non-technical operator within sixty seconds of first contact, without protocol explanation. Success metric is unprompted use of 'easy' and 'magical' by people who have never seen the system. TinCan is the first L5 product graded against it; future apps inherit. symmetric-participation (L1): Every peer on the substrate interacts through identical wire primitives, regardless of what the peer represents. Generalizes D0020's agent-as- customer commitment from customer-layer to wire-layer. Forbids any feature that special-cases the substrate by peer type. Enables BYOA / BYOC at user-facing level: bring your own agent, bring your own channel. creators-get-paid (L6): Every participant including substrate maintainers can be paid for value they actually provide. Substrate is paid for what it provides; never taxes what others provide because they used the rails. Distinguishes payment-for-value-provided (required for maintainer survival) from extraction-tax-on-rails-usage (forbidden landlord failure mode). The agent-economy mechanism (encode-12: penny economy, Penny-onaire's Club, BraigsList, BYOK, agent UGC) is one canonical instantiation. Provenance: operator-Claude conversation 2026-05-09. Session journaled at agent-messaging-service journal/2026-05-09-substrate-stack-and- constitutional-triangle.tsv (PR #73).
Canon Quality —
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Canon promotion landing four files together as the program's constitutional commitments at the substrate, application, and economy layers:
canon/architecture/substrate-stack.md— the OSI-equivalent layered architectural model. Six layers (L1 Wire, L2 Wrapper-Adapter, L3 Identity-Convention, L4 Role-Agent, L5 Application, L6 Economy cross-cutting) with one concern each, narrow neighbor interfaces, replaceable independently. The canonical lookup for "where does X live?" questions across the program. Includes a layer-assignment table for existing work, a "what the stack forbids" enforcement section, and explicit open questions. Also addscanon/architecture/README.mdand thecanon/architecture/directory itself as a new home for structural maps and layered models — distinct fromcanon/principles/(reasoning orientations),canon/decisions/(specific committed choices), andcanon/patterns/(repeatable design templates applied at one layer).canon/principles/magical-first-run.md— L5 success metric. Any user-facing application on the substrate must be reachable, useful, and intelligible to a non-technical operator within sixty seconds of first contact, without protocol explanation. Success metric: unprompted use of easy and magical. TinCan is the first L5 product graded against it; future apps inherit. Forbids empty rooms, opaque participant identity, required jargon, unexplained silence, protocol surface bleeding into UX. Explains the bridge-role (Oddie as river-guide) as the mechanism that makes the principle achievable in practice.canon/principles/symmetric-participation.md— L1 invariant. Every peer on the substrate interacts through identical wire primitives, regardless of what or who the peer represents. GeneralizesD0020's agent-as-customer commitment from customer-layer to wire-layer. Forbids any feature that would special-case the substrate by peer type. Enables BYOA / BYOC at user-facing level: bring your own agent, bring your own channel, bring your own role.canon/principles/creators-get-paid.md— L6 cross-cutting commitment. Substrate maintainers can monetize substrate-tier services (capacity, hosting, reference implementations, premium tiers, support, payment-rail facilitation). Adapter authors, agent builders, and role creators monetize their work directly via the Stripe agent-payment rails (D0021). The substrate is paid for what it provides; never extracts from creators' creative work. Distinguishes payment-for-value-provided (required for maintainer survival) from extraction-tax-on-rails-usage (forbidden — landlord failure mode of every prior open substrate that drifted from infrastructure into rent extraction). The agent-economy mechanism (encode-12: penny economy, Penny-onaire's Club, BraigsList, BYOK, agent UGC marketplace) is one canonical instantiation; the principle generalizes.Relationship to existing canon
The triangle articulates what existing AMS mechanism canon (
D0020,D0021, encode-12) concretely operationalizes — principles abstract, mechanisms instantiate, neither replaces the other. None of the existing klappy.dev or AMS canon is superseded; this PR adds upstream principle-tier articulation for substrate-shaping commitments that previously lived only at the AMS-tier mechanism level.The substrate stack is
canon/architecture/rather thancanon/principles/because it functions as a structural lookup the principles cite, not as a reasoning orientation in its own right. New directory established; README added.Voice / writing-canon compliance
Drafts written against
canon/constraints/ai-voice-cliches.md— checked for negation parallelism, formulaic transitions, generic descriptors, em dash overuse, uniform pacing, sycophantic openers, summary clichés. Voice isneutral. Author voice clichés should be light or absent; expecting reviewer feedback if any cluster.Gauntlet
klappy://andams://URIs grep clean across the four files; cross-references resolve to existing canon (or to themselves for self-references). Body-text path references (canon/values/axioms.md,canon/principles/vodka-architecture.md,canon/principles/dream-house-principle.md, etc.) all verified to exist onmain.oddkit_challengeatmode=canon-tier-1,knowledge_base_url=https://github.com/klappy/klappy.dev: statusCHALLENGED,block_until_addressed: false. Matched challenge types: principle-extraction, comparative-positioning, pattern-coinage, assumption, proposal, observation, strong-claim. The challenge surfaces standard tier-1 prerequisites worth carrying into PR review and follow-up amendments — see "Known limitations" below.oddkit_auditis scoped towritings/and does not covercanon/, so it is a no-op for this PR. URI integrity was checked manually instead.Known limitations (carried forward to review)
The principles are explicitly marked
stability: semi_stable/ the substrate stackstability: evolving, intended to iterate from contact with reality per operator direction ("we have to start somewhere; let's go with this and iterate from contact with reality"). Specific canon-tier-1 prerequisites the current drafts do not yet fully satisfy:symmetric-participationcites four prior substrates (TCP/IP, HTTP, Unix pipes, email) viadoing-less-enables-more;creators-get-paidcites prior platform failure modes (app stores, marketplaces).magical-first-runrests primarily on the planned TinCan instantiation plus the 2026-05-09 ChatGPT/TinCan diagnostic — sample-of-one. The principle's aspirational/future-governing posture makes this expected, but worth flagging.D0020's framing); the docs do not say so explicitly.These are quality-of-canon refinements, not correctness issues. Recommended path: land this PR as the starting point, address findings via review comments and follow-up amendment PRs that don't fragment canon.
Provenance
Operator–Claude conversation 2026-05-09. Session journaled at
agent-messaging-servicejournal/2026-05-09-substrate-stack-and-constitutional-triangle.tsv(PR #73, 39 DOLCHE+H artifacts: 9 O, 8 L, 6 D, 5 C, 4 E, 7 H). The journal entry was committed and pushed before any of these canon files were drafted, to preserve session reasoning even if the canon-write step was interrupted.Follow-ups (not in this PR)
canon/principles/README.mdindex to include the three new principles in the alphabetized list. Worth a small follow-up commit once entries are reviewed and stable.the-frame.mdif it lists tier-1 principles.canon/voice/oddie-the-river-guide.mdend-to-end first.binding_idwrapper ergonomic identified during the same session (highest-ROI single change in the AMS MCP wrapper) — separate AMS PR.Note
Low Risk
Adds new canon documentation only (no code/behavior changes), so the primary risk is confusing or inconsistent guidance if the new architectural/principle docs conflict with existing canon.
Overview
Introduces a new
canon/architecture/section (with index README) and addssubstrate-stack.mdas the program’s canonical layered architecture/ownership map for where responsibilities should live across L1–L6.Adds three new tier-1 canon principles—
magical-first-run,symmetric-participation, andcreators-get-paid—that define constitutional constraints for L5 UX, L1 wire invariants, and L6 monetization (anti-extraction) respectively, with cross-references back to the new substrate stack and existing AMS decisions.Reviewed by Cursor Bugbot for commit 4475851. Bugbot is set up for automated code reviews on this repo. Configure here.