The slice records leave the public tree; SLICES.md says what each slice committed - #74
Merged
Merged
Conversation
…ce committed The owner (2026-09-23): the team's full plans are not for the public repository, only the final overview of what each slice commits. The grandfathered archive under slices/ (243 files, slices 001 to 007: plans, findings, round logs, trees, gate runs) held board identifiers, local paths and working notes. Every file was first copied byte for byte into the internal repository (cmp over all 243: identical), since 001, 001b, 002, 003, 006 and 007 existed nowhere else; then removed here. SLICES.md replaces it: each landed slice, one line on what it committed, its pull request (001 landed as commit 36136a1, before pull requests were required; #1 and #2 predate the numbering rule and say so). Unlanded plans are not listed. The gate: tools/publication-allowlist.txt is empty and re-pinned (allowlist_sha in tools/gate.sh), so any tracked path under slices/ now fails the publication step. REUSE.toml only annotated the archive and goes; `reuse==6.2.0 lint`: compliant, 461 / 461 files with copyright and licence information. CONTRIBUTING and conformance.yml stop naming it. Citations of slice files in lib/ and test/ comments (and two tools' comments) now say which slice's record holds the measurement, "(internal)"; process-tool comments that describe where logs were written are history and stay. tools/archive_sweep.sh and tools/probe_archive_tally.sh read only that archive and nothing ran them: removed. History is not rewritten; the files remain in earlier commits. Signed-off-by: Ayla Croft <aylacroft@proton.me>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The team's full slice records leave the public tree;
SLICES.mdsays what each slice committed, with its pull request.slices/archive is removed: 243 files covering slices 001 to 007 (plans, findings, review logs, gate runs). Every file was copied byte for byte into the internal records first.slices/.REUSE.tomlonly annotated that archive and goes with it. The REUSE lint still passes: 461 of 461 files.Gate on 058ca48: Gate OK (publication: 0 grandfathered, allowlist pinned).