Every change begins as a suggestion, from an analyst, a support ticket, a customer or an engineer. The register is where that demand is admitted, de-duplicated and — before anyone is asked to author anything — classified.
Four classes, and one of them stops here
Change is classified as presentation, business rule, integration or architecture. The first two are what analysts author. The last is the one that matters most, because the most dangerous item in any backlog is the analyst request that quietly requires a new integration or a schema change.
An automated architecture impact check runs at admission. An item that reaches an author has therefore been proven not to need architecture work, which is a better answer to a head of engineering than any gate placed later in the process.
Admission control
- Duplicate detection against the standing register
- Classification with an automated architecture impact check
- Siloing by client organisation, so external contributors see only their own
Nobody authors architecture through ExaCollab. That is a deliberate limit, and naming it is what makes the rest of the process safe to widen.