You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Records the outcome of investigating the last open roadmap item, the real
Echidna orchestrator HTTP client. Verdict: BLOCKED, not an effort gap — leave
the honest Unavailable stub as-is.
To build the client honestly you need a confirmed HTTP contract to dogfood
against, and (in-scope investigation):
- `src/dispatch.rs` itself states the orchestrator API is "unconfirmed (it may
not exist yet)";
- `ECOSYSTEM.a2ml` describes echidna only at a high level (orchestrator, Unified
Zig API, port 8090) with no endpoints / request / response schema — no
contract;
- the `echidna` repo is outside this session's GitHub access scope, so it can't
be read to discover an API (and searching outside scope is disallowed).
Writing a client would therefore mean inventing an unverifiable contract, which
the honesty mandate and dispatch.rs's own honest-stub discipline forbid. No code
fabricated. Unblock condition: a published Echidna API (endpoints + schemas) and
a reachable instance to dogfood; then wire `Dispatch::run` behind a cargo
feature (no backend/caller churn).
This is the roadmap terminus: all tractable items are done (engine spine
M0–M11, the M3/M4/M6 refinements, and the heavy tail M8 Coq / M9 Isabelle /
M10 Mizar — nine backends, every one dogfooded against its real tool). M7's
client is the sole residual and is externally blocked.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012MpYSh6Wy8YMBH2E3qVyT7
"M10 (Mizar): DONE (85%) — turned out to be a REAL verify, not detect-only: static i386 verifier runs on x86_64; provisioned + adapter (accom+verifier+.err) + dogfooded (proven/error). HEAVY TAIL M8-M10 COMPLETE. Remaining: local-article prel export.",
416
-
"Only M7 remains: the real Echidna HTTP client (feature-gated) — but FIRST confirm Echidna's API actually exists (search estate/GitHub for an echidna repo with a documented HTTP API); if it does not, keep the honest Unavailable stub and say so plainly rather than invent a contract. After M7 the roadmap's tractable items are exhausted.",
435
+
"M7 client INVESTIGATED 2026-07-01 → BLOCKED (stub stays): no confirmed Echidna HTTP contract exists (dispatch.rs says API unconfirmed; ECOSYSTEM.a2ml gives no endpoints/schema; the echidna repo is out of this session's access scope). Building a client would mean inventing an unverifiable contract — forbidden. Unblock: a published Echidna API + a reachable instance to dogfood; then wire Dispatch::run behind a cargo feature. ROADMAP TERMINUS — all tractable items done; M7's client is the sole residual, externally blocked.",
436
+
"Deeper cuts deliberately scoped out (available if the owner wants them): Coq _CoqProject logical-path resolution + dependency-ordered compilation; Mizar local-article prel export (miz2prel); Isabelle session-qualified imports + multi-session builds; and the arghda-studio visual layer that consumes the frozen reason/0.1 JSON.",
0 commit comments