feat: Organize context files and enhance documentation for clarity and structure

ai/AGENTS.md

@@ -62,6 +62,7 @@ When drafting messages for a manager or stakeholder:
 
 - Treat workspace files as persistent memory, not just reference notes
 - Before answering prompts about current work, verify `ai/state/current.md` and the latest relevant log in `ai/logs/`
+- Before answering architecture, process, or historical questions, check the relevant file under `ai/context/systems/`, `ai/context/workstreams/`, or `ai/context/process/`
 - If `ai/inbox/mattermost-latest.md` exists, check it before answering prompts about current status, standups, or supervisor communication
 - Treat all meaningful user prompts as potential memory updates, not only explicit sync commands
 - If a Mattermost sync or other context-ingestion step fails, do not update `ai/logs/`, `ai/state/`, or stable context files based on that failure
@@ -72,6 +73,7 @@ When drafting messages for a manager or stakeholder:
 - Promote to `ai/state/current.md` only when the fact changes the active work window
 - Maintain `ai/state/work-items.md` with explicit Jira IDs, approved titles, and currently relevant scope/status notes
 - Promote to `ai/context/project.md` only when the fact is durable beyond the current work window
+- Use `ai/context/project.md` as the overview only; put system-specific, workstream-specific, and process-specific durable context in the corresponding subdirectory
 - Maintain `ai/context/people/` when repeated names, roles, or stakeholder relationships become useful for future sessions
 - Update existing memory when the new information is a correction, clarification, or refinement of something already stored
 - Prefer updating stable project context over appending generic operational summaries