Architecture change intelligence

Change Intelligence compares the latest two terminal architecture snapshots for a repository. It reports entity and relationship additions, verified removals, items that were not re-observed because source coverage changed, evidence references, and ownership hints.

Regression gate

The workspace policy controls a deterministic gate:

• minimum source coverage;
• whether compared snapshots must contain the same source families;
• whether any architecture change requires review;
• whether entity or relationship removals block;
• relationship kinds that block when newly introduced.

The result is one of pass, review, blocked, or insufficient_evidence. The reasons are returned as typed data rather than generated prose.

Coverage-aware removals

A resource absent from the newer snapshot is not automatically a deletion. When the source families differ, Hyperoru marks the item not_reobserved unless the policy and evidence establish a comparable source boundary. This prevents missing cloud, delivery, or runtime data from becoming a clean architecture verdict.

Ownership routing

Where entity or relationship evidence includes an owner, team, service, or repository attribute, the change item surfaces that owner hint. The workspace UI links the change to its source audit and lets reviewers ask Hyperoru about the existing evidence. It does not allow the assistant to override the deterministic gate.

GET /v1/workspaces/{workspace_id}/repositories/{repository_id}/changes

The response includes both snapshot IDs, source coverage, source parity, all change items, and the evaluated gate.