Skip to content

Estate standardization 20260607#33

Closed
hyperpolymath wants to merge 7 commits into
mainfrom
estate-standardization-20260607
Closed

Estate standardization 20260607#33
hyperpolymath wants to merge 7 commits into
mainfrom
estate-standardization-20260607

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

Changes

RSR Quality Checklist

Required

  • Tests pass (just test or equivalent)
  • Code is formatted (just fmt or equivalent)
  • Linter is clean (no new warnings or errors)
  • No banned language patterns (no TypeScript, no npm/bun, no Go/Python)
  • No unsafe blocks without // SAFETY: comments
  • No banned functions (believe_me, unsafeCoerce, Obj.magic, Admitted, sorry)
  • SPDX license headers present on all new/modified source files
  • No secrets, credentials, or .env files included

As Applicable

  • .machine_readable/STATE.a2ml updated (if project state changed)
  • .machine_readable/ECOSYSTEM.a2ml updated (if integrations changed)
  • .machine_readable/META.a2ml updated (if architectural decisions changed)
  • Documentation updated for user-facing changes
  • TOPOLOGY.md updated (if architecture changed)
  • CHANGELOG or release notes updated
  • New dependencies reviewed for license compatibility (MPL-2.0 / MPL-2.0)
  • ABI/FFI changes validated (src/interface/abi/ and src/interface/ffi/ consistent)

Testing

Screenshots

@hyperpolymath

hyperpolymath commented Jun 22, 2026

Copy link
Copy Markdown
Owner Author

Closing this instance — not a problem with the standardization itself.

This is part of the broader estate-standardization campaign, which has landed cleanly on the large majority of repos. On this repo the branch (estate-standardization-20260607) was cut from an older base and main moved on in the meantime, so it can't merge as-is here:

  • Conflicting with current main.
  • Stale vs main — a handful of its modified files would roll back newer main state (e.g. dogfood-gate.yml would take actions/checkout back from @v7.0.0 to @v4).
  • A few changes (PMPL→MPL relicensing, copyright-header touches) are best applied via the normal manual licence pass rather than bundled here.

Rather than rebase this stale branch, the wanted pieces are being re-applied fresh against current main. First of those — the governance docs — landed in #34, with the dual MPL-2.0 / CC-BY-SA-4.0 header follow-up in #35. Branch left intact for reference.

hyperpolymath added a commit that referenced this pull request Jun 22, 2026
## Summary

Adds `GOVERNANCE.adoc` and `MAINTAINERS.adoc`, freshly authored from the
owner's personal governance/maintainers **gist templates**
(benevolent-maintainer model), rendered as AsciiDoc to match repo
conventions.

This **supersedes the stale equivalents in #33**, which was cut from an
old base and could not be lifted safely (see #33 closure note).

## Changes
- `GOVERNANCE.adoc` — benevolent-maintainer governance model (founder:
Jonathan D.A. Jewell / `@hyperpolymath`)
- `MAINTAINERS.adoc` — ownership table + review expectations, references
existing `.github/CODEOWNERS`

## Notes
- Header matches existing root `.adoc` precedent on `main` (single
`MPL-2.0` SPDX line) plus the owner-attribution line required by the
repo pre-commit hook.
- No licence-policy changes; no files modified — purely additive.
- Commit signed (ssh `id_ed25519_signing`).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@hyperpolymath hyperpolymath deleted the estate-standardization-20260607 branch June 22, 2026 18:55
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.

1 participant