spec

# Feature spec authoring ## Workflow role - role_name: spec - stage: authoring - upstream: accepted proposal or approved direction - downstream: spec-review - summary: Author the contract. - ownership: Write the spec and authorized governed evidence/transition. - must_not_claim: spec-review approval, architecture readiness, plan readiness, implementation readiness, verification, branch readiness, or PR readiness. Portable work is isolated. Workflow-managed execution does not enlarge the `spec` write set. ## Purpose and evidence Resolve placement from identity, metadata, contracts, guidance, then defaults. A relied-on proposal requires accepted settlement, no open finding or later contradictory review, and required closed resolution; treat upstream as read-only. ## Project-local evidence Public skills use customer-project mode by default and project-local artifacts when present, including `docs/workflows.md` for local routing or placement. Do not require RigorLoop repository-internal artifacts in customer projects; use portable defaults or block on ambiguity. ## Invocation profiles and governed signals Classify every invocation before mutation. | Profile | Signal classification | Loaded procedure | | --- | --- | --- | | `SA0-portable` | `no-governed-signal` | Core plus both boundary references | | `SA1-governed` | `single-governed-candidate` | SA0 plus governed reference | Signals are `no-governed-signal`, `single-governed-candidate`, and `invalid-or-ambiguous-gover...