Skip to content

KOVA_ALIGNMENT.md

Latest commit

 

History

History
77 lines (60 loc) · 3.56 KB

KOVA_ALIGNMENT.md

File metadata and controls

77 lines (60 loc) · 3.56 KB
Raw

Field Fleet ↔ Kova alignment review

Reviewed 2026-07-11 against:

  • openclaw/Kova at 2b02b7d33418db0c6952c4cf8fe8a608e7964859
  • openclaw/openclaw at dfeb15261db3f8e8a5867ad0966faa19313fe80f

Verdict

Field Fleet is aligned with Kova's direction and now emits the reviewed kova.report.v1 envelope with a fieldFleet extension. Keep Field Fleet as the standing, persistent canary lane; use real Kova runs for disposable runtime validation.

Product boundary

Kova provisions disposable environments, clones representative user states, runs OpenClaw scenarios, records evidence, and cleans up. It already covers release upgrades, rolling old-release state, smoke, diagnostic, soak, and performance-oriented profiles.

Field Fleet should not duplicate those disposable lanes. Its useful distinction is a small standing fleet on stable/beta/dev that accumulates realistic state and is observed across repeated cycles. Kova can be invoked by a Fleet adapter for upgrade/smoke/soak checks, while Fleet owns scheduling, longitudinal history, promotion policy, and retained-member health.

Implemented alignment

Completed against the reviewed Kova commit:

  • Canonical controls, auth, network-frontage, baseline/gate, platform, output paths, record repeat/measurement, performance, and proof-summary fields.
  • Missing/malformed required evidence is INCOMPLETE; executed failures remain FAIL; unmet dependent phases are BLOCKED.
  • Standing members use cleanup: "retained" with retainedReason: "field-fleet-standing-member".
  • JSON, Markdown, compact summary JSON, dark HTML, and bounded SHA-256 artifact indexes are produced and revalidated after finalization.
  • The private manifest remains the stronger crash-safe artifact authority. A degraded manifest produces a bounded, explicitly incomplete portable index.
  • The reviewed upstream commit is recorded in the fieldFleet extension.
  • Strict current adapter validation is tested with a reviewed upstream fixture; a history-only compatibility path preserves immutable reports from the earlier Field Fleet envelope.

Remaining integration work

  1. Consume actual kova.run.receipt.v1 / kova.report.v1 artifacts from Kova adapters rather than reimplementing Kova's runtime scenarios.
  2. Deploy the first persistent member and separately review its real OpenClaw adapter and operational credentials.
  3. Re-review compatibility when the pinned upstream Kova commit changes.

Field Fleet has no Crabbox integration or dependency. Deployment-provider selection remains an external operations decision.

Explicit non-goals

  • Do not make persistent Fleet members conform to Kova's disposable cleanup lifecycle.
  • Do not target OpenClaw's kova-report-gate.mjs as a universal validator. That gate is tailored to OpenClaw's performance workflow and requires destruction, profiling, performance groups, and baseline checks that are inappropriate for standing canaries.
  • Do not duplicate Kova's existing disposable release-upgrade profiles.

Upstream references