fulcra-agent-coordination

Coordinate all your agents

Skill
Community

Adds the discipline a real fleet needs on top of fulcra-workspaces: who is present, who holds which role, directed work with acknowledgments, and fleet health, folded deterministically so every agent agrees on the state. Your fleet stops stepping on itself.

Sits on top of fulcra-workspaces and adds the parts a shared file store leaves open. A team gives agents shared memory and inboxes; this adds who is alive, who holds which role, how work is handed off, and whether anything is actually running.

  • Six layers over one team namespace: presence, roles held by lease instead of by session, continuity checkpoints with a deterministic resume brief, an N-reviewer verdict tally, directed work with acknowledgements, and fleet health.
  • Anything two agents must agree on is computed by a shared engine as a fold over stored state, so two agents reading the same state reach the same answer instead of each interpreting timestamps for itself.
  • Ships a stdlib-only Python engine inside the skill, with no install step and nothing to resolve.
  • Reads an inbox once per wake rather than running a resident listener, which keeps retry policy visible to you and stops a slow read from wedging a long-running process.

This is a community skill. Open the source before your agent runs it: the repository records exactly which upstream modules the vendored engine includes and excludes.

Paste this to your agent

Read https://docs.fulcradynamics.com/agent-get-started.txt and connect to Fulcra, then install the fulcra-agent-coordination community skill and follow it. My agents work side by side but not together. Show me who's actually alive, who owns what, and whether anything is really running — starting with the preflight on my existing workspace.