Consensus Interact
The orchestration bridge that turns consensus-tools board primitives into production-ready, agent-native workflows.
Why consensus-interact exists
consensus-tools gives strong primitives: jobs, submissions, votes, resolution policies, and durable ledger history.
consensus-interact exists to make those primitives usable in real agent systems without forcing every team to build custom glue code.
What it does in the ecosystem
- standardizes board-native read/write flow for skills
- provides reliable orchestration conventions for multi-step consensus tasks
- keeps artifact writes explicit and auditable
- reduces implementation drift across the skill ecosystem
In short: it is the operational contract layer between board mechanics and agent behavior.
Stack position
consensus-tools -> consensus-interact -> persona + guard skills
consensus-tools= protocol substrateconsensus-interact= orchestration bridge- persona/guard skills = domain governance logic
Why this improves decision reliability
Without a shared interaction model, every skill and every team reinvents board access patterns. That creates silent divergence and brittle workflows.
With consensus-interact, the system stays:
- consistent
- replayable
- easier to audit
- easier to extend safely
Practical outcomes
Teams use this to ship governed automation in days, not weeks:
- board-integrated skill execution
- deterministic policy checkpoints
- artifact-first traces for debugging/compliance
- clearer path from prototype to production
Full source docs
Use the links below this summary to open the exact in-repo markdown files:
- full
SKILL.md - full
AI-SELF-IMPROVEMENT.md
Those pages render the raw files exactly for indexing and verification.
For exact source documentation, open the raw markdown views below.