A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I1029
The gate refuses what would silently break the interface
Where it stands
devtask.issue- Readiness
- blocked 3 of its dependencies are not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
6- Waiting on
- Holds back
- Behind it in all
1- Evidence
0of2
| In the way | Subject | Detail |
|---|---|---|
| issue | I1021 | I1021 is not DONE |
| issue | I1022 | I1022 is not DONE |
| issue | I1023 | I1023 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Put the drift check, the enforcement rules, the parity test, the browser checks and the public-data scan into the existing verification workflow, so that a change leaving any derived surface stale or unsafe cannot merge.
- Why
- Every mechanism in this milestone depends on failing loudly at merge time. Without the gate they are conventions, and conventions are the thing this repository builds machinery to avoid needing.
- Now
- The verification workflow runs the repository's existing checks.
- Wanted
- The new checks belong to the same gate, run on every pull request, and the gate stays fast enough to be usable.
- Done when
- unknown: the record declares no `completion`
- Risk
- Browser checks in CI are where a suite becomes unreliable. They run against a built artifact with bounded waits, or they do not run at all.
Acceptance
- A stale derived surface, a missing required document, a missing required verification, a broken static link to a runtime-only surface and unsafe published metadata each fail the gate
- The browser checks and the parity test run on every pull request
- Caching keeps the added time proportionate, and the total is measured
- No check added here lives outside the existing verification hierarchy
- Validation
bash test/run.sh- Evidence required
gate_extendedgate_time_measured- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
.github/workflows/validate.yml- Not
A separate workflow for the interface checksA gate slow enough that people work around it- Depends on
- Priority
- p1
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-06
- Updated
- 2026-09-06
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.