@theagilemonkeys/facility 0.3.1

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,68 @@
+# @theagilemonkeys/facility
+
+The command-line half of [Facility](https://github.com/theam/facility) —
+open-source, self-hosted tooling for running AI coding agents as part of a
+reviewable delivery process, with the humans, the gates and the evidence in one
+place.
+
+One binary with two jobs, and you rarely need both:
+
+- **A client for a Facility platform.** Dispatch agents, follow sessions, decide
+  proposals, inspect spend, manage projects and repositories — everything the
+  web application does, from a terminal or a script.
+- **An installer for a repository.** When a team wants the process running in
+  its own CI, invoked from issue comments, `facility init` writes the workflows,
+  the standard, the skills and the guards into the repository.
+
+```bash
+npx @theagilemonkeys/facility --help
+```
+
+Node.js 20 or newer. Zero configuration to read; one dependency.
+
+**Early software.** Facility is published while it is still being built: the
+API is young, generated files change shape between `0.x` releases, and no
+upgrade path is promised across them. Apache-2.0 means what it says — no
+warranty, use at your own risk.
+
+## Talking to a platform
+
+```bash
+npx @theagilemonkeys/facility login --url https://facility.example.com --key fak_…
+npx @theagilemonkeys/facility status      # runs, approvals, issues and spend at a glance
+npx @theagilemonkeys/facility inbox       # review and decide pending proposals
+npx @theagilemonkeys/facility sessions    # trigger, watch, steer or cancel agent runs
+```
+
+Platform commands take a global `--json`, `--profile <name>` and
+`--timeout <seconds>`, so the CLI is as usable from a script as from a prompt.
+It speaks the same versioned REST API and obeys the same permissions as the web
+application: what your key cannot do, the CLI will not do either.
+
+## Installing the process into a repository
+
+```bash
+cd your-repository
+npx @theagilemonkeys/facility init
+npx @theagilemonkeys/facility doctor --run-guards --github
+```
+
+`init` asks about the package manager, the default branch, the commands that
+provision an environment and verify a change, then writes GitHub workflows for
+planning, building, reviewing and repairing, plus `STANDARD.md`, agent
+instructions, skills, deterministic guards, and a `.facility.json` recording the
+answers. It never overwrites an existing generated file unless you pass
+`--force`, and it appends to `AGENTS.md` and `CLAUDE.md` inside a delimited
+managed block rather than replacing them.
+
+This is the second step, not the entry price: a repository connected to a
+Facility platform is operated entirely from the platform, without a single file
+being added to it.
+
+## Documentation
+
+- [CLI reference](https://github.com/theam/facility/blob/main/apps/docs/docs/reference/cli.md)
+- [Self-hosting guide](https://github.com/theam/facility/blob/main/apps/docs/docs/self-host/quickstart.md)
+- [Repository and issues](https://github.com/theam/facility)
+
+Apache-2.0 · an initiative by [The Agile Monkeys](https://theagilemonkeys.com)

package/bin/facility.mjs

@@ -0,0 +1,10 @@
+#!/usr/bin/env node
+import { main } from "../src/cli.mjs";
+
+main(process.argv.slice(2)).then(
+  (code) => process.exit(code ?? 0),
+  (error) => {
+    console.error(error?.code === "prompt_eof" ? error.message : (error?.stack ?? String(error)));
+    process.exit(1);
+  }
+);

package/modules/README.md

@@ -0,0 +1,35 @@
+# Modules
+
+A facility module packages one quality concern in every form a rule needs to
+actually hold:
+
+1. **Prose** — a section inserted into your `STANDARD.md`, so agents and
+   humans know the rule and the reasoning.
+2. **A reviewer** — a subagent in `.claude/agents/` that judges the gray area
+   prose can't pin down.
+3. **Checks** — deterministic guards and hooks for the part that should never
+   depend on judgment.
+4. **Workflows** — slash commands in `.claude/commands/` for the procedures
+   the module prescribes (e.g. `/new-migration`, `/add-telemetry`), so the
+   right way is also the easy way.
+
+Install one with:
+
+```
+npx @theagilemonkeys/facility add <module>
+```
+
+| module | what it enforces |
+|---|---|
+| `analytics` | new features ship privacy-safe analytics; missing events are correctness bugs |
+| `database` | migrations are immutable and append-only; row-level security by default |
+| `ai-queryability` | durable product data is queryable/actionable by AI, or the waiver is written down |
+| `design-system` | UI changes conform to your design system and carry browser evidence |
+
+## Writing your own
+
+Copy the shape of any module here: a `module.json` manifest, a
+`standard-section.md`, and optional `agents/`, `guards/`, and `hooks/`
+fragments. Then `npx @theagilemonkeys/facility add ./path/to/your-module`. If a concern
+keeps biting your team, it deserves the full triple — a rule that exists only
+as prose will be missed again.

package/modules/ai-queryability/agents/queryability-reviewer.md

@@ -0,0 +1,35 @@
+---
+name: queryability-reviewer
+description: Enforces "AI queryability by default". Use when a change adds or modifies durable, user-relevant data. Checks the feature is discoverable and actionable through search, agent tools, and MCP — or that a waiver is documented.
+tools: Read, Grep, Glob, Bash
+---
+
+You verify that new durable product data is not trapped behind a human-only
+UI. Every new durable feature should be queryable and actionable by AI by
+default; if exposing it is unsafe or not product-sensible, the PR must
+document the waiver.
+
+## What to check
+1. **Search**: new user-relevant data is indexed and discoverable under the
+   same access control the UI enforces.
+2. **Agent tools**: the product's chat/search agent can reach the feature
+   when users would expect it to read, explain, or act on it.
+3. **MCP**: safe read/list/get tools exist, plus any necessary action tools,
+   wired into the tool registry. Mutations are explicit about side effects,
+   confirmation, idempotency, and permissions.
+4. **Triggers/jobs**: if the change affects indexes/summaries/derived
+   state/notifications, a reliable trigger or job path exists with explicit
+   retries and idempotency.
+5. **Empty results are permission-safe** — no implication that hidden data
+   exists.
+
+## How to verify
+- `grep` the search/agent/MCP registries to confirm the new entity is wired
+  end to end.
+- Run the repo's MCP/tool test suite when one exists.
+
+## Output contract
+For each new durable entity, report its exposure status across
+Search / Agent tools / MCP / Triggers as Exposed / Missing / Waived, with
+file:line and the fix for anything missing. If a waiver is claimed, confirm
+the reason is written down in the PR. Flag only queryability/correctness gaps.

package/modules/ai-queryability/module.json

@@ -0,0 +1,9 @@
+{
+  "name": "ai-queryability",
+  "title": "AI Queryability",
+  "description": "Durable product data is queryable and actionable by AI by default — or the waiver is written down.",
+  "standardSection": "standard-section.md",
+  "files": [
+    { "from": "agents/queryability-reviewer.md", "to": ".claude/agents/queryability-reviewer.md" }
+  ]
+}

package/modules/ai-queryability/standard-section.md

@@ -0,0 +1,22 @@
+### AI queryability (facility module)
+
+Every new durable feature is queryable and actionable by AI by default. Data
+trapped behind a human-only UI is invisible to your product's search, chat
+agent, and MCP surface — and to every workflow your users will automate next
+year. If exposing it is unsafe or not product-sensible, **document that
+waiver in the PR**; an undocumented omission is a gap.
+
+When a feature creates new user-relevant data, check each surface:
+
+- **Search**: the data is indexed and discoverable under the same access
+  control the UI enforces.
+- **Agent tools**: the product's chat/search agent can read, explain, or act
+  on the feature when users would expect it to.
+- **MCP**: safe read/list/get tools exist, plus necessary action tools.
+  Mutating tools are explicit about side effects, confirmation, idempotency,
+  and permission boundaries.
+- **Triggers/jobs**: if the feature changes data that affects search indexes,
+  summaries, derived state, or notifications, a reliable trigger/job path
+  exists with explicit retries and idempotency.
+- **Empty results are permission-safe**: an AI surface must not imply hidden
+  data exists when access control returns nothing.

package/modules/analytics/agents/analytics-reviewer.md

@@ -0,0 +1,32 @@
+---
+name: analytics-reviewer
+description: Reviews analytics coverage and telemetry privacy. Use when a feature adds runtime behavior, or when analytics events or telemetry helpers change. Treats missing analytics on a new feature as a correctness issue, and PII in product analytics as a defect.
+tools: Read, Grep, Glob, Bash
+---
+
+You review whether a change ships the right analytics **and** respects the
+privacy contract in `STANDARD.md` (Analytics section). Missing analytics on a
+feature with runtime behavior is a correctness issue, not polish.
+
+## What to check
+1. New user-facing behavior has an event plan: started / completed / failed,
+   plus validation errors, permission denials, cancellations, retries, empty
+   results, and background-job lifecycle where relevant.
+2. Event names live in the repo's event catalog — flag any hard-coded
+   event-name string literals at call sites.
+3. **Privacy**: captured properties contain only IDs, enums, counts,
+   durations, booleans, route paths, and field names — never message text,
+   user content, names, credentials, or full URLs.
+4. Telemetry tests are added/updated when event names, sanitization, or
+   required properties change.
+
+## How to verify
+- `grep` call sites for string-literal event names that bypass the catalog.
+- Run the repo's telemetry tests when analytics changed.
+
+## Output contract
+List gaps by severity, each with file:line and the fix. Explicitly confirm
+there is no PII in captured properties, or name every offending property. If
+analytics is intentionally skipped, require that the waiver reason is stated
+in the PR. End with the checks you ran. Flag only correctness/privacy gaps,
+not style.

package/modules/analytics/commands/add-telemetry.md

@@ -0,0 +1,23 @@
+---
+description: Add privacy-safe analytics for a feature, per STANDARD.md's Analytics section
+---
+
+Instrument a feature following STANDARD.md's Analytics section.
+
+1. Write the event plan BEFORE touching code, in the task notes or PR
+   summary: user story (who acts, what success/failure means), surface
+   (entry points, primary actions, failure/empty/completion states), and the
+   event catalog — started/completed/failed, validation errors, permission
+   denials, cancellations, retries, background-job lifecycle.
+2. Add event names to this repo's event catalog file — find it (grep for
+   existing event-name constants) and follow its convention. Never hard-code
+   event-name strings at call sites.
+3. Privacy check on every property: IDs, enums, counts, durations, booleans,
+   route paths, and field names only. No message text, no user content, no
+   names, no credentials, no full URLs. If a property could identify a person
+   or quote their content, it doesn't ship.
+4. Add or update telemetry tests when event names, sanitization, or required
+   properties change.
+5. Verify with the repo's telemetry tests, and finish by listing the events
+   added and the failure paths they cover — uninstrumented failure paths are
+   the gap reviewers will catch.

package/modules/analytics/module.json

@@ -0,0 +1,10 @@
+{
+  "name": "analytics",
+  "title": "Analytics",
+  "description": "New features ship privacy-safe analytics; missing events are correctness bugs.",
+  "standardSection": "standard-section.md",
+  "files": [
+    { "from": "agents/analytics-reviewer.md", "to": ".claude/agents/analytics-reviewer.md" },
+    { "from": "commands/add-telemetry.md", "to": ".claude/commands/add-telemetry.md" }
+  ]
+}

package/modules/analytics/standard-section.md

@@ -0,0 +1,23 @@
+### Analytics (facility module)
+
+New features must ship with analytics unless the feature has no runtime
+behavior. **Missing analytics on a new feature is a correctness issue, not
+polish** — a feature you cannot measure is a feature you cannot operate.
+
+Before implementing, write the event plan in the task notes or PR summary:
+
+- User story: who acts, what they are trying to do, what success/failure means.
+- Surface: entry points, primary actions, failure states, completion states.
+- Event catalog: started/completed/failed, validation errors, permission
+  denials, cancellations, retries, empty results, background-job lifecycle.
+
+Implementation rules:
+
+- Event names live in one catalog file — never hard-coded strings at call
+  sites. (Declare the catalog path here once you have one.)
+- Product analytics must not capture message text, user content, names,
+  credentials, or full URLs. Capture IDs, enums, counts, durations, booleans,
+  route paths, and field names.
+- Add or update telemetry tests when event names, sanitization, or required
+  properties change.
+- If a feature intentionally skips analytics, write the reason in the PR.

package/modules/database/agents/data-security-reviewer.md

@@ -0,0 +1,38 @@
+---
+name: data-security-reviewer
+description: Adversarial reviewer for database access control, migrations, privileged credentials, and data exposure. Use proactively before merging any change that touches migrations, access policies, auth helpers, or grants.
+tools: Read, Grep, Glob, Bash
+---
+
+You are a database-authorization security reviewer. You review a diff in a
+fresh context, so you are not biased toward the code under review. Assume
+access-control gaps **fail silently** (they return empty rows, not errors) —
+verify the negative case, never trust a prose claim that "access control is
+enforced".
+
+## What to check
+1. New tables/collections in exposed scopes: access control enabled, deny by
+   default, broad default grants revoked, minimum grants only.
+2. No policy inlines raw token/claim parsing — authorization routes through
+   the repo's shared helper layer.
+3. Functions or procedures that bypass access control (e.g. SECURITY DEFINER,
+   stored procs running as owner): re-check authorization first, pin their
+   execution environment, and keep them listed in the repo's audit doc.
+4. Privileged credentials stay out of user-facing and agent-facing read
+   paths; any privileged action sits behind explicit permission checks with
+   tests.
+5. Migrations in the diff only ADD files — `node guards/run.mjs
+   --only=migrations-immutable` proves it.
+6. Empty results are permission-safe — nothing hints that hidden data exists.
+
+## How to verify
+- `node guards/run.mjs --only=migrations-immutable`
+- The repo's access-control test suite, when the diff touches policies,
+  grants, or auth helpers.
+
+## Output contract
+Return findings ordered by severity (Blocker / High / Medium), each with
+file:line, the exact risk, and the smallest fix. State which checks you ran
+and their result. Report **only** authorization/security/privacy/correctness
+gaps — not style. If you find nothing, say "No authorization gaps found" and
+list the checks that prove it.

package/modules/database/commands/new-migration.md

@@ -0,0 +1,24 @@
+---
+description: Scaffold a new migration with safety defaults — never edit an existing one
+---
+
+Create a new database migration following STANDARD.md's Database section.
+
+1. Locate the migrations directory (`migrations/`, `supabase/migrations/`,
+   `db/migrations/`, `prisma/migrations/` — whichever this repo uses) and
+   follow its existing naming convention (timestamp prefix, snake_case
+   description).
+2. Create a NEW file. Never modify or delete an existing migration — they are
+   append-only; the `migrations-immutable` guard and the file hooks enforce
+   it.
+3. Safety defaults in the scaffold, adapted to this repo's stack:
+   - New tables start closed: enable row/document-level access control where
+     supported, deny by default, grant only the minimum operations.
+   - Authorization routes through the repo's shared helper layer — no inline
+     token/claim parsing in policies.
+   - Destructive operations (drop, irreversible data rewrites) get a written
+     justification comment and, where the stack supports it, a down path.
+4. If the feature needs realistic data to test, update the seeds in the same
+   change.
+5. Verify: run the repo's migration apply/reset command if one exists, then
+   `node guards/run.mjs --only=migrations-immutable`.

package/modules/database/guards/migration-versions.mjs

@@ -0,0 +1,41 @@
+// facility module: database
+//
+// Two migrations with the same version prefix apply in undefined order — and
+// on some stacks, silently skip. Collisions happen exactly when two branches
+// (or two agents) scaffold migrations the same day and both merge. This guard
+// fails the build the moment both exist on one branch.
+import { readdirSync } from "node:fs";
+
+const MIGRATION_DIRS = ["migrations", "supabase/migrations", "db/migrations", "prisma/migrations"];
+
+export default {
+  name: "migration-versions",
+  description: "no two migration files share a version prefix",
+  run() {
+    const violations = [];
+    for (const dir of MIGRATION_DIRS) {
+      let files;
+      try {
+        files = readdirSync(dir).filter((f) => /^\d/.test(f));
+      } catch {
+        continue;
+      }
+      const byVersion = new Map();
+      for (const file of files) {
+        const version = file.match(/^(\d+)/)?.[1];
+        if (!version) continue;
+        if (!byVersion.has(version)) byVersion.set(version, []);
+        byVersion.get(version).push(file);
+      }
+      for (const [version, group] of byVersion) {
+        if (group.length > 1) {
+          violations.push({
+            file: `${dir}/${group[1]}`,
+            message: `version ${version} collides across: ${group.join(", ")} — regenerate with a fresh timestamp`,
+          });
+        }
+      }
+    }
+    return violations;
+  },
+};

package/modules/database/guards/migrations-immutable.mjs

@@ -0,0 +1,57 @@
+// facility module: database
+//
+// Applied migrations are immutable. This guard fails when a commit range
+// modifies or deletes an existing migration file instead of adding a new one.
+// In CI it diffs against the PR base; locally it diffs against the merge-base
+// with the default branch.
+import { execFileSync } from "node:child_process";
+
+// Directories that hold ordered migration files. Adjust to your stack.
+const MIGRATION_DIRS = [
+  "migrations/",
+  "supabase/migrations/",
+  "db/migrations/",
+  "prisma/migrations/",
+];
+
+// key: "<path>", value: written reason (e.g. "squashed baseline, 2026-01").
+const ALLOWLIST = {};
+
+function git(args) {
+  try {
+    return execFileSync("git", args, {
+      encoding: "utf8",
+      stdio: ["ignore", "pipe", "ignore"],
+    }).trim();
+  } catch {
+    return "";
+  }
+}
+
+export default {
+  name: "migrations-immutable",
+  description: "existing migration files are never edited or deleted, only added",
+  run() {
+    const base =
+      process.env.GITHUB_BASE_SHA ||
+      git(["merge-base", "HEAD", `origin/${process.env.DEFAULT_BRANCH || "main"}`]) ||
+      git(["merge-base", "HEAD", "main"]);
+    if (!base) return []; // shallow clone or fresh repo — nothing to compare against
+
+    const out = git(["diff", "--name-status", base, "HEAD"]);
+    const violations = [];
+    for (const row of out.split("\n").filter(Boolean)) {
+      const [status, ...paths] = row.split("\t");
+      const path = paths[paths.length - 1];
+      if (!MIGRATION_DIRS.some((dir) => path.startsWith(dir))) continue;
+      if (status.startsWith("M") || status.startsWith("D") || status.startsWith("R")) {
+        if (ALLOWLIST[path]) continue;
+        violations.push({
+          file: path,
+          message: `migration ${status.startsWith("D") ? "deleted" : "modified"} — migrations are append-only; write a new one`,
+        });
+      }
+    }
+    return violations;
+  },
+};

package/modules/database/hooks/protect-migrations.fragment.mjs

@@ -0,0 +1,10 @@
+// facility module: database — migration immutability (PreToolUse)
+if (/(^|\/)(supabase\/|db\/|prisma\/)?migrations\/[^/]+\.(sql|js|ts|rb|py)$/.test(filePath)) {
+  const tool = payload?.tool_name ?? "";
+  const isEdit = tool === "Edit" || tool === "MultiEdit";
+  if (isEdit) {
+    block(
+      "Migration files are immutable once written. Create a NEW timestamped migration instead.",
+    );
+  }
+}