Spec Template

1. Summary

One paragraph: what is built, for whom, why, and the measurable outcome.

2. Goals and non-goals

Goals: {measurable outcomes}

Non-goals: {explicitly out of scope}

3. Users and scenarios

4. Functional requirements

5. Non-functional requirements

6. Architecture

{Two or three sentences on components, data flow and trust boundaries.}

7. Agents

8. Components and Azure services

9. Data

Entities, fields, ownership, retention and classification. Name the sample or synthetic data source and where it lives.

Seed rules. For every seeded record a rule reads, freeze the values the rule needs (dates, counts, amounts, window anchors) and each tool’s result for that ID, including empty results. Labels and names carry no decision facts.

10. Implementation contract (frozen)

Service names, environment variables, endpoints, protocols, request, response and error schemas, streaming, auth and versions. Change this section before changing any code that depends on it.

Decision rules. Each rule reads only frozen facts or tools in the consuming agent’s list, and a decision tool has a frozen derivation. A window names its anchor date; trigger categories are closed lists. Guards, routing and sort keys cover every enum value plus null or invalid agent output. Recompute each scenario’s expected outcome from these rules. Tables keep the header’s cell count. Describe credentials and Authorization values in words, never as literals.

11. Workstreams

At most four. The phase lead owns the foundation, the contract, shared configuration and integration.

12. Verification plan

Evaluation: {n} scenarios from section 3 with expected behaviour; metrics: task adherence, groundedness (when grounded) and safety.

13. Assumptions and open questions