@amsterdamdatalabs/adl-agent-control-linux-x64 0.1.4

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

@@ -0,0 +1,250 @@
+"""What is allowed to sit at a repository's root, declared once.
+
+Three gates ask this question — `layout.placement` (LAY-008),
+`layout.root-closed-set` (LAY-012) and `layout.root-markdown-allowlist`
+(LAY-013) — and each carried its own copy of the answer. The copies had already
+drifted: LAY-012 had been corrected to `.gitattributes`/`.gitignore` while
+LAY-008 still carried the shell script's original typos `.attributes`/`.ignore`,
+so the same file was permitted by one gate and reported by another.
+
+Three lists expressing one policy is the drift this package exists to catch,
+so the policy lives here and the gates import it.
+
+**These are PERMITTED, not required.** A closed set says "nothing outside
+this"; it says nothing about what must be inside. LAY-012 used to run both
+rules off one list and reported a missing file for every permitted entry a
+repository did not happen to use.
+
+**Language sections are unavoidable, and deliberately marked.** A JS toolchain
+puts `tsconfig.json` and its lockfile at the root by convention rather than by
+choice — none can be moved into an owning tree without breaking the tool that
+reads them. The same is true of `pyproject.toml` for Python and `Cargo.toml`
+for Rust. A repository using none of a section simply never matches its
+entries; an entry that permits an absent file costs nothing.
+"""
+
+from __future__ import annotations
+
+# ── Files ─────────────────────────────────────────────────────────────────────
+
+VCS_AND_META: frozenset[str] = frozenset({
+    ".cursorrules",
+    ".dockerignore",
+    ".editorconfig",
+    ".gitattributes",
+    ".gitignore",
+    ".lfsconfig",
+    ".mcp.json",
+    "VERSION",
+})
+
+GUIDES: frozenset[str] = frozenset({
+    "AGENTS.md",
+    "CLAUDE-INVARIANTS.md",
+    "CLAUDE.md",
+    "INDEPENDENT-VERIFICATION.md",
+    "INVARIANTS.md",
+    "README.md",
+})
+
+GOVERNANCE: frozenset[str] = frozenset({
+    "CHANGELOG.md",
+    "CODE_OF_CONDUCT.md",
+    "CONTRIBUTING.md",
+    "GOVERNANCE.md",
+    "LICENSE",
+    "MAINTAINERS.md",
+    "NOTICE",
+    "RELEASE.md",
+    "SECURITY.md",
+    "SUPPORT.md",
+})
+
+# Registers read by whoever picks the work up next. They sit at the root
+# because that is where someone arriving at the repository looks.
+#
+# STATUS.md (the live checklist) and DRIFT.md (the drift audit) are the same
+# kind of object: a register read by whoever picks the work up next, not
+# narrative documentation that belongs under docs/. (Tarun, 2026-09-27.)
+REGISTERS: frozenset[str] = frozenset({
+    "GAPS-AND-FINDINGS.md",
+    "OPEN-ITEMS.md",
+    "STATUS.md",
+    "DRIFT.md",
+})
+
+NODE_TOOLCHAIN: frozenset[str] = frozenset({
+    ".npmrc",
+    ".nvmrc",
+    ".prettierrc",
+    ".prettierignore",
+    # Same tool as `.prettierrc` above, the same relationship `.dockerignore`
+    # already has to Docker in `VCS_AND_META` — a paired root-required ignore
+    # file, not a look-alike added on resemblance. Deliberately NOT extended
+    # to `.markdownlint.json`/`.markdownlintignore`/`.yamllint.yml`: grepped
+    # for real in the one consumer repository that carries all three
+    # (enact-extensions) — zero hits in `package.json`, `bun.lock`, any
+    # `scripts/` file, or `azure-pipelines.yml`. Nothing in that repository's
+    # own tooling invokes markdownlint or yamllint; they read as editor-only
+    # preference files there, not a root file some build step requires to
+    # find, so they stay off this list until a consumer shows otherwise.
+    "biome.json",
+    "bun.lock",
+    "bunfig.toml",
+    "eslint.config.js",
+    "index.html",
+    "knip.json",
+    "opencode.json",
+    "opencode.jsonc",
+    "package-lock.json",
+    "package.json",
+    "playwright.config.ts",
+    "pnpm-lock.yaml",
+    "svelte.config.js",
+    "tsconfig.json",
+    "tsconfig.base.json",
+    "vite.config.ts",
+    "vitest.config.ts",
+    "yarn.lock",
+})
+
+PYTHON_TOOLCHAIN: frozenset[str] = frozenset({
+    "conftest.py",
+    "pyproject.toml",
+    "uv.lock",
+})
+
+RUST_TOOLCHAIN: frozenset[str] = frozenset({
+    "Cargo.lock",
+    "Cargo.toml",
+    "rust-toolchain.toml",
+})
+
+# Configuration that names the repository itself, so it can only live here.
+PROJECT_CONFIG: frozenset[str] = frozenset({
+    ".env.example",
+    "Dockerfile",
+    "azure-pipelines.yml",
+    # This package's own `pre_push` feature is literally `azdo-push` — Azure
+    # Pipelines status is a thing this package reads back — and yet no
+    # category named the CI definition file itself. Measured for real: both
+    # consumer repositories checked against this package ship
+    # `azure-pipelines.yml` at their root, and `layout.placement`/
+    # `layout.root-closed-set` both reported it as undeclared, a false
+    # failure on every Azure-DevOps-driven consumer this package can
+    # plausibly serve. Same shape as `docker-compose.yml` below: a
+    # build/deploy pipeline definition naming THIS repository's own stages,
+    # not a language-specific toolchain file.
+    "coverage-floor.json",
+    "ctx_overlays.json",
+    "docker-compose.yml",
+    "drizzle.config.ts",
+    "adl-config.toml",
+    "justfile",
+})
+
+ALLOWED_ROOT_FILES: frozenset[str] = (
+    VCS_AND_META
+    | GUIDES
+    | GOVERNANCE
+    | REGISTERS
+    | NODE_TOOLCHAIN
+    | PYTHON_TOOLCHAIN
+    | RUST_TOOLCHAIN
+    | PROJECT_CONFIG
+)
+
+# ── Directories ───────────────────────────────────────────────────────────────
+
+AGENT_TREES: frozenset[str] = frozenset({
+    ".agents",
+    ".claude",
+    # One plugin root per host. `.claude-plugin` was here alone because it was the
+    # only one when this list was written; the per-host plugin migration created the
+    # rest, and a list that knows one of a set knows none of it. Same omission as
+    # PUBLISHED_PACKAGE_ROOTS in layout.root_markdown_allowlist, found the same day.
+    ".claude-plugin",
+    ".codex-plugin",
+    ".cursor-plugin",
+    ".kimi-plugin",
+    ".code-review-graph",
+    ".codex",
+    ".cursor",
+    ".kimi-code",
+    ".opencode",
+    ".workflows",
+})
+
+KNOWLEDGE_TREES: frozenset[str] = frozenset({
+    ".changeset",
+    ".docs",
+    ".donors",
+    "docs",
+    "plans",
+    "specs",
+})
+
+SOURCE_TREES: frozenset[str] = frozenset({
+    # `apps/` (deployables) and `packaging/` are sanctioned root directories in
+    # the Enact monorepo layout this repository follows — the Enact monorepo
+    # itself carries both. (Tarun, 2026-09-27.)
+    "apps",
+    "packaging",
+    "backend",
+    "compliance",
+    "docker",
+    "bin",
+    "dev",
+    "frontend",
+    "infra",
+    "live-probes",
+    "packages",
+    "scripts",
+    "server",
+    "shared",
+    "src",
+    "src-tauri",
+    "static",
+    "tests",
+    # The CI tree: pipelines, pipeline-templates, scripts, tools. Distinct from
+    # `.workflows/`, which is adl-repo-controls' managed hook stubs and lock, and
+    # both are live — one is what Azure runs, the other is what git runs. A repository
+    # carrying both is not mid-migration, and LAY-012 calling this one undeclared said
+    # it was. (Owner decision, 2026-09-15.)
+    "workflows",
+})
+
+EDITOR_TREES: frozenset[str] = frozenset({".vscode"})
+
+# Directories this estate's OWN tooling requires at the root.
+#
+# `coverage/` is not a convention, it is a dependency: adl-repo-controls' coverage
+# ratchet reads `coverage/coverage-summary.json` on every push
+# (`workflows/scripts/coverage/paths.ts`), and `doctor` fails when it is absent while
+# `pre_push.coverage_ratchet` is on. LAY-012 reported it as an undeclared top-level
+# directory — one estate, two gates, opposite opinions about the same path, which is
+# the contradiction f958c0d removed for `feat`/`feature`.
+#
+# This set is for paths OUR tools demand. A directory that merely happens to hold
+# build output does not belong here: `test-results/` and `test-evidence/` are
+# committed build artifacts nothing requires, and they stay reportable.
+TOOLING_TREES: frozenset[str] = frozenset({
+    "coverage",
+})
+
+# Retired trees, still permitted so that a repository mid-migration is not
+# reported twice for the same fact. LAY-009 already names a leftover `.plans`
+# as legacy and says what to do about it; a second gate calling it "undeclared"
+# adds noise, not information.
+RETIRED_TREES: frozenset[str] = frozenset({
+    ".code-review-graph_old",
+})
+
+ALLOWED_ROOT_DIRS: frozenset[str] = (
+    AGENT_TREES | KNOWLEDGE_TREES | SOURCE_TREES | EDITOR_TREES | RETIRED_TREES | TOOLING_TREES
+)
+
+# What a repository must actually HAVE, as opposed to what it may have. Kept
+# deliberately tiny: this package installs into repositories whose shape it does
+# not know, and every entry here is a demand made of all of them.
+REQUIRED_ROOT_FILES: frozenset[str] = frozenset({"AGENTS.md"})

package/packages/repo-controls/package/adl-compliance/src/adl_compliance/policy/severity-policy.yaml

@@ -0,0 +1,114 @@
+# severity.yaml — what H, M and L mean for a gate profile row.
+#
+# FROZEN 2026-08-22 by .plans/a_new/26-08-22-enterprise-gate-estate-rebuild.md
+# (Wave 0). No lane may edit this file.
+#
+# Severity applies to two things, with the same three levels and the same
+# meaning in both:
+#   1. a gate profile row  (.workflows/config/profiles/*.yaml)
+#   2. an exception entry  (.workflows/config/exceptions/*.yaml, inline included)
+#
+# The compliance mapping is NOT restated here. It already exists in
+# docs/compliance/controls/control-matrix.yaml — 203 controls across five id
+# namespaces, each carrying its own cross_framework_mappings. A profile row
+# names control ids; this file only says what naming one obliges you to do.
+
+schema: adl.severity/v1
+frozen: '2026-08-22'
+authority: .plans/a_new/26-08-22-enterprise-gate-estate-rebuild.md
+control_matrix: docs/compliance/controls/control-matrix.yaml
+gap_register: docs/compliance/gaps/gap-register.yaml
+
+levels:
+
+  H:
+    name: High
+    means: >
+      The gate discharges an obligation under a control in the adl control
+      matrix. If it does not block, a compliance control is not operating.
+    requires:
+      controls: at least one existing control id
+      bidirectional_evidence: >
+        the row's evidence path must appear in that control's evidence: list
+    blocks_at: [pre-commit, pre-push, ci]
+    demotion: forbidden
+    inline_suppression: forbidden
+    exception_policy:
+      new_entries: forbidden
+      existing_entries_require: [id, owner, reason, created, expires, controls]
+      max_expiry_days: 90
+      ratchet: strictly decreasing
+      on_expiry: hard fail
+      no_upstream_fix: >
+        Becomes an accepted-risk row with compliance sign-off recorded against
+        the control, not a silently renewed exception.
+
+  M:
+    name: Medium
+    means: >
+      General industry practice. Real quality signal, no framework obligation
+      behind it. Regression is unacceptable; the current level is tolerated.
+    requires:
+      controls: optional
+    blocks_at: [pre-push, ci]
+    blocks_how: ratchet only — count must not increase versus integration
+    demotion: not applicable
+    inline_suppression: allowed with a register id
+    exception_policy:
+      new_entries: allowed
+      existing_entries_require: [id, owner, reason, created, expires]
+      max_expiry_days: 180
+      ratchet: non-increasing
+      on_expiry: hard fail
+
+  L:
+    name: Low
+    means: >
+      Preference, style, ergonomics. Useful to see, never worth failing a build.
+    requires:
+      controls: forbidden
+    blocks_at: []
+    blocks_how: report only
+    demotion: not applicable
+    inline_suppression: allowed, unregistered
+    exception_policy:
+      new_entries: not tracked
+      ratchet: none
+
+# Which control namespace an H row is likely to be discharging. Advisory only —
+# the authoritative statement is the control record itself. Counts as of the
+# 2026-07-28 assessment.
+control_namespaces:
+  EC-A:
+    framework: ISO/IEC 27001:2022 Annex A
+    count: 93
+    typical_gate_subjects: [secure coding, vulnerability management, secrets, change control, source-code access]
+  ISO:
+    framework: ISO/IEC 27001:2022 clauses 4-10
+    count: 7
+    typical_gate_subjects: [management system, documented information]
+  SOC2:
+    framework: SOC 2 Type II (CC, Availability, Confidentiality, Processing Integrity, Privacy)
+    count: 51
+    typical_gate_subjects: [logical access, change management, vulnerability detection, monitoring]
+  GDPR:
+    framework: GDPR
+    count: 21
+    typical_gate_subjects: [log redaction, secret handling, data protection by design]
+  EUAI:
+    framework: EU AI Act - Regulation (EU) 2024/1689
+    count: 31
+    typical_gate_subjects: [record-keeping, technical documentation, robustness and cybersecurity]
+
+# Boundaries. A gate proves a code property. It cannot prove lawful basis, DPIA
+# completion, retention schedules, human-oversight design, or model
+# documentation. Those controls stay open in the gap register and must not be
+# claimed as satisfied because a related gate exists.
+#
+# Statement of Applicability, SOC 2 scope selection, and legal applicability
+# require qualified external review — as control-matrix.yaml already records in
+# its metadata.limitations. Nothing in this file substitutes for that.
+limits:
+  gates_prove: [code properties, repository state, build-time invariants]
+  gates_do_not_prove: [lawful basis, DPIA completion, retention execution, human oversight, operating effectiveness over a period]
+  external_review_required: [Statement of Applicability, SOC 2 scope, legal applicability]

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

@@ -0,0 +1,11 @@
+"""Shared analyzer providers, keyed by the name declared on ``BatchCheck``."""
+
+from __future__ import annotations
+
+from ..core.batch import BatchProvider
+
+# Explicit like checks.CHECKS: adding a provider and wiring it are separate,
+# reviewable acts. Stage 3 registers the Svelte/Tailwind analyzer here.
+PROVIDERS: dict[str, BatchProvider] = {}
+
+__all__ = ["PROVIDERS"]