Charter

Charter repo development knowledge: solution layout, build/test/run commands, dotnet-tool packaging, native-binary distribution, testing conventions and gotchas. Use when implementing, testing, running, or packaging Charter, or onboarding an agent to the codebase. SELF-UPDATING: When your work changes the solution layout, conventions, packaging, distribution, or any fact below, you MUST update the affected section(s) before completing your task.

Charter product knowledge for all agents working in this repo. Use when working on anything related to Charter: - The deliverable model: block-structured markdown, the block catalog, the question block - The comment-in-place review loop, anchors, and the anchor→markdown source-map - The author → review → handoff workflow and the Guardrails handoff contract - The settled format decision (markdown+directives) and why not the alternatives - Load-bearing invariants, where-truth-lives, and roadmap/status Provides: the mental model, review-loop semantics, the format rationale, and pointers to the single-source-of-truth documents. SELF-UPDATING: When your work changes the deliverable model, block catalog, review-loop semantics, format decision, handoff contract, or roadmap, you MUST update the affected section(s) here before completing your task.

Use when you must turn a task into a reviewable plan with Charter — author a block-structured .charter.md, render/serve it for a human to annotate in the browser, then hand off plain CommonMark to Guardrails. Covers the author → review → handoff workflow and the block catalog.

The normative Charter `.charter.md` block catalog and `:::question` open/resolved schema — the single format source of truth cited by the charter authoring skill (to WRITE blocks) and by Guardrails plan-breakdown (to INTERPRET them). Use whenever you must read, write, or interpret Charter `:::` directive blocks.