erix/meta
Template
Watch
1
0
Fork
You've already forked meta
 0
Code Issues 2 Pull requests 1 Projects Releases Packages Wiki Activity Actions

WIP: Validate immutable governance cohorts across the repository fleet #4

Draft
erikinkinen wants to merge 1 commit from feature/posix-compat into main
pull from: feature/posix-compat
merge into: erix:main
Conversation 0 Commits 1 Files changed 10 +1391 -88
erikinkinen commented 2026-09-12 10:14:02 +02:00
Owner
Copy link

Summary and rationale

Maintain an explicit 76-repository governance roster independently of runtime
build catalogs. A bounded validator compares the six canonical policy/template
files from original Git objects at explicitly selected complete commit hashes.
New compatibility repositories receive governance coverage without pretending
that their services or build targets already exist.

Tracking and scope

  • Coordination: erix/meta#2. Repository audit: erix/meta#3.
  • Add the roster, original local-object reader, strict cohort/schema checks,
    exclusive private receipts, meaningful regressions and exact-source CI.
  • Update canonical repository documents and the focused validation contract.
  • Synchronization, complete fleet audit, runtime behavior and self-hosting
    acceptance remain separate work. Shared policy/template bytes are unchanged.

Architecture, authority and failure behavior

The caller selects the meta commit, local object stores, source map, Git
executable, output path and adjustable budgets. The checker performs no fetch,
branch fallback, repository code execution, source mutation or credential lookup.
It verifies original commit/tree/blob hashes and ordinary policy-path entries.
Missing, extra, ambiguous or mismatched members cannot pass complete coverage.

Only the owned Git reader is killed/reaped. Total deadlines cover input parsing,
model work and publication; nested read limits cannot extend an enclosing limit
or replace an existing caller timer. An existing receipt is never overwritten.
Partial output and roster-only success do not establish fleet equality.

Validation evidence

Signed head: 81a9df741aae44e9c4053e1c7d8df48e81094790.

  • All 15 warning-denied tests pass, covering original object fixtures, changed
    bytes, missing/corrupt objects, path links, exact membership, timer ownership,
    blocked-reader cleanup and deadlines through publication.
  • All 10 Markdown files, workflow YAML/shell syntax, template headings and
    whitespace checks pass. The six shared policy files remain unchanged.
    Authored code files have at most 310 physical lines.
  • A separately selected real cohort passes all 456 canonical file comparisons
    across 76 repositories. Source-map SHA-256:
    a442ffe12de88a46e8ec01287eb89847fb818e788a010d4c10db2b3d5cfcb3d6.
    Receipt SHA-256: f25bef79846eaaed6eb8409093a6bb4da71230c353132f53135c690dccb2ab6e.
    This verifies selected policy bytes, not signatures or a runtime source graph.
  • Exact-head push CI 18
    and PR CI 19 pass. All
    four complete job logs contain no warning/failure candidates.
    Rust formatting, Clippy and VM tests are
    inapplicable: this repository has no Cargo target or guest implementation.

Review checklist

  • Original implementation and independent synthetic object fixtures
  • Signed canonical commit and relevant documentation
  • Strict local checks and real complete-cohort byte comparison
  • No runtime registration or build claim from governance membership
  • Exact-head push/PR CI and full job-log review
  • Complete repository audit
  • Full phase and self-hosting acceptance

Retain the WIP prefix while declared work and dependent validation remain open.
Readiness does not authorize merging or release publication.

## Summary and rationale Maintain an explicit 76-repository governance roster independently of runtime build catalogs. A bounded validator compares the six canonical policy/template files from original Git objects at explicitly selected complete commit hashes. New compatibility repositories receive governance coverage without pretending that their services or build targets already exist. ## Tracking and scope - Coordination: erix/meta#2. Repository audit: erix/meta#3. - Add the roster, original local-object reader, strict cohort/schema checks, exclusive private receipts, meaningful regressions and exact-source CI. - Update canonical repository documents and the focused validation contract. - Synchronization, complete fleet audit, runtime behavior and self-hosting acceptance remain separate work. Shared policy/template bytes are unchanged. ## Architecture, authority and failure behavior The caller selects the meta commit, local object stores, source map, Git executable, output path and adjustable budgets. The checker performs no fetch, branch fallback, repository code execution, source mutation or credential lookup. It verifies original commit/tree/blob hashes and ordinary policy-path entries. Missing, extra, ambiguous or mismatched members cannot pass complete coverage. Only the owned Git reader is killed/reaped. Total deadlines cover input parsing, model work and publication; nested read limits cannot extend an enclosing limit or replace an existing caller timer. An existing receipt is never overwritten. Partial output and roster-only success do not establish fleet equality. ## Validation evidence Signed head: `81a9df741aae44e9c4053e1c7d8df48e81094790`. - All 15 warning-denied tests pass, covering original object fixtures, changed bytes, missing/corrupt objects, path links, exact membership, timer ownership, blocked-reader cleanup and deadlines through publication. - All 10 Markdown files, workflow YAML/shell syntax, template headings and whitespace checks pass. The six shared policy files remain unchanged. Authored code files have at most 310 physical lines. - A separately selected real cohort passes all 456 canonical file comparisons across 76 repositories. Source-map SHA-256: `a442ffe12de88a46e8ec01287eb89847fb818e788a010d4c10db2b3d5cfcb3d6`. Receipt SHA-256: `f25bef79846eaaed6eb8409093a6bb4da71230c353132f53135c690dccb2ab6e`. This verifies selected policy bytes, not signatures or a runtime source graph. - Exact-head [push CI 18](https://git.erikinkinen.fi/erix/meta/actions/runs/18) and [PR CI 19](https://git.erikinkinen.fi/erix/meta/actions/runs/19) pass. All four complete job logs contain no warning/failure candidates. Rust formatting, Clippy and VM tests are inapplicable: this repository has no Cargo target or guest implementation. ## Review checklist - [x] Original implementation and independent synthetic object fixtures - [x] Signed canonical commit and relevant documentation - [x] Strict local checks and real complete-cohort byte comparison - [x] No runtime registration or build claim from governance membership - [x] Exact-head push/PR CI and full job-log review - [ ] Complete repository audit - [ ] Full phase and self-hosting acceptance Retain the WIP prefix while declared work and dependent validation remain open. Readiness does not authorize merging or release publication.
feat: Validate immutable governance cohorts across the repository fleet
All checks were successful
CI / markdown (push) Successful in 38s
Details
CI / governance (push) Successful in 43s
Details
CI / markdown (pull_request) Successful in 16s
Details
CI / governance (pull_request) Successful in 25s
Details
81a9df741a
 
Register governance membership independently of runtime build catalogs and
compare six canonical policy files from explicitly selected original Git
objects. Bound local readers and all validation stages, preserve owned timer
and process cleanup, and reject incomplete or ambiguous source cohorts.

Fifteen warning-denied tests exercise original fixtures and failure cleanup.
CI validates its exact roster and tests the checker; a separately selected
real cohort remains required for fleet equality evidence.
All checks were successful
CI / markdown (push) Successful in 38s
Details
CI / governance (push) Successful in 43s
Details
CI / markdown (pull_request) Successful in 16s
Details
CI / governance (pull_request) Successful in 25s
Details
This pull request is marked as a work in progress.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feature/posix-compat:feature/posix-compat
git switch feature/posix-compat

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff feature/posix-compat
git switch feature/posix-compat
git rebase main
git switch main
git merge --ff-only feature/posix-compat
git switch feature/posix-compat
git rebase main
git switch main
git merge --no-ff feature/posix-compat
git switch main
git merge --squash feature/posix-compat
git switch main
git merge --ff-only feature/posix-compat
git switch main
git merge feature/posix-compat
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
bug
Something is not working

  
ci

   
docs

   
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
help wanted
Need some help

  
invalid
Something is wrong

  
performance
Measured performance profiling, bottleneck analysis, and regression budgets.

  
phase-6
Phase 6: POSIX compatibility, full EriX self-hosting, and its required audits and validation.

  
question
More information is needed

  
refactor
Code cleanup, removal of obsolete paths, and structural improvements preserving behavior.

  
security

   
wontfix
This won't be fixed

No labels
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/meta!4
No description provided.