spec: the developer council (2 to 5 heterogeneous models on one OpenSpec change) - #5
Merged
Conversation
added 2 commits
July 23, 2026 07:54
…pec change) The approved design for an optional produce-loop developer that implements an OpenSpec change with 2 to 5 diverse models that propose, cross-critique, synthesize and verify against the spec's tests, and always return one result. Spec-and-test-grounded (not consensus), fixed proposer + lead-synthesizer roles, both provider modes, reuses the test agents for verify, records the council's reasoning to the audit log so the system learns from it, and runtime-neutral so it works in every operator kit. Non-normative: the council is a developer; review and test stay independent, and it never merges or reviews itself. This is the spec-driven first step; the implementation follows against it. Agent: claude-code (Opus 4.8) Signed-off-by: Christoph <awchristoph@gmail.com>
Expand the acceptance criteria so "delivered in every operator kit" is testable, not implied: the orchestrator ships with a self-test, the Goose kit wires it and init copies it (completeness asserted), the bring-your-own runtime contract is documented in agents/runtime.md, and every reference surface documents it. Agent: claude-code (Opus 4.8) Signed-off-by: Christoph <awchristoph@gmail.com>
|
ASDD review - advisory (recommendation:
Dry-run: the ASDD review pipeline ran but no agent runtime is wired (no runtime key (set ASDD_RUNTIME_TOKEN, or ASDD_RUNTIME_TOKEN__REVIEWER for this role)). Diff stats only. Security scan (deterministic + SAST): no new issues. Impact scan: 1 finding(s), 0 block. CODE - skippedNo findings. SECURITY - okNo findings. SPEC - skippedNo findings. QUALITY - skippedNo findings. IMPACT - ok
Generated by the ASDD advisory review. Mode: |
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
1 participant
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.
Disclosure (required: ASDD 1)
Change scope (required: ASDD framework-impact lens)
What this does
Adds the approved spec for the developer council: an optional produce-loop developer that implements an OpenSpec change with 2 to 5 heterogeneous models that propose, cross-critique, synthesize and verify against the spec's tests, and always return one result to the user.
Key decisions, locked with the maintainer:
test-author/test-runneragents on distinct models).asdd dev-council), so it works in every operator kit (Goose + bring-your-own).corpusandknowledgederive from it and the system learns from the council's process over time.This is the spec-driven first step. The implementation follows as its own PR against this spec.
Spec:
docs/specs/developer-council.md.