The Agents Council

FREE REQUIRED RUNTIME — github.com/ercoledevs/the-council-runtime

Install the free macOS/Linux companion once. No Rust compiler, GitHub account or source access is required. The skill purchase covers the workflows; the runtime is freely downloadable by everyone.

The Council gives your coding agent a complete path from a promising idea to a reviewed decision and verified implementation.

Forge brings together five specialized creators to shape a buildable proposal. It preserves constraints, checks numerical convergence, records each round and targets unresolved divergence. Council challenges the proposal through architecture, reliability, security, product, contrarian and performance perspectives, with anonymous peer review, accuracy ceilings and visible dissent. Mind connects creation and judgment, then hands the unchanged approved scope to Hyper when implementation is authorized.

Hyper uses the smallest justified execution plan: bounded read-only investigation, one implementation writer and fresh independent falsification when required. Every required check stays visible as PASS, FAIL or UNKNOWN. A blocker cannot disappear inside a high average score.

Tune seven named roles with Alters while preserving evidence and safety requirements. Add Leonardo for a dedicated UX critique and Bob for actual browser scenarios. Bob never votes; missing browser evidence remains unknown.

The local Rust core provides deterministic scoring, persistent Forge rounds, scope and source checks, estimates, profiles, statistics and private history. Its Decision Runtime projects legacy evidence into typed Cells and a frontier view, compares their semantics, plans advisory impact, applies append-only patches and supports replay, explicit recovery, rollback and retention. It never changes the Council verdict or dispatches agents on its own.

Designed for Codex, Claude Code and Cursor, using the host's models and tools. The runtime targets macOS and Linux and is required for the complete feature set. Install it separately from the supplied companion source or a creator-provided release. No extra model-provider key is required by The Council. Host model and tool usage still consumes your existing allowance.

Use it for consequential architecture decisions, complex changes, reusable skills, frontend interactions and ideas that need a disciplined route into tested code. Ordinary small edits can stay small. Your agent thinks. Rust checks the contract.

Key features

• Complete named workflows: Forge, Council, Mind, Hyper, Alters, Leonardo/Bob and Decision Runtime in one progressively loaded skill.
• Five-creator Forge: bounded rounds, separate synthesis, alignment/spread gates, preserved dissent and a three-round ceiling.
• Evidence-led review: six core lenses, a dedicated skill-review panel, risk-aware routing and the original five-dimension Council rubric.
• Scope-bound implementation: explicit handoffs, source fingerprints, one writer and fresh verification when required; verified edits and deletions are supported.
• Practical frontend gates: UX dissent, exact browser cases, observable interactions, saved artifact digests and zero Bob votes.
• Local analytics: transparent estimates, optional sourced credit rates, consented history calibration, dashboards and path-only audit bundles.
• Recoverable shadow state: private immutable generations, stale-write protection, typed patches, frontier comparison, replay and explicit recovery/retention.
• Legacy evidence import: preserve original session bytes, historical prompts and browser evidence while creating a separate native session.

Requirements and compatibility

The host must load the entrypoint and all required supporting references, expose a terminal for the Rust companion and provide the target project's tools. Independent review requires isolated agents; persona labels alone are insufficient. The host concurrency limit determines wave size. Required cold verification blocks completion when isolation is unavailable. Browser acceptance requires actual browser tools and a runnable target.

The full feature set requires the-council 0.2 or later on macOS/Linux. The companion source is included separately in this creator kit; a stable Rust/Cargo toolchain builds it. The first build downloads pinned dependencies. The Agensi upload itself contains text instructions and examples, with no native executable. Agensi's reference loader and the creator's permitted companion-delivery channel must both be checked before selling the full workflow.

Codex, Claude Code and Cursor are intended hosts. Local format/CLI validation is distinct from a live test in each product version or Agensi marketplace approval. See the release verification record for executed tests. Token estimates are local heuristics, not billing telemetry or account limits.

Example prompts

1. “Use The Council Forge to design a local job queue. Keep the API small, bound memory, and make rollback explicit.”
2. “Use The Council to review this migration for data loss, privacy, operational failure and rollback. Preserve every blocker and dissent.”
3. “Use The Council Mind to shape this idea, judge it and implement the unchanged scope I authorize once its gates pass.”
4. “Use The Council Hyper to fix this concurrency defect. Keep one writer, run the regression and obtain a fresh verifier.”
5. “Use The Council with Leonardo and Bob for this modal flow. Verify keyboard focus, background interception, Escape and mobile controls.”
6. “Preview an Ada alter focused on Rust service boundaries. Keep all Council gates intact; show the compiled tuning before saving.”
7. “Project this completed session into Decision Runtime, compare the frontier representation, and show the advisory impact of this typed patch.”

Expected output

Council returns build, revise or stop, with confidence, capability limits, evidence-backed blockers, refinements, dissent and verification. Forge returns a proposal and explicit convergence result. Mind separates creative dissent, review judgment and implementation evidence. Hyper completion includes acceptance/check results, falsification, rollback and residual risks. Rust validates supplied records; it does not authenticate that the host executed a command or obtained human consent.