foundation, stage-contract, index: the foundation and thin chain as one page, replacing runs, products, checks and releases

AGENTS.md

@@ -196,15 +196,16 @@ on anything outside it.
 ## The system section
 
 `system/` holds one page per register: `specification.md` is the design
-authority; `decisions.md` records the team's rulings; `products.md`,
-`runs.md` and `stage-contract.md` are the three model pages everything
-else builds on; each pipeline stage has its own page (`reference`,
+authority; `decisions.md` records the team's rulings; `foundation.md`
+and `stage-contract.md` are the two model pages everything else builds
+on, and `foundation.md` governs where an older page still describes the
+retired run model; each pipeline stage has its own page (`reference`,
 `difference`, `load`, `maintain`, `crossmatch`, `statistics`,
 `finalize`, `alerts`, `prune`, `export`); `photometry.md` is not a
 stage page, since the rebuild carries no photometry stage, and holds
-the unported-forced-photometry note instead; `releases.md`,
-`tool.md`, `loop.md`, `checks.md` and `observability.md` cover the
-mechanisms that run stages rather than a stage itself; and
+the forced-photometry note instead; `tool.md`, `loop.md` and
+`observability.md` cover the mechanisms that run stages rather than a
+stage itself; and
 `operations.md` holds operations proposals still open. Dated reviews go
 in the log, not in `system/`. `index.md`'s table is the map: its Scope
 column names what each page owns, and a page's own content should never

log/2026-09-26-direction-review.md

@@ -154,7 +154,7 @@ These go beyond consistency: each removes a mechanism.
 - **One notion of "current".** `vbest` on the `dev` tables and
   `current_selection` both answer "which one do consumers see", and
   promotion maintains both. Consumers moving to `current_selection` is
-  already the recorded direction ([products](../system/products.md));
+  already the recorded direction ([foundation](../system/foundation.md));
   retiring `vbest` maintenance waits for the team's existing queries to
   move.
 - **The transitional cleanup grant.** The workstation role still carries
@@ -268,7 +268,7 @@ field per source changes no row count: it writes one column's value. The
 lead's approval of that stamping (2026-09-26) is recorded on
 [load](../system/load.md).
 
-Two consequences for the pages. [products](../system/products.md) says ZOGY
+Two consequences for the pages. [foundation](../system/foundation.md) says ZOGY
 registers "as in `dev`", but `dev`'s own run of 2026-08-09 registered its
 SFFT difference for this exposure; which differencer `dev` registers is a
 question for the lead. And the rebuild's execution records hold `{}` for

system/alerts.md

@@ -2,6 +2,11 @@
 
 **Status: DRAFT**
 
+The module this page describes was retired from the `rebuild` branch with
+the run model. The [foundation](foundation) page states what replaced it;
+this page stays as the record of the port until the replacement's own page
+supersedes it.
+
 The `alerts` stage builds an Avro container for one finalized difference
 image and records each alert in an outbox. It lands on the pipeline
 repository's `rebuild` branch
@@ -12,7 +17,7 @@ repository's `rebuild` branch
 `pipeline/produceAlertsForProcDate.py` and `alerts/` (schema
 `rapid.v00_04`). Every ported stage minimises differences from `dev` and
 leaves optional features designed in but off by default. The
-[products](products) page fixes the vocabulary; this page states how
+[foundation](foundation) page fixes the vocabulary; this page states how
 the stage meets it and amends two of its paragraphs below.
 
 ## In plain terms
@@ -176,7 +181,7 @@ pruned-set rule above.
 
 "Any result set" is restricted here to the source sets named by the
 association chains (each key's `source_sets`). Every history and
-association read must satisfy the [products](products) page's reading
+association read must satisfy the [foundation](foundation) page's reading
 rule: the source set must be complete, retained, and either the alerts
 run's own or `candidate`/`current` from a selected attempt. A chain
 naming a scratch or unselected source set exits 65. Only the named sets
@@ -300,7 +305,7 @@ cutout are small enough to share a block.
 `UNIQUE (instance, candidate)` is the row's own idempotency key, the
 same pair a rerun's recovery reads back.
 
-This amends the general locator description in [runs.md](runs)'s
+This amends the general locator description in [foundation](foundation)'s
 storage-layout paragraph: the locator is an Avro block plus the record's
 position within it and within the container.
 

system/crossmatch.md

@@ -2,9 +2,14 @@
 
 **Status: DRAFT**
 
+The module this page describes was retired from the `rebuild` branch with
+the run model. The [foundation](foundation) page states what replaced it;
+this page stays as the record of the port until the replacement's own page
+supersedes it.
+
 `crossmatch` assigns newly loaded sources to astronomical objects and
 records the associations in `astroobjects_<field>` and `merges_<field>`.
-The [products](products) page fixes the vocabulary.
+The [foundation](foundation) page fixes the vocabulary.
 
 ## In plain terms
 
@@ -236,7 +241,7 @@ recorded disposition. It does not reuse a different attempt's set if
 that attempt committed rows and then failed, or still has no disposition.
 Those rows stay the run's own, but a fresh attempt writes a fresh set.
 The check uses `db/objects.find_complete_result_set`, joining `attempts`;
-the [runs](runs) page has the general rule. The gap between a committed
+the [foundation](foundation) page has the general rule. The gap between a committed
 write and a published manifest remains a stage-contract matter, not
 closed here.