Skip to content

deed: add hypatia_chora.deed with the ADR-009 egress declarations - #1011

Merged
hyperpolymath merged 3 commits into
mainfrom
claude/hypatia-deed
Nov 5, 2026
Merged

hyperpolymath merged 3 commits into
mainfrom
claude/hypatia-deed

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

The last step of the RE001 / governance-gate work (#966, #967, #968, #973, #974). The order was eliminate the credential, then harden the job, then declare what remains. This PR is the declaring step: hypatia's first repo deed, following one-deed-per-repo (standards#837) and modelled on standards_chora.deed.

Translated from .machine_readable/CLADE.a2ml under clade-to-repo-deed.adoc:

  • (identity), (clade), (forges), (lineage) and (status).
  • :repo-uuid is the ADR-008 v8 form re-derived from the name (spec §5 P-1), not the retired v5 that CLADE holds.
  • CLADE's [identity] name and project aren't in the mapping table, and both repeat canonical-name, so they aren't emitted.

Not translated, and named in the header. These records stay live, as standards' are:

  • AGENTIC (max-automation, sprint-patterns, workflow-pin-detection), NEUROSYM (proof-integration) and PLAYBOOK (crg-promotion-criteria) carry sections their mapping table doesn't list, so a2ml_to_deed.py refuses them rather than guess.
  • META and ECOSYSTEM aren't translated either.
  • STATE waits on state-v1-decision.adoc.

(egress …): all 10 jobs on main that read a secret other than GITHUB_TOKEN.

  • Each uses :enforcement harden-runner-block.
  • Each :endpoints list is that job's harden-runner allowed-endpoints, byte for byte, so a later check can test the two for equality.
  • The one exception is push-email-notify's mail host. It is itself a secret, so it's written secret:SMTP_HOST.
workflow jobs secret
ci-health-sweep sweep HYPATIA_DISPATCH_PAT
estate-rescan preflight, publish HYPATIA_DISPATCH_PAT
hypatia-remediation-sweep sweep HYPATIA_DISPATCH_PAT
inbox-steward-intake record-report, analyze-patterns, update-ruleset, dispatch-to-farm FARM_PAT
push-email-notify notify SMTP_*
roadmap-sync sync App private key

How has this been verified?

  • Linters, from standards main e0645391: bun deed_lint.js OK, and bun deed_lint.js --egress OK with 10 jobs. These are the checks standards' deed-conformance.yml runs. deed_lint.py rejects the #u8 form, but it rejects standards_chora.deed with the same error, and CI doesn't run it.
  • Hypatia's own reader and rule, compiled from main: Hypatia.Deed.egress_declarations/1 reads all 10 entries. RE001 reports 0, with no drift, stale, enforcement or computed-key findings.
  • Negative control: a wrong secret in one entry gives exactly one drift finding, so the comparison is running.
  • Differential self-scan of all 15 rule modules over main and this branch: no content rule flags the new file.

Notes for reviewers

  • The deed changes no workflow behaviour. Harden-runner already clears RE001, and the declarations add attestation on top.
  • hypatia-remediation-sweep, ci-health-sweep and estate-rescan are still red on main. HYPATIA_DISPATCH_PAT returns 401 (reported 10-27), and there were startup failures on 11-04 while the lock was being repaired. Neither is caused by this PR.

Generated by Claude Code

The repo deed of hypatia (one deed per repo, standards#837):

- (identity) (clade) (forges) (lineage) (status), translated field for
  field from .machine_readable/CLADE.a2ml under clade-to-repo-deed.adoc;
- :repo-uuid is the ADR-008 v8 derived from the name (spec P-1), not the
  retired v5 CLADE still holds;
- CLADE's [identity] name and project are not in the mapping table. Both
  repeat canonical-name, so they are not emitted.

AGENTIC, NEUROSYM and PLAYBOOK carry sections their mapping table does not
list, so a2ml_to_deed.py refuses them. META, ECOSYSTEM and STATE are not
translated either. As in standards_chora.deed, they stay live and
untranslated, and the header names each one and why.

(egress ...) declares the 10 jobs that read a secret other than
GITHUB_TOKEN. Each uses :enforcement harden-runner-block, and each
:endpoints list is the job's harden-runner allowed-endpoints, byte for byte.
The exception is push-email-notify's mail host, which is a secret and so is
written secret:SMTP_HOST.

Checked against standards main (e0645391): deed_lint.js OK, and
deed_lint.js --egress OK with 10 jobs. Hypatia.Deed reads all 10, and RE001
reports 0. A negative control (a wrong secret in one entry) gives one drift
finding, so the comparison is live.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J4QvDfStHgMdZGTeqaBgM1
@coderabbitai

coderabbitai Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 48 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 46d7f21f-b153-4a4f-9b3e-7e0a46ce12ff
Commits

Reviewing files that changed from the base of the PR and between 15bc0f0 and 2c4c343.

Files selected for processing: 1

  • hypatia_chora.deed
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 5, 2026 00:34
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-05T00:44:55.934614Z 2c4c343 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@sonarqubecloud

sonarqubecloud Bot commented Nov 5, 2026

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath merged commit 2101b14 into main Nov 5, 2026
74 checks passed
@hyperpolymath
hyperpolymath deleted the claude/hypatia-deed branch November 5, 2026 00:47
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