context

name	context
description	Load when reading or writing project notes, weekly/monthly summaries, or journal/agent.md. Owns GET/PATCH for context files except today.md and roadmap.md, which use their dedicated skills.
allowed-tools	["Bash(curl *)","Read"]

Context File Update Guide

Output language: context files are Policy B — see <output_language_policy>. Preserve user-customized headers verbatim (whichever language the user rewrote them in).

Context files are the agent's working memory, stored in the primary management vault. All writes go through the Daemon API — never touch files on disk directly.

/api/context/* is the only legal write path to the primary vault, regardless of where that vault physically lives: whether it is ~/.personal-agent/context/ (plain mode) or a user-chosen Obsidian-style directory (obsidian mode, primaryVaultPath). Never write to those paths directly via Edit / Write / shell redirects, and never reach them via /api/obsidian/* — that endpoint targets a separate external Obsidian vault, not this primary store.

File responsibilities

File	Purpose	Owner	Lock?
state/today.md	Today's schedule, tasks, agent log, handoff	See today skill	Yes (Morning Routine)
plans/roadmap.md	Long-horizon agent action plan + Long-term Plans	See roadmap skill	Yes (Roadmap Refresh)
plans/projects/*.md	Project state summaries	Any event on material state change	No
journal/weekly/YYYY-Www.md	Weekly review snapshots	Friday Weekly Review only (PUT)	No
journal/monthly/YYYY-MM.md	Monthly review snapshots	Month-end Monthly Review only (PUT)	No
policies/*.md	User-controlled policy files	Explicit user request only	No
policies/management-captures/<slug>.md	Durable management policies captured from DM	management-policy skill — do not write from here	No
policies/management-captures/_index.md	Readable index of active policies	management-policy skill — do not write from here	No
policies/routines/*.md	Per-cadence check rulebooks	Explicit user request only	No
identity/profile.md	User identity and preferences	user-profile skill — do not write from here	No
identity/*.md	Detailed user dictionary	user-profile skill — do not write from here	No

Morning Routine scans roadmap daily and processes matching Preparation Timeline rows into state/today.md — see the roadmap skill for the full entry taxonomy and the morning routine task-flow for the scanning rules.

plans/projects/*.md

Update on status changes, milestones reached/delayed, or active set changes. Use GET /api/context/list/plans/projects to discover files. The source of truth is always the individual plans/projects/<slug>.md notes; _active.base is only the Obsidian Bases view config, not a narrative summary note.

The canonical frontmatter schema is documented in plans/projects/_index.md (seeded from agent-assets/templates/plans/projects/_index.md). The API validates only type: project, owner: shared, updated, and an H1 (context-frontmatter.ts). Conventional but unvalidated fields — slug, state, start, due, stakeholders, next_milestone, tags — should still be written for new files because the plans/projects/_active.base Obsidian view filters on state.

Project DM-intent detection

DM-driven project writes are dispatched by _partials/dm-intent.project.md (the decision tree — match, decline markers, confirm sub-flow, slug grammar, tie-breakers — lives there). This skill is the writer: it executes the plans/projects/*.md PUT / PATCH / archive per the API Reference below.

Snapshot files — weekly / monthly / policies / routines

Weekly and monthly review snapshots, the user-controlled policies/*.md policy files, the built-in policies/routines/<cadence>.md rulebooks, legacy custom-routine files under policies/routines/custom/ (inert — converted to Agents at the Agents-hub redesign), and the agent-private journal/agent.md all have stable per-file conventions (writer event, verb, frontmatter, retention) documented in the snapshot-files reference below.

DM handlers and Activity Scans should generally not write these files — the cadence-matching routine is the right writer.

{{> ref:snapshot-files }}

Required frontmatter for guarded files

Full-file writes to identity/*.md, policies/*.md, plans/projects/*.md, journal/daily/*.md, journal/weekly/*.md, and journal/monthly/*.md must open with the matching YAML frontmatter (type, owner, updated) followed by at least one H1 heading. Per-glob values and the common rejection envelope are in the required-frontmatter reference below.

{{> ref:required-frontmatter }}

API Reference

The full /api/context/* surface — read / write / list / lock / archive / restore / health / repair / action-log — is organised by operation in the reference below. Add X-Lock-Id on every PUT / PATCH to state/today.md (<today_write_lock_id>) or plans/roadmap.md (<roadmap_write_lock_id>) when the matching lock-id tag is in your context.

{{> ref:api }}

Knowledge map — file responsibilities (auto-curated)

Knowledge map — frontmatter requirements (auto-curated)