Supporting federation map and conformance surface for the Universal Law research program.
The only public front door is d6g8k5htny-coder/main. This repository is deliberately narrower: it maps the repository set, pins observed cross-repository control inputs, and runs fail-closed structural checks. It is not a second research home and it is not a scientific-status authority.
main
PUBLIC FRONT DOOR
│
┌──────────────┼──────────────┐
▼ ▼ ▼
Math- query- meta-framework
PROOF VAULT LOOKUP CATALOG
│ │ │
└──────────────┼──────────────┘
▼
CUSTODY / CONFORMANCE
│
┌───────────┼───────────┐
▼ ▼ ▼
google-drive trial governance-
custody integration protocols
sandbox = bounded experimentation
this repo = federation map + pinned topology
New here? Read main first.
Reading mathematics? Go to Math-.
Looking for an exact artifact? Use query-.
- the supporting federation map;
- observed, byte-addressed pointers to canonical cross-repository control inputs;
- structural conformance checks for that map;
- engineering coordination for cross-repository navigation.
It does not decide theorem correctness, claim grade, terminal classification, review disposition, lemma closure, independence credit, or promotion. It also does not own the machine repository-role map; existing repository roles remain in meta-framework/registry.json.
The machine-readable boundary is workspace/repositories.json. Its validator rejects scientific-state fields and duplicate machine role metadata.
- main — canonical public front door
- Math-
- meta-framework
- query-
- google-drive (archived)
- trial (archived)
- governance-
- sandbox (archived)
- Universal-Law-Workspace
For canonical repository roles and public/private routing metadata, consult the pinned repository_registry source in workspace/repositories.json.
Beside the map, this repository pins each federation repository's default
branch tip as a git submodule under repos/. A pin is a gitlink: a pointer to
one commit, recorded in .gitmodules and in pins.json. No tree
is copied here and no branch is merged here; the research repositories stay
where they are and keep their own status records.
| repository | path | default branch | pinned commit | note |
|---|---|---|---|---|
| main | repos/main |
main | 02973f3975a1c4cc91b7c51d372f65717c9b3c5c | default tip at generation time |
| Math- | repos/Math- |
main | 9bdfc54b76173b57912503bfcf901a5f9d43b09c | default tip at generation time |
| meta-framework | repos/meta-framework |
main | 0f5894f81a5462c10ee5ec8f8109f466e712e47e | default tip at generation time |
| query- | repos/query- |
main | fb4c457b5861dc49696fd0a8e11c7c405056c05f | default tip under CBZ directive; prior pin retained in history |
| google-drive | repos/google-drive |
main | ad08584b3ea9d533af10113e85169f471fa8ec93 (archived) | default tip at generation time |
| trial | repos/trial |
main | 3738c859d519d2dbf1e388fe48fe0ae60c9487a3 (archived) | observed default tip; original import history remains in pins.json |
| governance- | repos/governance- |
main | 1b62ca2f64b3012c2fdbbf7f55ced236c3042891 | default tip at generation time |
| sandbox | repos/sandbox |
main | dce04a4174835107126ab4f36c199a2dc320f964 (archived) | opt-in (update = none); made public 2026-09-26 during the import, see below |
pins.json is the authoritative list; this table is a manually maintained
rendering of it. Keep the matching table row synchronized whenever a pin changes.
tools/verify_pins.py checks pins.json against the committed HEAD gitlinks
and .gitmodules; it does not read or validate this README table. With
--network, it also checks that public pinned commits exist on their remotes.
The test suite separately checks this README's full commit links and SHA set.
Fresh clone with the public submodules, shallow:
git clone --recurse-submodules --shallow-submodules https://github.com/d6g8k5htny-coder/universal-law-workspaceExisting clone:
git submodule update --init --depth 1Neither command touches repos/sandbox (see below), so both work without
credentials.
repos/sandbox is committed as a gitlink like the others, but .gitmodules
marks it update = none, so --recurse-submodules and submodule update --init skip it. The repository was private when this workspace was first
measured (2026-09-26T15:16Z) and was made public at 2026-09-26T15:19:20Z
while the import was running; the opt-in marking was kept so that a clone
never fails if the visibility changes again. Those with access initialise it
explicitly with --checkout, which overrides update = none for that one
command (without --checkout git prints "Skipping submodule 'repos/sandbox'"
and leaves the directory empty):
git submodule update --init --checkout --depth 1 repos/sandboxDropping the opt-in is a one-line pull request that removes update = none
from .gitmodules and sets opt_in to false in pins.json.
Start from a clean working tree on an isolated branch. Move the gitlink and
the matching pins.json entry together, manually update the table above, then
commit the local candidate before checking it (replace the placeholders):
git update-index --add --cacheinfo 160000,<full-sha>,repos/<name>
# edit pins.json: pinned_sha for repos/<name>
# update the matching README table row to the same full SHA
git add pins.json README.md
git diff --cached --check
git diff --cached --submodule=short
git commit -m "Update <name> pin"
python3 tools/verify_pins.py --networkReview the staged diff before committing. The checker reads gitlinks from
HEAD, not the index, so checking before the commit would compare the edited
pins.json with the old committed gitlink. Run verification from the clean
candidate checkout; a local commit does not push or merge anything. After the
checks pass, open the candidate pull request for review.
CI (.github/workflows/pins.yml) runs the checker in two modes. The legacy
--network mode requires full-SHA gitlink, .gitmodules, pins.json and
remote-commit agreement while reporting tip differences. CI then runs the
strict mode below; it rejects drift, missing or contradictory default/HEAD/branch
evidence, lookup failures and skipped non-public repositories:
python3 tools/verify_pins.py --require-currentThis strict mode implies remote checks. Its observations are sequential, not
an atomic cross-repository snapshot, and it does not validate the four source
blobs in workspace/repositories.json or prove mathematical claims. Remote
network access is required. The negative controls in
tests/ show the checker fails when any of these is broken:
python3 -m unittest discover -s tests -vA pin is a pointer to a commit. It is not a review of that commit, not an
endorsement, and not a status. Status words for the program's claims live in
the registers in repos/main; nothing in this repository reads, sets or
implies them. The scientific effect of this repository is NONE: no proof is
held here, no original prize problem is solved here, and moving a pin changes
no claim's grade anywhere.
MIT, see LICENSE. Cite via CITATION.cff.
python3 tools/check_workspace.py
python3 tools/verify_pins.py --network
python3 tools/verify_pins.py --require-current
python3 -m unittest discover -s tests -p 'test_*.py' -vA green run means the local federation contract is structurally valid and the
submodule pins agree with pins.json and exist on their remotes. It does not
verify mathematics.
For the current baseline mission, start with STATUS.md, INVENTORY.md and GOVERNANCE.md. Historical project coordination remains in board #619, with architecture discussion at #666 and #275's residuals at #669. These links are sources of recorded work, not proof that an obligation is closed.
The completed bootstrap record remains in issue #1. Keep this repository map-sized: no proof-body migration, no duplicate status database, and no attempt to flatten the research repositories into this tree.