Skip to content

docs(governance): adopt repository trust policy - #16

Merged
szmyty merged 1 commit into
mainfrom
feat/organization-trust-policy
Aug 21, 2026
Merged

docs(governance): adopt repository trust policy#16
szmyty merged 1 commit into
mainfrom
feat/organization-trust-policy

Conversation

@szmyty

@szmyty szmyty commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Summary

Adopt the organization-facing trust-policy contract required by #9 while preserving the agreed policy-first dependency direction.

This pull request:

  • selects DCO 1.1 for human contribution attestation;
  • defines correction, bot-exemption, fail-closed enforcement, and time-bounded exception behavior;
  • defines cryptographic expectations for commits, tags, releases, containers, packages, and published document bundles;
  • introduces four output-based repository classes (R0R3);
  • specifies digest-bound provenance and artifact-specific SBOM requirements by class;
  • defines explicit legacy-unclassified, planned, piloting, enforcing, conformant, and retired migration states;
  • prevents organization checks from blocking legacy repositories without a reviewed migration record;
  • records the policy-first dependency decision in the repository architecture corpus; and
  • adds the trust policy to the repository entry point.

Dependency resolution

This is the normative policy layer, not implementation evidence:

  1. .github defines the policy first.
  2. Relay 🧠 [platform] Configure organization-wide Copilot instructions #1 and 💰 [platform] Setup Patreon and integrate with GitHub funding #4 can implement reusable DCO, verification, signing, SBOM, provenance, and release profiles against it.
  3. Realm feat(reflector): bootstrap pass-based organization discovery audit engine #7 can prove the R3 image requirements.
  4. Empathy can prove the repository-local golden-consumer adoption contract.
  5. Organization adoption evidence can then be recorded without reopening the policy decision.

Scope boundary

This pull request does not:

  • add or copy reusable workflow YAML;
  • change organization or repository branch-protection settings;
  • mutate sibling repositories;
  • add signing keys, credentials, or secret material;
  • claim Relay, Realm, Empathy, or any legacy repository is already conformant; or
  • make checks blocking before a repository records an explicit adoption state.

Validation

trust-policy acceptance structure complete
local Markdown links resolve
Markdown has no trailing whitespace
boundary scan clean: egohygiene/.github
git diff --check: clean

The branch contains one DCO-signed scoped commit over current main.

Review gates

  • Confirm DCO enforcement and automated-contribution exemptions are sufficiently explicit.
  • Confirm the six signing subjects have the right minimum expectations.
  • Confirm the R0R3 class matrix maps cleanly to Relay release profiles.
  • Confirm legacy repositories cannot become blocking without explicit migration state.
  • Confirm exception ownership, expiry, renewal, and break-glass behavior are acceptable.
  • Confirm Relay, Realm, Empathy, Hygiene, and .github responsibilities remain separate.

Fixes #9

Signed-off-by: Codex <codex@openai.com>
@szmyty
szmyty marked this pull request as ready for review August 21, 2026 11:10
@szmyty
szmyty merged commit 2c04a1f into main Aug 21, 2026
@szmyty
szmyty deleted the feat/organization-trust-policy branch August 21, 2026 11:10
@devactivity-app

Copy link
Copy Markdown

Pull Request Summary by devActivity

Metrics

Cycle Time: 1h 7m Coding Time: < 1 min

Achievements

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.

Adopt organization repository trust policy for DCO, signing, and provenance

1 participant