Skip to content

I1029 — The gate refuses what would silently break the interface

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.

BLOCKED wave 6 · p1 · implementation profile · parallel safe

Part of capability-graph — One capability graph, two projections, and no second inventory of what this repository can do.

Blocked. This issue cannot start until I1021, I1022, I1023 are done. The status is derived from that, not declared.

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.

Current state

The verification workflow runs the repository's existing checks.

Desired state

The new checks belong to the same gate, run on every pull request, and the gate stays fast enough to be usable.

Scope

  • .github/workflows/validate.yml

Out of scope

  • A separate workflow for the interface checks
  • A gate slow enough that people work around it

Dependencies

What waits on this

Acceptance criteria

  • 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_extended
  • gate_time_measured

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

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.

Timeline

started
—
verified
—
completed
—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I1029.yaml. Read it back with majordomus plan show I1029.