stratt-hq eva applicability drift (state ≠ registry)
Observation
Section titled “Observation”During petrova-wire-traceo scoping, the following drift was observed:
registry.yaml:stratt-hq.integrations_applicability.eva == requiredstate/stratt-hq.yaml.current_status.eva == not_applicable
This is the inverse of the choco-hq drift fixed in Task 1 — here, the registry expresses governance intent (eva is required for stratt-hq) but the state file claims the integration doesn’t apply.
Why this matters
Section titled “Why this matters”When eva-hq’s consumption surface launches (deferred per
2026-05-06-rocky-ownership-and-eva-introduction.md), the
petrova-wire-eva sub-project will need to wire stratt-hq among others.
If the state file still says not_applicable at that point, the next
sweep will overwrite registry intent or trigger a false-positive
conflict alert.
Resolution path (not this sub-project)
Section titled “Resolution path (not this sub-project)”When petrova-wire-eva activates:
- Confirm stratt-hq is still
eva: requiredin registry. - Flip
state/stratt-hq.yaml.current_status.evafromnot_applicabletopending(the honest pre-wiring state). - Proceed with wiring per the (yet-to-be-written) eva wire prompt.
If by that time the registry has been amended (eva no longer required for stratt-hq), align the state accordingly without wiring.
Cross-references
Section titled “Cross-references”docs/superpowers/specs/2026-05-20-petrova-wire-traceo-design.md§2docs/superpowers/specs/2026-05-20-petrova-wire-rocky-design.md§2 (notes the same stratt-hq drift in passing)