Use GitHub fully, and make progress public automatically
People should be able to follow the project without anyone writing status updates: the issues, pull requests, releases and dashboards on GitHub should be produced from the project’s own records and opened and closed on their own.
The user, 2026-10-21: “#2. must be much broader. #3. as said do not hesitate to scratch everything and redo if needed, i really want it to be A1, must automate, publish, all that as much as possible, i want people to be able to follow along without us having to post updates or things like that, we could even publish tasks, issues, etc and of course resolve them automatically. like i want to exploit github at 200%, all its features, it must be novel.”
- Secrets: protection is organization-wide and broad, with one pattern registry (the harness’s redaction owner) generating every scanner. Histories are scanned and purged before they are imported.
- Progress is public and automatic: issues, projects, pull requests, reviews, releases, discussions and a Pages dashboard, all generated from the harness’s records and opened and closed automatically.
- Per-role GitHub Apps: the door, the verifier and the publisher.
- Every relevant GitHub feature is used deliberately (GITHUB-300).
Done so far: the secret gate (scripts/check-secrets.mjs, run by
.github/workflows/secret-scan.yml) takes its secret-file rules from the
engine’s one owner instead of a copy, and the public roadmap’s status tables
are generated from the tracker (scripts/floor/roadmap-status.ts).
Still missing: the scanner’s content patterns are not yet generated from the one redaction registry; issues, the project board, releases and discussions are not yet projected from the records (P5.3); the per-role Apps do not exist yet (P1.2).