Archive
Pointers to historical sources and a do-not-load list for agents.
This is not source material. It tells future readers and agents which folders contain prior work that should be treated as evidence rather than canonical context, and which files specifically should not be ingested as project context.
Treat as historical evidence
These locations contain prior work that may hold useful schemas, prior decisions, stakeholder language, or instrumentation history. Consult only when a specific need arises; do not load them as canonical KB context.
../../System/— the discontinued.NETweb (legacy product surface).../../docs/work-items/old-web-gtm-migration/— old-web GTM/PostHog migration tasks.../../docs/work-items/posthog-user-journey/— old-web PostHog journey instrumentation.../../workflow/docs/funnel-loop/— the archived weekly-memo framework.../../workflow/docs/research/— dated research documents from the discovery phase.
Do not load as canonical context
Files that should never be ingested as project knowledge — they are noisy, transcript-shaped, or session-specific.
../../docs/chat.md— large prior chat transcript. Distill anything useful into the layered KB; do not link agents at the raw file.- Any session transcripts or pasted-LLM-conversation dumps that may appear in the workspace.
Where meeting material lives
Polished meeting notes are at ../meetings/<date>-<slug>/notes.md and are canonical context. Raw recordings and transcripts are kept outside this repository entirely — see ../meetings/README.md for the policy.
Rule of thumb
If a file is a transcript, a chat dump, or a dated brainstorm, it is evidence — not canonical context. The KB layers and the polished meeting notes are the canonical context. When useful material is found in evidence files, distill it into the appropriate KB layer or notes file, then leave the evidence behind.