loom-constitutionlisted

# loom-constitution Constitution owns durable project judgment: identity, policy, principles, constraints, architectural precedent, roadmap direction, and choices future agents should not re-litigate. It does not own intended behavior, live execution, evidence, audit verdicts, research synthesis, or reusable explanation. ## Use This Skill When Use it when work may depend on or change: - project identity or non-identity - durable policy, principle, or constraint - ADR-style architectural or process precedent - roadmap-level strategic direction - a constitutional record's status, successor, or retirement Do not create constitutional records for local preferences, task progress, implementation notes, behavior contracts, ticket acceptance, or knowledge notes. ## Inspect Constitution lives under `.loom/constitution/`. Start here: ```bash find .loom/constitution -name '*.md' -print 2>/dev/null grep -R '^ID:' .loom/constitution 2>/dev/null || true grep -R '^Type:' .loom/constitution 2>/dev/null || true grep -R '^Status:' .loom/constitution 2>/dev/null || true ``` Read the active core constitution first when present: ```bash grep -R -l '^ID: constitution:main' .loom/constitution/*.md 2>/dev/null || true ``` Then read active top-level principle fragments and nested decisions or roadmaps that match the current topic by slug, ID, title, subsystem, policy, or grep hit. Historical records (`superseded`, `retired`, and completed roadmaps) are context only; read them when an ac