#Specs

Behavioural specifications for features in sigit-si. A spec describes the contract a feature must satisfy: inputs, outputs, error cases, authorization, and acceptance criteria. It is the source of truth for what the code is supposed to do, independent of how it is implemented.

Conventions:

• One file per feature, kebab-cased (mcp-server.md).
• Front-matter carries name, description, status, and the implementing paths so a reader can jump from contract to code.
• status is one of draft, implemented, or deprecated.
• Write to the same rules as the rest of this repo (see ../AGENTS.md): technical and neutral, no AI-writing tells, no em dashes.
• When behaviour changes, update the spec in the same change as the code.