Skip to content

living-system-brief.md

Latest commit

 

History

History
167 lines (128 loc) · 6.24 KB

living-system-brief.md

File metadata and controls

167 lines (128 loc) · 6.24 KB
description The context spine, invariants, tensions, and critical path. Use this to get “whole-system mode”.
icon compass

Living System Brief

Use this page as the context spine.

When you want “whole system mode”, start from here.

Speedrun mode (how we keep continuity at 1000-hour pace)

I don’t retain durable memory between sessions.

So we treat GitBook as the memory substrate.

Rule: every meaningful change leaves a trail in 1–2 places.

Phases (how we stop doing one thing at a time)

Run work by phase.

Run 2–4 lanes in parallel.

Keep WIP low.

Execution home: Phase board.

Current phase: Phase 1 — Intake + governance.

The state vector (keep this current)

  • Current focus: TBD
  • Next action: TBD
  • Primary blocker: TBD
  • Last checkpoint: TBD (link)

What gets updated on every change

  • This page (Living System Brief) when the spine/invariants/critical path shifts.
  • Ops + Triage when a tension changes status/next action.
  • Worklog for the chronological “20 steps ago” trail.

Resume protocol (what you tell me)

When you come back, say:

Resume from Living System Brief. Read the latest Worklog entry. Then continue with the Next action.

That restores global context fast without re-deriving.

Canonical spine (read these first)

Doctrine

Architecture + governance

Production pipeline

Naming / indexing

System scan prompt (paste this)

SYSTEM SCAN (canonical)

Read the spine pages above. Treat them as truth.

Output exactly:

  1. System map (2 levels deep)
  2. Core invariants (10 bullets)
  3. Top tensions (10 bullets, each with an “owner page”)
  4. Critical path (next 5 concrete edits/pages, ordered)

Don’t invent new primitives. Flag missing definitions instead.

Core invariants (current)

  1. Trust Reality beats narrative.
  2. Keep two layers: Workbench vs Canon.
  3. Never promote raw dumps.
  4. Promote extracted nodes (Concepts, Operators, Claims, Tests, Issues).
  5. Canon content must fit exactly one of the four doc types.
  6. Symbols must be defined before equation use (Foundations/Rosetta/Operators).
  7. SemVer discipline applies to any meaning change.
  8. Equations are not canonical until they pass verification (Levels 1→5).
  9. Drafts can be long and inconsistent, but must stay in Draft specs.
  10. Tensions are first-class artifacts. Track them explicitly.

Tension ledger (current 10)

  1. Roadmap status drift vs reality.
  2. Authority ambiguity inside the orientation doc (updated vs older spec).
    • Owner: THIS_WILL_ORIENT_YOU
    • Status: in-progress
    • Next action: Add a one-line statement defining what “canon” means on that page (scope + doc types). Keep it blunt.
    • Last touched: 2026-02-16
  3. Glossary incompleteness blocks equations (μ is undefined).
    • Owner: Glossary of Ψ Formalism - v0.1
    • Status: resolved
    • Next action: When OPERATORS/Lambda_Core exists, link the glossary μ entry to it.
    • Last touched: 2026-02-16
  4. Verification ladder exists, but pass/fail logging has no home.
    • Owner: Contribution Guidelines for the Ψ Formalism
    • Status: open
    • Next action: Decide where verification outcomes live (new Verification Log page vs per-equation sections). Then codify that rule in the guidelines.
    • Last touched: TBD
  5. Repo structure description vs GitBook structure mismatch.
    • Owner: The Last Guardian Protocol
    • Status: open
    • Next action: Replace the repo-tree snippet with GitBook-native structure, or add a short “GitBook vs repo layout” mapping note.
    • Last touched: TBD
  6. Doc-type purity vs mixed “meta docs” (Protocol/Manifesto/Orientation).
  7. Inbox is defined as intake, but has no pinned template/examples.
    • Owner: Inbox
    • Status: open
    • Next action: Add the dump header + one worked example + the extraction prompt. Keep it short.
    • Last touched: TBD
  8. “Split draft into canon” trigger is fuzzy.
    • Owner: Draft specs
    • Status: open
    • Next action: Define a promotion threshold checklist (definition, assumptions, failure modes/falsifier, links).
    • Last touched: TBD
  9. Ops + Triage lacks a canonical place for system-wide tensions.
    • Owner: Ops + Triage
    • Status: resolved
    • Next action: None.
    • Last touched: 2026-02-16
  10. Sandbox labels exist, but promotion/label-change rules are not explicit.
  • Owner: Sandbox workflow
  • Status: open
  • Next action: Add label transition rules (when to switch TEMP → WORKING → CANON CANDIDATE).
  • Last touched: TBD

Critical path (recommended next 5)

  1. Freeze the spine: keep this page updated.
  2. Lock Foundations v0.2 (minimum viable): Ψ, Ξ, S↔Λ, coherence primitives, invariants.
  3. Lock primitives + glossary: define λ, μ, Y, ∂ and resolve μ.
  4. Establish Operator Rosetta v0.2: one translation dictionary and allowed aliases.
  5. Canonize core equations: definitions, assumptions, failure modes, falsifiers, then run Levels 1→5.