kybernetes AGENTS.md

Kybernetes - Agent Instructions

Kybernetes is an open-source steering layer for agentic work of any kind — coding, marketing campaigns, cold outreach, research, operations, or anything else an agent can run. Keep repository guidance generic, portable, and independent from any maintainer's private workspace.

Repository Shape

skills/
  kybernetes-loop-governor/  # canonical controller, `kybernetes:loop-governor`
  kybernetes-loop-architect/  # advisory execution-contract design
  kybernetes-loop-closeout/  # checkpoint, handoff, and retirement
  kybernetes-verify-run/  # independent rejection-capable verification
  kybernetes-capture-learning/  # evidence-gated constraint proposals
docs/
  architecture/              # runtime and boundary design
  product/                   # product model and non-goals
examples/                    # durable example control records
tests/
  pressure-scenarios/        # behavioral pressure scenarios for skill changes

Public Boundary

• Public defaults must work for people who do not know the maintainer's private projects, vaults, or workflows.
• Do not add private workspace content, customer context, secrets, credentials, internal URLs, or production data.
• Do not make any personal knowledge base, issue tracker, chat service, or project-management tool the default persistence layer.
• Runtime-specific assumptions belong in runtime binding references, not in generic loop-governor semantics.
• New installable skills need pressure-scenario evidence before creating a SKILL.md; planned skills stay in docs/architecture/planned-skills.md.
• Committed .kybernetes/ and .agent-runs/ live-run artifacts are out of bounds unless they are intentionally promoted examples under examples/ or tests.

Working Rules

• Read PUBLIC_BOUNDARY.md before changes that could affect public/private scope.
• Read CONTRIBUTING.md before changing skill behavior.
• For skill changes, update or add a pressure scenario in tests/pressure-scenarios/, show the failure or gap, then change the smallest relevant skill text.
• Keep skills/kybernetes-loop-governor/SKILL.md focused on operational instructions. Put deeper runtime details in references/.
• Do not add placeholder folders under skills/; every folder there must contain a real SKILL.md.
• Preserve the V1 control contract: kybernetes:loop-governor is the sole canonical lifecycle controller. Pressure-backed helper skills may inspect state and return owned outputs, but they cannot mutate parent canonical state or accept completion.
• Before proposing a public merge, classify the change under docs/releases/evidence-gated-release-policy.md. Significant or unknown behavioral changes require a preregistered private evaluation and signed accepted attestation. Minor documentation, maintenance, security, or governance changes require an explicit signed exemption.
• Never copy private evaluation contracts, fixtures, graders, transcripts, credentials, repository identities, or personal paths into this repository. Public release attestations contain only the safe allowlisted fields.
• The evaluation runner and evidence reviewer must be different identities. Agents may prepare evidence but cannot self-review or sign their own run.