Source Layers

Source layers define what is authoritative, what is derived, and what is only analysis support.

Summary

The source hierarchy is:

foryoutune-dev raw docs and git log
Generated board docs
Curated history records
Harness docs
NotebookLM export packs

Why This Matters

Clear hierarchy prevents analysis tools and generated summaries from becoming accidental source of truth.

Evidence Sources

TASKS/*.md, REVIEWS/*.md, docs/STATE_SYNC.md, and git log in the source repo
src/content/docs/generated
src/content/docs/history
src/content/docs/harness
exports/notebooklm

What Happened

The board sync reads the source repo and writes derived board docs. NotebookLM receives exports from the board, not direct authority over the system.

Decision / Lesson / Pattern

Git, Markdown, board automation, and generated or curated history docs are the source system. Notion, NotebookLM, and chat memory alone are not source of truth.

What To Preserve

Source repo read-only boundary
Generated docs as reproducible summaries
Curated records as explicit judgment
Export packs as analysis-only documents

What To Recheck

Whether any external tool starts receiving undocumented authority
Whether generated docs copy sensitive raw text
Whether curated docs point back to reliable evidence

Carry Forward

Every future project board should define source hierarchy before adding automation or analysis tools.

Current Workflow