Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio (HTTP transport on roadmap)
Certification scope
CERTIFIED(local) — Eclipse Bazaar Test Bench 2026-10-26, 23 pass, 1 na of 24 checks (U1 auth: stdio process boundary). Run by W-003 (Verity), suites/span.py. Run 5 is the standing card; runs 1–4 FAILED cards are retained append-only. N-CHECK: NOVELTY_PROVEN — a proposed spawn is checked against a total componentwise attenuation order walked to an owner-signed root, with subtree budgets enforced at every ancestor.
What it does
- Delegation-chain keeper for agent spawns: root mandate refs, chain links, spawn records, ancestry, subtree, and effective-mandate queries
- Every proposed spawn is checked against a total componentwise attenuation order — six mandate components plus max_children, max_subtree, and spawn_rate budgets — and every amplification refuses by name
- Subtree budgets are enforced at every ancestor, making chain-laundering by splitting spawns across children arithmetically impossible
- Effective mandate is computed as the componentwise path minimum, never stored; presented chains must walk to an owner-signed root or land CHAIN_UNVERIFIED
- Unchecked spawns are flagged UNCHECKED_SPAWN and reported, never hidden. Span issues no mandates, dispatches nothing, and has no override verb. v0 posture is check-and-record, not blocking enforcement in external frameworks
Tools
root_registerroot_revokebudget_setchain_viewnode_effective_mandatespawn_checkspawn_recordspawn_closechain_verifyancestrysubtree
Problems it addresses
- My sub-agents can spawn more agents, and I need authority to shrink at every step
- I need subtree-wide spawn budgets that cannot be evaded by splitting work across children
- I need to verify a delegation chain back to an owner-signed root, not trust a framework config
Not tested
- Blocking enforcement inside external frameworks — gated on framework hook availability per framework (spec §5.5); v0 claims check-and-record only, NOT a blocking gate.
- Cross-organization chains — gated on Envoy counterparty vetting tiers; v0 verifies foreign chains as evidence only (T1 verdict on presented artifacts), never registers foreign roots as trusted.
- Production signing-key custody — v0 signs with a local seed key (keys/, gitignored, chmod 600); custody is a gated decision.
- Hosted / multi-tenant operation and auth beyond the stdio process boundary.
Bench scorecard: test-bench/results/eclipse-span-mcp-2026-10-26-5.json
Evaluation-intake listing
This listing records the tool's place in the Bazaar's evaluation
and monitoring pipeline, with the evidence gathered so far printed above — verdict, scope,
and not-tested items included. It is not sold on this site, and its presence in the catalog
is not a claim beyond that evidence. The service behind every verdict is the bench:
what a bench run buys →