ArghDA M11: studio JSON freeze (reason/0.1) + Groove discovery manifest#39
Merged
Merged
Conversation
Closes the one remaining OPEN v0.1 milestone (Groove service manifest). Two deliverables: ## Studio JSON freeze (reason/0.1) A JSON-contract test in `src/reason/mod.rs` pins the schema arghda-studio / Groove consumers depend on — top-level (`version`/`dag`/`nodes`/`edges`/ `crt_roots`), per-node (`id`/`self_verdict`/`effective`/`verdict_evidence`/ `soundness`/`wired`), per-edge (`from`/`to`/`junct`/`kind`). A rename now breaks a test: bump the version, don't silently edit. ## Groove manifest (`src/groove.rs`, `arghda groove`) Groove is the estate's HTTP service-discovery protocol. `GrooveManifest` (`groove: "0.1"`; capabilities = live backend probes + CLI commands + the frozen `dag/0.1` + `reason/0.1` schema versions). `arghda groove [--output <path>]` emits it to stdout, or writes a `/.well-known/groove` file (creating parent dirs). arghda-core is a CLI, so it *emits* the manifest; serving it over HTTP at `/.well-known/groove` is the host's (PanLL's) job — honest. Backends are probed live, so the manifest reflects what this machine can actually run. ## Verified (ran, not inferred) - `cargo test` → 121 passing, 0 failed (+1 groove unit, +1 reason-contract freeze). - clippy -D warnings, fmt, SPDX clean. - Dogfooded: `arghda groove` → all 6 backends runnable, schemas 0.1; `arghda groove --output /tmp/site/.well-known/groove` wrote the file. - STATE.a2ml: M11 = 100%, and the route-to-mvp "Groove service manifest" milestone = 100% — the v0.1 spec is now closed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012MpYSh6Wy8YMBH2E3qVyT7
hyperpolymath
marked this pull request as ready for review
July 1, 2026 09:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Closes the one remaining open v0.1 milestone (Groove service manifest). Two deliverables:
Studio JSON freeze (
reason/0.1)A JSON-contract test in
src/reason/mod.rspins the schema arghda-studio / Groove consumers depend on — top-level (version/dag/nodes/edges/crt_roots), per-node (id/self_verdict/effective/verdict_evidence/soundness/wired), per-edge (from/to/junct/kind). A rename now breaks a test: bump the version, don't silently edit.Groove manifest (
src/groove.rs,arghda groove)Groove is the estate's HTTP service-discovery protocol.
GrooveManifest(groove: "0.1"; capabilities = live backend probes + CLI commands + the frozendag/0.1+reason/0.1schema versions).arghda groove [--output <path>]emits it to stdout, or writes a/.well-known/groovefile (creating parent dirs).arghda-core is a CLI, so it emits the manifest; serving it over HTTP at
/.well-known/grooveis the host's (PanLL's) job — honest, no embedded HTTP server. Backends are probed live, so the manifest reflects what this machine can actually run.Verified (ran, not inferred)
cargo test→ 121 passing, 0 failed (+1 groove unit, +1 reason-contract freeze).cargo clippy -D warningsclean ·cargo fmt --checkclean ·check-spdx.shOK.arghda groove→ all 6 backends runnable, schemas0.1, commands listed;arghda groove --output /tmp/site/.well-known/groovewrote the file.Milestone status
The v0.1 spec is now closed (Groove was the last open milestone), and STATE records M11 = 100%. The engine-spine deliverable (M0–M7 + M11) is complete bar M7 (Echidna dispatch seam), which is the natural next step. Beyond that: the M3/M4/M6 follow-ons and the heavy-prover tail M8–M10.
Generated by Claude Code