Knowledge Vault

Ops-Core

2 min read

Overview

Ops-core is the governance layer of the Aloysius Productions development environment — the single source of authority for standards, zone rules, compliance requirements, and monitoring definitions. It is the most protected zone in the ecosystem: all other zones operate under its authority, and changes to ops-core require explicit approval rather than autonomous modification. The core mandate is “comply or escalate — never ignore,” making ops-core a hard constraint rather than a soft guideline. Every repo that enters production (apps/) must pass an ops-core compliance checklist before it ships.

Key Concepts

  • Zone Map — The AP ecosystem is divided into six zones: Governance (ops-core/), Production (apps/), Lab (lab/), Knowledge (library/), Infrastructure (infra/), and Staging (staging/). Each zone has defined write access and compliance burden.
  • Staging Gate — All new repos start in staging/. Graduation to apps/ requires passing the compliance checklist. No exceptions.
  • Compliance Checklist — Every apps/ repo must have .management/ files (status, knowledge, resources), GitHub configuration (PR template, CODEOWNERS, security workflow), and AI tooling configuration (CLAUDE.md, copilot-instructions.md).
  • Archive Protocol — Decommissioning a repo requires a specific 7-step sequence: ship-log entry, directory deletion, MEMORY.md update, nested copy cleanup, compliance tooling verification, Linear ticket closure, and GitHub Actions disablement.
  • Port Registry — Port allocations are managed via ops-core/shared-resources/ship-log/ports.yaml and the sea-captain CLI. All port assignments must be registered before use.
  • Quality Gates — QG-1 covers code quality (error handling, security, test coverage ≥80%, no hardcoded secrets). QG-2 covers output quality (completeness, specificity, evidence, actionability). Both gates are mandatory for their respective work types.

Graph View

Backlinks