trellis-update-spec

To capture executable contracts after debugging, run the update-spec workflow to turn insights into structured code-spec documents. This preserves actionable learning by outlining scope, triggers, validation rules, and test points for future sessions.

Preventing knowledge loss from infrastructure decisions requires centralizing executable contracts into .trellis/spec/ documents. This standardizes governance by specifying precise signatures, payloads, and environment keys to ensure decisions are actionable and verifiable.

Documenting verifiable code-specs requires specifying precise signatures, payloads, environment keys, validation rules, and test points. This structured approach ensures the executable contracts remain actionable and reproducible across cross-project changes.

The update-spec workflow does not require specific dependencies to manage code-spec documents. It operates independently to guide users through a standardized process of capturing executable contracts into the .trellis/spec/ directory.

You should not use a code-spec document for capturing implementation patterns when the changes are trivial or lack executable contracts, as the framework mandates defining precise signatures, payloads, and validation rules for actionable verifiability.