feat: declare E0007.1 — Vodka Architecture principles and posture lapse detection#73
Merged
Merged
Conversation
added 9 commits
April 5, 2026 04:28
…se detection E0007.1 extends E0007 (From Passive to Proactive) with: - Vodka Architecture: named design pattern for epistemic infrastructure (thin, stateless, domain-agnostic, load-bearing) - Six principle spinoffs with full governance structure: KISS, DRY, Consistency, Maintainability, Prompt Over Code, Antifragile Each follows ritual-is-a-smell template: smell test → failure modes → exclusions → required response - Posture Lapse: meta-governance article for detecting when proactive cognitive rhythm breaks down - Epoch 7.1 declaration document All principles validated by oddkit's own production evidence. Coined 'Vodka Architecture' from speech-to-text transcription error. 9 new documents. Canon grows from 439 to 448.
The story of oddkit's write path: four planning sessions, twenty-five decisions, two feature branches, two PRs — none shipped. Then the problem dissolved when the platform caught up. Introduces Bypass as the 6th B in the 5B method: the discipline of recognizing that friction might not be yours to solve. Grounded in real session history. Zero maintenance code. 45 docs/week.
…e (Encode) DOLCHE = Decisions, Observations, Learnings, Constraints, Handoffs, Encodes. The E closes the loop: the act of encoding is itself trackable. Reorders to lead with Decisions (highest stakes). Backward-compatible with OLDC+H journals.
… type The E tracks the act of crystallization itself, not a category of content. Five artifact types (D, O, L, C, H) + one meta-level action (E). Added storage-at-scale note (format-agnostic, implementation-neutral).
…ments DOLCHE types are defaults, not a closed set. Any KB can extend with custom types (P for Prayer Requests, R for Rulings, A for Automations) via governance documents. oddkit handles any type string generically. Prompt over code applied to the vocabulary itself.
All scalar values now quoted. Fixes potential renderer issues with unquoted dates (parsed as date objects), unquoted integers (tier), and unquoted strings (audience, exposure, etc.). Project instructions require: 'YAML frontmatter: all values quoted, inline tag arrays use quoted strings.' All 11 files corrected.
New: canon/meta/frontmatter-schema.md — authoritative reference for all YAML frontmatter fields. Defines universal required fields, audience-specific fields, quoting rules, smell tests, and required responses. Supersedes template-based field guidance. Fix: writings/the-feature-i-never-shipped.md — add missing required essay fields (slug, author, type, public, description, hook, subtitle, og_title, og_description). Quote public as string. These fields were missing because no schema existed to enforce them.
The previous commit quoted all values as strings. The site renderer expects native YAML types: booleans (public: true), integers (tier: 2), dates (date: 2026-04-04), and simple identifiers (audience: canon) must be UNQUOTED. Only strings with special characters get quotes. Fixed all 12 files. Updated frontmatter-schema.md to document the correct quoting rules derived from working articles.
klappy
pushed a commit
that referenced
this pull request
Apr 9, 2026
klappy
added a commit
that referenced
this pull request
Apr 9, 2026
* feat: add essay — One Hour with Claude Managed Agents Documents the first hour with Anthropic's Managed Agents + oddkit: proactive epistemic posture, the Vodka Architecture search miss, and an autonomous agent filing PR #72 to fix the bug. public: false (draft) * add model selection insight (Sonnet for review, Opus for synthesis) * fix: model selection insight — Opus for authoring, Sonnet for review * fix: three-stage model pipeline — Opus writes, Sonnet validates, Opus fixes * fix: add missing renderer fields (exposure, tier, voice, stability, og_type) * fix: 'weeks ago' → 'five days earlier' (verified: date 2026-04-04) * fix: remove cliché AI structure per Birch's feedback * add learning: inline vs agentic validation tradeoffs (from today's session) * fix: correct attribution — AI co-author broke frontmatter, human caught it * final: add deployment capstone, fix public: true, link PRs #72 + #73 * fix: stability: evolving (not draft) — bugbot keeps reverting public: true --------- Co-authored-by: Klappy <klappy@eten.bible>
klappy
pushed a commit
that referenced
this pull request
May 9, 2026
…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).
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.
E0007.1 — Vodka Architecture and Principled Governance
E0007.1 extends E0007 (From Passive to Proactive) with three layers:
1. Vodka Architecture (parent design pattern)
2. Six Principle Spinoffs (full governance articles)
Each follows the
ritual-is-a-smelltemplate: smell test → failure modes → exclusions → required response.canon/principles/kiss-simplicity-is-the-ceiling.mdcanon/principles/dry-canon-says-it-once.mdcanon/principles/consistency-same-pattern-every-time.mdcanon/principles/maintainability-one-person-indefinitely.mdcanon/principles/prompt-over-code.mdcanon/principles/antifragile-failures-grow-canon.md3. Posture Lapse Detection
docs/oddkit/proactive/posture-lapse.mdEpoch Declaration
docs/appendices/epoch-7-1.md9 new documents. Canon grows from 439 to 448.
All documents pass Writing Canon 7-point checklist. Zero TruthKit details.
Triggered by research into Claude Code source leak (March 31, 2026) and Pliny agent chaos incident — both validating oddkit gate mechanisms and the need for named architectural principles.
Note
Low Risk
Documentation-only PR adding new governance/epoch articles; low implementation risk, with the main risk being downstream process reliance on the new frontmatter/type guidance conflicting with older templates.
Overview
Declares sub-epoch E0007.1 by adding a new
docs/appendices/epoch-7-1.mdand a Vodka Architecture design-pattern canon (canon/principles/vodka-architecture.md) with six new principle articles (KISS/DRY/Consistency/Maintainability/Prompt-over-code/Antifragile) formalized into smell tests, failure modes, exclusions, and required responses.Adds operational governance docs for proactive workflows: a new posture lapse detection guide (
docs/oddkit/proactive/posture-lapse.md) and a DOLCHE session-capture vocabulary that supersedes OLDC+H (docs/oddkit/proactive/dolche-vocabulary.md).Introduces an authoritative frontmatter schema (
canon/meta/frontmatter-schema.md) to standardize required fields, types, and quoting rules across audiences (explicitly superseding template frontmatter guidance), and adds a new draft public essay (writings/the-feature-i-never-shipped.md).Reviewed by Cursor Bugbot for commit ee274f5. Bugbot is set up for automated code reviews on this repo. Configure here.