Tool matrix

POM tools

Tool	Approval	Responsibility
`pom_state`	write	Read/configure project state and record decisions, assumptions, or warnings
`pom_stage`	write	Start, navigate, evidence, block, resolve, and pass stages (validation-gated)
`pom_artifact`	write	Measure, hash, version, classify, and register a canonical artifact
`pom_validate`	read	Run deterministic scoped checks and emit an expandable report card
`pom_prompt`	read	List or retrieve bundled/project prompt fragments and provenance
`pom_hive`	write	Plan native task batches, record IRC signals, and persist synthesis
`pom_export`	write	Build and fully verify checkpoint or final archives

Primitive	POM use
`task`	Exactly one bounded batch per independent specialist wave
IRC	Short ownership, dependency, alert, handoff, and completion signals
todo	Exact phase plan for the active stage
Swarm extension	Optional unattended parallel/sequential/pipeline DAG
session entries	Append-only POM state restoration across branches
model roles	Deep planning/audit versus sustained drafting
active-tool profiles	Minimize context and risk for each stage

Scope	Checks
`quick`	State shape and basic invariants
`stage`	Active stage contract, artifacts, evidence, and blockers
`canon`	Canon-oriented artifacts and manifest metadata
`continuity`	Timeline, continuity ledger, and unresolved issue markers
`knowledge`	Vault structure and wikilink targets
`files`	Manifest paths, sizes, hashes, duplicates, and symlinks
`delivery`	All delivery prerequisites, rights metadata, checksums, and package structure
`all`	Broad project validation; final delivery should still use `delivery`