Workflows

Architecture change intelligence

Compare the latest architecture snapshots, distinguish removals from missing coverage, and evaluate deterministic regression gates.

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.

A missing observation is not a deletionComparable snapshots and source parity distinguish verified change from incomplete collection.HYPERORU FIELD GUIDEEVIDENCE FIRSTA missing observation is not a deletionComparable snapshots and source parity distinguish verified change from incomplete collection.TB1TB2SNAPSHOTSCOMPAREGATEcompareevaluate01Snapshot NPrior truth02Snapshot N + 1Current truth03Source parityComparable coverage04Classify changeAdded · removed · unseen05Regression gatePass · review · blockedChanged collection coverage stays visible as not re-observed.
A missing observation is not a deletion

Review change against intent

The workspace navigation exposes Architecture, Intent & decisions, Drift & changes, and Coverage. Inspect the map and evidence before interpreting a change as a weakness. A single snapshot establishes context; drift needs a baseline and a later observation.

A recorded architectural decision binds its human rationale, owner, affected entities, supporting evidence, and guardrails to a baseline snapshot. Ratification is an explicit approval by a named workspace member. It does not turn a free-text guardrail into an automatic check: only structured success criteria can be evaluated deterministically, and missing evidence can leave a result inconclusive.

The change view compares repository snapshots. Archive reviews can support truth exploration and decision proposals, but they do not establish repository history by themselves. No history means no drift verdict.

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.