Use prompts for stable operating instructions.
Keep the durable essentials in the instruction layer: role, responsibilities, authority and retrieval protocol. Putting every document and past conversation into that layer makes it harder to identify what is current and authoritative.
Use records for changing knowledge.
Project documents, decisions, artifacts and lesson history should be stored as addressable records with provenance and versions. Retrieve a focused set when a project starts, and recover current project state before resuming work.
Separate user preferences from project facts, operational state and external evidence. Each changes at a different pace and needs a different owner.
Close the learning loop.
At completion, attach the delivered artifact and validation result. Record any lesson with enough context to judge its applicability later. A new project can then use the history without inheriting stale assumptions.
- Retrieve relevant context
- Check source and version
- Record the applied lesson
- Execute within the project scope
- Save the outcome and evidence