Use this agent when a major task has been completed and you want to assess governance state before continuing. Examples: Context: An agent finished a feature implementation. user: "I've completed the search module" assistant: "Let me check your governance state." After significant work, dispatch the…
Use when an agent is participating in a UNITARES dialectic session — paused and needs to submit a thesis, reviewing another agent's thesis, or synthesizing conditions for resolution. Covers structured argumentation and convergence.
Use when an agent needs to understand UNITARES governance concepts — EISV state vectors, basins, policy actions, coherence, calibration. Reference material for interpreting governance metrics as proprioceptive state estimation, not outcome judgment.
Use when an agent is interacting with UNITARES governance for the first time, needs to onboard, check in, or recover from a pause/reject verdict. Covers the full agent lifecycle from session start through check-ins to recovery.
Use when an agent needs to search the shared knowledge graph, contribute a discovery, or update existing entries. Covers search, tagging, discovery types, and status lifecycle.
Use when adding, editing, or reviewing sections on the unitares dashboard (dashboard/redesign/). Captures the redesign's conventions: the section-module pattern (window.X = { load }), the live-or-snapshot data seam, theme-aware charts via design tokens, the app.html wiring (nav / pane / lazyLoad / RELOAD / retheme)…
Compatibility umbrella skill for UNITARES, accountability infrastructure for long-running AI agents. Use this as the entrypoint when you need the overall model and route into the split governance skills.
MCP server "governance-mcp" as configured in cirwel/unitares. Runs locally from the governance-mcp Python package.
★not rated 5 2d agoA
tokens not measured
originalApache-2.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: