Specifications

A specification describes a change that affects more than one repository in the rettX ecosystem. Specs are the unit of planning above any single repository.

Where specs live

Specifications live under specs/ in this repository, one folder per spec, named NNNN-slug/. Each spec folder contains:

• spec.md — the what and the why, including a constitution check.
• plan.md — the how, broken down by repository.
• tasks.md — the work, grouped by target repository so it can be fanned out into tracked issues on merge.

How a spec gets written

1. Someone opens a Spec proposal issue in rettx describing the problem.
2. A maintainer triages it and decides whether it needs a full spec or a smaller fix in a single downstream repo.
3. If a full spec is needed, a draft PR is opened adding a new folder under specs/.
4. The draft is iterated on until it passes the constitution check. Stakeholders for each affected repository review their slice.
5. On merge, the Iris automation creates linked issues in each target repository with the squad label, where the work is actually executed.

Templates

The empty templates that every new spec starts from are at specs/template/. Copy them, don’t symlink them.

Currently live specs

There are no merged specifications yet. Watch this space — and the issues with the spec label in the meantime.