Skip to content
PETROVA

2026-05-20-traceo-optional-deferral

title: Defer Traceo wiring for optional repos (eva-hq, skyflow-hq) date: 2026-05-20 status: ratified mr_compliance: [MR-7, MR-13] ranks_under: docs/decisions/2026-05-01-traceo-wire-adoption.md

Section titled “title: Defer Traceo wiring for optional repos (eva-hq, skyflow-hq) date: 2026-05-20 status: ratified mr_compliance: [MR-7, MR-13] ranks_under: docs/decisions/2026-05-01-traceo-wire-adoption.md”

Context

Section titled “Context”

Sub-project C ratified integrations_applicability.traceo: required for 5 repos and optional for 2 (eva-hq, skyflow-hq). The petrova-wire-traceo execution sub-project does not pursue the optional wirings in this cycle because:

  • eva-hq is pre-launch: the eva consumption surface itself is not yet published (see 2026-05-06-rocky-ownership-and-eva-introduction.md).
  • skyflow-hq has no state/skyflow-hq.yaml and is not currently governed by the integration spine; introducing Traceo would require an onboarding pass first.

The state schema’s current_status enum has no deferred_optional value. Per the kahn-hq crumb precedent (registry.yaml notes on crumb: not_applicable with review_by 2026-08-01), we model “optional + not pursued this cycle” as current_status: not_applicable with a review_by clause recorded in the registry notes and the state probe_history detail.

Decision

Section titled “Decision”
  • eva-hq: flip state/eva-hq.yaml.current_status.traceo from pending to not_applicable. Append a registry note recording traceo.review_by: 2026-08-20.
  • skyflow-hq: no state file change (it has no state file). Append a registry note recording traceo.review_by: 2026-08-20.
  • Revisit on 2026-08-20: if the eva surface has launched OR skyflow-hq has been onboarded, re-evaluate applicability and open a wiring decision.

Consequences

Section titled “Consequences”
  • petrova doctor reports traceo: not_applicable for both repos rather than pending — no false-negative noise on the dashboard.
  • The optional applicability declaration in registry is unchanged (governance intent is preserved per the ARES sub-project B rollback precedent — applicability declarations are never silently downgraded).
  • This decision creates a calendar dependency: an explicit review on 2026-08-20.

Schema follow-up (not blocking)

Section titled “Schema follow-up (not blocking)”

Open question for future sub-project: introduce a current_status: deferred_optional enum value so the “optional, not pursued” state is distinguishable from genuine not_applicable. Out of scope here; tracked as a finding.