History Architecture
The history architecture separates evidence from summaries, summaries from curated judgment, and curated judgment from analysis exports.
Summary
Section titled “Summary”The board uses five layers:
- Layer 0 Raw Evidence
- Layer 1 Generated Summary
- Layer 2 Curated History
- Layer 3 Next-Generation Carryover
- Layer 4 NotebookLM Analysis Export
Why This Matters
Section titled “Why This Matters”Each layer has a different trust level. Raw evidence is authoritative. Generated summaries are reproducible. Curated history adds judgment. Carryover makes the history reusable. NotebookLM receives derived packs for analysis only.
Evidence Sources
Section titled “Evidence Sources”- Layer 0:
foryoutune-devdocs, reviews, tasks, and git log - Layer 1:
src/content/docs/generated - Layer 2:
src/content/docs/history - Layer 3:
src/content/docs/history/next-generation-carryover - Layer 4:
exports/notebooklm
What Happened
Section titled “What Happened”The board started as a generated project archive. Automation now keeps generated content and NotebookLM packs current. The history section adds the curated layer needed for long-term intelligence.
Decision / Lesson / Pattern
Section titled “Decision / Lesson / Pattern”Do not collapse the layers. Generated docs should not become raw evidence, curated docs should cite generated and raw sources, and exports should remain disposable derived artifacts.
What To Preserve
Section titled “What To Preserve”- Layer boundaries
- Record status values
- Source references
- Derived export disclaimers
What To Recheck
Section titled “What To Recheck”- Generated docs should remain safe summaries, not raw source copies.
- Curated history should be updated when decisions or lessons change.
- NotebookLM exports should not introduce new source-of-truth claims.
Carry Forward
Section titled “Carry Forward”Use this layered structure as the default memory architecture for future SaaS boards.