# Evozeus Registry Release

> Use when working on EvoZeus registry pointers, default official factors, official release references, manifest compatibility, checksum, SBOM, attestation, deprecation, or yank behavior.

- Skill: `metainflow/evozeus-registry-release` (Agent Skill)
- Install (CLI): `npx get-skill add metainflow/evozeus-registry-release`
- Raw SKILL.md: https://api.skillmd.com/api/skills/metainflow/evozeus-registry-release/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: metainflow (https://skillmd.com/u/metainflow)
- Updated: 2026-11-16
- Page: https://skillmd.com/skills/metainflow/evozeus-registry-release

---


# EvoZeus Registry Release

The main Repo owns built-in Factor bodies and registry pointers. Runtime resolves built-in Factors from the same product Commit and verifies independent third-party releases through immutable metadata.

## Registry Consumption Flow

```text
EvoZeus registry pointer
  -> official release manifest
  -> checksum
  -> SBOM / attestation
  -> selected pack
  -> runtime lockfile
```

## Main Repo Responsibilities

- define registry schema and compatibility rules
- point to allowlisted official releases
- define default official factor set
- track channel, version pinning, review state, deprecation, and yank behavior
- route built-in pack body changes to `packs/session-signal/`

## Default Official Factors

Default factors must be explicit, not silent:

- default means recommended, not automatically enabled
- runtime must show what will be installed or enabled
- runtime must verify manifest, checksum, SBOM / attestation, compatibility, and review state
- missing release metadata blocks enablement

## Boundaries

- Keep built-in pack bodies under `packs/session-signal/`.
- Do not reference lab moving branches.
- Do not invent manifests, checksums, or reviewed status.
- Do not let runtime bypass the registry pointer.

