Skip to content
PETROVA

2026-10-20 — Reconcile contract drift for traceo-mcp-server

rank: decision outranks: []

Section titled “rank: decision outranks: []”

2026-10-20 — Reconcile contract drift for traceo-mcp-server

Section titled “2026-10-20 — Reconcile contract drift for traceo-mcp-server”

Date: 2026-10-20 Status: ratified Verb: petrova_act_reconcile_drift Slug: traceo-mcp-server MR-compliance: MR-4, MR-7, MR-12

Rationale

Section titled “Rationale”

Sweep at 2026-10-20T10:34:41.490Z reported actual_contract_sha=ccf2f16c7a14 against registered=99df3d222d0f. Bumping registry.yaml > repos[traceo-mcp-server].contract_sha to match the consumer’s source of truth.

The substantive contract change is the consumer’s responsibility and is recorded in that repo’s git history at ccf2f16c7a14. This verb records that the control plane has acknowledged the drift and realigned. No verification round required (MR-10 does not apply to registry-edit verbs).

Pre-edit registry.yaml sourced from origin/main.

Change summary

Section titled “Change summary”

registry.yaml > repos[traceo-mcp-server] after this verb:

- slug: traceo-mcp-server
  url: https://github.com/traceo-cat/traceo-mcp-server
  default_branch: main
  role: scaffold
  profile: standard
  fleets_allowed: []
  added: '2026-04-30'
  contract_sha: ccf2f16c7a14
  integrations_applicability:
    ares: optional
    traceo: not_applicable
    crumb: not_applicable
    rocky: not_applicable
    eva: not_applicable
  contract_committers:
    - humans
  notes: |
    ares applicability downgraded required → optional on 2026-09-22 per
    docs/decisions/2026-09-22-ares-registry-reclassification.md — actual
    state is `pending` (never wired).
    Traceo.ai MCP server for requirements management and traceability;
    downstream archive endpoint per .archive-manifest.yaml (accepts: []).
    Receives baseline content via the ariel pip git dependency pinned in
    traceo_mcp_server/pyproject.toml; never authored directly. Integration
    contract upstream at ariel/specs/08-traceo-integration.md.
    PETROVA control loop scaffolded 2026-04-30 under M-1 (Petrova scaffold
    bootstrap), closed same day; verification round at
    docs/decisions/0002-m1-verification-round.md (6 friction items
    F-1..F-6 dispositioned). Role/profile chosen in
    docs/decisions/0001-adopt-petrova-scaffold-profile.md: scaffold
    because no discipline track record yet, permissive because the
    append-only convention has not been load-tested. MILESTONES.md and
    docs/north-star/intent.md exist as sources; CLAUDE.md and AGENTS.xml
    at repo root project from them.
    Promoted to profile=standard 2026-08-13 under M-2, per
    traceo_mcp_server/docs/decisions/0044-promote-profile-permissive-to-standard.md
    (phase opened by 0040). The gate — first supersession in
    docs/decisions/ — fired 2026-05-20 when 0029 superseded 0028; the
    convention has since held under pressure twice more (0024 left in its
    pre-convention shape rather than retro-edited; 0037's knowingly-false
    constraint corrected by 0042 rather than by editing 0037).
    Registry posture audit clean 7/7 at promotion per
    traceo_mcp_server/docs/findings/20260813-0900-registry-posture-audit-m2-promotion.md.
    Branch protection is unavailable (HTTP 403 — private repo, plan without
    protected branches), so strict is unreachable here; standard follows the
    bhava-blue precedent (2026-07-29). CI exists and runs on every push and
    PR: docs-invariants green, petrova-notify-state green, Traceo CI
    currently red on pre-existing Rust/Docker/ariel infra failures.
    fleets_allowed stays empty by design — under standard that makes the
    promotion a tightening (fleet:* actors can no longer auto-merge at all);
    admitting a fleet is its own decision.
    Was the first registry entry to use profile=permissive; schema-valid per
    registry.schema.json HEAD on 2026-04-30.

Envelope

Section titled “Envelope”
idempotency_key: 8b68173a2dbe90e398b45e8a479946fa0e20c4e6b07c374ed575f72105781d5f
schema_fingerprint: 1856849c5806
actor: human:cli
triggered_by:
  kind: human_request
  ref: cli
applied_at_iso: '2026-10-20T11:23:14.342Z'

Sign-off

Section titled “Sign-off”

Human merge required per MR-12 — this PR is opened with the awaiting-human-merge label and does not auto-merge.