A human-led architecture for durable knowledge, bounded orchestration, and evidence-backed work.
Keep authority with the human, durable knowledge in Markdown, retrieval rebuildable, and execution replaceable. Every handoff names its input, output, and verification.
Write the desired outcome, constraints, and acceptance test in plain language.
Assign knowledge, retrieval, procedure, tool, model, and evidence responsibilities.
Grant only the capabilities needed for this task; keep credentials and secrets scoped.
Assemble only the minimal, verified sources needed for the task.
Follow the procedure, invoke allowed tools, and return evidence for review.
Only import curated summaries; never index raw transcripts or chat logs.
Keep credentials, tokens, and keys in encrypted secret manager, not in notes.
Ensure a usable plain-Markdown navigation fallback exists.
Design an Obsidian vault structure for [PROJECT]. Use ordinary Markdown, separate canonical notes from inbox and archive material, add minimal metadata, and preserve manual navigation.
Use placeholders for paths, accounts, endpoints, identities, and credentials. Never publish secret values, private records, or a live control surface.