Last updated: 2026-09-27
This is the human-facing dashboard for current repo state. Keep it short,
latest-first, and pointer-based. Do not use this file as a changelog or
execution ledger. When older shipped detail is no longer needed for today's
orientation, move it to plans, ADRs, retrospectives, or docs/human/** and
leave a link.
Codex Responses and CloudML batch evaluation are retired from active support.
Full Codex SDK runs failed at the first model request (403) despite header and
protocol probes; no client repair was verified. Local evals and the remaining
provider routes continue. See
docs/status/active/codex-responses-api-investigation.md for evidence and limits.
The latest full local baseline refresh completed: 29 rows, 26 passed, 0 failed,
3 blocked. MiMo TP fixed-prior cleanup stalled during a model call; five
MiniMax cleanup trials were blocked by explicit, non-retryable Token Plan quota
exhaustion. The prior 24-passed/3-failed/2-blocked packet and targeted follow-up
reruns remain separate historical evidence. No baseline was promoted. See
docs/status/active/local-eval-baseline-refresh.md.
The 2026-09-28 targeted rerun of all three blocked rows now passes: MiMo TP
fixed-prior 2/2, MiniMax dynamic-routed 3/3, and MiniMax sandbox-skills 3/3.
No Token Plan 2056 response recurred. These checks confirm current provider
availability and remain separate evidence; the historical full packet is not
rewritten or promoted.
The State-First Context Manager implementation is complete for typed
snapshots/checkpoints, pre-call bounded reconstruction, and checkpointed
continuation. Real Grounding DINO MapBuild proof and automated desktop/mobile
operator-console QA now pass; fresh SDK rechecks with MiniMax, Kimi, and MiMo
all completed DINO-as-input successfully. The earlier DINO blocker was only an
unstarted loopback sidecar. MiMo reached 96,350 provider-reported input tokens
against the configured 96,000-token hard limit on an accepted final call, so it
has a residual accounting/headroom caveat but no reproduced context overflow.
Milestone v1.99 remains at Phase 4 partial because the 2026-09-25 focused eval
packet has a Kimi quota-blocked comparison slice. The new local refresh proves
Kimi's fixed-prior route but does not rerun that historical comparison. See
docs/status/active/state-first-context-manager.md and
.planning/phases/04-route-proof-and-rollout/04-LIVE-PROOF.md.
The Opik-only observability migration is complete. Opik 2.2.36 is the sole
supported external backend for the roboclaws-runtime and roboclaws-eval
Projects; local JSON, Markdown, run artifacts, graders, and human promotion
remain canonical. Runtime and eval projection are bounded, loopback-only,
idempotent, privacy-denying, and fail-open. See ADR-0150 and
docs/plans/2026-08-25-opik-only-observability-migration.md.
The production Dashboard is available at http://127.0.0.1:5174/ and through
the explicit trusted-LAN review bind configured by the operator. The example
configuration uses the documentation-only address 192.0.2.60. It links
the full reviewed 65-row Dataset and states the fidelity boundary: 25 rows have
native Experiment/trace drilldown and 40 remain Dataset-only. Opik 2.2.36 keeps
a desktop-width Dashboard canvas on mobile, so narrow screens require
horizontal navigation.
Phoenix and the Eval Harness HTML companion are retired from active code,
deployment, tests, commands, and docs. New terminal harness runs atomically
publish only eval_harness.json and eval_harness.md, then write completion v2
and a fail-open opik_projection.json. Retained output/phoenix/ and
output/opik-poc/ remain inactive historical evidence and were not deleted.
The reviewed multi-scene Skill-delivery comparison remains inconclusive and did
not change the product default or publish a baseline. See
docs/status/active/skill-delivery-multiscene-probe.md and
docs/plans/2026-08-03-agent-skill-delivery-eval.md for the paired evidence.
Eval Evolution Phases 0-4 are complete under
docs/plans/2026-08-04-eval-evolution-agent-sdk.md. Candidate identity,
isolation, sealed holdout, and human-only promotion are enforced; no candidate
was promoted. The blocked-by-default public facade remains
just agent::eval evolve|evolve-promote.
The invalid hybrid candidate at output/eval-harness/20260803T023049Z/ remains
retained as evidence and unpublished. Its checker/eval ownership regression is
fixed: product checker failures now fail closed, done is terminal, and one
canonical completion snapshot is shared across runtime evidence surfaces.
The active product shape is:
surface=household-worldfor no-preset open household goals.surface=household-world preset=map-buildfor Runtime Metric Map evidence.surface=household-world preset=cleanupfor cleanup.surface=planner-prooffor the confidence route.
Current household map/runtime contracts:
- Base Metric Map is the required start-of-run map context.
- Runtime Metric Map owns map-build and observation semantic evidence.
- Runtime Map Prior Snapshot is the downstream prior wrapper.
- Canonical Runtime Map Priors are explicitly promoted, content-addressed, and reused read-only across normal provider consumer matrices.
- Product runtime, smoke helpers, and current tests fail loudly when a required Base Metric Map bundle is missing.
Eval suites are first-class architecture evidence. Deterministic suites are available through:
just agent::eval suite=smoke_regression budget=smoke
just agent::eval suite=open_ended_goals budget=smoke
just agent::eval suite=map_build_quality budget=smoke
just agent::eval suite=map_consumer_no_prior budget=smokeLive eval execution is opt-in with live_execution=run; default non-direct eval
requests record blocked identity/preflight packets instead of launching real
providers.
Keep both full baseline packets and the four follow-up result bundles as separate evidence. Reconsider baseline promotion only through the existing human review process. The historical Kimi cleanup comparison remains a separate State-First Phase 4 gate; no additional state-first implementation repair is currently indicated.
Use the Opik Dashboard for current external review and local JSON/Markdown for canonical decisions. The Eval Harness candidate and Skill-delivery baseline decisions remain unchanged.
- The latest 2026-09-27 local baseline rerun is not passing: three rows are blocked by one MiMo TP model-call stall and MiniMax Token Plan exhaustion. The prior packet's three failed and two blocked rows remain preserved; none of these packets has been promoted.
- State-First Phase 4's historical 2026-09-25 packet has five Kimi cleanup comparison trials blocked by the provider's 5-hour quota. The latest Kimi fixed-prior samples passed, but they do not replace that comparison slice.
- The
20260817T072338Zeval candidate is not publishable because it contains one behavior failure and one blocked trial bundle. - Agibot and B1 injected dependency readiness passes with the existing local SDK, Map 12 bundle, B1 scene, and alignment/navigation proofs. Real-robot movement remains unauthorized and requires a present operator plus the existing localization, run-enablement, and E-stop gates.
- Project orientation:
README.md - Architecture and contracts:
ARCHITECTURE.md - Public command grammar:
just/README.md - Skill-first MCP design:
docs/human/mcp-skills-and-semantic-profiles.md - Local runtime and provider keys:
docs/human/local-runtime.md - Evaluation docs:
docs/human/evaluation.md - Current model/provider notes:
docs/human/model-matrix.md - Human docs index:
docs/human/README.md
Plans:
docs/plans/2026-08-02-household-backend-port-refactor.md,
docs/plans/2026-07-31-refactor-just-command-surface.md,
docs/plans/2026-07-30-aggressive-architecture-migration.md,
docs/plans/2026-07-30-retire-openclaw-and-local-docker-surfaces.md,
docs/plans/2026-07-30-post-cleanup-saturation-refactors.md,
docs/plans/2026-07-28-forward-only-post-review-cleanup.md,
docs/plans/2026-07-27-restore-codex-mimo-responses-cells.md,
docs/plans/2026-07-01-recommended-runtime-map-prior-selection.md,
docs/plans/2026-06-26-map-build-quality-eval-harness.md,
docs/plans/2026-06-20-cross-environment-map-waypoint-source-of-truth.md,
docs/plans/2026-06-18-b1-map12-semantic-and-public-nav-followups.md,
docs/plans/2026-06-17-b1-map12-two-map-alignment-blocker.md,
docs/plans/2026-06-17-sim-map-surface-simplification.md,
docs/plans/2026-06-16-open-ended-eval-matrix-expansion.md,
docs/plans/2026-06-15-non-cleanup-eval-support.md,
docs/plans/2026-06-14-eval-driven-architecture.md, and
docs/plans/2026-06-11-household-map-launch-open-ended-contracts.md.
ADRs:
docs/adr/0140-use-eval-suites-as-first-class-architecture-layer.md,
docs/adr/0136-use-base-metric-map-and-first-class-household-launch-contracts.md,
and docs/adr/0138-use-detector-only-visual-grounding-sidecar.md.
- Agent operating details:
docs/agents/operating-runbook.md - GSD execution state:
.planning/STATE.md - Current GSD phase details: follow the latest phase link in
.planning/STATE.md - Pre-GSD plans:
docs/plans/ - Durable decisions:
docs/adr/ - Shipped history:
docs/retrospectives/ - Concurrent standalone work:
docs/status/active/
- Queued implementation tasks unrelated to the current active focus:
TODOS.md - Scratch ideas and future directions unrelated to the current active focus:
THOUGHTS.md - GitHub issues track externally visible work for
MiaoDX/roboclaws.
The cleanup plan is mechanically archiving only explicitly terminal active capsules; active, blocked, ambiguous, and JSON evidence surfaces remain in place.
Use the staged workflow:
idea -> docs/plans/<slug>.md -> review/autoplan -> GSD plan/execute -> verify -> retrospective
Rules:
STATUS.mdanswers "what is happening now?"docs/plans/owns pre-GSD plans..planning/is GSD-owned execution detail.docs/human/is the human-readable doc set.docs/adr/records durable decisions, not progress.- Root
PLAN.mdis a legacy pointer, not an active plan. TODOS.mdandTHOUGHTS.mdare parked-work surfaces, not current status.- Parallel terminals should use one task-owned file under
docs/status/active/. - At GSD closeout/verify/ship, update this file only if repo-level current focus, latest phase, next action, or blocker changed.