Documenting Decisions

Checkpoint tags

Tag	When to mark
`ARCH`	New abstractions, deps, data models, component boundaries — anything that shapes long-term structure.
`SCOPE`	You resolved an ambiguity in the task by choosing an interpretation.
`IFACE`	Changed a public API, config schema, CLI flag, env var, or wire format.
`SEC`	Touched auth, crypto, permissions, network exposure, or input validation.
`IRREV`	Created a migration, data deletion, deployment trigger, or external side effect.
`NOVEL`	No existing repo pattern to follow — you interpolated from training data.

Do not mark routine changes (pattern-following, boilerplate, refactoring).

See this skill's references/ decision-markers.md and (if needed) marker-examples.md.