trellis-update-spec

To document code conventions after debugging, capture executable contracts into durable code-specs using a seven-section template covering scope, signatures, validation matrices, and test cases to preserve actionable decisions and prevent knowledge loss.

You need to update code specifications when triggers occur, such as new or changed API signatures, cross-layer contract modifications, database schema migrations, or infrastructure wiring changes, ensuring boundary behaviors and payload fields remain auditable.

The best way to formalize institutional memory is generating structured code-spec documents that define signatures, validation error matrices, and wrong versus correct implementation cases, preserving decision rationale for future sessions and new team members.

Yes, structured spec tracking applies to cross-layer contract changes and infrastructure wiring updates by capturing payload fields, environment keys, and boundary behavior into testable, auditable specifications with required validation and error matrix sections.

An executable code-spec document requires seven sections: Scope/Trigger, Signatures, Contracts, Validation & Error Matrix, Good/Base/Bad Cases, Tests Required, and Wrong vs Correct, ensuring precise and testable coding convention specifications.