Build a polyrhythmic reasoning graph
Use this skill for a non-high-risk task that benefits from explicit problem-mode and user-mode tracks.
Process
- Choose strict-lcm only when exact 4/5 alignment at activation 20 is the intended behavior. Choose adaptive when evidence-backed early convergence is allowed under the hard ceiling.
- Use one of the approved domains: technical troubleshooting, conceptual explanation, practical planning, or theoretical comparison.
- Keep user state unknown unless a user-stated evidence item supports a declared non-sensitive state.
- Choose agent-only or agent-plus-read-only-tool. Never widen the latter past filesystem:read and sideEffectMode: none.
- Build through lib/polyrhythmic-reasoning.mjs, validate the returned FlowGraph, and execute through the normal composition adapter.
- Preserve conflicts and failed/skipped beats in typed state and events. Publish only the final synthesis.
Do not use the generic pattern for healthcare, financial advice, or another high-risk domain. Do not claim that the topology improves quality or efficiency without reproducible benchmark evidence.
See docs/polyrhythmic-reasoning.md and the four files under examples/.