Skip to content

policy-catalogue: update README count and rows for the seven merged entries - #30

Merged
ecogetaway merged 1 commit into
ecogetaway:mainfrom
sjh9714:catalogue-readme-rollup
Jul 31, 2026
Merged

policy-catalogue: update README count and rows for the seven merged entries#30
ecogetaway merged 1 commit into
ecogetaway:mainfrom
sjh9714:catalogue-readme-rollup

Conversation

@sjh9714

@sjh9714 sjh9714 commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

The single follow-up you asked for once #21, #23#29 were in — all eight merged, so this is the one PR touching the README.

  • Count: 13 → 20 of 60+
  • Rows: seven added
  • Closing line: twelve adopted policies → nineteen, plus the one proposal

Each row's distinctive feature is the axis that entry adds to the catalogue rather than a précis of the policy, matching how the existing rows read:

Home Assistant the only policy disclosing the project's own AI use; template bypass as the observable proxy for autonomy
Mesa the only graduated disclosure vocabulary — and incompatible with both Fedora and Kubernetes on the same mechanism
OpenStreetMap the only permissive policy asking for no disclosure at all, enforcing on absence of understanding
FreeBSD the only policy protecting the project as training data; its AI clause is a routing rule, not a stance
Bevy the only policy reasoning about its own enforceability
Zig the strictest, and the only one reaching upstream of the artifact
Asahi Linux the only stance derived from a pre-existing rule rather than written fresh

Checked before sending: all 20 links in the table resolve to a file, and every file in policy-catalogue/ other than README and TEMPLATE appears in the table.

Stances were taken from the merged entry files rather than from my drafts, so the table and the entries cannot disagree.

…ntries

The single follow-up promised once #21, #23-#29 were in. Count 13 to 20,
seven rows added, and the closing line from twelve adopted policies to
nineteen plus the one proposal.

Each row's distinctive feature is the axis that entry adds to the
catalogue rather than a summary of the policy, matching the existing rows:

- Home Assistant — the only policy disclosing the project's own AI use,
  and template bypass as the observable proxy for autonomy
- Mesa — the only graduated disclosure vocabulary, and incompatible with
  both Fedora and Kubernetes on the same mechanism
- OpenStreetMap — the only permissive policy asking for no disclosure at
  all, enforcing on absence of understanding
- FreeBSD — the only policy protecting the project as training data; its
  AI clause is a routing rule rather than a stance
- Bevy — the only policy reasoning about its own enforceability
- Zig — the strictest, and the only one reaching upstream of the artifact
- Asahi Linux — the only stance derived from a pre-existing rule rather
  than written fresh

Every link in the table resolves to a file, and every file in
policy-catalogue/ except README and TEMPLATE appears in the table.
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