@amsterdamdatalabs/adl-agent-control-linux-x64 0.1.10 → 0.1.26

package/packages/repo-controls/package/adl-compliance/src/adl_compliance/cli.py

@@ -10,17 +10,21 @@ is the CONSUMER's, and the consumer is this file. `git ls-files --cached
 --others --exclude-standard` is called here so that gitignored paths never enter
 a set, which is why no row needs to exclude `node_modules/` or `.scratch/`, and
 why no check needs to know git exists (K-41).
+
+Git is also asked, here, for the one fact a check cannot read off the worktree:
+the size of the blob Git STORES for a path (`committed_blob_sizes`). It is
+measured only when a selected row declares `reads_committed_sizes` (LFS-001) and
+handed down in `Context.committed_sizes`; every other run spawns no extra process.
 """
 
 from __future__ import annotations
 
 import argparse
-import json
 import os
 import subprocess
 import sys
 import tomllib
-from collections.abc import Mapping, Sequence
+from collections.abc import Iterable, Mapping, Sequence
 from concurrent.futures import ThreadPoolExecutor
 from pathlib import Path
 from typing import TextIO
@@ -30,6 +34,7 @@ from pydantic import ValidationError
 
 from . import runner
 from .core.constants import Constants
+from .core.errors import CouldNotRun
 from .core.receipt import from_verdict
 from .core.verdict import Outcome, Verdict
 from .policy.registry import (
@@ -85,6 +90,85 @@ def visible_files(root: Path) -> tuple[str, ...]:
     return tuple(line for line in completed.stdout.splitlines() if line)
 
 
+def committed_blob_sizes(root: Path, paths: Iterable[str]) -> dict[str, int]:
+    """Path -> size in bytes of the blob Git STORES for it, among `paths`.
+
+    The worktree is not what Git stores: a correctly tracked LFS file is a
+    ~132-byte pointer in the repository and the full file on disk, because the
+    filter smudges it on checkout. A check that grades size must be told the
+    stored size, and a check cannot ask git (K-41) -- so this is where it is
+    measured, for the rows that declare `reads_committed_sizes`.
+
+    "Stores" is the INDEX entry: for a clean checkout that is `HEAD`'s blob, and
+    while staging it is the blob about to be committed, the same reading
+    `check.sh` made with `:path`. Two git processes however many paths there
+    are -- `ls-files --stage` for every entry's object id, then ONE
+    `cat-file --batch-check` over the distinct ids -- never one per file.
+
+    A path gets no entry, and is therefore graded by its worktree file by the
+    check, when it has no stage-0 blob: untracked, not given, a gitlink
+    (submodule), or an unmerged path. Absence is never a size.
+
+    Git failing here is `CouldNotRun`, never an empty result: an empty map reads
+    as "nothing is known", which is a silent return to grading the smudged
+    worktree. `-z` means no path quoting, so `core.quotePath` cannot matter.
+    """
+    wanted = set(paths)
+    staged = subprocess.run(
+        ["git", "ls-files", "--stage", "-z"], cwd=root, capture_output=True, check=False
+    )
+    if staged.returncode != 0:
+        raise CouldNotRun(
+            "git ls-files --stage failed: " + staged.stderr.decode("utf-8", "replace").strip()
+        )
+
+    by_object: dict[str, list[str]] = {}
+    for record in staged.stdout.split(b"\0"):
+        if not record:
+            continue
+        meta, _, raw_path = record.partition(b"\t")
+        mode, object_id, stage = meta.decode("ascii").split(" ")
+        path = os.fsdecode(raw_path)
+        if mode == "160000" or stage != "0" or path not in wanted:
+            continue
+        by_object.setdefault(object_id, []).append(path)
+    if not by_object:
+        return {}
+
+    measured = subprocess.run(
+        ["git", "cat-file", "--batch-check"],
+        cwd=root, input="\n".join(by_object) + "\n", capture_output=True, text=True, check=False,
+    )
+    if measured.returncode != 0:
+        raise CouldNotRun(f"git cat-file --batch-check failed: {measured.stderr.strip()}")
+
+    sizes: dict[str, int] = {}
+    for line in measured.stdout.splitlines():
+        object_id, _, rest = line.partition(" ")
+        kind, _, size = rest.partition(" ")
+        if object_id not in by_object or kind != "blob" or not size.isdigit():
+            raise CouldNotRun(
+                f"git cat-file --batch-check could not size {line!r} "
+                f"(the index entry for {', '.join(by_object.get(object_id, ['?']))})"
+            )
+        for path in by_object[object_id]:
+            sizes[path] = int(size)
+    return sizes
+
+
+def reads_committed_sizes(row: Row) -> bool:
+    """Whether the check implementing `row` grades `Context.committed_sizes`.
+
+    A row no check implements answers False: the runner reports it could-not-run
+    on its own, and git has nothing to measure for it."""
+    from .checks import lookup
+
+    try:
+        return lookup(row.id).reads_committed_sizes
+    except KeyError:
+        return False
+
+
 def selected_rows(
     registry: Registry, target: str | None, only: Sequence[str] | None = None
 ) -> list[Row]:
@@ -288,7 +372,27 @@ def main(argv: Sequence[str] | None = None) -> int:
         help="a fact the repository states about itself, as `license=Proprietary` "
              "(repeatable). Read from [controls.compliance] and passed through: the "
              "package grades a repository against what it declares, it does not hold "
-             "the answer. `license` is the only name consumed today (REP-001).",
+             "the answer. Names consumed today: `license` (REP-001), and "
+             "`root-files` / `root-dirs` (LAY-006/008/012/013), each a comma-separated "
+             "list of repository-root names beyond the standard set, as "
+             "`root-files=STATUS.md,DRIFT.md` or `root-dirs=apps,packaging`; and "
+             "`scripts-direct-files` (LAY-014), a positive integer replacing the "
+             "default limit of 15 direct files per scripts directory, as "
+             "`scripts-direct-files=20`; `open-gaps` and `open-plans` (LAY-016), "
+             "each a positive integer replacing the default cap of 10 open gaps "
+             "or open plans, as `open-gaps=37` and `open-plans=11`; and "
+             "`markdown-roots` (LAY-006), a "
+             "comma-separated list of repository-relative directories whose "
+             "Markdown is allowed in addition to the declared docs trees "
+             "([controls.compliance.markdown].roots), as "
+             "`markdown-roots=apps/marketing,apps/platform/src/content`; and "
+             "`bun-manifests` / `bun-lockfiles` and `cargo-manifests` / "
+             "`cargo-lockfiles` (REP-002), comma-separated repository-relative "
+             "`package.json` / `Cargo.toml` paths or globs and literal lockfile "
+             "paths ([controls.compliance.lockfiles]), declared as a pair per "
+             "ecosystem and replacing that ecosystem's tree-derived scope, as "
+             "`bun-manifests=package.json,apps/*/package.json` with "
+             "`bun-lockfiles=bun.lock`.",
     )
     parser.add_argument(
         "--tree", metavar="NAME=PATH", action="append", default=[],
@@ -409,6 +513,20 @@ def main(argv: Sequence[str] | None = None) -> int:
             for gate, names in inputs_by_gate.items()
         }
 
+    # What Git stores, measured here because a check cannot call git (K-41), and
+    # only when a selected row declares it reads them -- every other run pays for
+    # no git process. Not for `--exhaustive`: that is a snapshot the caller vouches
+    # IS the candidate commit, with no `.git` of its own, so the bytes on disk are
+    # what is stored and asking whichever repository encloses it would mix an
+    # unrelated store back into the verdict.
+    committed_sizes: dict[str, int] = {}
+    if not args.exhaustive and any(reads_committed_sizes(row) for row in rows):
+        try:
+            committed_sizes = committed_blob_sizes(root, given)
+        except CouldNotRun as exc:
+            print(f"adl-compliance: {exc}", file=sys.stderr)
+            return int(Outcome.COULD_NOT_RUN)
+
     batch_results = runner.prepare_batches(
         rows,
         root,
@@ -435,6 +553,7 @@ def main(argv: Sequence[str] | None = None) -> int:
             # gate runs, `adl-config.toml` decides.
             declared_trees=declared_trees,
             batch_results=batch_results,
+            committed_sizes=committed_sizes,
         )
 
     # Threads, not processes. Nearly every check is I/O or a subprocess

package/packages/repo-controls/package/adl-compliance/src/adl_compliance/core/check.py

@@ -89,7 +89,7 @@ class Check(Constants, ABC):
     The other half of `inputs`, and the distinction is who owns the document:
 
         inputs      the CONSUMER's, named by a `<tree>` path. Measured evidence
-                    that changes per repository — a coverage summary, a lockfile.
+                    that changes per repository — a lockfile, a package manifest.
         resources   the PACKAGE's, sitting beside this check. Policy that ships
                     with the gate and means nothing without it — a profile
                     register, a rule table.
@@ -134,10 +134,42 @@ class Check(Constants, ABC):
     counting only the changed plans would turn eleven open plans into one.
     """
 
+    @classmethod
+    def declared_scope(
+        cls, scope: tuple[str, ...], declarations: Mapping[str, str]
+    ) -> tuple[str, ...] | None:
+        """The row's `engine.scope`, restated from what the repository declares.
+
+        `scope` is the row's RAW scope (`<tree>` placeholders intact) and the
+        return value is a replacement for it, expanded through the same tree map
+        as any scope. `None`, the default and what every row but REP-002 answers,
+        means the repository declared nothing for this row and the registry's
+        scope stands, byte for byte.
+
+        A restated scope is graded WHOLE, exactly like `whole_scope`: the caller's
+        narrowed set only decides whether the gate applies, then the check is
+        handed every file the declared scope matches in the complete universe.
+        That is the only set from which a check can say that something the
+        repository declared matches nothing, which it must say loudly.
+
+        Raise `CouldNotRun` naming the declaration when it is malformed: it
+        becomes the row's could-not-run verdict, never a quietly wider or
+        narrower scope.
+        """
+        return None
+
     requires: ClassVar[tuple[str, ...]] = ()
     """External executables this check drives. Verified by the runner, which
     removes the `command -v x || exit 2` prologue every shell check re-typed."""
 
+    reads_committed_sizes: ClassVar[bool] = False
+    """The check grades `ctx.committed_sizes`: the size of the blob Git stores.
+
+    Declared, not discovered, so a run that selects no such row pays for no git
+    process: the CLI measures the sizes (a check cannot reach an object store,
+    K-41) only when a selected row sets this, and hands them down in the Context.
+    """
+
     # ---------------------------------------------------------------- template
 
     def run(self, ctx: Context, files: FileSet) -> Iterator[Report]:

package/packages/repo-controls/package/adl-compliance/src/adl_compliance/core/constants.py

@@ -89,17 +89,6 @@ class Constants:
     SLUG_PATTERN: ClassVar[str] = r"^[a-z0-9]+(-[a-z0-9]+)*$"
     TITLE_LIMIT: ClassVar[int] = 80
 
-    # ----------------------------------------------------- coverage vocabulary
-    # The four names every coverage gate reports against, and the contract the
-    # two summary readers in `checks/coverage/baseline.py` both have to meet:
-    # the Istanbul reader iterates this tuple, and the coverage.py reader maps
-    # its own differently-named fields onto these same four keys. Three more
-    # coverage rows in the registry are still shell and will read it too.
-
-    COVERAGE_METRICS: ClassVar[tuple[str, ...]] = (
-        "lines", "statements", "functions", "branches",
-    )
-
 
 CONSTANTS: Final = Constants
 """Alias for the callers that reach these without inheriting: `cli` and

package/packages/repo-controls/package/adl-compliance/src/adl_compliance/core/context.py

@@ -69,12 +69,27 @@ class Context(StrictModel):
     which is a gate deciding a company's licensing rather than enforcing it.
     """
 
+    committed_sizes: dict[str, int] = Field(default_factory=dict)
+    """Repository-relative path -> size in bytes of the blob Git STORES for it.
+
+    A fact the CLI measures with git (a check cannot reach an object store, K-41)
+    and only for a check that declares `reads_committed_sizes`. It exists because
+    the worktree is not what Git stores: a correctly tracked LFS file is a
+    ~132-byte pointer in the repository and the full file on disk, so grading
+    the worktree reports the very files that are doing the right thing.
+
+    A path ABSENT from this map has no committed fact -- untracked, new, a
+    gitlink, or a root with no git repository -- and a check must grade it by
+    the worktree as it always did. Absence is never "small": a missing fact must
+    not turn into a silent pass.
+    """
+
     inputs: dict[str, Path] = Field(default_factory=dict)
     """Named inputs, already resolved to absolute paths by the runner.
 
     A check declares the logical names it needs and reads `ctx.inputs["x"]`. It
     never joins a path, and a test overrides an input by building a Context —
-    not by exporting `COVERAGE_BASELINE_CONFIG` into the process.
+    not by exporting an environment variable into the process.
     """
 
     batch_reports: tuple[Report, ...] | None = None

package/packages/repo-controls/package/adl-compliance/src/adl_compliance/policy/config.py

@@ -21,9 +21,8 @@ import tomllib
 from collections.abc import Mapping
 from functools import cache
 from importlib import resources
-from typing import Annotated
 
-from pydantic import Field, ValidationError, field_validator
+from pydantic import ValidationError, field_validator
 
 from ..core.constants import Constants
 from ..core.models import StrictModel

package/packages/repo-controls/package/adl-compliance/src/adl_compliance/policy/docs_shape.py

@@ -6,7 +6,8 @@ this", and the answer is declared once, here, so a second docs gate does not
 grow its own, independently drifting copy the way LAY-008/LAY-012 once did for
 the repository root (see `root_shape.py`'s module docstring).
 
-Nothing below is invented — every entry is read off an EXISTING docs gate:
+Every entry below is read off an EXISTING docs gate, except `notes.md`, which
+is declared by an explicit decision (see its entry):
 
 ALLOWED_DOCS_DIRS
     architecture, research, compliance, operations
@@ -42,6 +43,15 @@ ALLOWED_DOCS_FILES
         no repository in this estate ships a top-level `docs/index.md` today,
         and declaring it costs nothing.
 
+    notes.md
+        the task ledger. Not read off a docs gate: Tarun's global agent rule
+        (decision of 2026-10-01) requires every agent to append one line to
+        `docs/notes.md` when it starts a task and one when it finishes
+        (append-only, at most 100 characters per line), so the file exists in
+        every repository an agent works in and this gate would otherwise flag
+        it as undeclared. `docs-okf-profiles.yaml` carries a matching
+        `docs/notes.md` profile so `docs.okf-profile` (DOC-006) grades it too.
+
 These are PERMITTED, not required — the same distinction `root_shape.py`
 draws for the repository root. A repository using only two of the five
 directories is not missing three findings; it has simply not written those
@@ -62,4 +72,5 @@ ALLOWED_DOCS_FILES: frozenset[str] = frozenset({
     "AGENTS.md",
     "CLAUDE.md",
     "index.md",
+    "notes.md",
 })

package/packages/repo-controls/package/adl-compliance/src/adl_compliance/policy/gate-registry.alt.yaml

@@ -32,69 +32,6 @@
 schema: adl.gate-profile/v1
 rows:
 
-  # ---- coverage ----
-  - id: COV-001
-    name: backend-crate
-    domain: coverage
-    title: Run retained backend crate coverage gate
-    severity: M
-    controls:
-      - EC-A.8.29
-    engine:
-      scope:
-        - <rust>/**
-    grants: 0
-    timeout_ms: 60000
-  - id: COV-002
-    name: backend-ratchet
-    domain: coverage
-    title: Reject backend coverage decline below its ratchet
-    severity: H
-    controls:
-      - EC-A.8.28
-    engine:
-      scope:
-        - <rust>/**
-    grants: 0
-    timeout_ms: 60000
-  - id: COV-003
-    name: baseline
-    domain: coverage
-    title: Run retained coverage baseline gate
-    severity: M
-    controls:
-      - EC-A.8.29
-    engine:
-      scope:
-        - <rust>/**
-    grants: 0
-    timeout_ms: 60000
-  - id: COV-004
-    name: config-committed
-    domain: coverage
-    title: Require coverage ratchet data to be committed
-    severity: M
-    controls:
-      - EC-A.8.29
-    engine:
-      scope:
-        - <compliance>/policy/inputs/coverage-baseline.json
-    grants: 0
-    timeout_ms: 60000
-  - id: COV-005
-    name: full
-    domain: coverage
-    title: Run retained coverage gate
-    severity: M
-    controls:
-      - EC-A.8.29
-    engine:
-      scope:
-        - <rust>/**
-        - <compliance>/checks/coverage/full/coverage-modules.list
-    grants: 0
-    timeout_ms: 60000
-
   # ---- docs ----
   - id: DOC-001
     name: adr-lifecycle
@@ -238,7 +175,7 @@ rows:
     grants: 0
     timeout_ms: 60000
 
-  # ---- frontend ----
+  # ---- docs (continued: indexes, ledger, closed-set) ----
   - id: DOC-008
     name: indexes
     domain: docs
@@ -301,6 +238,104 @@ rows:
         - '<docs>/**'
     grants: 0
     timeout_ms: 60000
+  - id: DOC-011
+    name: filename
+    domain: docs
+    title: Require docs/ Markdown stems to be lower-kebab
+    severity: M
+    controls:
+      - EC-A.5.37
+    engine:
+      # docs/ only. The plans tree is deliberately NOT here: its pages answer
+      # to the board (LAY-009 owns plans/ frontmatter) and a filename rule is
+      # no more able to grade them than a profile is.
+      #
+      # The scope below mirrors DOC-006 (docs.okf-profile) EXACTLY -- one
+      # tree, both docs/ content gates walking it -- with the rationale
+      # comments carried over, adjusted only where they were
+      # profile-specific:
+      scope:
+        - <docs>/**
+        # A holding area for work that is not yet a Feature on the board.
+        # DOC-006 excludes it from profiling by design; mirrored here so a
+        # page DOC-006 does not grade is not graded for its filename either.
+        - '!<docs>/proposals/**'
+        # DOC-006 has excluded compliance/ since 2026-09-15, pending a real
+        # compliance audit (its pages answer to audit metadata, not to a
+        # gate a writer can satisfy from the document). The exclusion is
+        # mirrored here unchanged.
+        - '!<docs>/compliance/**'
+        # Tree guides are not pages: AGENTS.md and CLAUDE.md say what
+        # belongs in a directory and are governed by layout.agents-layout.
+        # The check also exempts the two names by rule -- a name may not be
+        # lower-kebab and still be correct -- so these excludes are
+        # belt-and-braces over that exemption, mirroring DOC-006.
+        - '!<docs>/**/AGENTS.md'
+        - '!<docs>/AGENTS.md'
+        - '!<docs>/**/CLAUDE.md'
+        - '!<docs>/CLAUDE.md'
+        # A knowledge index is a catalog of a tree, not a page about the
+        # system (DOC-006's reasoning); its stem ("index") is
+        # kebab-conforming anyway, and the exclusion is mirrored so both
+        # gates walk the same tree.
+        - '!<docs>/**/index.md'
+    grants: 0
+    timeout_ms: 60000
+  - id: DOC-012
+    name: directory-size
+    domain: docs
+    title: Cap each docs/ directory's page count via the directory ratchet
+    severity: M
+    controls:
+      - EC-A.5.38
+    engine:
+      # docs/ only. The plans tree is deliberately NOT here: its pages answer
+      # to the board (LAY-009 owns plans/ frontmatter) and a page-count cap
+      # is no more able to grade them than a filename rule is.
+      #
+      # The cap is CONFIG, not register content (owner ruling 2026-10-02):
+      # it is the repository's declared
+      # [controls.compliance.limits].docs_pages_per_directory, arriving as
+      # the docs-pages-per-directory declaration; absent, the engine default
+      # of 15 stands. The LAY-004 directory-ratchet register holds ONLY
+      # per-directory exemption baselines (docs_pages.baseline): an entry
+      # exempts its directory up to the recorded count; an absent register or
+      # section means NO exemptions, so the cap is enforced bare. At zero
+      # exemptions the register file is deleted. docs/decisions/ is exempt by
+      # rule at any depth below it — the flat ADR log is flat-by-design, not
+      # an over-cap directory.
+      #
+      # The scope below mirrors DOC-006 (docs.okf-profile) EXACTLY -- one
+      # tree, all three docs/ content gates walking it -- with the rationale
+      # comments carried over, adjusted only where they were
+      # filename-specific:
+      scope:
+        - <docs>/**
+        # A holding area for work that is not yet a Feature on the board.
+        # DOC-006 excludes it from profiling by design; mirrored here so a
+        # page DOC-006 does not grade is not counted against the cap either.
+        - '!<docs>/proposals/**'
+        # DOC-006 has excluded compliance/ since 2026-09-15, pending a real
+        # compliance audit (its pages answer to audit metadata, not to a
+        # gate a writer can satisfy from the document). The exclusion is
+        # mirrored here unchanged.
+        - '!<docs>/compliance/**'
+        # Tree guides are not pages: AGENTS.md and CLAUDE.md say what
+        # belongs in a directory and are governed by layout.agents-layout.
+        # The check's rule-level exemption is decisions/ (the flat ADR log,
+        # flat-by-design) rather than these names, so these excludes are
+        # the whole of the guide story here, mirroring DOC-006.
+        - '!<docs>/**/AGENTS.md'
+        - '!<docs>/AGENTS.md'
+        - '!<docs>/**/CLAUDE.md'
+        - '!<docs>/CLAUDE.md'
+        # A knowledge index is a catalog of a tree, not a page about the
+        # system (DOC-006's reasoning); it does not count against the page
+        # cap either, and the exclusion is mirrored so the docs gates walk
+        # the same tree.
+        - '!<docs>/**/index.md'
+    grants: 0
+    timeout_ms: 60000
 
   # ---- layout ----
   - id: LAY-001
@@ -366,6 +401,14 @@ rows:
     controls:
       - EC-A.5.36
     engine:
+      # The ceilings are CONFIG, not register content (generic ratchet
+      # principle, owner ruling 2026-10-02): they live in
+      # [controls.compliance.directory-ratchet].max_children and reach the
+      # engine as the directory-ceilings declaration. The LAY-004 register
+      # records exemption baselines only; an absent register means no
+      # exemptions allowed, so the ceilings are enforced bare. At zero
+      # recorded state the register file is deleted. No ceilings declared
+      # means nothing to enforce — the gate is inert.
       scope:
         - <typescript>/**
         - <rust>/**
@@ -390,11 +433,16 @@ rows:
         - '!**/Cargo.toml'
         - '!**/build.rs'
         - '!**/main.tf'
-        # No named-input entry for the ratchet register: it is package data now
-        # (src/adl_compliance/checks/layout/directory_ratchet/grants.yaml,
-        # read via `resources`, not a consumer path), so editing it does not
-        # select this gate -- the same known gap DOC-006's packaged profile
-        # register has (see INVARIANTS.md, "What is not true yet").
+        # The ratchet register is a named INPUT of this gate, not a scope entry:
+        # it is the CONSUMER's own file (<compliance>/ratchets/
+        # LAY-004-over-limit-directory.yaml -- the estate's settled location for
+        # a consumer-owned ratchet number, see packages/repo-controls/src/
+        # config.ts), and <compliance> is not one of this row's scope trees, so
+        # editing the register does not select this gate -- the same known gap
+        # DOC-006's packaged profile register has. It shipped as package data
+        # once and graded one donor repository's shape against every other
+        # repository (K-42); the `inputs` entry and
+        # test_the_register_is_not_packaged_data guard that return.
     # Tree-scoped only. Every verdict is a directory's DIRECT FILE COUNT, which
     # is only knowable by listing all of that directory's children: on a diff
     # scope DIR-002 can never fire and DIR-001's single-file rule misfires on
@@ -404,7 +452,8 @@ rows:
     # removes. `full` (`selects: all-rows`) picks this row up regardless.
     # Not an exception catalogue: `structural_grant = True` on the check
     # already forces the allowance to 0 regardless of this field. The ratchet
-    # register itself is package data, read via `resources` (see check.py).
+    # register itself is the consumer's own file, reached through the check's
+    # named `inputs`, not package data (see check.py).
     grants: 0
     timeout_ms: 60000
   - id: LAY-006
@@ -466,25 +515,6 @@ rows:
         - <plans>/**
     grants: 0
     timeout_ms: 60000
-  - id: LAY-010
-    name: profile-data
-    domain: layout
-    title: Enforce data-backed layout profile predicates
-    severity: M
-    controls:
-      - EC-A.5.36
-    engine:
-      # The two `*.md` globs are removed. They are residue from the multi-mode
-      # profile-data.sh this engine was split out of: its `layout.markdown-trees`
-      # branch read Markdown, and that branch now lives in its own gate
-      # (check-markdown-tree-location.sh) with its own row. This engine reads
-      # PostgreSQL migrations and nothing else, so the globs only made every
-      # documentation change schedule a gate with nothing to say. A stale scope
-      # is a silent pass in one direction and dead work in the other (K-17).
-      scope:
-        - <rust>/crates/**
-    grants: 0
-    timeout_ms: 60000
   - id: LAY-011
     name: references
     domain: layout
@@ -592,7 +622,7 @@ rows:
   - id: LAY-016
     name: open-work-cap
     domain: layout
-    title: No open plans or open gaps
+    title: Cap open plans and open gaps at ten
     severity: M
     controls:
       - EC-A.5.36
@@ -613,14 +643,16 @@ rows:
     engine:
       scope:
         - '**'
-        # The LFS fixtures are deliberately oversized binaries committed WITHOUT
-        # LFS -- that is precisely what they prove the check detects. Grading
-        # them means a package that fixture-tests "large blobs must use LFS"
-        # can never pass its own gate.
+        # LFS-001's own test cases are generated at test time under tmp_path
+        # (the committed LFS fixtures were retired 2026-10-01), so this gate no
+        # longer commits oversized binaries. The `!**/fixtures/**` exclusion
+        # remains because OTHER gates still commit fixtures, and fixture data
+        # is test input, not repository content to grade.
         - '!**/fixtures/**'
     grants: 0
     timeout_ms: 60000
 
+  # ---- pipeline ----
   - id: PIP-004
     name: phase-disjoint
     domain: pipeline
@@ -675,6 +707,13 @@ rows:
       - EC-A.5.21
     engine:
       scope:
+        # The tree-derived DEFAULT: each half is exactly two entries under its own
+        # tree. A repository whose manifests do not sit one level under its tree
+        # (enact-combined: a brace-union `typescript` tree, manifests at the root and
+        # under apps/*/) states the paths itself with `[controls.compliance.lockfiles]`
+        # (`bun-manifests`/`bun-lockfiles`, `cargo-manifests`/`cargo-lockfiles`); a
+        # declared half REPLACES that half's two entries, in the scope and in what the
+        # check grades. See `LockfileIntegrity.declared_scope`.
         - <rust>/Cargo.toml
         - <rust>/Cargo.lock
         - <typescript>/package.json
@@ -736,56 +775,3 @@ rows:
         - '**'
     grants: 0
     timeout_ms: 60000
-  - id: REL-001
-    name: changeset-plan
-    domain: release
-    title: Run retained changeset-plan gate
-    severity: M
-    controls:
-      - EC-A.8.32
-    engine:
-      scope:
-        # The gate's own "release-relevant" case list, which is six paths, not
-        # one tree. `.changeset/**` alone understated it by five: while the gate
-        # resolved its own diff those five were still tested, so the row and the
-        # code disagreed and the code won. Now the row is the narrowing, so a
-        # missing entry here is a file the gate can no longer see.
-        - .changeset/**
-        - VERSION
-        - CHANGELOG.md
-        - <workflows>/package.json
-        - <workflows>/changesets/package.json
-        - <workflows>/changesets/bun.lock
-    grants: 0
-    timeout_ms: 60000
-  - id: REL-004
-    name: version-release
-    domain: release
-    title: Run retained version-release gate
-    severity: M
-    controls:
-      - EC-A.8.32
-    engine:
-      scope:
-        # The FOUR files check.sh actually reads: VERSION and CHANGELOG.md
-        # directly, plus the two entries in its `versioned_files` array. The
-        # prior brace-glob form, `{VERSION,CHANGELOG.md,backend/Cargo.toml,
-        # frontend/package.json,.changeset}/**`, appended `/**` after each
-        # FILE name -- `_glob_bash_pattern` in lib/glob.sh requires a literal
-        # "/" then more characters after the alternation, which a bare file
-        # never has, so the pattern matched none of VERSION, CHANGELOG.md,
-        # backend/Cargo.toml or frontend/package.json and only `.changeset/**`
-        # ever selected this row (K-13: a positive glob matching nothing
-        # excludes everything). backend/Cargo.toml (0.1.52) and
-        # frontend/package.json (2.1.41) carry their own independent
-        # versioning, not the release VERSION (0.0.11) -- check.sh does not
-        # read either, so they are not restored here; adding them would
-        # trigger this gate for two files it has no logic to grade.
-        - VERSION
-        - CHANGELOG.md
-        - <workflows>/package.json
-        - <workflows>/changesets/package.json
-    grants: 0
-    timeout_ms: 60000
-
-  # ---- rust ----