UNITARES Governance

This umbrella skill exists for backward compatibility and as a stable top-level entrypoint into the UNITARES framework.

Core Model

UNITARES evaluates agent state with the EISV model:

• E: effective energy / execution drive
• I: integrity / coherence of alignment
• S: entropy / disorder / instability
• V: valence (signed E-I imbalance)

Agents typically start with start_session(force_new=true) and continue with sync_state() as their main check-in loop. These are the primary workflow tools; raw implementation tools such as onboard(...) and process_agent_update(...) remain available for compatibility. The full raw payload remains available under raw_governance.

Session Continuity

Use start_session(force_new=true) to register a fresh process identity. If the process is continuing prior work, declare that with parent_agent_id=<prior uuid> and spawn_reason="new_session". Use raw onboard(...) instead for older servers or raw response shape.

Use identity(agent_uuid=..., continuity_token=..., resume=true) only when rebinding the same live owner to an existing UUID. The continuity_token is short-lived ownership proof for anti-hijack gates, not indefinite cross-process continuity. A bare onboard() or bare identity(agent_uuid=..., resume=true) can rely on weak evidence or an unsigned UUID claim; do not teach those as normal flow.

In-process tool calls thread the response's client_session_id through subsequent invocations to maintain transport continuity within a single process. client_session_id is in-session continuity only — weak across processes, not identity proof on its own.

Use sync_state() after meaningful work to record progress, complexity, and confidence, then read the returned governance verdict. Use raw process_agent_update() when you need the raw handler response.

Knowledge Layer

The governance system is coupled to the knowledge graph. Agents should search existing knowledge before duplicating work, and contribute discoveries, questions, and answers as they learn.

Split Skills

The old monolithic skill was split into focused skills:

• skills/governance-lifecycle/SKILL.md for onboarding, check-ins, and recovery
• skills/governance-fundamentals/SKILL.md for EISV, basins, coherence, and verdicts
• skills/knowledge-graph/SKILL.md for knowledge graph search and contribution
• skills/dialectic-reasoning/SKILL.md for thesis/antithesis/synthesis workflows
• skills/discord-bridge/SKILL.md for the Discord governance bridge

If you need the full mental model, start here. If you know the task shape, prefer the focused skill directly.