Repository navigation
Conversation
Adds the agent-team coordination layer on top of the existing pulsing-forge tool runtime (which serves a single agent): - pulsing-forge-core: gates, closure semantics, Orchestrator trait with six built-ins (relay/pipeline/debate/saboteur/broadcast/review); 29 tests drawn from a 16-entry agent-team failure taxonomy. - pulsing-forge-hub: TideHub — per-agent mailboxes, exactly-once journaled ledger, MCP control port (pulsing_send / pulsing_broadcast / pulsing_drain_mail / pulsing_health / pulsing_recall), fan-in debounced shop scheduler, forced closure; 10 tests. - pulsing-forge-runner: forge run <scenario.toml>, forge attach MCP bridge, swimlane dashboard; deterministic + sleep-benchmark + codex (live LLM) adapters. examples/forge/ ships six scenarios plus a sanitized Responses-to-Chat proxy for live-LLM runs; docs/forge/orchestration.md positions the tier (agents hosted on the pulsing-forge runtime participate via the four MCP tools — zero runtime modifications). Verified on this branch: cargo build/test green (39 tests) and the deterministic leak-review scenario completes a full closed loop.
This branch has not been deployed
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
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 this adds
The existing
pulsing-forgecrate is the per-agent tool runtime (codex-compatible sandbox/handlers, Python bindings). This PR adds the missing team coordination tier on top of it — three new workspace crates:pulsing-forge-coreOrchestratortrait + six built-ins (relay / pipeline / debate / saboteur / broadcast / review). 29 tests drawn from a 16-entry agent-team failure taxonomy (docs/forge/failure-taxonomy.md)pulsing-forge-hubpulsing_send / pulsing_broadcast / pulsing_drain_mail / pulsing_health / pulsing_recall, fan-in-debounced scheduler, forced closure. 10 testspulsing-forge-runnerforge run <scenario.toml>one-command scenarios,forge attachMCP stdio bridge, swimlane dashboard; deterministic / sleep-benchmark / codex (live-LLM) adaptersAny MCP-capable agent runtime joins a team with zero modifications — the whole agent-side contract is those four tools. Agents hosted on the existing pulsing-forge runtime call the same tools.
Related: #79 prototypes actor-mailbox collaboration via MCP; this PR is the productionized mailbox/orchestrator layer in that direction, hardened by 100-scenario testing and fleet benchmarks (10 sandboxes × 50 agents, 38/40 closed loops, real-LLM decision-making).
Verified on this branch
cargo build/cargo test -p pulsing-forge-core -p pulsing-forge-hub: 39/39 greenforge run examples/forge/leak-review.tomlcompletes a full closed loop (12 turns, 21 letters, dual-channel closure)Contents
crates/pulsing-forge-{core,hub,runner}— Rust sources, unit tests, scenario schemaexamples/forge/— six runnable scenarios + a sanitized Responses-to-Chat proxy for live-LLM runs (no endpoints or credentials embedded)docs/forge/— failure taxonomy, scenario schema, ledger format, adapters, design notes (orchestration.mdpositions the tier; mkdocs nav wiring left to maintainers)Notes for reviewers
-hub(mailbox hub) and-runner(scenario CLI) deliberately avoidruntime, which the existingpulsing-forgecrate owns conceptually.pulsing-actortransports for multi-node mailboxes is a natural follow-up — trait boundaries were drawn to allow it.