Cadence docs
docsuai-explorerredacted view

Cadence v6 Phase 6 Write-Side Pilot

The Cadence v6 Phase 6 write-side pilot is the controlled cutover that

Updated 2026-06-25·Freshness: Reference·No secret-like patterns were observed in this view.

Cadence v6 Phase 6 Write-Side Pilot

The Cadence v6 Phase 6 write-side pilot is the controlled cutover that

Body

Cadence v6 Phase 6 Write-Side Pilot

Purpose

The Cadence v6 Phase 6 write-side pilot is the controlled cutover that flips the first Cadence route from "not-enforced" to "enforced," moving Rust Cadence v6 from read-parity into controlled write territory while the Python fallback stays intact. This is WS-B B.3 of the cross-product migration ops framework. Per operator default applied 2026-06-20, the actual cutover is parked until the 0.01 foundation (July 10–15); this plan drafts the procedure so it is ready when the gate opens.

Current State

  • Status: plan drafted; cutover parked until 0.01 foundation (July 10–15).
  • Source workstream: WS-B "Cadence Finalization" — action B.3 (G0 doc).
  • Authoritative Phase 6 source: docs/director-rust-axum-migration-plan.md §Phase 6 (lines 160–172) on NUC-IPEX.
  • Phase 0 contract snapshot: the frozen inputs the pilot will write against.

Pilot Route Selected

  • First flip: echo-rtx3060.health-embedding — the only route currently at enforcement_state=not-enforced in production.
  • Why this route: single not-enforced row, sandbox-class worker (not production dispatch path), auth_mode=planned-auth, not in the external enforcement tier.

Phase 6 Constraints (from source plan)

  • Allow Rust to update a throwaway local copy first.
  • Then allow Rust to update non-risky local fields on the real DB.
  • Keep Python fallback intact.
  • Suggested first write: record a local heartbeat event.
  • Do NOT start with job status mutation.
  • Do NOT rewrite the database schema casually.
  • Do NOT run Rust and Python writers against the same DB without lock strategy.
  • Do NOT remove Python Director until Rust acceptance passes.
  • Do NOT use CT103 as the migration host.

Key Components / Locations

  • Plan doc: /root/ua....md.
  • Phase 0 snapshot: /var/lib....md (mirror at /root/cadence-v6-mirror/docs/).
  • Parent ops dir: /root/ua....md §B.3.

Relationships

  • Child of: uai-doc-... (WS-B B.3).
  • Target product: uai-doc-ecosystem-product-cadence-v6.
  • Producer of writes to: Cadence v6 production DB (under /var/lib/cadence-v6/).

Status

plan only — cutover parked until 0.01 foundation (July 10–15).

See Also

  • uai-doc-...
  • uai-doc-ecosystem-product-cadence-v6