Skip to content

Adopt the zeo.yml canon v2.3 - #4

Open
matorclawson wants to merge 2 commits into
mainfrom
principal/zeo-canon-v2.3-20260925
Open

matorclawson wants to merge 2 commits into
mainfrom
principal/zeo-canon-v2.3-20260925

Conversation

@matorclawson

Copy link
Copy Markdown
Contributor

Adopts the zeo.yml canon v2.3, which the elders issued (ruling r2 on ZEO-RT-SOW-41).

  • Byte-identical in all five repos that carry zeo.yml (sovereign-agent, sovereign-agent-resources, ffmpeg-zeo, homework-pub-booking, zeocore). sha256 9d45eba3329d05c4693009c68574cdbe36810cd7b00f759eb6ca9c96a799d762.

  • What changes from v2.2:

    • a top-level permissions: contents: read;
    • the three actions pinned to full commit SHAs.

    Nothing else changes: the job names zeo and zeo-certify (required checks), the steps, zero-employee==0.12.0, the timeouts and concurrency all stay. Repos on v1 or a drifted v2.2 move to v2.3 in full.

  • Pins, read live from each tag on 2026-09-25 at 13:38Z, all matching what SOW-41 recorded:

    • actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 (v7)
    • astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86 (v5)
    • actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff (v5)
  • Checked with zeo check actions: v2.3 meets all five R-36a conditions.

A pin never moves without a PR the operator approves. Merging is the operator's act (auto-merge welcome).

🤖 Generated with Claude Code

The elders adopted canon v2.3 (ruling r2 on ZEO-RT-SOW-41). It adds a
top-level read-only token and pins the three actions to full commit
SHAs, read live from their tags on 2026-09-25. Byte-identical across
the five repos that carry zeo.yml (sha256 9d45eba3329d05c4693009c68574cdbe36810cd7b00f759eb6ca9c96a799d762).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants