Files
dotfiles/claude/memory/feedback-engine-sources-become-permanent-chamber-collection.md
T

1.8 KiB

name, description, metadata
name description metadata
feedback-engine-sources-become-permanent-chamber-collection Standing steward policy (2026-06-28) — any work added for the engine to write with becomes part of the permanent chamber-library collection unless expressly stated; the chamber grows richer over time; all Making sources must be graduated into it.
node_type type originSessionId
memory feedback 24f4f06b-31a0-4984-b176-3dca24ad5ff6

Steward directive, 2026-06-28: from here on, unless expressly stated otherwise, every work added for use with the studium engine (for writing) also becomes part of the permanent collection in the chamber library — graduated to the canonical gold-standard bar, not merely staged/converted for one-time use.

Why: the chamber is an accumulating substrate, not a per-task scratch. Over time it becomes richer and more subtle. Engine-use and chamber-membership are therefore unified — adding a source for the engine is graduating it into the chamber. (Partly resolves the morning-of-2026-06-28 "serious future decision on where sources live" — see the-maturation-of-the-chamber-a-dialogue-2026-06-28.)

How to apply: when converting/adding any engine source, take it all the way — clean → verify_conversion PASS → graduate_to_canonical → catalogue → author the sidecar at graduation (sidecars-as-we-go). Never leave an engine source as a throwaway in scratch/ or /tmp.

Immediate consequence: all ~30 Making sources (not just the Position-I subset) need graduating into the chamber. Census/work-list: chamber-library/docs/making-corpus-conversion-readiness-2026-06-27.md. Related: project-making-sequence-source-set, reference-studium-engine-architectural-charter. Candidate to formalize into the chamber-library specification (§ on what belongs in the chamber) when next revised.