ziros-operator-core

Load and govern the ZirOS operator core to enforce truth separation between repo authority, agents discipline, and Hermes state.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/AnubisQuantumCipher/ziros --skill ziros-operator-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ziros-operator-core
Source: https://github.com/AnubisQuantumCipher/ziros/tree/main/.codex/skills/ziros-operator-core
Command: npx skills add https://github.com/AnubisQuantumCipher/ziros --skill ziros-operator-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Load and govern the ZirOS operator core while preserving the authority split between repo truth, AGENTS discipline, and Hermes posture, and keep local Hermes state classified as non-canonical overlay state.

Core Features & Use Cases

  • Read docs/agent/OPERATOR_CORE.md before treating local memory or prompts as truth.
  • Use live commands and repo truth ahead of local ~/.hermes/** state.
  • Preserve the lane split: strict-proof, operator-managed, support-evidence, external-delegated.
  • Preserve the repo authority split:
    • machine truth for claims
    • AGENTS.md for repo mutation and verification discipline
    • HERMES_CONSTITUTION.md for operator law

Quick Start

Run ziros agent hermes doctor --json to verify the operator core health and readiness.

Frequently Asked Questions about ziros-operator-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce truth separation between repo authority and agent state in DevOps workflows?

Truth separation is enforced by loading the operator core to partition machine repo truth, AGENTS.md discipline, and Hermes constitution law. This governance ensures local Hermes state stays a non-canonical overlay while repository files drive behavior.

What is operator core governance for live agent runtimes and when is it needed?

Operator core governance loads system constitution files and agent guidelines to preserve lane splits like strict-proof and operator-managed. It is needed during live runtimes when Hermes state, AGENTS policies, and repo truth determine behavior, reproducibility, and audits.

How do I verify ZirOS operator core health and readiness before executing commands?

You can verify operator core health by running the command `ziros agent hermes doctor --json`. This checks the system's readiness to preserve lane splits and authority partitions before executing the first commands in a governance workflow.

Why should AGENTS.md and repo truth take precedence over local Hermes state?

AGENTS.md and repo truth take precedence because local `~/.hermes/**` state is classified as a non-canonical overlay. Reading `docs/agent/OPERATOR_CORE.md` ensures that machine truth and repository authority dictate mutation and verification discipline.

Can I preserve lane splits like strict-proof and operator-managed during live audits?

Yes, the operator core preserves lane splits including strict-proof, operator-managed, support-evidence, and external-delegated. This authority partitioning maintains reproducibility and audit integrity across live operator runtimes and governance workflows.