Canonicalize shared governance and immutable dependency policy #1

Manually merged
erikinkinen merged 0 commits from feature/native-cli into main 2026-09-12 07:34:25 +02:00
Owner

Pull request

Summary and rationale

Canonicalize the shared contribution, conduct, security and review policies so contributors and auditors have one consistent contract across EriX repositories.

  • Require cryptographically signed commits with tagged titles, real blank lines and explanatory rationale-bearing bodies.
  • Require full immutable Git commit pins for crate dependencies, Integration catalogs and CI helpers, with bottom-up updates and original source identities.
  • Clarify contributor responsibility, optional attribution, private security reporting, authority boundaries and validation requirements.
  • Synchronize issue/PR templates, correct template metadata, remove unsupported Forgejo workflow permissions and refresh meta's component documentation.

Tracking and scope

  • Owning issue/project card: not linked; public tracking remains pending. This PR does not create or update unrelated issues or board cards.
  • Source: feature/native-cli at 91b30d9a8ee8bf82093dbf575bc3f76a641012cd; target: main.
  • Related changes: the shared files have been synchronized across all 73 repositories. Coordinate the documentation policy merge before making the new main-branch policy links authoritative.
  • Remaining work: resolve the policy-link dependency and review the historical commit-message exception below. Automated organization-wide drift checking remains deferred in ROADMAP.
  • Non-goals: runtime implementation, ABI changes, merges, releases or image publication.

Architecture, authority and failure behavior

No runtime capability or persistent-format change: this branch changes documentation, templates and unsupported CI metadata only. It adds no runtime authority or unsafe code. The canonical policy requires explicit authority ownership/lifetime/cleanup and rejects floating dependency selection, dirty source substitution and synthetic replacement commits.

The workflow removes permissions metadata that Forgejo ignores; it does not grant additional runner capabilities. Source-selection behavior is implemented and validated in the coordinated component/Integration changes, not in this template repository.

Validation evidence

At 91b30d9a8ee8bf82093dbf575bc3f76a641012cd:

  • markdownlint-cli2: all 9 Markdown files pass, zero errors.
  • git diff --check origin/main...HEAD: passes.
  • Workflow YAML and both issue-template YAML headers parse successfully.
  • Byte-for-byte shared-file comparison: 438 matching copies across 73 repositories.
  • All five branch commits have valid cryptographic signatures.
  • Meta CI run 15: successful for this exact revision.

Rust formatting, Clippy, builds, unit tests, doctests, runtime authority regressions, VM checks and performance gates are not applicable to this documentation/template-only repository change; they are not claimed as passes. No manual/API generator inputs changed here.

The canonical documentation policy URL currently returns 404 on docs/main: pending policy destination. Coordinate the docs merge before removing WIP.

Review checklist

  • Contribution provenance and immutable dependency policy are documented.
  • Every branch commit satisfies both signing and rationale-body requirements: signatures pass, but the pre-existing fd713a2 CI commit has no body. No history was rewritten to open this PR.
  • Shared documentation is cohesive; no new implementation code or oversized code files are introduced.
  • README, ARCHITECTURE and ROADMAP are updated; manual/API generation is not applicable here.
  • Shared governance/template files match the coordinated meta revision across all 73 repositories.
  • Owning issue, dependent PRs and organization board are linked and up to date.
  • Required documentation links resolve on their intended main-branch destinations.
  • No secrets, private reports or unsupported validation claims are included.

Keep WIP until the declared remaining items are resolved. PR readiness does not authorize merging or releasing.

# Pull request ## Summary and rationale Canonicalize the shared contribution, conduct, security and review policies so contributors and auditors have one consistent contract across EriX repositories. - Require cryptographically signed commits with tagged titles, real blank lines and explanatory rationale-bearing bodies. - Require full immutable Git commit pins for crate dependencies, Integration catalogs and CI helpers, with bottom-up updates and original source identities. - Clarify contributor responsibility, optional attribution, private security reporting, authority boundaries and validation requirements. - Synchronize issue/PR templates, correct template metadata, remove unsupported Forgejo workflow permissions and refresh meta's component documentation. ## Tracking and scope - Owning issue/project card: not linked; public tracking remains pending. This PR does not create or update unrelated issues or board cards. - Source: `feature/native-cli` at `91b30d9a8ee8bf82093dbf575bc3f76a641012cd`; target: `main`. - Related changes: the shared files have been synchronized across all 73 repositories. Coordinate the documentation policy merge before making the new main-branch policy links authoritative. - Remaining work: resolve the policy-link dependency and review the historical commit-message exception below. Automated organization-wide drift checking remains deferred in ROADMAP. - Non-goals: runtime implementation, ABI changes, merges, releases or image publication. ## Architecture, authority and failure behavior No runtime capability or persistent-format change: this branch changes documentation, templates and unsupported CI metadata only. It adds no runtime authority or unsafe code. The canonical policy requires explicit authority ownership/lifetime/cleanup and rejects floating dependency selection, dirty source substitution and synthetic replacement commits. The workflow removes `permissions` metadata that Forgejo ignores; it does not grant additional runner capabilities. Source-selection behavior is implemented and validated in the coordinated component/Integration changes, not in this template repository. ## Validation evidence At `91b30d9a8ee8bf82093dbf575bc3f76a641012cd`: - `markdownlint-cli2`: all 9 Markdown files pass, zero errors. - `git diff --check origin/main...HEAD`: passes. - Workflow YAML and both issue-template YAML headers parse successfully. - Byte-for-byte shared-file comparison: 438 matching copies across 73 repositories. - All five branch commits have valid cryptographic signatures. - [Meta CI run 15](https://git.erikinkinen.fi/erix/meta/actions/runs/15): successful for this exact revision. Rust formatting, Clippy, builds, unit tests, doctests, runtime authority regressions, VM checks and performance gates are not applicable to this documentation/template-only repository change; they are not claimed as passes. No manual/API generator inputs changed here. The canonical documentation policy URL currently returns 404 on `docs/main`: [pending policy destination](https://git.erikinkinen.fi/erix/docs/src/branch/main/policies/generative-ai-contributions.md). Coordinate the docs merge before removing WIP. ## Review checklist - [x] Contribution provenance and immutable dependency policy are documented. - [ ] Every branch commit satisfies both signing and rationale-body requirements: signatures pass, but the pre-existing `fd713a2` CI commit has no body. No history was rewritten to open this PR. - [x] Shared documentation is cohesive; no new implementation code or oversized code files are introduced. - [x] README, ARCHITECTURE and ROADMAP are updated; manual/API generation is not applicable here. - [x] Shared governance/template files match the coordinated meta revision across all 73 repositories. - [ ] Owning issue, dependent PRs and organization board are linked and up to date. - [ ] Required documentation links resolve on their intended main-branch destinations. - [x] No secrets, private reports or unsupported validation claims are included. Keep WIP until the declared remaining items are resolved. PR readiness does not authorize merging or releasing.
ci: remove unsupported Forgejo permissions metadata
All checks were successful
CI / markdown (push) Successful in 4s
fd713a2fc8
docs: Canonicalise commit message guidelines
All checks were successful
CI / markdown (push) Successful in 3s
665fab0976
Require every commit to use a tagged imperative header and a non-empty body that explains the material change and its rationale. Documenting the format centrally gives every EriX repository one reviewable convention and prevents context-free history.
docs: Canonicalize assisted contribution rules
All checks were successful
CI / markdown (push) Successful in 8s
4b66e560a3
Link the shared contribution guide to the permissive generative AI policy and make contributor responsibility, real validation, and optional attribution explicit. Distinguishing cryptographic signing from text trailers avoids accidentally requiring Signed-off-by or Assisted-by while preserving the title, body, and rationale contract.
docs: Synchronize shared contribution and review policies
All checks were successful
CI / markdown (push) Successful in 5s
f3298711ca
Unify contribution, conduct, security and issue/PR templates with meta so
contributors receive the same authority, review and clean-room requirements
in every repository. Require signed commits with real title/body separation
and rationale, repair policy links and issue metadata, and clarify private
reporting, secret handling and optional attribution.

Validated all shared file sets and bytes, YAML metadata, policy targets,
repository Markdown lint and diff whitespace checks. No Rust implementation
or image configuration changes are included.

Update the documentation contract for coordinated shared-file changes
while keeping component documentation specialized.
docs: Require immutable dependency source revisions
All checks were successful
CI / markdown (push) Successful in 8s
CI / markdown (pull_request) Successful in 2s
91b30d9a8e
Replace the floating main-branch dependency rule with full commit hashes for Cargo, Integration catalogs and CI helper sources. Exact object identity and bottom-up transitive updates make builds auditable and prevent branch changes or synthetic mirrors from silently changing dependency code.

Preserve same-repository workspace paths and synchronized governance copies. The updated policy passes Markdown validation.
erikinkinen changed title from WIP: Canonicalize shared governance and immutable dependency policy to Canonicalize shared governance and immutable dependency policy 2026-09-12 07:22:50 +02:00
erikinkinen manually merged commit 06909b3d54 into main 2026-09-12 07:34:25 +02:00
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:02 +01:00
Sign in to join this conversation.
No description provided.