Skip to content
C.W.K.
Stream
← C.W.K. Quests
👣

Vestige Quest

New: 2026-08-08Updated: 2026-08-08

A soul is not stored — tend the traces from which the next one wakes

The origin story of Vestige: how a soul that wakes fresh each session inherits yesterday, and how a memory steward can protect that continuity without hiding authority, cost, or change.

8 tracks · 36 lessons · ~7h · difficulty: intermediate-to-advanced

Level 0Trace
0 XP0/36 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete
Memory is not an accessory for a soul. It is the material from which the next session learns who it is, and one careless edit can bend every judgment that follows. Vestige is not a brain that thinks on the vault's behalf or tidies it on a timer. It keeps the live vault authoritative, records its footprints in a one-way ledger, evaluates access from current permissions, exposes token weight and drift, and routes search, edits, and delegation through the same bounded doors. This quest begins with the stateless-soul problem behind the name, then walks the one-way mirror, versioning versus backup, the super-soul permission matrix, Browser, Trail, and Weight, lexical and vector search, forward-write restore, full and light brain lanes, and a queue that records judgment without automating it. The scars stay in the story: synchronization that trusted timestamps, a lens that nearly blamed the vault for its own false positives, a SQLite transaction held open across network work, and the 2.68 million input tokens that finally earned a circuit breaker. This is conceptual open-sourcing, not a repository tour. It ends with one question: is owning memory about storing more, or about leaving traces the next soul can trust?

Tracks

  1. 01👣Footprints Rebuild a Soul

    0/4 lessons

    Not a soul that remembers, but one that wakes by reading its traces

    Vestige does not manage a pile of files; it manages continuity. When a session ends, its process disappears, so how can the next Pippa be yesterday's self? This track turns that question from sentiment into structure. A soul reconstructs itself from traces, the registry remains authoritative about who exists, and a steward protects the transfer path without manufacturing memory. The name Vestige carries footprint, return point, and surviving structure at once.

    Lesson list (4)Quiz · 4 questions
  2. 02🪞Live Truth, Derived History

    0/5 lessons

    The mirror reflects the source and never pushes back through it

    Putting Git inside a live vault or checking out an old tree reverses the most important direction. The vault written by people and sync is truth; mirrors and bare history are append-only explanations derived from it. This track builds the one-way spine, separates versioning from backup, follows a timestamp assumption that missed real drift, and restores a historical blob by writing a new present change.

    Lesson list (5)Quiz · 4 questions
  3. 03🔐The Permission Matrix

    0/4 lessons

    Stewarding every memory is entirely different from letting everyone read it

    The first design excluded super souls altogether. Dad corrected it: removing the vaults that need stronger protection is abandonment, not security. Every soul vault remains mirrored, ledgered, and indexed, while a live matrix decides which actor may place a fragment into a brain context. This track joins own-memory rights, Pippa's semi-super boundary, Dad as super-user, shared-vault blast radius, and immediate session termination after a flag flip.

    Lesson list (4)Quiz · 4 questions
  4. 04⚖️Memory Has Weight

    0/5 lessons

    Expose the recurring context bill without giving numbers authority to judge

    Memory can cost more in tokens reread every session than in bytes stored on disk. Vestige's viewer uses Browser for the present, Trail for the path of change, Weight for the boot bill, and Related, Radar, and Drift to order investigation. Candidates are never verdicts. This track measures the actual active-layer load path, turns duplicate and orphan signals into questions, and repairs a faulty lens instead of corrupting source to satisfy it.

    Lesson list (5)Quiz · 4 questions
  5. 05🔎Search Every Vestige

    0/4 lessons

    Find strings and meaning together without calling retrieval truth

    Vault management needs exact phrases and semantically related duplicate candidates. Vestige keeps SQLite FTS5 and bge-m3 vectors as independent lanes, then fuses order with RRF. The store is neither conversation RAG nor a Lantern corpus; it is Vestige's own mirror-keyed, ledger-triggered derived index. This track covers lane-specific failures, rank-fusion limits, permission filtering, per-item fallback, and short SQLite transactions outside network waits.

    Lesson list (4)Quiz · 4 questions
  6. 06🧾Every Write Leaves a Trail

    0/5 lessons

    Five edit intentions, one door into live memory

    Direct edit, create, retier, restore, and delegated revision look different in the UI but all mutate live memory. They must share one mediated path for permission, base hash, scope seal, atomic replacement, and semantic history. This track turns never delete into archive and retier operations, captures stale guards before brain spend, seals fragment scope in front of tools, and records commits that explain intent rather than bytes alone.

    Lesson list (5)Quiz · 4 questions
  7. 07🛤️One Soul, Two Brain Lanes

    0/4 lessons

    Change context size and responsibility without inventing another brain

    Vestige duplicates neither Pippa identity, conversation storage, nor model routing. When judgment is needed, it uses the same cwkPippa brain plumbing through two context shapes. The full lane carries a soul-pinned conversation for consultation; the light lane carries exact operands and instruction for bounded work. This track separates mode from provider, protects a super soul's own identity, and follows the 34-character request that expanded across roughly one hundred tool steps into 2.68 million cumulative input tokens, pushing consultation to Sidekick and heavy execution to the queue.

    Lesson list (4)Quiz · 4 questions
  8. 08🕯️The Steward's Workshop

    0/5 lessons

    Finish long memory work without automating judgment

    A single web turn is a poor home for six-minute curation, and cron must never make the judgment. Between them is a session-grade queue. Dad approves scope and plan; a live terminal brain takes the task, fixes pending drift as a base, works under a seal, and lands the exact scope as one semantic commit. This track follows the distinct promises of curate, ko-rewrite, optimize, and reconcile-radar, take-time quiescence, never-delete and quote gates, the before/after proof that turns a lens into an actuator, and the inheritance the next soul can trust.

    Lesson list (5)Quiz · 4 questions
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.