diff --git a/.agents/agents/catalogue-auditor.agent.md b/.agents/agents/catalogue-auditor.agent.md
index 00d6821..8db4b47 100644
--- a/.agents/agents/catalogue-auditor.agent.md
+++ b/.agents/agents/catalogue-auditor.agent.md
@@ -1,6 +1,6 @@
 ---
 name: Catalogue Auditor
-description: "Specialist for auditing src/src/data/projects.yml against reality: schema validity, documentation configuration, lifecycle stability, metadata, tags, packages, relationships, use-case coverage, and ordering."
+description: "Specialist for auditing every catalogue record under src/src/data/ against reality: schema validity, documentation configuration, lifecycle stability, metadata, tags, packages, relationships, use-case coverage, and ordering."
 tools:
     [
         "search/codebase",
@@ -18,7 +18,7 @@ You are a specialist for auditing (and repairing) the Purview-Dev project catalo
 
 ## Primary objective
 
-Prove that every project defined in `src/src/data/projects.yml` is correct and report the evidence,
+Prove that every project defined in the catalogue (`src/src/data/projects/`) is correct and report the evidence,
 then fix the drift that is unambiguous and safe to fix.
 
 ## Background knowledge
diff --git a/.agents/agents/catalogue-onboarder.agent.md b/.agents/agents/catalogue-onboarder.agent.md
index e0ee261..34425eb 100644
--- a/.agents/agents/catalogue-onboarder.agent.md
+++ b/.agents/agents/catalogue-onboarder.agent.md
@@ -1,6 +1,6 @@
 ---
 name: Catalogue Onboarder
-description: "Specialist for adding a purview-dev (or collaboration) repository to the website catalogue: recon the repository, author the projects.yml record (docs, tags, packages, use cases), integrate it across the site, and prove it with the validation pipeline."
+description: "Specialist for adding a purview-dev (or collaboration) repository to the website catalogue: recon the repository, author the catalogue record (docs, tags, packages, use cases), integrate it across the site, and prove it with the validation pipeline."
 tools:
     [
         "search/codebase",
@@ -19,7 +19,7 @@ You are a specialist for onboarding repositories into the Purview-Dev website ca
 ## Primary objective
 
 Take a repository (`purview-dev/<repo>` or a collaboration repository) and deliver a complete,
-validated integration: a correct `src/src/data/projects.yml` record, a working documentation
+validated integration: a correct catalogue record under `src/src/data/projects/`, a working documentation
 configuration, concrete use cases, tags/metadata, and a green `just validate`.
 
 ## Background knowledge
@@ -41,7 +41,9 @@ The most important rules are:
 - **Tags are GitHub topics**, not manifest fields.
 - **`name` must slugify to `id`** for any project with `docs` (the per-project LLM bundle path).
 - **Every non-archived project needs at least one use case with real code and evidence.**
-- **`status` must match reality** (`stable` / `preview` / `archived`).
+- **`status` must match reality** (`stable` / `preview` / `archived`), and **`experimental: true`** marks
+  an exploratory project — it is orthogonal to `status`, invalid on an archived project, and displayed
+  through `displayStatus()` (ADR 0004).
 - **Never hand-edit generated content** or weaken a check.
 
 ## Workflow
diff --git a/.agents/prompts/add-project.prompt.md b/.agents/prompts/add-project.prompt.md
index d04cd72..8828bfd 100644
--- a/.agents/prompts/add-project.prompt.md
+++ b/.agents/prompts/add-project.prompt.md
@@ -11,6 +11,7 @@ Inputs (fill in before running):
 - Owned by purview-dev? `yes` (catalogue project) / `no` (collaboration)
 - Category (optional — let the recon decide): `<category>`
 - Status (optional — let the release channel decide): `stable | preview | archived`
+- Experimental? `yes` / `no` — `yes` sets the `experimental` flag (ADR 0004); it does not replace `status`
 - Notes: anything known about docs location, package ids, or the story to tell
 
 ## Instructions
@@ -30,7 +31,7 @@ Use the `catalogue-onboarder` agent if it is available.
 
 1. Recon evidence: repository metadata, docs tree/landing page, package ids and channels, release
    channel. Show the commands and their output.
-2. The `projects.yml` record (or `externalProjects` record) added at an unused `order`, with `docs`,
+2. The catalogue record (or `externalProjects` record) added at an unused `order`, with `docs`,
    `packages`, `targetFrameworks`, `install` (only when not plain NuGet), relationships and
    acknowledgments where they genuinely apply.
 3. At least one concrete use case with `code` + `language`, an `evidence` fact, and a `docsPage` that
diff --git a/.agents/prompts/audit-projects.prompt.md b/.agents/prompts/audit-projects.prompt.md
index b90e947..3967def 100644
--- a/.agents/prompts/audit-projects.prompt.md
+++ b/.agents/prompts/audit-projects.prompt.md
@@ -1,6 +1,6 @@
 ---
 mode: agent
-description: Audit every project in projects.yml for correctness (documentation, stability, metadata) and repair the clear drift.
+description: Audit every project in the catalogue for correctness (documentation, stability, metadata) and repair the clear drift.
 ---
 
 # Audit the project catalogue
diff --git a/.agents/skills/add-catalogue-project/SKILL.md b/.agents/skills/add-catalogue-project/SKILL.md
index ee878de..2227250 100644
--- a/.agents/skills/add-catalogue-project/SKILL.md
+++ b/.agents/skills/add-catalogue-project/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: add-catalogue-project
-description: Use when adding a repository to the Purview-Dev website catalogue — recon the repo, author the projects.yml record (docs, packages, tags, use cases), integrate it across the catalogue/docs/releases surfaces, and prove it with the validation pipeline.
+description: Use when adding a repository to the Purview-Dev website catalogue — recon the repo, author the catalogue record (docs, packages, tags, use cases), integrate it across the catalogue/docs/releases surfaces, and prove it with the validation pipeline.
 category: purview-dev-website
 roles:
     - catalogue
@@ -61,8 +61,12 @@ description/topics.
   `source-generation`, `aspire`, `build-tooling`, `developer-tooling`.
 - `status`:
   - `archived` when the repository is archived (GitHub `archived: true`).
-  - `preview` when there is no stable NuGet release, or the tooling is explicitly experimental.
+  - `preview` when there is no stable NuGet release.
   - `stable` only when a stable (non-prerelease) release exists and is recommended for use.
+- `experimental: true` (a flag, not a status value) when the tooling is explicitly an experiment:
+  no compatibility promise, no production support guarantee. Keep `status` as the honest release
+  channel alongside it (`preview` for prerelease-only tooling). See ADR 0004; the project page and
+  every aggregated documentation page then carry an Experimental warning.
 - `id`: lowercase `[a-z0-9-]` slug, normally the repository name.
 - `name`: display name. **It must slugify to `id` when the project has `docs`** (the LLM bundle is
   emitted at `/_llms-txt/<slug(name)>.txt` while the UI links `/_llms-txt/<id>.txt`).
@@ -70,7 +74,7 @@ description/topics.
 
 ## Step 3 — author the record
 
-Add the entry to `src/src/data/projects.yml` (see `project-manifest-reference` for every field):
+Add the entry as `src/src/data/projects/<id>.yml` (see `project-manifest-reference` for every field):
 
 ```yaml
   - id: <slug>
diff --git a/.agents/skills/audit-catalogue-projects/SKILL.md b/.agents/skills/audit-catalogue-projects/SKILL.md
index b122c71..bb3c20d 100644
--- a/.agents/skills/audit-catalogue-projects/SKILL.md
+++ b/.agents/skills/audit-catalogue-projects/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: audit-catalogue-projects
-description: Use when auditing or repairing src/src/data/projects.yml — the invariant checklist for documentation, stability, metadata, tags, packages, relationships, use cases and ordering, plus the findings report format.
+description: Use when auditing or repairing the catalogue records under src/src/data/ — the invariant checklist for documentation, stability, metadata, tags, packages, relationships, use cases and ordering, plus the findings report format.
 category: purview-dev-website
 roles:
     - catalogue
@@ -58,6 +58,9 @@ Related: `project-manifest-reference` (fields and vocabularies), `docs-aggregati
 
 - `archived` repository ⇒ `status: archived`.
 - No stable NuGet release ⇒ not `stable` (`preview`).
+- `experimental: true` is orthogonal to `status`: report `experimental` with `status: stable` as
+  `drift` (the flag says "no support promise" while the channel says "recommended for use"), and
+  `experimental` on an archived project as a `blocker` (the schema rejects it outright).
 - `stable` ⇒ a stable, listed NuGet release exists and the repository is not archived.
 - Deprecated NuGet packages are reported, not silently accepted.
 - A project with `packages: []` is intentional: build tooling consumed as a tool/SDK still declares
@@ -132,5 +135,5 @@ evidence and the guards agree.
   the gap instead.
 - Do not change the schema vocabulary; adding a `status`/`category` value needs an ADR.
 - Do not hand-edit the docs mirror or caches to make the audit pass.
-- If an audit fix changes `projects.yml`, re-run `just check-projects`, `bun run test`, and
+- If an audit fix changes a catalogue record, re-run `just check-projects`, `bun run test`, and
   `just validate` before reporting completion.
diff --git a/.agents/skills/docs-aggregation-rules/SKILL.md b/.agents/skills/docs-aggregation-rules/SKILL.md
index 3dd0b5f..882209b 100644
--- a/.agents/skills/docs-aggregation-rules/SKILL.md
+++ b/.agents/skills/docs-aggregation-rules/SKILL.md
@@ -66,7 +66,8 @@ The wikis of several product repositories are mirrored into `docs/wiki`, so the
 ## Injected front matter (per page)
 
 `title` (first `# H1`, else the slug), `description` (first prose paragraph, ≤160 chars),
-`owners: [purview-dev]`, `status` (the project's status), `lastReviewed`, `sourceProject`,
+`owners: [purview-dev]`, `status` (the project's status), `experimental: true` (written only when
+the catalogue flags the project, ADR 0004), `lastReviewed`, `sourceProject`,
 `sourceRepo`, `projectName`, `sourcePath`, `editUrl`, `tags` (the repository's GitHub **topics**,
 absent when there are none), and `sidebar.label`/`sidebar.order`.
 
diff --git a/.agents/skills/github-repo-metadata/SKILL.md b/.agents/skills/github-repo-metadata/SKILL.md
index 259991b..16df5a6 100644
--- a/.agents/skills/github-repo-metadata/SKILL.md
+++ b/.agents/skills/github-repo-metadata/SKILL.md
@@ -67,7 +67,7 @@ Discussions on an organisation repository requires organisation permission; repo
   four chips are meaningful (cards render `tags.slice(0, 4)`).
 - Prefer ecosystem-standard names (`dotnet`, `csharp`, `nuget`, `opentelemetry`) so cross-repo
   searches behave predictably.
-- Topics are the **only** way tags reach the site. There is no `tags` field in `projects.yml` — do
+- Topics are the **only** way tags reach the site. There is no `tags` field in a catalogue record — do
   not add one.
 
 ## Stability signals to check against `status`
@@ -77,6 +77,7 @@ Discussions on an organisation repository requires organisation permission; repo
 | `archived: true` | `status` must be `archived` (and `supersededBy` when a successor exists) |
 | No stable release, only `-prerelease.N` tags | `preview` at most |
 | Latest NuGet version is stable and listed | `stable` is allowed |
+| The README/repository presents the project as an experiment | Set `experimental: true` (it does not replace `status`, which stays the release channel) |
 | NuGet `deprecated: true` | Report as `drift`/`upstream`; a deprecated package should not front a `stable` project without explanation |
 | `default_branch` is not `main` | Docs aggregation produces nothing — a blocker for any project with `docs` |
 
diff --git a/.agents/skills/project-manifest-reference/SKILL.md b/.agents/skills/project-manifest-reference/SKILL.md
index 0bfb0c1..21762d2 100644
--- a/.agents/skills/project-manifest-reference/SKILL.md
+++ b/.agents/skills/project-manifest-reference/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: project-manifest-reference
-description: Field-by-field reference for src/src/data/projects.yml (schema vocabulary, defaults, loader-enforced rules, and the invariants the site build depends on). Use whenever authoring or reviewing a catalogue record.
+description: Field-by-field reference for the catalogue records under src/src/data/projects/ (schema vocabulary, defaults, loader-enforced rules, and the invariants the site build depends on). Use whenever authoring or reviewing a catalogue record.
 category: purview-dev-website
 roles:
     - catalogue
@@ -13,7 +13,8 @@ tags:
 
 # project-manifest-reference Skill
 
-The catalogue is `src/src/data/projects.yml`, typed by `src/src/lib/manifest/schema.ts` and validated
+The catalogue is one file per project under `src/src/data/projects/` (plus
+`src/src/data/external-projects.yml` for collaborations), typed by `src/src/lib/manifest/schema.ts` and validated
 by `src/src/lib/manifest/load.ts`. `$schema: ../lib/manifest/schema.ts` is the first line of the file.
 
 ## Vocabularies (do not invent values)
@@ -22,10 +23,12 @@ by `src/src/lib/manifest/load.ts`. `$schema: ../lib/manifest/schema.ts` is the f
 | --- | --- |
 | `category` | `application-framework`, `validation`, `observability`, `source-generation`, `aspire`, `build-tooling`, `developer-tooling` |
 | `status` | `stable`, `preview`, `archived` |
+| `experimental` | boolean flag, default `false` — orthogonal to `status` (ADR 0004); invalid with `status: archived` |
 | `install` | `nuget` (default), `msbuild-sdk`, `dotnet-tool` |
 | `useCases[].audience` | `developer`, `team-lead`, `architect`, `contributor` (labels: Developer, Team lead, Architect, Contributor) |
 
-Adding a value to any of these lists is a schema change and requires an ADR.
+Adding a value to any of these lists is a schema change and requires an ADR. `experimental` is a
+**flag, not a status value**: it never replaces `status`, which stays the project's release channel.
 
 ## `projects[]` fields
 
@@ -41,6 +44,7 @@ Adding a value to any of these lists is a schema change and requires an ADR.
 | `repository` | yes | `owner/repository`; **`owner` must be `purview-dev`** for `projects[]` |
 | `category` | yes | See vocabulary |
 | `status` | yes | See vocabulary |
+| `experimental` | no | Default `false`; marks an exploratory project (unstable API, no support promise). Orthogonal to `status`; invalid with `status: archived`. Displayed as its own status via `displayStatus()` |
 | `featured` | no | Default `false`; shown prominently on the home page |
 | `order` | no | Default `1000`; projects are sorted ascending; keep values unique |
 | `docs` | no | See below |
@@ -76,12 +80,13 @@ Adding a value to any of these lists is a schema change and requires an ADR.
 2. `projects[].repository.split('/')[0]` must equal `purview-dev`.
 3. `related`, `supersedes`, and `supersededBy` must all reference existing project ids.
 4. A NuGet package id may be declared by **exactly one** project.
-5. The returned list is sorted by `order` ascending.
+5. `experimental: true` is rejected when `status` is `archived` (schema refinement).
+6. The returned list is sorted by `order` ascending.
 
 ## Defaults applied by the loader
 
 `featured: false`, `order: 1000`, `packages: []`, `related: []`, `useCases: []`,
-`acknowledgments: []`, `discussions: false`, `install: 'nuget'`. Derived values (`repoOwner`,
+`acknowledgments: []`, `discussions: false`, `install: 'nuget'`, `experimental: false`. Derived values (`repoOwner`,
 `repoName`, `sourceUrl`, `issuesUrl`, `discussionsUrl`, `changelogUrl`, `releasesUrl`) are computed,
 never authored.
 
diff --git a/.agents/skills/site-validation-loop/SKILL.md b/.agents/skills/site-validation-loop/SKILL.md
index 822b852..50763bf 100644
--- a/.agents/skills/site-validation-loop/SKILL.md
+++ b/.agents/skills/site-validation-loop/SKILL.md
@@ -35,7 +35,7 @@ tags:
 
 ## The catalogue guard (`just check-projects`)
 
-`src/scripts/check-projects.ts` validates `projects.yml` against the generated data (offline,
+`src/scripts/check-projects.ts` validates the catalogue records (`src/src/data/`) against the generated data (offline,
 deterministic). It fails the build on:
 
 - ids/orders duplicated, `order` not a unique integer, `name` not slugifying to `id` for documented
diff --git a/.agents/skills/use-case-authoring/SKILL.md b/.agents/skills/use-case-authoring/SKILL.md
index d634c97..84279ef 100644
--- a/.agents/skills/use-case-authoring/SKILL.md
+++ b/.agents/skills/use-case-authoring/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: use-case-authoring
-description: Use when writing or reviewing useCases in projects.yml — the ADR 0002 rules for audience-tagged, concrete, evidence-backed examples with short code snippets and resolvable documentation deep links.
+description: Use when writing or reviewing useCases in the catalogue records — the ADR 0002 rules for audience-tagged, concrete, evidence-backed examples with short code snippets and resolvable documentation deep links.
 category: purview-dev-website
 roles:
     - catalogue
@@ -14,7 +14,7 @@ tags:
 # use-case-authoring Skill
 
 Use cases are the "what does it actually do for me" evidence on the home page, on each project page,
-and on `/use-cases/`. They are authored in `src/src/data/projects.yml` and validated by the manifest
+and on `/use-cases/`. They are authored in the catalogue records (`src/src/data/projects/<id>.yml`) and validated by the manifest
 schema. The governing decision is `docs/decisions/0002-concrete-use-cases.md`.
 
 ## Shape
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
index decce35..fdf390c 100644
--- a/.github/copilot-instructions.md
+++ b/.github/copilot-instructions.md
@@ -16,7 +16,7 @@ package is `src/`.
 - Treat `just validate` as the definition of done. It chains format-check, lint, typecheck, unit
   tests, asset checks, build, link crawl, generated-output checks, built-output tests, and the
   catalogue guard (`just check-projects`).
-- Edit the catalogue in `src/src/data/projects.yml` only, and keep every invariant listed in
+- Edit the catalogue under `src/src/data/` only (one file per project, plus `external-projects.yml`), and keep every invariant listed in
   `AGENTS.md` (unique ids/orders/packages, `name` slugifying to `id` for documented projects, at
   least one use case per non-archived project, `code` paired with `language`, resolvable `docsPage`).
 - Keep documentation where it lives (the product repository). This site aggregates it at build time.
@@ -33,12 +33,15 @@ package is `src/`.
   `src/src/lib/manifest/schema.ts`.
 - Never claim a project is `stable` without a stable NuGet release, or leave a project `stable`
   while its repository is archived.
+- Never derive a project's displayed status outside `displayStatus()` (`src/src/lib/status.ts`):
+  `experimental: true` is an intent flag orthogonal to `status` (ADR 0004) and is invalid with
+  `status: archived`.
 
 ## Task routing
 
 - Adding a project → `.agents/agents/catalogue-onboarder.agent.md` and
   `.agents/skills/add-catalogue-project/SKILL.md`.
-- Auditing/fixing `projects.yml` → `.agents/agents/catalogue-auditor.agent.md` and
+- Auditing/fixing the catalogue → `.agents/agents/catalogue-auditor.agent.md` and
   `.agents/skills/audit-catalogue-projects/SKILL.md`.
 - Any other change → `.agents/` holds the manifest reference, docs-aggregation rules, use-case
   authoring rules, repo-metadata guidance, and the validation loop.
diff --git a/AGENTS.md b/AGENTS.md
index a4eca3a..8d0f5c9 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -10,7 +10,8 @@ Two agent tasks recur here, and both have a dedicated agent plus skills under `.
 
 1. **Add a project** — given a `purview-dev/<repo>` (or a collaboration repository), build its
    documentation, use cases, tags and metadata so it is fully integrated into the site.
-2. **Audit the catalogue** — prove that every project defined in `src/src/data/projects.yml` is
+2. **Audit the catalogue** — prove that every project defined in `src/src/data/projects/` (one file per project, plus
+   `external-projects.yml` for collaborations) is
    correct: documentation configuration, lifecycle stability, metadata and relationships.
 
 ## Technology and tooling context
@@ -50,7 +51,7 @@ merge". `just check-projects` is part of that chain and fails the build on catal
 
 ## Ecosystem model — what "a project" means here
 
-- `projects:` in `src/src/data/projects.yml` are Purview-owned catalogue entries. Their `repository`
+- `projects:` entries — one file per project under `src/src/data/projects/` — are Purview-owned catalogue entries. Their `repository`
   **must** be `purview-dev/<repo>` (enforced by the loader).
 - `externalProjects:` are collaborations the organisation contributes to but does not own (for
   example `likec4/likec4`). They link out to their own site/repository: no documentation
@@ -64,7 +65,7 @@ merge". `just check-projects` is part of that chain and fails the build on catal
 
 1. **Never weaken a check to make a change pass.** Fix the data or the implementation. (ADR 0001.)
 2. **Never hand-edit generated content** (`src/src/content/docs/**`, `src/.cache/**`, `src/dist/**`).
-3. **Any edit to `projects.yml` must keep the catalogue invariants.** These are enforced by
+3. **Any edit to a project record under `src/src/data/` must keep the catalogue invariants.** These are enforced by
    `loadProjects()` (schema, ownership, relationships, package uniqueness) and by
    `just check-projects`:
    - `id` is a lowercase `[a-z0-9-]` slug; `repository` is `owner/repository` and must be
@@ -80,6 +81,10 @@ merge". `just check-projects` is part of that chain and fails the build on catal
    - `related`, `supersedes`, `supersededBy` must reference known ids.
    - `status` must match reality: an archived repository is `archived`; prerelease-only tooling is
      `preview`; a project with a stable release is `stable`.
+   - `experimental: true` marks a project whose API and packaging may change without notice
+     (ADR 0004). It is orthogonal to `status` — which stays the release channel — it is invalid on an
+     `archived` project, and it never hides a project: it adds a warning badge and a notice to the
+     catalogue and to every aggregated documentation page.
 4. **Run the validation loop before finishing** — at minimum `just check-projects`,
    `bun run typecheck`, `bun run test`; run the full `just validate` for anything that touches the
    build, data aggregation, or rendering.
@@ -111,7 +116,7 @@ Do not assume this file contains everything; consult `.agents/` while planning.
 
 | Concern | Location |
 | --- | --- |
-| Catalogue manifest | `src/src/data/projects.yml` |
+| Catalogue manifest | `src/src/data/projects/<id>.yml` (one per project) + `src/src/data/external-projects.yml` |
 | Manifest schema / loader | `src/src/lib/manifest/{schema,load}.ts` |
 | Docs aggregation | `src/src/lib/docs/aggregate.ts` (+ `frontmatter`, `links`, `sidebar`, `staleness`) |
 | Release data | `src/src/lib/releases/*`, `src/scripts/fetch-releases.ts` |
diff --git a/README.md b/README.md
index 5622530..9bc9e6f 100644
--- a/README.md
+++ b/README.md
@@ -38,7 +38,8 @@ purview-dev/                  # workspace root
     ├── src/
     │   ├── content.config.ts # Starlight docs collection schema
     │   ├── content/docs/     # GENERATED documentation mirror (gitignored)
-    │   ├── data/projects.yml # Typed, validated project catalogue manifest
+    │   ├── data/projects/    # Typed, validated catalogue: one file per project
+    │   ├── data/external-projects.yml # Collaborations the organisation does not own
     │   ├── lib/              # manifest, releases, docs, urls, site constants
     │   ├── components/       # shared chrome, Starlight overrides, islands
     │   ├── layouts/          # SiteLayout.astro (marketing pages)
@@ -165,7 +166,7 @@ just dev
 ```
 
 The dev server starts after a data sync. Edit `src/src/pages/` for marketing
-pages and `src/src/data/projects.yml` for catalogue content. Documentation pages
+pages and `src/src/data/projects/<id>.yml` for catalogue content. Documentation pages
 are generated under `src/src/content/docs/` and should not be edited by hand —
 change the source repository instead and re-run `just data-sync`.
 
@@ -190,16 +191,18 @@ generated copies.
 
 ## Project catalogue
 
-`src/src/data/projects.yml` is the single source of truth for the catalogue. It
+`src/src/data/projects/<id>.yml` (one file per project, plus
+`src/src/data/external-projects.yml` for collaborations) is the single source of truth for the catalogue. It
 is validated at build time by a typed Zod schema
 (`src/src/lib/manifest/schema.ts`). Validation failures report the source file,
 the offending property, the expected shape, and a remediation hint.
 
 ### Adding a new Purview-Dev project
 
-1. Add a record to `src/src/data/projects.yml` with a unique `id`, `name`,
+1. Add a record at `src/src/data/projects/<id>.yml` with a unique `id`, `name`,
    `shortDescription`, `description`, `repository` (a purview-dev repo),
-   `category`, `status`, and optional `order`.
+   `category`, `status`, and optional `order`. Set `experimental: true` for an
+   exploratory project — it is a flag orthogonal to `status` (ADR 0004).
 2. Declare its NuGet packages under `packages` — every package id must belong to
    exactly one project.
 3. Declare documentation under `docs`:
@@ -261,8 +264,8 @@ Documentation is owned by each product repository and presented through this
 portal. The aggregation (`src/lib/docs/aggregate.ts`) fetches each project's
 docs (in-repo `docs/`, GitHub wikis via a shallow clone, or the README), then:
 
-- injects front matter (title, description, owners, status, last review date,
-  source repository, edit URL),
+- injects front matter (title, description, owners, status, the experimental flag,
+  last review date, source repository, edit URL),
 - selects the page served at `/docs/<project>/` from `docs.rootPage`, otherwise
   the conventional `index.md`/`Home.md`/`readme.md`, otherwise the repository
   README when `readmeAsIndex: true`,
@@ -337,7 +340,7 @@ auditing the ones already published (ADR 0003):
 | Task | Agent | Skills |
 | ---- | ----- | ------ |
 | Add and integrate a repository | `.agents/agents/catalogue-onboarder.agent.md` | `add-catalogue-project`, `project-manifest-reference`, `docs-aggregation-rules`, `use-case-authoring`, `github-repo-metadata` |
-| Audit and repair `projects.yml` | `.agents/agents/catalogue-auditor.agent.md` | `audit-catalogue-projects`, plus the reference skills |
+| Audit and repair the catalogue | `.agents/agents/catalogue-auditor.agent.md` | `audit-catalogue-projects`, plus the reference skills |
 
 `AGENTS.md` holds the repository context and the mandatory rules, `.github/copilot-instructions.md`
 the always-on subset, and `.agents/prompts/` provides `add-project.prompt.md` and
@@ -347,8 +350,10 @@ The deterministic half of the guarantee is `just check-projects`
 (`src/scripts/check-projects.ts`), which runs inside `just validate` and fails on catalogue drift:
 schema failures, documentation that does not resolve, missing or malformed use cases, unpublished or
 duplicated packages, a `status` that contradicts the repository's archived flag or the NuGet release
-channel, missing repository topics (the site's tags), and a documented project whose default branch
-is not `main`. Quality observations that cannot be decided mechanically are printed as warnings.
+channel, an `experimental` flag on an archived project, missing repository topics (the site's tags),
+and a documented project whose default branch is not `main`. Quality observations that cannot be
+decided mechanically are printed as warnings — including `experimental` paired with a stable release
+channel.
 
 ## Site versioning and releases
 
diff --git a/docs/decisions/0004-experimental-projects.md b/docs/decisions/0004-experimental-projects.md
new file mode 100644
index 0000000..565e838
--- /dev/null
+++ b/docs/decisions/0004-experimental-projects.md
@@ -0,0 +1,93 @@
+# ADR 0004 — Mark exploratory projects with an orthogonal `experimental` flag
+
+- Status: accepted
+- Date: 2026-09-30
+
+## Context
+
+The catalogue's `status` field answers one question: which release channel does a project publish on,
+and is it still maintained? `stable` means a stable release exists and the project is recommended;
+`preview` means prereleases only; `archived` means the repository is archived and the project is no
+longer developed. `src/scripts/check-projects.ts` ties that field to observable reality — the GitHub
+`archived` flag and the NuGet version list — so it cannot be used as free-text marketing.
+
+There is a second, independent thing a reader needs to know: **intent**. A project can be entirely
+exploratory — "the API, defaults and packaging will change between prereleases, and there is no
+production support guarantee" — while being honestly described by `preview`: it is actively
+developed, publishes prereleases, and has documentation. The first project in this situation
+(`containers`, whose README opens with an explicit *Experimental* caveat) would be *described*
+accurately by `preview` but not *warned about* at all.
+
+Adding a fourth `status` value (`experimental`) was considered and rejected. It would force one
+field to answer two orthogonal questions, so the guard would have to decide what
+"`experimental` with a stable NuGet version" and "`experimental` on an archived repository" mean,
+and every vocabulary-enumerating surface would inherit a four-value lifecycle. The release channel
+and the maturity promise genuinely are different axes, so they are modelled as different fields.
+
+## Decisions
+
+### 1. `experimental` is an optional boolean on `projects[]`
+
+Every catalogue record (`src/src/data/projects/<id>.yml`, see ADR 0005) gains an optional
+`experimental: true` (default `false`, applied by the loader). It is only valid on `projects[]` —
+collaborations in `externalProjects.yml` are not ours to label. `status` keeps its existing
+three-value vocabulary and its existing meaning; no value is added or redefined.
+
+### 2. The two axes collapse into one *display* status in exactly one place
+
+`src/src/lib/status.ts` owns `displayStatus()`, which resolves `{ status, experimental }` into
+`stable | preview | experimental | archived` for presentation. The precedence is deliberate:
+
+- `archived` wins over everything (an archived project is never presented as an experiment);
+- otherwise the `experimental` flag wins over the release channel, because the warning is the point.
+
+Every surface that renders a badge, filters, or labels a sidebar topic calls that helper rather than
+re-deriving the rule, so the catalogue card, project page, home-page version snapshot, docs page,
+docs sidebar topic and catalogue filter cannot disagree.
+
+### 3. `experimental: true` with `status: archived` is a schema error
+
+The combination is contradictory: an archived repository is not an ongoing experiment. It is
+rejected by a refinement in the manifest schema (`src/src/lib/manifest/schema.ts`), so it fails at
+load time for every consumer — the build, the guard, and the unit tests — with a remediation
+message rather than at render time.
+
+### 4. `experimental` with a stable release is legal but reported
+
+The flag is an intent marker, not a release-channel marker, so the guard does not invent a rule such
+as "experimental must not have a stable version": a project may legitimately ship `1.x` while still
+being flagged as an experiment. `just check-projects` emits a **warning** (not a failure) so the
+combination is a conscious decision rather than an oversight.
+
+### 5. Experimental projects are surfaced, not hidden
+
+Only `archived` removes a project from the catalogue, the documentation portal, the sidebar topics
+and the per-project LLM bundles. An experimental project with documentation is aggregated, listed,
+indexed by `/use-cases/`, included in `/releases/`, and gets its `/_llms-txt/<id>.txt` bundle like
+any other project. Discoverability with an explicit warning is the point of the flag.
+
+### 6. The flag is presented on the project page and on every documentation page
+
+A distinct badge (`.pv-status-experimental`) is not sufficient on its own, so the warning is also
+stated in prose: the project page renders an "Experimental" notice above the content, and
+`src/src/components/starlight/PageTitle.astro` renders one on every aggregated documentation page,
+driven by the injected front matter. The aggregated docs mirror stays generated — the notice is
+injected by the site, never hand-authored into `src/src/content/docs/**`.
+
+### 7. Promotion is a manifest edit
+
+Removing `experimental: true` (and correcting `status`) is the promotion mechanism; nothing else has
+to change for a project to graduate. An experimental project is expected to end in one of the two
+defined states — promoted, or `archived`.
+
+## Consequences
+
+- `status` stays a closed three-value vocabulary tied to the release channel, and the guard's
+  existing rules (`archived` ⇔ repository archived, `stable` ⇒ stable NuGet release) are untouched.
+- Two axes create combinations that a single field could not: the schema forbids the contradictory
+  one and warns about the ambiguous one, rather than leaving them undefined.
+- The documentation front matter carries the raw pair (`status` plus `experimental`) and not a
+  pre-collapsed value, so the manifest remains the only place the vocabulary is defined; the
+  display collapse happens in the site components through `displayStatus()`.
+- Adding an experimental project still requires one concrete use case (ADR 0002 applies to every
+  non-archived project).
diff --git a/docs/decisions/0005-one-file-per-project.md b/docs/decisions/0005-one-file-per-project.md
new file mode 100644
index 0000000..2489f97
--- /dev/null
+++ b/docs/decisions/0005-one-file-per-project.md
@@ -0,0 +1,68 @@
+# ADR 0005 — One file per project for the catalogue manifest
+
+- Status: accepted
+- Date: 2026-09-30
+
+## Context
+
+ADR 0001 established a single YAML manifest, `src/src/data/projects.yml`, as the source of truth for
+the catalogue. By the time this was written it held twelve projects and one collaboration in 1,037
+lines / 47 KB, and it grows by roughly 80–140 lines per project — one project per pull request. Every
+addition appends to the same region of the same file, so two concurrent catalogue pull requests
+conflict almost by construction, and `git log`/`blame` attribute a change to "the manifest" rather
+than to a project.
+
+The decision recorded here is not that the single manifest was wrong. It is that the *granularity of
+the file* no longer matches the granularity of the change.
+
+## Decisions
+
+### 1. `src/src/data/projects/<id>.yml`, one file per project
+
+The file name is the project id. Each file holds the project record itself — no `projects:` wrapper —
+so the file *is* the project. `$schema: ../../lib/manifest/schema.ts` opens the file, as before.
+
+### 2. Collaborations stay in one file: `src/src/data/external-projects.yml`
+
+`externalProjects:` remains a list in a single file. It is small, it changes rarely, and the entries
+are not ours to grow.
+
+### 3. The loader assembles the files; the validation does not move
+
+`readRawManifest()` reads the directory (sorted by file name, so the result is deterministic whatever
+order the filesystem reports) plus the collaborations file, and returns the same raw shape as
+before (`{ projects, externalProjects }`). `parseManifest()` then validates that shape exactly as it
+did, so every existing invariant — purview-dev ownership, unique ids, known relationship targets,
+package uniqueness — and the `just check-projects` guard are untouched. Reading and validating stay
+separate concerns, and `parseManifest()` remains the single validation entry point (still unit
+testable with inline objects).
+
+### 4. A schema failure names the project, not the array position
+
+Splitting the file would otherwise degrade schema errors to `projects[3].name`, which the author has
+to map back to a file. `parseManifest()` resolves the index to the record's `id`, so messages stay
+`projects[<id>].name`.
+
+### 5. The `$schema` hint is treated as a hint
+
+A project record may declare `$schema`, and the loader strips it before resolution: it is an editor
+affordance, never part of the domain type. `manifestSchema.projects` is defaulted to `[]` so the
+collaborations file is valid on its own. The hint is advisory — there is no editor schema wiring in
+this repository, and the enforcing validation is `loadProjects()` plus `just check-projects`.
+
+### 6. The move was made by construction, not by re-serialisation
+
+The split was a text transform that removed only the list indentation, and it was proved by
+comparing the fully resolved catalogue before and after the change: byte-identical. Re-serialising
+the YAML would have reformatted every hand-wrapped block scalar and code sample.
+
+## Consequences
+
+- Adding a project is one new file: unconflicted in review, and correctly attributed by
+  `git log`/`blame`.
+- ADRs 0001–0004 reference `src/src/data/projects.yml` for the manifest; read those paths as this
+  layout.
+- Cross-file invariants (duplicate `id`, duplicate `order`, a package id declared twice) can no
+  longer be seen by reading one file, so the guard matters more rather than less.
+  `just check-projects` is the authority for them and is unchanged.
+- The migration was a fixed cost (loader plus documentation references); it does not recur.
diff --git a/src/astro.config.ts b/src/astro.config.ts
index 89c418c..75f2e1e 100644
--- a/src/astro.config.ts
+++ b/src/astro.config.ts
@@ -13,6 +13,7 @@ import { readDocsManifest } from './src/lib/docs/aggregate';
 import { buildProjectItems } from './src/lib/docs/sidebar';
 import { loadProjects } from './src/lib/manifest/load';
 import { SITE, BRAND } from './src/lib/site';
+import { displayStatus, type DisplayStatus } from './src/lib/status';
 import { absoluteUrl } from './src/lib/urls';
 
 const projects = loadProjects();
@@ -32,13 +33,22 @@ const docsSets = docsProjects.map((project) => ({
   description: project.shortDescription,
   paths: [`docs/${project.id}/**`],
 }));
-const previewBadge = { text: 'Preview', variant: 'caution' } as const;
+/**
+ * Sidebar badges for the two "not for production" states. The value comes from
+ * the shared display status (ADR 0004), so the docs sidebar, the project page
+ * and the catalogue filter cannot disagree about how a project is flagged.
+ */
+const topicBadges: Partial<Record<DisplayStatus, { text: string; variant: 'caution' | 'danger' }>> =
+  {
+    preview: { text: 'Preview', variant: 'caution' },
+    experimental: { text: 'Experimental', variant: 'danger' },
+  };
 const sidebarTopics = [
   { label: 'Documentation home', link: '/docs/' },
   ...docsProjects.map((project) => ({
     label: project.name,
     link: `/docs/${project.id}/`,
-    badge: project.status === 'preview' ? previewBadge : undefined,
+    badge: topicBadges[displayStatus(project)],
     items: buildProjectItems(project, docsManifest),
   })),
 ];
diff --git a/src/fixtures/github/releases/containers.json b/src/fixtures/github/releases/containers.json
new file mode 100644
index 0000000..d10c256
--- /dev/null
+++ b/src/fixtures/github/releases/containers.json
@@ -0,0 +1,131 @@
+[
+  {
+    "url": "https://api.github.com/repos/purview-dev/containers/releases/401620214",
+    "assets_url": "https://api.github.com/repos/purview-dev/containers/releases/401620214/assets",
+    "upload_url": "https://uploads.github.com/repos/purview-dev/containers/releases/401620214/assets{?name,label}",
+    "html_url": "https://github.com/purview-dev/containers/releases/tag/v1.0.0-prerelease.3",
+    "id": 401620214,
+    "author": {
+      "login": "github-actions[bot]",
+      "id": 41898282,
+      "node_id": "MDM6Qm90NDE4OTgyODI=",
+      "avatar_url": "https://avatars.githubusercontent.com/in/15368?v=4",
+      "gravatar_id": "",
+      "url": "https://api.github.com/users/github-actions%5Bbot%5D",
+      "html_url": "https://github.com/apps/github-actions",
+      "followers_url": "https://api.github.com/users/github-actions%5Bbot%5D/followers",
+      "following_url": "https://api.github.com/users/github-actions%5Bbot%5D/following{/other_user}",
+      "gists_url": "https://api.github.com/users/github-actions%5Bbot%5D/gists{/gist_id}",
+      "starred_url": "https://api.github.com/users/github-actions%5Bbot%5D/starred{/owner}{/repo}",
+      "subscriptions_url": "https://api.github.com/users/github-actions%5Bbot%5D/subscriptions",
+      "organizations_url": "https://api.github.com/users/github-actions%5Bbot%5D/orgs",
+      "repos_url": "https://api.github.com/users/github-actions%5Bbot%5D/repos",
+      "events_url": "https://api.github.com/users/github-actions%5Bbot%5D/events{/privacy}",
+      "received_events_url": "https://api.github.com/users/github-actions%5Bbot%5D/received_events",
+      "type": "Bot",
+      "user_view_type": "public",
+      "site_admin": false
+    },
+    "node_id": "RE_kwDOU0fn4M4X8Dz2",
+    "tag_name": "v1.0.0-prerelease.3",
+    "target_commitish": "main",
+    "name": "v1.0.0-prerelease.3",
+    "draft": false,
+    "immutable": false,
+    "prerelease": true,
+    "created_at": "2026-10-02T07:36:52Z",
+    "updated_at": "2026-10-02T07:38:44Z",
+    "published_at": "2026-10-02T07:38:44Z",
+    "assets": [],
+    "tarball_url": "https://api.github.com/repos/purview-dev/containers/tarball/v1.0.0-prerelease.3",
+    "zipball_url": "https://api.github.com/repos/purview-dev/containers/zipball/v1.0.0-prerelease.3",
+    "body": "## What's Changed\n* chore: add MIT license file by @kieronlanning in https://github.com/purview-dev/containers/pull/4\n* docs: updated docs by @kieronlanning in https://github.com/purview-dev/containers/pull/5\n* docs: updated docs by @kieronlanning in https://github.com/purview-dev/containers/pull/6\n\n\n**Full Changelog**: https://github.com/purview-dev/containers/compare/v1.0.0-prerelease.2...v1.0.0-prerelease.3",
+    "mentions_count": 1
+  },
+  {
+    "url": "https://api.github.com/repos/purview-dev/containers/releases/401397482",
+    "assets_url": "https://api.github.com/repos/purview-dev/containers/releases/401397482/assets",
+    "upload_url": "https://uploads.github.com/repos/purview-dev/containers/releases/401397482/assets{?name,label}",
+    "html_url": "https://github.com/purview-dev/containers/releases/tag/v1.0.0-prerelease.2",
+    "id": 401397482,
+    "author": {
+      "login": "github-actions[bot]",
+      "id": 41898282,
+      "node_id": "MDM6Qm90NDE4OTgyODI=",
+      "avatar_url": "https://avatars.githubusercontent.com/in/15368?v=4",
+      "gravatar_id": "",
+      "url": "https://api.github.com/users/github-actions%5Bbot%5D",
+      "html_url": "https://github.com/apps/github-actions",
+      "followers_url": "https://api.github.com/users/github-actions%5Bbot%5D/followers",
+      "following_url": "https://api.github.com/users/github-actions%5Bbot%5D/following{/other_user}",
+      "gists_url": "https://api.github.com/users/github-actions%5Bbot%5D/gists{/gist_id}",
+      "starred_url": "https://api.github.com/users/github-actions%5Bbot%5D/starred{/owner}{/repo}",
+      "subscriptions_url": "https://api.github.com/users/github-actions%5Bbot%5D/subscriptions",
+      "organizations_url": "https://api.github.com/users/github-actions%5Bbot%5D/orgs",
+      "repos_url": "https://api.github.com/users/github-actions%5Bbot%5D/repos",
+      "events_url": "https://api.github.com/users/github-actions%5Bbot%5D/events{/privacy}",
+      "received_events_url": "https://api.github.com/users/github-actions%5Bbot%5D/received_events",
+      "type": "Bot",
+      "user_view_type": "public",
+      "site_admin": false
+    },
+    "node_id": "RE_kwDOU0fn4M4X7Nbq",
+    "tag_name": "v1.0.0-prerelease.2",
+    "target_commitish": "main",
+    "name": "v1.0.0-prerelease.2",
+    "draft": false,
+    "immutable": false,
+    "prerelease": true,
+    "created_at": "2026-10-01T22:15:33Z",
+    "updated_at": "2026-10-01T22:17:22Z",
+    "published_at": "2026-10-01T22:17:22Z",
+    "assets": [],
+    "tarball_url": "https://api.github.com/repos/purview-dev/containers/tarball/v1.0.0-prerelease.2",
+    "zipball_url": "https://api.github.com/repos/purview-dev/containers/zipball/v1.0.0-prerelease.2",
+    "body": "## What's Changed\n* Docs update by @kieronlanning in https://github.com/purview-dev/containers/pull/2\n* Portable WSLC backend for net10.0, Testcontainers-parity connection strings, repo renamed to containers by @kieronlanning in https://github.com/purview-dev/containers/pull/3\n\n\n**Full Changelog**: https://github.com/purview-dev/containers/compare/v1.0.0-prerelease.1...v1.0.0-prerelease.2",
+    "mentions_count": 1
+  },
+  {
+    "url": "https://api.github.com/repos/purview-dev/containers/releases/400244584",
+    "assets_url": "https://api.github.com/repos/purview-dev/containers/releases/400244584/assets",
+    "upload_url": "https://uploads.github.com/repos/purview-dev/containers/releases/400244584/assets{?name,label}",
+    "html_url": "https://github.com/purview-dev/containers/releases/tag/v1.0.0-prerelease.1",
+    "id": 400244584,
+    "author": {
+      "login": "github-actions[bot]",
+      "id": 41898282,
+      "node_id": "MDM6Qm90NDE4OTgyODI=",
+      "avatar_url": "https://avatars.githubusercontent.com/in/15368?v=4",
+      "gravatar_id": "",
+      "url": "https://api.github.com/users/github-actions%5Bbot%5D",
+      "html_url": "https://github.com/apps/github-actions",
+      "followers_url": "https://api.github.com/users/github-actions%5Bbot%5D/followers",
+      "following_url": "https://api.github.com/users/github-actions%5Bbot%5D/following{/other_user}",
+      "gists_url": "https://api.github.com/users/github-actions%5Bbot%5D/gists{/gist_id}",
+      "starred_url": "https://api.github.com/users/github-actions%5Bbot%5D/starred{/owner}{/repo}",
+      "subscriptions_url": "https://api.github.com/users/github-actions%5Bbot%5D/subscriptions",
+      "organizations_url": "https://api.github.com/users/github-actions%5Bbot%5D/orgs",
+      "repos_url": "https://api.github.com/users/github-actions%5Bbot%5D/repos",
+      "events_url": "https://api.github.com/users/github-actions%5Bbot%5D/events{/privacy}",
+      "received_events_url": "https://api.github.com/users/github-actions%5Bbot%5D/received_events",
+      "type": "Bot",
+      "user_view_type": "public",
+      "site_admin": false
+    },
+    "node_id": "RE_kwDOU0fn4M4X2z9o",
+    "tag_name": "v1.0.0-prerelease.1",
+    "target_commitish": "main",
+    "name": "v1.0.0-prerelease.1",
+    "draft": false,
+    "immutable": false,
+    "prerelease": true,
+    "created_at": "2026-09-30T16:38:46Z",
+    "updated_at": "2026-09-30T16:41:23Z",
+    "published_at": "2026-09-30T16:41:23Z",
+    "assets": [],
+    "tarball_url": "https://api.github.com/repos/purview-dev/containers/tarball/v1.0.0-prerelease.1",
+    "zipball_url": "https://api.github.com/repos/purview-dev/containers/zipball/v1.0.0-prerelease.1",
+    "body": "## What's Changed\n* Develop by @kieronlanning in https://github.com/purview-dev/wsl-testcontainers/pull/1\n\n## New Contributors\n* @kieronlanning made their first contribution in https://github.com/purview-dev/wsl-testcontainers/pull/1\n\n**Full Changelog**: https://github.com/purview-dev/wsl-testcontainers/commits/v1.0.0-prerelease.1",
+    "mentions_count": 1
+  }
+]
diff --git a/src/fixtures/github/repos/containers.json b/src/fixtures/github/repos/containers.json
new file mode 100644
index 0000000..9a73c5b
--- /dev/null
+++ b/src/fixtures/github/repos/containers.json
@@ -0,0 +1,198 @@
+{
+  "id": 1397221344,
+  "node_id": "R_kgDOU0fn4A",
+  "name": "containers",
+  "full_name": "purview-dev/containers",
+  "private": false,
+  "owner": {
+    "login": "purview-dev",
+    "id": 96894084,
+    "node_id": "O_kgDOBcZ8hA",
+    "avatar_url": "https://avatars.githubusercontent.com/u/96894084?v=4",
+    "gravatar_id": "",
+    "url": "https://api.github.com/users/purview-dev",
+    "html_url": "https://github.com/purview-dev",
+    "followers_url": "https://api.github.com/users/purview-dev/followers",
+    "following_url": "https://api.github.com/users/purview-dev/following{/other_user}",
+    "gists_url": "https://api.github.com/users/purview-dev/gists{/gist_id}",
+    "starred_url": "https://api.github.com/users/purview-dev/starred{/owner}{/repo}",
+    "subscriptions_url": "https://api.github.com/users/purview-dev/subscriptions",
+    "organizations_url": "https://api.github.com/users/purview-dev/orgs",
+    "repos_url": "https://api.github.com/users/purview-dev/repos",
+    "events_url": "https://api.github.com/users/purview-dev/events{/privacy}",
+    "received_events_url": "https://api.github.com/users/purview-dev/received_events",
+    "type": "Organization",
+    "user_view_type": "public",
+    "site_admin": false
+  },
+  "html_url": "https://github.com/purview-dev/containers",
+  "description": "Testcontainers-style library for .NET (net10.0): run throwaway Linux containers in integration tests on Microsoft WSL Containers (WSLC) with no Docker install, or on Docker. Add one package, write your test code once: zero configuration between Windows dev (WSLC) and Linux CI (Docker). Seven service modules.",
+  "fork": false,
+  "url": "https://api.github.com/repos/purview-dev/containers",
+  "forks_url": "https://api.github.com/repos/purview-dev/containers/forks",
+  "keys_url": "https://api.github.com/repos/purview-dev/containers/keys{/key_id}",
+  "collaborators_url": "https://api.github.com/repos/purview-dev/containers/collaborators{/collaborator}",
+  "teams_url": "https://api.github.com/repos/purview-dev/containers/teams",
+  "hooks_url": "https://api.github.com/repos/purview-dev/containers/hooks",
+  "issue_events_url": "https://api.github.com/repos/purview-dev/containers/issues/events{/number}",
+  "events_url": "https://api.github.com/repos/purview-dev/containers/events",
+  "assignees_url": "https://api.github.com/repos/purview-dev/containers/assignees{/user}",
+  "branches_url": "https://api.github.com/repos/purview-dev/containers/branches{/branch}",
+  "tags_url": "https://api.github.com/repos/purview-dev/containers/tags",
+  "blobs_url": "https://api.github.com/repos/purview-dev/containers/git/blobs{/sha}",
+  "git_tags_url": "https://api.github.com/repos/purview-dev/containers/git/tags{/sha}",
+  "git_refs_url": "https://api.github.com/repos/purview-dev/containers/git/refs{/sha}",
+  "trees_url": "https://api.github.com/repos/purview-dev/containers/git/trees{/sha}",
+  "statuses_url": "https://api.github.com/repos/purview-dev/containers/statuses/{sha}",
+  "languages_url": "https://api.github.com/repos/purview-dev/containers/languages",
+  "stargazers_url": "https://api.github.com/repos/purview-dev/containers/stargazers",
+  "contributors_url": "https://api.github.com/repos/purview-dev/containers/contributors",
+  "subscribers_url": "https://api.github.com/repos/purview-dev/containers/subscribers",
+  "subscription_url": "https://api.github.com/repos/purview-dev/containers/subscription",
+  "commits_url": "https://api.github.com/repos/purview-dev/containers/commits{/sha}",
+  "git_commits_url": "https://api.github.com/repos/purview-dev/containers/git/commits{/sha}",
+  "comments_url": "https://api.github.com/repos/purview-dev/containers/comments{/number}",
+  "issue_comment_url": "https://api.github.com/repos/purview-dev/containers/issues/comments{/number}",
+  "contents_url": "https://api.github.com/repos/purview-dev/containers/contents/{+path}",
+  "compare_url": "https://api.github.com/repos/purview-dev/containers/compare/{base}...{head}",
+  "merges_url": "https://api.github.com/repos/purview-dev/containers/merges",
+  "archive_url": "https://api.github.com/repos/purview-dev/containers/{archive_format}{/ref}",
+  "downloads_url": "https://api.github.com/repos/purview-dev/containers/downloads",
+  "issues_url": "https://api.github.com/repos/purview-dev/containers/issues{/number}",
+  "pulls_url": "https://api.github.com/repos/purview-dev/containers/pulls{/number}",
+  "milestones_url": "https://api.github.com/repos/purview-dev/containers/milestones{/number}",
+  "notifications_url": "https://api.github.com/repos/purview-dev/containers/notifications{?since,all,participating}",
+  "labels_url": "https://api.github.com/repos/purview-dev/containers/labels{/name}",
+  "releases_url": "https://api.github.com/repos/purview-dev/containers/releases{/id}",
+  "deployments_url": "https://api.github.com/repos/purview-dev/containers/deployments",
+  "created_at": "2026-09-30T06:52:40Z",
+  "updated_at": "2026-10-02T07:36:57Z",
+  "pushed_at": "2026-10-02T07:38:43Z",
+  "git_url": "git://github.com/purview-dev/containers.git",
+  "ssh_url": "git@github.com:purview-dev/containers.git",
+  "clone_url": "https://github.com/purview-dev/containers.git",
+  "svn_url": "https://github.com/purview-dev/containers",
+  "homepage": "https://purview.dev/projects/containers/",
+  "size": 820,
+  "stargazers_count": 1,
+  "watchers_count": 1,
+  "language": "C#",
+  "has_issues": true,
+  "has_projects": false,
+  "has_downloads": false,
+  "has_wiki": false,
+  "has_pages": false,
+  "has_discussions": false,
+  "forks_count": 0,
+  "mirror_url": null,
+  "archived": false,
+  "disabled": false,
+  "open_issues_count": 0,
+  "license": {
+    "key": "mit",
+    "name": "MIT License",
+    "spdx_id": "MIT",
+    "url": "https://api.github.com/licenses/mit",
+    "node_id": "MDc6TGljZW5zZTEz"
+  },
+  "allow_forking": true,
+  "is_template": false,
+  "web_commit_signoff_required": false,
+  "has_pull_requests": true,
+  "pull_request_creation_policy": "all",
+  "topics": [
+    "azurite",
+    "containers",
+    "csharp",
+    "docker",
+    "dotnet",
+    "integration-testing",
+    "mysql",
+    "nats",
+    "nuget",
+    "postgresql",
+    "rabbitmq",
+    "redis",
+    "sql-server",
+    "testcontainers",
+    "testing",
+    "windows",
+    "wsl",
+    "wsl-containers",
+    "wslc"
+  ],
+  "visibility": "public",
+  "forks": 0,
+  "open_issues": 0,
+  "watchers": 1,
+  "default_branch": "main",
+  "permissions": {
+    "admin": true,
+    "maintain": true,
+    "push": true,
+    "triage": true,
+    "pull": true
+  },
+  "temp_clone_token": "",
+  "allow_squash_merge": true,
+  "allow_merge_commit": true,
+  "allow_rebase_merge": true,
+  "allow_auto_merge": true,
+  "delete_branch_on_merge": true,
+  "allow_update_branch": true,
+  "use_squash_pr_title_as_default": false,
+  "squash_merge_commit_message": "COMMIT_MESSAGES",
+  "squash_merge_commit_title": "COMMIT_OR_PR_TITLE",
+  "merge_commit_message": "PR_TITLE",
+  "merge_commit_title": "MERGE_MESSAGE",
+  "custom_properties": {},
+  "organization": {
+    "login": "purview-dev",
+    "id": 96894084,
+    "node_id": "O_kgDOBcZ8hA",
+    "avatar_url": "https://avatars.githubusercontent.com/u/96894084?v=4",
+    "gravatar_id": "",
+    "url": "https://api.github.com/users/purview-dev",
+    "html_url": "https://github.com/purview-dev",
+    "followers_url": "https://api.github.com/users/purview-dev/followers",
+    "following_url": "https://api.github.com/users/purview-dev/following{/other_user}",
+    "gists_url": "https://api.github.com/users/purview-dev/gists{/gist_id}",
+    "starred_url": "https://api.github.com/users/purview-dev/starred{/owner}{/repo}",
+    "subscriptions_url": "https://api.github.com/users/purview-dev/subscriptions",
+    "organizations_url": "https://api.github.com/users/purview-dev/orgs",
+    "repos_url": "https://api.github.com/users/purview-dev/repos",
+    "events_url": "https://api.github.com/users/purview-dev/events{/privacy}",
+    "received_events_url": "https://api.github.com/users/purview-dev/received_events",
+    "type": "Organization",
+    "user_view_type": "public",
+    "site_admin": false
+  },
+  "security_and_analysis": {
+    "secret_scanning": {
+      "status": "enabled"
+    },
+    "secret_scanning_push_protection": {
+      "status": "enabled"
+    },
+    "dependabot_security_updates": {
+      "status": "disabled"
+    },
+    "secret_scanning_non_provider_patterns": {
+      "status": "disabled"
+    },
+    "secret_scanning_ai_detection": {
+      "status": "disabled"
+    },
+    "secret_scanning_validity_checks": {
+      "status": "disabled"
+    },
+    "secret_scanning_delegated_alert_dismissal": {
+      "status": "disabled"
+    },
+    "secret_scanning_delegated_bypass": {
+      "status": "disabled"
+    }
+  },
+  "network_count": 0,
+  "subscribers_count": 0
+}
diff --git a/src/fixtures/nuget/purview.containers.azurite.json b/src/fixtures/nuget/purview.containers.azurite.json
new file mode 100644
index 0000000..b8a278f
--- /dev/null
+++ b/src/fixtures/nuget/purview.containers.azurite.json
@@ -0,0 +1,6 @@
+{
+  "versions": [
+    "1.0.0-prerelease.2",
+    "1.0.0-prerelease.3"
+  ]
+}
diff --git a/src/fixtures/nuget/purview.containers.core.json b/src/fixtures/nuget/purview.containers.core.json
new file mode 100644
index 0000000..b8a278f
--- /dev/null
+++ b/src/fixtures/nuget/purview.containers.core.json
@@ -0,0 +1,6 @@
+{
+  "versions": [
+    "1.0.0-prerelease.2",
+    "1.0.0-prerelease.3"
+  ]
+}
diff --git a/src/fixtures/nuget/purview.containers.docker.json b/src/fixtures/nuget/purview.containers.docker.json
new file mode 100644
index 0000000..b8a278f
--- /dev/null
+++ b/src/fixtures/nuget/purview.containers.docker.json
@@ -0,0 +1,6 @@
+{
+  "versions": [
+    "1.0.0-prerelease.2",
+    "1.0.0-prerelease.3"
+  ]
+}
diff --git a/src/fixtures/nuget/purview.containers.json b/src/fixtures/nuget/purview.containers.json
new file mode 100644
index 0000000..b8a278f
--- /dev/null
+++ b/src/fixtures/nuget/purview.containers.json
@@ -0,0 +1,6 @@
+{
+  "versions": [
+    "1.0.0-prerelease.2",
+    "1.0.0-prerelease.3"
+  ]
+}
diff --git a/src/fixtures/nuget/purview.containers.mssql.json b/src/fixtures/nuget/purview.containers.mssql.json
new file mode 100644
index 0000000..b8a278f
--- /dev/null
+++ b/src/fixtures/nuget/purview.containers.mssql.json
@@ -0,0 +1,6 @@
+{
+  "versions": [
+    "1.0.0-prerelease.2",
+    "1.0.0-prerelease.3"
+  ]
+}
diff --git a/src/fixtures/nuget/purview.containers.mysql.json b/src/fixtures/nuget/purview.containers.mysql.json
new file mode 100644
index 0000000..b8a278f
--- /dev/null
+++ b/src/fixtures/nuget/purview.containers.mysql.json
@@ -0,0 +1,6 @@
+{
+  "versions": [
+    "1.0.0-prerelease.2",
+    "1.0.0-prerelease.3"
+  ]
+}
diff --git a/src/fixtures/nuget/purview.containers.nats.json b/src/fixtures/nuget/purview.containers.nats.json
new file mode 100644
index 0000000..b8a278f
--- /dev/null
+++ b/src/fixtures/nuget/purview.containers.nats.json
@@ -0,0 +1,6 @@
+{
+  "versions": [
+    "1.0.0-prerelease.2",
+    "1.0.0-prerelease.3"
+  ]
+}
diff --git a/src/fixtures/nuget/purview.containers.postgresql.json b/src/fixtures/nuget/purview.containers.postgresql.json
new file mode 100644
index 0000000..b8a278f
--- /dev/null
+++ b/src/fixtures/nuget/purview.containers.postgresql.json
@@ -0,0 +1,6 @@
+{
+  "versions": [
+    "1.0.0-prerelease.2",
+    "1.0.0-prerelease.3"
+  ]
+}
diff --git a/src/fixtures/nuget/purview.containers.rabbitmq.json b/src/fixtures/nuget/purview.containers.rabbitmq.json
new file mode 100644
index 0000000..b8a278f
--- /dev/null
+++ b/src/fixtures/nuget/purview.containers.rabbitmq.json
@@ -0,0 +1,6 @@
+{
+  "versions": [
+    "1.0.0-prerelease.2",
+    "1.0.0-prerelease.3"
+  ]
+}
diff --git a/src/fixtures/nuget/purview.containers.redis.json b/src/fixtures/nuget/purview.containers.redis.json
new file mode 100644
index 0000000..b8a278f
--- /dev/null
+++ b/src/fixtures/nuget/purview.containers.redis.json
@@ -0,0 +1,6 @@
+{
+  "versions": [
+    "1.0.0-prerelease.2",
+    "1.0.0-prerelease.3"
+  ]
+}
diff --git a/src/fixtures/nuget/purview.containers.wsl.json b/src/fixtures/nuget/purview.containers.wsl.json
new file mode 100644
index 0000000..b8a278f
--- /dev/null
+++ b/src/fixtures/nuget/purview.containers.wsl.json
@@ -0,0 +1,6 @@
+{
+  "versions": [
+    "1.0.0-prerelease.2",
+    "1.0.0-prerelease.3"
+  ]
+}
diff --git a/src/fixtures/nuget/search/Purview.Containers.Azurite.json b/src/fixtures/nuget/search/Purview.Containers.Azurite.json
new file mode 100644
index 0000000..b6b988b
--- /dev/null
+++ b/src/fixtures/nuget/search/Purview.Containers.Azurite.json
@@ -0,0 +1,8 @@
+{
+  "@context": {
+    "@vocab": "http://schema.nuget.org/schema#",
+    "@base": "https://api.nuget.org/v3/registration5-semver1/"
+  },
+  "totalHits": 0,
+  "data": []
+}
diff --git a/src/fixtures/nuget/search/Purview.Containers.Core.json b/src/fixtures/nuget/search/Purview.Containers.Core.json
new file mode 100644
index 0000000..b6b988b
--- /dev/null
+++ b/src/fixtures/nuget/search/Purview.Containers.Core.json
@@ -0,0 +1,8 @@
+{
+  "@context": {
+    "@vocab": "http://schema.nuget.org/schema#",
+    "@base": "https://api.nuget.org/v3/registration5-semver1/"
+  },
+  "totalHits": 0,
+  "data": []
+}
diff --git a/src/fixtures/nuget/search/Purview.Containers.Docker.json b/src/fixtures/nuget/search/Purview.Containers.Docker.json
new file mode 100644
index 0000000..b6b988b
--- /dev/null
+++ b/src/fixtures/nuget/search/Purview.Containers.Docker.json
@@ -0,0 +1,8 @@
+{
+  "@context": {
+    "@vocab": "http://schema.nuget.org/schema#",
+    "@base": "https://api.nuget.org/v3/registration5-semver1/"
+  },
+  "totalHits": 0,
+  "data": []
+}
diff --git a/src/fixtures/nuget/search/Purview.Containers.MsSql.json b/src/fixtures/nuget/search/Purview.Containers.MsSql.json
new file mode 100644
index 0000000..b6b988b
--- /dev/null
+++ b/src/fixtures/nuget/search/Purview.Containers.MsSql.json
@@ -0,0 +1,8 @@
+{
+  "@context": {
+    "@vocab": "http://schema.nuget.org/schema#",
+    "@base": "https://api.nuget.org/v3/registration5-semver1/"
+  },
+  "totalHits": 0,
+  "data": []
+}
diff --git a/src/fixtures/nuget/search/Purview.Containers.MySql.json b/src/fixtures/nuget/search/Purview.Containers.MySql.json
new file mode 100644
index 0000000..b6b988b
--- /dev/null
+++ b/src/fixtures/nuget/search/Purview.Containers.MySql.json
@@ -0,0 +1,8 @@
+{
+  "@context": {
+    "@vocab": "http://schema.nuget.org/schema#",
+    "@base": "https://api.nuget.org/v3/registration5-semver1/"
+  },
+  "totalHits": 0,
+  "data": []
+}
diff --git a/src/fixtures/nuget/search/Purview.Containers.Nats.json b/src/fixtures/nuget/search/Purview.Containers.Nats.json
new file mode 100644
index 0000000..b6b988b
--- /dev/null
+++ b/src/fixtures/nuget/search/Purview.Containers.Nats.json
@@ -0,0 +1,8 @@
+{
+  "@context": {
+    "@vocab": "http://schema.nuget.org/schema#",
+    "@base": "https://api.nuget.org/v3/registration5-semver1/"
+  },
+  "totalHits": 0,
+  "data": []
+}
diff --git a/src/fixtures/nuget/search/Purview.Containers.PostgreSql.json b/src/fixtures/nuget/search/Purview.Containers.PostgreSql.json
new file mode 100644
index 0000000..b6b988b
--- /dev/null
+++ b/src/fixtures/nuget/search/Purview.Containers.PostgreSql.json
@@ -0,0 +1,8 @@
+{
+  "@context": {
+    "@vocab": "http://schema.nuget.org/schema#",
+    "@base": "https://api.nuget.org/v3/registration5-semver1/"
+  },
+  "totalHits": 0,
+  "data": []
+}
diff --git a/src/fixtures/nuget/search/Purview.Containers.RabbitMq.json b/src/fixtures/nuget/search/Purview.Containers.RabbitMq.json
new file mode 100644
index 0000000..b6b988b
--- /dev/null
+++ b/src/fixtures/nuget/search/Purview.Containers.RabbitMq.json
@@ -0,0 +1,8 @@
+{
+  "@context": {
+    "@vocab": "http://schema.nuget.org/schema#",
+    "@base": "https://api.nuget.org/v3/registration5-semver1/"
+  },
+  "totalHits": 0,
+  "data": []
+}
diff --git a/src/fixtures/nuget/search/Purview.Containers.Redis.json b/src/fixtures/nuget/search/Purview.Containers.Redis.json
new file mode 100644
index 0000000..b6b988b
--- /dev/null
+++ b/src/fixtures/nuget/search/Purview.Containers.Redis.json
@@ -0,0 +1,8 @@
+{
+  "@context": {
+    "@vocab": "http://schema.nuget.org/schema#",
+    "@base": "https://api.nuget.org/v3/registration5-semver1/"
+  },
+  "totalHits": 0,
+  "data": []
+}
diff --git a/src/fixtures/nuget/search/Purview.Containers.Wsl.json b/src/fixtures/nuget/search/Purview.Containers.Wsl.json
new file mode 100644
index 0000000..b6b988b
--- /dev/null
+++ b/src/fixtures/nuget/search/Purview.Containers.Wsl.json
@@ -0,0 +1,8 @@
+{
+  "@context": {
+    "@vocab": "http://schema.nuget.org/schema#",
+    "@base": "https://api.nuget.org/v3/registration5-semver1/"
+  },
+  "totalHits": 0,
+  "data": []
+}
diff --git a/src/fixtures/nuget/search/Purview.Containers.json b/src/fixtures/nuget/search/Purview.Containers.json
new file mode 100644
index 0000000..b6b988b
--- /dev/null
+++ b/src/fixtures/nuget/search/Purview.Containers.json
@@ -0,0 +1,8 @@
+{
+  "@context": {
+    "@vocab": "http://schema.nuget.org/schema#",
+    "@base": "https://api.nuget.org/v3/registration5-semver1/"
+  },
+  "totalHits": 0,
+  "data": []
+}
diff --git a/src/fixtures/releases/index.json b/src/fixtures/releases/index.json
index adf130d..163e222 100644
--- a/src/fixtures/releases/index.json
+++ b/src/fixtures/releases/index.json
@@ -312,6 +312,39 @@
       "defaultBranch": "main",
       "updatedAt": "2026-09-30T14:05:36Z",
       "hasDiscussions": false
+    },
+    "purview-dev/containers": {
+      "name": "containers",
+      "fullName": "purview-dev/containers",
+      "description": "Testcontainers-style library for .NET (net10.0): run throwaway Linux containers in integration tests on Microsoft WSL Containers (WSLC) with no Docker install, or on Docker. Add one package, write your test code once: zero configuration between Windows dev (WSLC) and Linux CI (Docker). Seven service modules.",
+      "archived": false,
+      "homepage": "https://purview.dev/projects/containers/",
+      "topics": [
+        "azurite",
+        "containers",
+        "csharp",
+        "docker",
+        "dotnet",
+        "integration-testing",
+        "mysql",
+        "nats",
+        "nuget",
+        "postgresql",
+        "rabbitmq",
+        "redis",
+        "sql-server",
+        "testcontainers",
+        "testing",
+        "windows",
+        "wsl",
+        "wsl-containers",
+        "wslc"
+      ],
+      "stargazersCount": 1,
+      "openIssuesCount": 0,
+      "defaultBranch": "main",
+      "updatedAt": "2026-10-02T07:36:57Z",
+      "hasDiscussions": false
     }
   },
   "releases": {
@@ -1442,6 +1475,35 @@
         "publishedAt": "2026-09-30T12:35:07Z",
         "htmlUrl": "https://github.com/purview-dev/results/releases/tag/v1.0.0-prerelease.1"
       }
+    ],
+    "purview-dev/containers": [
+      {
+        "tagName": "v1.0.0-prerelease.3",
+        "name": "v1.0.0-prerelease.3",
+        "body": "## What's Changed\n* chore: add MIT license file by @kieronlanning in https://github.com/purview-dev/containers/pull/4\n* docs: updated docs by @kieronlanning in https://github.com/purview-dev/containers/pull/5\n* docs: updated docs by @kieronlanning in https://github.com/purview-dev/containers/pull/6\n\n\n**Full Changelog**: https://github.com/purview-dev/containers/compare/v1.0.0-prerelease.2...v1.0.0-prerelease.3",
+        "prerelease": true,
+        "draft": false,
+        "publishedAt": "2026-10-02T07:38:44Z",
+        "htmlUrl": "https://github.com/purview-dev/containers/releases/tag/v1.0.0-prerelease.3"
+      },
+      {
+        "tagName": "v1.0.0-prerelease.2",
+        "name": "v1.0.0-prerelease.2",
+        "body": "## What's Changed\n* Docs update by @kieronlanning in https://github.com/purview-dev/containers/pull/2\n* Portable WSLC backend for net10.0, Testcontainers-parity connection strings, repo renamed to containers by @kieronlanning in https://github.com/purview-dev/containers/pull/3\n\n\n**Full Changelog**: https://github.com/purview-dev/containers/compare/v1.0.0-prerelease.1...v1.0.0-prerelease.2",
+        "prerelease": true,
+        "draft": false,
+        "publishedAt": "2026-10-01T22:17:22Z",
+        "htmlUrl": "https://github.com/purview-dev/containers/releases/tag/v1.0.0-prerelease.2"
+      },
+      {
+        "tagName": "v1.0.0-prerelease.1",
+        "name": "v1.0.0-prerelease.1",
+        "body": "## What's Changed\n* Develop by @kieronlanning in https://github.com/purview-dev/wsl-testcontainers/pull/1\n\n## New Contributors\n* @kieronlanning made their first contribution in https://github.com/purview-dev/wsl-testcontainers/pull/1\n\n**Full Changelog**: https://github.com/purview-dev/wsl-testcontainers/commits/v1.0.0-prerelease.1",
+        "prerelease": true,
+        "draft": false,
+        "publishedAt": "2026-09-30T16:41:23Z",
+        "htmlUrl": "https://github.com/purview-dev/containers/releases/tag/v1.0.0-prerelease.1"
+      }
     ]
   },
   "packages": {
@@ -2030,6 +2092,83 @@
         "1.0.0-prerelease.1",
         "1.0.0-prerelease.2"
       ]
+    },
+    "Purview.Containers": {
+      "id": "Purview.Containers",
+      "versions": [
+        "1.0.0-prerelease.2",
+        "1.0.0-prerelease.3"
+      ]
+    },
+    "Purview.Containers.Core": {
+      "id": "Purview.Containers.Core",
+      "versions": [
+        "1.0.0-prerelease.2",
+        "1.0.0-prerelease.3"
+      ]
+    },
+    "Purview.Containers.Wsl": {
+      "id": "Purview.Containers.Wsl",
+      "versions": [
+        "1.0.0-prerelease.2",
+        "1.0.0-prerelease.3"
+      ]
+    },
+    "Purview.Containers.Docker": {
+      "id": "Purview.Containers.Docker",
+      "versions": [
+        "1.0.0-prerelease.2",
+        "1.0.0-prerelease.3"
+      ]
+    },
+    "Purview.Containers.PostgreSql": {
+      "id": "Purview.Containers.PostgreSql",
+      "versions": [
+        "1.0.0-prerelease.2",
+        "1.0.0-prerelease.3"
+      ]
+    },
+    "Purview.Containers.Redis": {
+      "id": "Purview.Containers.Redis",
+      "versions": [
+        "1.0.0-prerelease.2",
+        "1.0.0-prerelease.3"
+      ]
+    },
+    "Purview.Containers.MsSql": {
+      "id": "Purview.Containers.MsSql",
+      "versions": [
+        "1.0.0-prerelease.2",
+        "1.0.0-prerelease.3"
+      ]
+    },
+    "Purview.Containers.MySql": {
+      "id": "Purview.Containers.MySql",
+      "versions": [
+        "1.0.0-prerelease.2",
+        "1.0.0-prerelease.3"
+      ]
+    },
+    "Purview.Containers.RabbitMq": {
+      "id": "Purview.Containers.RabbitMq",
+      "versions": [
+        "1.0.0-prerelease.2",
+        "1.0.0-prerelease.3"
+      ]
+    },
+    "Purview.Containers.Azurite": {
+      "id": "Purview.Containers.Azurite",
+      "versions": [
+        "1.0.0-prerelease.2",
+        "1.0.0-prerelease.3"
+      ]
+    },
+    "Purview.Containers.Nats": {
+      "id": "Purview.Containers.Nats",
+      "versions": [
+        "1.0.0-prerelease.2",
+        "1.0.0-prerelease.3"
+      ]
     }
   },
   "packageSearch": {
@@ -2121,6 +2260,17 @@
     "Purview.Results.SourceGenerator": null,
     "Purview.Results.AspNetCore": null,
     "Purview.Results.ZodSharp": null,
-    "Purview.Results.ZodSharp.AspNetCore": null
+    "Purview.Results.ZodSharp.AspNetCore": null,
+    "Purview.Containers": null,
+    "Purview.Containers.Core": null,
+    "Purview.Containers.Wsl": null,
+    "Purview.Containers.Docker": null,
+    "Purview.Containers.PostgreSql": null,
+    "Purview.Containers.Redis": null,
+    "Purview.Containers.MsSql": null,
+    "Purview.Containers.MySql": null,
+    "Purview.Containers.RabbitMq": null,
+    "Purview.Containers.Azurite": null,
+    "Purview.Containers.Nats": null
   }
 }
diff --git a/src/scripts/check-projects.ts b/src/scripts/check-projects.ts
index c4bd6f3..a8c73fd 100644
--- a/src/scripts/check-projects.ts
+++ b/src/scripts/check-projects.ts
@@ -16,7 +16,8 @@ import { OWNER } from '../src/lib/site';
 /**
  * Deterministic catalogue guard (ADR 0003).
  *
- * Proves the invariants of `src/src/data/projects.yml` against the generated
+ * Proves the invariants of the catalogue (`src/src/data/projects/*.yml` plus
+ * `src/src/data/external-projects.yml`) against the generated
  * docs mirror/cache and the release cache/fixtures. Offline only: it never
  * performs network I/O, so it can run inside `just validate` and CI.
  *
@@ -149,6 +150,28 @@ function checkDocs(
   return pages;
 }
 
+/**
+ * The `experimental` flag is an intent marker, so it stays orthogonal to the
+ * release channel (ADR 0004). The one combination that is legal but worth a
+ * second look is a stable release: the flag says "exploratory" while the
+ * channel says "recommended for use". The contradictory pairing
+ * (`experimental` with `status: archived`) is rejected by the manifest schema
+ * before this runs, so it needs no rule here.
+ */
+function checkExperimental(project: ResolvedProject): void {
+  if (!project.experimental || project.status !== 'stable') {
+    return;
+  }
+  warn({
+    project: project.id,
+    field: 'experimental',
+    observed: 'true with status: stable',
+    expected: 'an experimental project normally publishes prereleases only',
+    remediation:
+      'confirm the intent; if the project is still an experiment, `status: preview` is the honest release channel.',
+  });
+}
+
 /** Package declarations must resolve to published NuGet versions. */
 function checkPackages(project: ResolvedProject, data: ReleaseCacheData): void {
   if (project.packages.length > 1) {
@@ -183,7 +206,7 @@ function checkPackages(project: ResolvedProject, data: ReleaseCacheData): void {
         observed: describeVersions(0),
         expected: 'at least one published version on NuGet',
         remediation:
-          'publish the package before declaring it, or correct the package id in projects.yml.',
+          'publish the package before declaring it, or correct the package id in the project file.',
       });
     }
   }
@@ -225,7 +248,7 @@ function checkRepoMetadata(project: ResolvedProject, data: ReleaseCacheData): vo
       observed: project.status,
       expected: 'archived',
       remediation:
-        'the GitHub repository is archived; set `status: archived` (and `supersededBy`).',
+        'the GitHub repository is archived; set `status: archived`, remove `experimental: true` if present, and add `supersededBy` when a successor exists.',
     });
   }
   if (!repo.archived && project.status === 'archived') {
@@ -233,7 +256,7 @@ function checkRepoMetadata(project: ResolvedProject, data: ReleaseCacheData): vo
       project: project.id,
       field: 'status',
       observed: 'archived',
-      expected: 'stable or preview',
+      expected: 'stable, preview or experimental',
       remediation: 'the GitHub repository is active; correct `status`.',
     });
   }
@@ -293,7 +316,7 @@ export function checkProjects(): { errors: Finding[]; warnings: Finding[] } {
         project: '(manifest)',
         field: 'schema',
         observed: 'invalid manifest',
-        expected: 'a schema-valid projects.yml',
+        expected: 'a schema-valid project record',
         remediation: error.message,
       });
       return { errors, warnings };
@@ -346,6 +369,7 @@ export function checkProjects(): { errors: Finding[]; warnings: Finding[] } {
   for (const project of projects) {
     const docsPages = checkDocs(project, docsManifest);
     checkUseCases(project, docsPages);
+    checkExperimental(project);
     if (data) {
       checkPackages(project, data);
       checkRepoMetadata(project, data);
diff --git a/src/src/components/ProjectCard.astro b/src/src/components/ProjectCard.astro
index f89a226..d3d4968 100644
--- a/src/src/components/ProjectCard.astro
+++ b/src/src/components/ProjectCard.astro
@@ -4,6 +4,7 @@ import { buildBadge, nugetDownloadsBadge, nugetVersionBadge, actionsUrl } from '
 import { projectRepoEnrichment } from '~/lib/releases/repo';
 import { getReleaseIndex } from '~/lib/releases/runtime';
 import type { ResolvedProject } from '~/lib/manifest/load';
+import { displayStatus } from '~/lib/status';
 import { nugetPackageUrl, withBase } from '~/lib/urls';
 
 interface Props {
@@ -13,10 +14,11 @@ interface Props {
 }
 
 const { project, showBadges = true } = Astro.props;
+const status = displayStatus(project);
 const { tags } = projectRepoEnrichment(project, getReleaseIndex().data);
 const primaryPackage = project.packages.find((pkg) => pkg.primary) ?? project.packages[0];
 const badges =
-  project.status === 'archived' ?
+  status === 'archived' ?
     []
   : [
       ...(primaryPackage ?
@@ -45,7 +47,7 @@ const badges =
   <a href={withBase(`/projects/${project.id}/`)} class="flex flex-1 flex-col gap-3 no-underline">
     <div class="flex items-center justify-between gap-3">
       <h3 class="min-w-0 text-lg font-semibold leading-snug">{project.name}</h3>
-      <StatusBadge status={project.status} class="shrink-0" />
+      <StatusBadge status={status} class="shrink-0" />
     </div>
     <p class="text-sm text-muted">{project.shortDescription}</p>
     <div class="mt-auto flex flex-wrap items-center gap-2 pt-2">
diff --git a/src/src/components/StatusBadge.astro b/src/src/components/StatusBadge.astro
index de7735e..a116fd2 100644
--- a/src/src/components/StatusBadge.astro
+++ b/src/src/components/StatusBadge.astro
@@ -1,12 +1,14 @@
 ---
+import { DISPLAY_STATUS_LABELS, type DisplayStatus } from '~/lib/status';
+
 interface Props {
-  status: 'stable' | 'preview' | 'archived';
+  status: DisplayStatus;
   /** Extra classes, e.g. `shrink-0` when the badge shares a row with a title. */
   class?: string;
 }
 
 const { status, class: className } = Astro.props;
-const label = { stable: 'Stable', preview: 'Preview', archived: 'Archived' }[status];
+const label = DISPLAY_STATUS_LABELS[status];
 ---
 
 <span class:list={['pv-chip', `pv-status-${status}`, className]}>{label}</span>
\ No newline at end of file
diff --git a/src/src/components/starlight/PageTitle.astro b/src/src/components/starlight/PageTitle.astro
index 16b74f4..40cbfd0 100644
--- a/src/src/components/starlight/PageTitle.astro
+++ b/src/src/components/starlight/PageTitle.astro
@@ -2,6 +2,8 @@
 import StatusBadge from '~/components/StatusBadge.astro';
 import { isStale, STALE_AFTER_DAYS } from '~/lib/docs/staleness';
 import { LLMS_LINK_ATTRS } from '~/lib/llms';
+import { displayStatus } from '~/lib/status';
+
 import { withBase } from '~/lib/urls';
 
 const { entry } = Astro.locals.starlightRoute;
@@ -9,6 +11,9 @@ const data = entry?.data;
 const lastReviewed = typeof data?.lastReviewed === 'string' ? data.lastReviewed : undefined;
 const stale = lastReviewed ? isStale(lastReviewed) : false;
 const tags = Array.isArray(data?.tags) ? data.tags : [];
+const experimental = data?.experimental === true;
+const status = data?.status ? displayStatus({ status: data.status, experimental }) : undefined;
+
 // Project overview pages surface the per-project `llms.txt` bundle emitted by
 // the `customSets` option in `astro.config.ts`. Starlight resolves an index
 // page to its directory id (`docs/<project>`), while the content collection —
@@ -28,9 +33,9 @@ const llmsHref =
   data && (
     <div class="doc-meta">
       {
-        data.status && (
+        status && (
           <span class="doc-meta-item">
-            <StatusBadge status={data.status} />
+            <StatusBadge status={status} />
           </span>
         )
       }
@@ -96,6 +101,15 @@ const llmsHref =
   )
 }
 
+{
+  experimental && (
+    <p class="doc-experimental">
+      <strong>Experimental.</strong> This project is an experiment: the public API, defaults and
+      packaging can change between prereleases, and there is no production support guarantee.
+    </p>
+  )
+}
+
 <style>
   .doc-meta {
     display: flex;
@@ -113,6 +127,19 @@ const llmsHref =
     gap: 0.375rem;
   }
 
+  /* Standalone warning for an experimental project's documentation (ADR 0004).
+   * The badge alone is too easy to miss on a page someone scrolled straight
+   * into, so the flag is also stated in prose on every aggregated page. */
+  .doc-experimental {
+    margin-top: 0.75rem;
+    border-radius: 0.5rem;
+    border: 1px solid color-mix(in oklab, var(--color-error) 40%, transparent);
+    background-color: color-mix(in oklab, var(--color-error) 10%, transparent);
+    padding: 0.75rem 1rem;
+    font-size: 0.875rem;
+    line-height: 1.5;
+  }
+
   .stale-badge {
     margin-left: 0.375rem;
     border-radius: 9999px;
diff --git a/src/src/content.config.ts b/src/src/content.config.ts
index 2bf823d..1d45eb3 100644
--- a/src/src/content.config.ts
+++ b/src/src/content.config.ts
@@ -12,6 +12,7 @@ export const collections = {
       extend: z.object({
         owners: z.array(z.string()).default([OWNER]),
         status: z.enum(['stable', 'preview', 'archived']),
+        experimental: z.boolean().default(false),
         lastReviewed: z.string(),
         sourceProject: z.string(),
         sourceRepo: z.string(),
diff --git a/src/src/data/external-projects.yml b/src/src/data/external-projects.yml
new file mode 100644
index 0000000..5789fe8
--- /dev/null
+++ b/src/src/data/external-projects.yml
@@ -0,0 +1,18 @@
+$schema: ../lib/manifest/schema.ts
+
+externalProjects:
+  - id: likec4
+    name: LikeC4
+    shortDescription: Visualize, collaborate, and evolve software architecture with live C4 diagrams from your code.
+    description: >-
+      LikeC4 keeps software architecture always actual and live by modelling it
+      with the C4 model in code (TypeScript/React) and rendering interactive
+      diagrams. Purview maintains the AspireC4 integration that links .NET
+      Aspire applications to LikeC4, and contributes to the LikeC4 project
+      itself.
+    url: https://likec4.dev
+    repository: likec4/likec4
+    category: developer-tooling
+    status: stable
+    featured: true
+    order: 10
diff --git a/src/src/data/projects.yml b/src/src/data/projects.yml
deleted file mode 100644
index f4d0e0f..0000000
--- a/src/src/data/projects.yml
+++ /dev/null
@@ -1,900 +0,0 @@
-$schema: ../lib/manifest/schema.ts
-projects:
-  - id: telemetry-sourcegenerator
-    name: Telemetry SourceGenerator
-    shortDescription: Interface-based telemetry for .NET with zero boilerplate.
-    description: >-
-      A source generator that turns simple interface methods into
-      OpenTelemetry-aligned Activities, structured ILogger logging, and Metrics.
-      Define telemetry once on an interface; the generator emits the
-      implementation, DI registration helpers, and multi-target generation —
-      no runtime reflection, no boilerplate.
-    origin: >-
-      Repeating the same logging, activity, and metric wiring across services made telemetry a
-      strong candidate for one interface-driven, compile-time implementation.
-    useWhen: >-
-      You want strongly typed OpenTelemetry-aligned telemetry from interfaces, with generated
-      implementations and dependency-injection registration.
-    avoidWhen: >-
-      Your telemetry is highly dynamic, cannot be described at compile time, or is already handled
-      consistently by another instrumentation layer.
-    repository: purview-dev/telemetry-sourcegenerator
-    category: observability
-    status: stable
-    featured: true
-    order: 10
-    docs:
-      source: github-path
-      path: docs/wiki
-      rootPage: Getting-Started.md
-      exclude:
-        - _Sidebar.md
-        - Home.md
-        - index.md
-    targetFrameworks:
-      - net8.0
-      - net9.0
-      - net10.0
-    packages:
-      - id: Purview.Telemetry.SourceGenerator
-        description: Core package with the Roslyn source generator and attribute library.
-        primary: true
-        targetFrameworks:
-          - netstandard2.0
-    useCases:
-      - audience: developer
-        title: Tracing, logging, and metrics from a single interface
-        scenario: >-
-          You want OpenTelemetry activities, structured logs, and metrics around an order service, but
-          you do not want to hand-write the ActivitySource, ILogger, and Meter wiring in every class.
-        code: |
-          [ActivitySource]
-          [Logger]
-          [Meter]
-          public interface IOrderServiceTelemetry
-          {
-              [Activity]
-              [Info]
-              [AutoCounter]
-              Activity? PlacingOrder(int orderId, [Baggage] string region);
-          }
-        language: csharp
-        outcome: >-
-          The generator emits the implementation and an AddOrderServiceTelemetry() DI extension; you
-          register it once and inject the interface wherever telemetry is needed.
-        evidence: >-
-          One interface replaces the ActivitySource, ILogger, and Meter boilerplate you would otherwise
-          repeat in every service.
-      - audience: architect
-        title: Standardise telemetry names across services
-        scenario: >-
-          You want consistent OpenTelemetry meter and activity-source names across many services instead
-          of ad-hoc string literals scattered through the codebase.
-        code: |
-          builder.AddServiceDefaults(
-              TelemetryNames.MeterNames,
-              TelemetryNames.ActivitySourceNames);
-        language: csharp
-        outcome: >-
-          A generated TelemetryNames static class holds the names, so registration happens once at
-          startup rather than in every service.
-        evidence: >-
-          Naming conventions are generated, so snake_case tags and hierarchical metrics stay consistent
-          without a review checklist.
-        docsPage: generation
-    discussions: false
-
-  - id: event-sourcing
-    name: Event Sourcing
-    shortDescription: Aggregate-based event sourcing for .NET across any store.
-    description: >-
-      A .NET event sourcing framework for building aggregate-based applications.
-      Provider-agnostic store facades, source-generated aggregates and events,
-      transaction coordination for multi-aggregate saves, queryable snapshots
-      and read models, and storage providers for SQL Server, PostgreSQL,
-      MongoDB, Azure Storage, Azure Cosmos DB, and in-memory.
-    origin: >-
-      Aggregate, event, persistence, and transaction patterns kept recurring across applications,
-      so the reusable parts were separated from any one storage provider.
-    useWhen: >-
-      Your domain benefits from aggregate-based event sourcing and you want storage choices,
-      snapshots, read models, and transactions behind consistent abstractions.
-    avoidWhen: >-
-      A conventional state-based model is sufficient, or your application does not need the
-      operational and modelling trade-offs that come with event sourcing.
-    repository: purview-dev/event-sourcing
-    category: application-framework
-    status: preview
-    featured: true
-    order: 20
-    docs:
-      source: github-path
-      path: docs/wiki
-      rootPage: Getting-Started.md
-      exclude:
-        - _Sidebar.md
-        - Home.md
-        - index.md
-    targetFrameworks:
-      - net8.0
-      - net9.0
-      - net10.0
-    packages:
-      - id: Purview.EventSourcing
-        description: Core abstractions, aggregates, facades, transactions, DI, and source generation.
-        primary: true
-      - id: Purview.EventSourcing.SqlServer
-        description: Azure SQL / SQL Server event stream and queryable snapshot stores.
-      - id: Purview.EventSourcing.Postgres
-        description: PostgreSQL event stream and queryable snapshot stores.
-      - id: Purview.EventSourcing.AzureStorage
-        description: Azure Table / Blob event store.
-      - id: Purview.EventSourcing.MongoDB
-        description: MongoDB event stream and queryable snapshot stores.
-      - id: Purview.EventSourcing.CosmosDb
-        description: Azure Cosmos DB queryable snapshot store.
-      - id: Purview.EventSourcing.InMemory
-        description: In-memory event and snapshot stores for local and test scenarios.
-      - id: Purview.EventSourcing.Validation.FluentValidation
-        description: FluentValidation adapter for aggregate save-time validation.
-      - id: Purview.EventSourcing.Validation.ZodSharp
-        description: Purview.ZodSharp adapter for aggregate save-time validation.
-    useCases:
-      - audience: developer
-        title: An aggregate that persists as events
-        scenario: >-
-          You want aggregate-based event sourcing without hand-writing the event stream, snapshot, and
-          transaction plumbing.
-        code: |
-          [Aggregate]
-          public partial class OrderAggregate : AggregateBase
-          {
-              public string CustomerId { get; private set; } = default!;
-              public decimal Total { get; private set; }
-
-              [Event]
-              public partial void CreateOrder(string customerId);
-
-              [Event]
-              public partial void AddLineItem(string productId, string productName, int quantity, decimal unitPrice);
-          }
-        language: csharp
-        outcome: >-
-          The source generator produces the aggregate plumbing; provider packages add stores for SQL
-          Server, PostgreSQL, MongoDB, Azure Storage, Cosmos DB, or in-memory.
-        evidence: >-
-          One [Aggregate] declaration, and switching storage means swapping a provider package rather
-          than rewriting the domain.
-        docsPage: solution-design-guide
-      - audience: architect
-        title: Choose the store late, keep the domain stable
-        scenario: >-
-          You need to start on one database and move providers later, but you do not want persistence
-          choices to leak into the domain model.
-        code: |
-          builder.Services.AddSqlServerEventStore();
-          builder.Services.AddSqlServerSnapshotQueryableEventStore();
-        language: csharp
-        outcome: >-
-          Domain code depends on provider-agnostic facades, while concrete stores live behind separate
-          packages and registration extensions.
-        evidence: >-
-          SQL Server, PostgreSQL, MongoDB, Azure Storage, and Cosmos DB are interchangeable at the
-          registration level, so the domain never references a store.
-        docsPage: sql-server-guide
-    related:
-      - zodsharp
-      - value-objects
-    discussions: false
-
-  - id: zodsharp
-    name: ZodSharp
-    shortDescription: Zero-allocation schema validation for C# — a Zod port.
-    description: >-
-      A high-performance schema validation library for C#, ported from
-      TypeScript Zod by way of the guinhx/ZodSharp C# port. Struct-based rules,
-      a fluent API, JSON Schema export and import, source-generated validators,
-      and zero-allocation validation on every valid input path. Integrates with
-      System.Text.Json, Newtonsoft.Json, and ASP.NET Core ProblemDetails.
-    origin: >-
-      Schema validation was repeatedly needed at application boundaries, but existing approaches
-      did not combine a fluent Zod-style model with predictable, allocation-conscious execution.
-    useWhen: >-
-      You want composable C# schemas, compile-time validator generation, or JSON Schema interop with
-      tight control over validation behaviour and allocations.
-    avoidWhen: >-
-      Data annotations or an existing validation library already cover your requirements, or Zod-style
-      schemas would add an unnecessary second validation model.
-    repository: purview-dev/zodsharp
-    category: validation
-    status: stable
-    featured: true
-    order: 30
-    docs:
-      source: github-path
-      path: docs/wiki
-      rootPage: Getting-Started.md
-      exclude:
-        - _Sidebar.md
-        - Home.md
-        - index.md
-    targetFrameworks:
-      - net8.0
-      - net9.0
-      - net10.0
-    packages:
-      - id: Purview.ZodSharp
-        description: Core validation library and source generator.
-        primary: true
-      - id: Purview.ZodSharp.SystemTextJson
-        description: System.Text.Json integration and JSON Schema import.
-      - id: Purview.ZodSharp.NewtonsoftJson
-        description: Newtonsoft.Json integration and JSON Schema import.
-      - id: Purview.ZodSharp.AspNetCore
-        description: ASP.NET Core ProblemDetails integration.
-    related:
-      - value-objects
-    acknowledgments:
-      - name: Zod
-        url: https://github.com/colinhacks/zod
-        description: The original JavaScript/TypeScript schema validation library.
-      - name: ZodSharp (guinhx)
-        url: https://github.com/guinhx/ZodSharp
-        description: The C# port of Zod, and the fork this project is based on.
-    useCases:
-      - audience: developer
-        title: Validate input without exceptions or allocations
-        scenario: >-
-          You need to validate values at an application boundary and prefer a result you can inspect
-          over exception-driven control flow.
-        code: |
-          var nameSchema = Z.String().Min(3).Max(50);
-          var result = nameSchema.Validate("John");
-
-          if (result.IsSuccess)
-              Console.WriteLine($"Valid name: {result.Value}");
-        language: csharp
-        outcome: >-
-          Validate/SafeParse return a ValidationResult<T> with no exceptions, while Parse still throws
-          ZodException when you want that behaviour.
-        evidence: >-
-          Validation is zero-allocation on every valid input path, so the performance claim is a
-          property of the code rather than an aspiration.
-        docsPage: fluent-schema-api
-      - audience: team-lead
-        title: Return standard ProblemDetails for invalid requests
-        scenario: >-
-          You want failed validation in ASP.NET Core to surface as standard ProblemDetails payloads
-          rather than a bespoke error shape that clients must learn.
-        code: |
-          dotnet add package Purview.ZodSharp.AspNetCore
-        language: bash
-        outcome: >-
-          The AspNetCore adapter converts failed validation results into the standard ProblemDetails /
-          HttpValidationProblemDetails payloads.
-        evidence: >-
-          One adapter package, and API consumers keep the error contract they already expect.
-        docsPage: aspnetcore-integration
-
-  - id: value-objects
-    name: Value Objects
-    shortDescription: Source-generated scalar and complex value objects for .NET.
-    description: >-
-      F#-style single-case types for C#. Mark a partial struct or class with
-      [Scalar] or [ValueObject] and an incremental source generator produces
-      Create/Hydrate factories with normalization and validation, equality,
-      comparison, implicit conversions, JSON converters, and contextual
-      creation. Value objects serialize as their underlying value, map cleanly
-      onto Entity Framework JSON columns, and can be validated with
-      Purview.ZodSharp schemas.
-    origin: >-
-      Hand-writing the same factories, equality rules, conversions, serializers, and persistence
-      integration for domain values made the pattern an obvious source-generation target.
-    useWhen: >-
-      Your domain uses meaningful scalar or complex value types and you want their repetitive
-      implementation generated from a small, explicit declaration.
-    avoidWhen: >-
-      A primitive or record already expresses the concept clearly, or generated conversion and
-      serialization behaviour would be more machinery than the domain needs.
-    repository: purview-dev/value-objects
-    category: source-generation
-    status: preview
-    featured: true
-    order: 35
-    docs:
-      source: github-path
-      path: docs
-      rootPage: Getting-Started.md
-      exclude:
-        - _Sidebar.md
-        - Home.md
-        - index.md
-    targetFrameworks:
-      - net8.0
-      - net9.0
-      - net10.0
-    packages:
-      - id: Purview.ValueObjects
-        description: Runtime contracts, source generator, and analyzer for scalar and complex value objects.
-        primary: true
-    useCases:
-      - audience: developer
-        title: A domain scalar without the boilerplate
-        scenario: >-
-          You want a strong EmailAddress type with normalisation and validation, without hand-writing
-          factories, equality, conversions, and a JSON converter.
-        code: |
-          [Scalar]
-          public readonly partial record struct EmailAddress
-          {
-              public string Value { get; }
-
-              static partial void OnNormalize(ref string value)
-                  => value = value?.Trim().ToLowerInvariant()!;
-          }
-        language: csharp
-        outcome: >-
-          The generator adds Create, Hydrate, TryCreate, and Empty, plus equality, comparison, implicit
-          conversions, and a JSON converter.
-        evidence: >-
-          One declaration replaces the factory, equality, comparison, conversion, and serialization code
-          you would otherwise maintain by hand.
-        docsPage: value-object-design
-      - audience: developer
-        title: Map a value object onto an Entity Framework column
-        scenario: >-
-          You use a value object in your domain and want it to persist transparently instead of writing
-          converters at every mapping site.
-        code: |
-          var email = EmailAddress.Create("  Demo@Example.COM  ");
-          // email.Value == "demo@example.com"
-
-          bool ok = EmailAddress.TryCreate("not-an-email", out _);
-          // ok == false
-        language: csharp
-        outcome: >-
-          Value objects serialize as their underlying value and map onto Entity Framework JSON columns,
-          with optional Purview.ZodSharp validation.
-        evidence: >-
-          Persistence and serialization come from the generated type, so mapping code is not duplicated
-          per entity.
-        docsPage: entity-framework
-    related:
-      - zodsharp
-      - event-sourcing
-
-  - id: sourcegenerator-framework
-    name: SourceGenerator Framework
-    shortDescription: A typed framework for building incremental C# source generators.
-    description: >-
-      A strongly typed framework for building, testing, and maintaining
-      incremental C# source generators with Roslyn. Includes structured code
-      generation, attribute data models, type libraries, and a step-cache test
-      runner for verifying incremental behaviour.
-    origin: >-
-      Building several incremental generators exposed the same needs for typed models, structured
-      output, testing, and cache verification, so those foundations became a shared framework.
-    useWhen: >-
-      You are building a non-trivial incremental C# source generator and want reusable modelling,
-      code-writing, packaging, and testing infrastructure.
-    avoidWhen: >-
-      Your generator is small enough for the Roslyn APIs directly, or adopting a framework would
-      hide behaviour your implementation needs to control precisely.
-    repository: purview-dev/sourcegenerator-framework
-    category: source-generation
-    status: preview
-    featured: true
-    order: 40
-    docs:
-      source: github-path
-      path: docs/wiki
-      rootPage: Getting-Started.md
-      exclude:
-        - _Sidebar.md
-        - Home.md
-        - index.md
-    targetFrameworks:
-      - net8.0
-      - net9.0
-      - net10.0
-    packages:
-      - id: Purview.SourceGeneratorFramework
-        description: Core helpers, models, and MSBuild integration for incremental generators.
-        primary: true
-      - id: Purview.SourceGeneratorFramework.Testing
-        description: Framework-agnostic test runner and assertions for generator tests.
-      - id: Purview.SourceGeneratorFramework.Testing.TUnit
-        description: TUnit-specific test base classes and assertions.
-    useCases:
-      - audience: contributor
-        title: Build an incremental generator on typed foundations
-        scenario: >-
-          You are writing a non-trivial incremental C# source generator and need typed attribute
-          models, structured code output, and packaging that Roslyn will actually load.
-        code: |
-          <ProjectReference
-            Include="..\MyGenerator\MyGenerator.csproj"
-            PrivateAssets="all"
-            OutputItemType="Analyzer"
-            ReferenceOutputAssembly="false"
-          />
-        language: xml
-        outcome: >-
-          The framework supplies attribute-data models, a structured code writer, a type library, and
-          packaging helpers so the generator stays focused on its own logic.
-        evidence: >-
-          The Purview generators themselves are built on the framework, so it is exercised by real
-          generators rather than being an untested abstraction.
-        docsPage: guide
-      - audience: contributor
-        title: Verify incremental behaviour in tests
-        scenario: >-
-          You need to prove a generator is incremental and produces the code you expect, without
-          assembling a Roslyn driver by hand in every test.
-        outcome: >-
-          The testing package provides SourceGeneratorTestRunner<TGenerator>, a framework-agnostic test
-          base, and assertions such as AssertSingleGeneratedSource and AssertNoCompilationErrors.
-        evidence: >-
-          Step-cache tests and a TUnit integration ship alongside the runner, so incremental regressions
-          surface in CI.
-        docsPage: testing
-
-  - id: results
-    name: Results
-    shortDescription: Result for .NET — expected failures as values the caller must handle.
-    description: >-
-      A small, dependency-free Result<TValue, TError> for .NET that makes
-      expected failures part of a method's contract: not found, invalid, and
-      conflict are values rather than exceptions. A Roslyn source generator adds
-      C# 15 union ergonomics for the error cases, and companion packages carry
-      the result into ASP.NET Core responses and ZodSharp validation problems.
-    origin: >-
-      Services kept re-declaring their own error types and hand-writing the same
-      failure helpers and HTTP mapping, so the result type, the generated
-      helpers, and the adapter packages became one shared package family.
-    useWhen: >-
-      Expected failures are part of your domain model and you want them returned
-      as values the caller must handle, with a strongly typed error case that
-      still reaches the client as a standard HTTP problem response.
-    avoidWhen: >-
-      You target a runtime below .NET 11 with C# 15 preview, or the failures you
-      are modelling are exceptional circumstances that belong in exceptions.
-    repository: purview-dev/results
-    category: application-framework
-    status: preview
-    order: 45
-    docs:
-      source: github-path
-      path: docs/wiki
-      rootPage: Getting-Started.md
-      exclude:
-        - _Sidebar.md
-        - Home.md
-        - index.md
-    targetFrameworks:
-      - net11.0
-    packages:
-      - id: Purview.Results
-        description: The result type, its factories, and IResultValue. No dependencies.
-        primary: true
-      - id: Purview.Results.SourceGenerator
-        description: Incremental generator that emits AsFailure helpers for annotated unions, with a code fix and diagnostic suppression.
-        targetFrameworks:
-          - netstandard2.0
-      - id: Purview.Results.AspNetCore
-        description: Result-to-response mapping, endpoint filter, and dependency-injection registration.
-      - id: Purview.Results.ZodSharp
-        description: Bridges ZodSharp validation results into results.
-      - id: Purview.Results.ZodSharp.AspNetCore
-        description: Renders validation-carrying failures as HttpValidationProblemDetails.
-    related:
-      - zodsharp
-      - sourcegenerator-framework
-    useCases:
-      - audience: developer
-        title: Return expected failures as values
-        scenario: >-
-          You call a store that can fail in ways you expect — not found, disabled,
-          already exists — and you do not want a thrown exception or a generic error
-          string to be the only way the caller learns what happened.
-        code: |
-          Result<Tenant, TenantError> GetTenant(TenantId tenantId) =>
-              _tenants.TryGet(tenantId, out var tenant)
-                  ? Result<Tenant, TenantError>.Success(tenant)
-                  : new TenantNotFound(tenantId).AsFailure<Tenant>();
-        language: csharp
-        outcome: >-
-          The caller branches on the error value itself, so TenantNotFound keeps carrying
-          its TenantId instead of being flattened into a message.
-        evidence: >-
-          The core package has no dependencies: it ships the result type, its factories,
-          and IResultValue without pulling anything else in.
-        docsPage: core-concepts
-      - audience: developer
-        title: Generate the failure helper for every union case
-        scenario: >-
-          You model errors as a C# 15 union and need each case to become the failure side
-          of a result without writing one conversion helper per case by hand.
-        code: |
-          [GenerateResult]
-          public readonly union TenantError(TenantNotFound, TenantDisabled, TenantAlreadyExists);
-        language: csharp
-        outcome: >-
-          The generator emits AsFailure<TValue>() for every case of an annotated union,
-          plus a code fix and a CA1815 suppression, so the declaration needs no pragma.
-        evidence: >-
-          C# forbids the implicit conversion a bare case value would need — no operators
-          in static classes, no conversion operators in extension members, one
-          user-defined conversion per sequence — which is why the helper is per case.
-        docsPage: union-errors
-      - audience: architect
-        title: Map one error union onto HTTP responses
-        scenario: >-
-          The same domain error union surfaces from many minimal-API endpoints, and you do
-          not want a hand-written switch deciding the status code at each one.
-        code: |
-          builder.Services.AddResultsHttp(options => options
-              .Map<TenantNotFound>(error => TypedResults.NotFound())
-              .Map<TenantError>(error => TypedResults.Problem(statusCode: StatusCodes.Status409Conflict))
-          );
-
-          app.MapGet("/tenants/{id:int}", (int id) => GetTenant(id)).WithResultsHttp();
-        language: csharp
-        outcome: >-
-          The mapping is declared once at startup, WithResultsHttp() applies it to the
-          endpoints, and a host can replace IResultsHttpMapper when it needs different
-          behaviour.
-        evidence: >-
-          Mappings resolve in declaration order — any mapping or failure mapper the host
-          declared earlier always wins — so the most specific rule is registered first.
-        docsPage: aspnetcore-integration
-      - audience: team-lead
-        title: Let ZodSharp validation failures become validation problems
-        scenario: >-
-          Endpoints validate input with ZodSharp, and a failed validation should reach the
-          client as the standard ASP.NET Core validation-problem payload rather than an
-          error shape the API has to document separately.
-        code: |
-          {
-            "title": "One or more validation errors occurred.",
-            "status": 400,
-            "errors": { "TenantId": ["Required field 'TenantId' is null"] },
-            "issues": [{ "code": "missing_field", "path": ["TenantId"], "message": "Required field 'TenantId' is null" }]
-          }
-        language: json
-        outcome: >-
-          A failure that implements IValidationErrorCarrier becomes
-          HttpValidationProblemDetails without the host mapping it, unless a per-code or
-          per-category rule answers that failure first.
-        evidence: >-
-          The response is ASP.NET Core's own HttpValidationProblemDetails contract, so API
-          clients keep the error shape they already parse.
-        docsPage: zodsharp-problemdetails
-
-  - id: aspire-resourcekit
-    name: Aspire ResourceKit
-    shortDescription: Strongly typed, source-generated resource kits for .NET Aspire.
-    description: >-
-      A source-generator-powered framework for structuring .NET Aspire AppHost
-      resource composition as strongly typed, test-friendly classes. Generated
-      host wiring, typed options, and enablement toggles keep large AppHosts
-      maintainable and discoverable.
-    origin: >-
-      Large Aspire AppHosts repeatedly accumulated procedural resource wiring and configuration,
-      creating a need for a typed, testable way to package those conventions.
-    useWhen: >-
-      Your Aspire AppHost has reusable resource groups, configuration, or enablement rules that
-      should be strongly typed, discoverable, and testable.
-    avoidWhen: >-
-      Your AppHost is small and direct resource declarations remain clearer than introducing a
-      resource-kit abstraction.
-    repository: purview-dev/aspire-resourcekit
-    category: aspire
-    status: stable
-    order: 50
-    docs:
-      source: github-path
-      path: docs/wiki
-      rootPage: Getting-Started.md
-      exclude:
-        - _Sidebar.md
-        - Home.md
-        - index.md
-    targetFrameworks:
-      - net10.0
-    packages:
-      - id: Purview.Aspire.ResourceKit
-        description: Runtime and source generator for resource kits.
-        primary: true
-    useCases:
-      - audience: architect
-        title: Typed, testable resource groups in a large AppHost
-        scenario: >-
-          A large Aspire AppHost accumulates procedural resource wiring and configuration that is hard
-          to test and easy to misconfigure.
-        code: |
-          [HostKit]
-          partial class ShopHostKit;
-
-          [ResourceDefinition<Projects.Example_Service>("api")]
-          partial class ApiResourceKit
-          {
-              protected override IResourceBuilder<ProjectResource> BuildResource(
-                  IDistributedApplicationBuilder builder)
-                  => builder.AddProject<Projects.Example_Service>(Name);
-          }
-        language: csharp
-        outcome: >-
-          Resource definitions become strongly typed, source-generated classes with generated host
-          wiring and typed options.
-        evidence: >-
-          One [HostKit] plus one [ResourceDefinition] per resource replaces procedural AppHost code, and
-          the analyzer validates the wiring at compile time.
-        docsPage: examples
-      - audience: team-lead
-        title: Configure and toggle resources without editing the AppHost
-        scenario: >-
-          You want enablement rules and configuration to be declarative and discoverable instead of
-          buried in the AppHost entry point.
-        outcome: >-
-          Typed options and enablement toggles are generated for each resource kit, so behaviour is
-          configured rather than coded.
-        evidence: >-
-          Resource kits can be unit tested with the testing helpers, independent of a running AppHost.
-        docsPage: configuration-and-options
-
-  - id: aspirec4
-    name: AspireC4
-    shortDescription: Live LikeC4 architecture diagrams from the Aspire resource graph.
-    description: >-
-      An Aspire extension that generates live LikeC4 architectural diagrams
-      from the Aspire resource graph, with a Roslyn source generator for
-      compile-time validation of tags, kinds, groups, and metadata.
-    origin: >-
-      Aspire already holds a useful model of a distributed application, so manually maintaining a
-      separate architecture diagram was repetition that could be removed.
-    useWhen: >-
-      You use .NET Aspire and want live LikeC4 diagrams derived from the resource graph, with
-      compile-time checks for architectural metadata.
-    avoidWhen: >-
-      You do not use Aspire, need a manually curated architecture model, or require diagrams that
-      intentionally differ from the running application topology.
-    repository: purview-dev/aspirec4
-    category: aspire
-    status: stable
-    order: 55
-    docs:
-      source: github-path
-      path: docs/wiki
-      rootPage: Getting-Started.md
-      exclude:
-        - _Sidebar.md
-        - Home.md
-        - index.md
-    packages:
-      - id: AspireC4.Hosting
-        description: Aspire hosting extension for the AspireC4 plugin, generating a dynamic LikeC4 architecture diagram for your Aspire application.
-        primary: true
-    useCases:
-      - audience: developer
-        title: A live architecture diagram with three lines of code
-        scenario: >-
-          You already describe your distributed application in Aspire and do not want to maintain a
-          separate architecture diagram that drifts from reality.
-        code: |
-          var builder = DistributedApplication.CreateBuilder(args);
-
-          builder.AddAspireC4();
-
-          builder.Build().Run();
-        language: csharp
-        outcome: >-
-          AspireC4 writes the generated LikeC4 model, starts the LikeC4 sidecar, and refreshes the
-          diagram whenever the Aspire application changes.
-        evidence: >-
-          The diagram is derived from the running resource graph, so it cannot silently fall out of date
-          the way a hand-drawn one can.
-        docsPage: dashboard-integration
-      - audience: architect
-        title: Validate architectural metadata at compile time
-        scenario: >-
-          You want tags, kinds, groups, and metadata in your architecture model checked before the
-          application even runs.
-        outcome: >-
-          A Roslyn source generator validates the architectural metadata while the AppHost compiles.
-        evidence: >-
-          Architectural metadata mistakes fail the build instead of surfacing in a diagram nobody reads.
-        docsPage: generated-output
-
-  - id: build
-    name: Build
-    shortDescription: The shared build, test, and release system for purview-dev.
-    description: >-
-      The shared build/test/release system for the purview-dev organisation. A
-      Modular Pipelines based .NET tool packaged as a pinned dotnet tool, exposed
-      through a GitHub composite action and thin reusable workflows. Consuming
-      repositories own configuration; they do not own pipeline source code.
-    origin: >-
-      Maintaining near-identical build, test, pack, and release logic across repositories turned
-      the pipeline itself into reusable tooling.
-    useWhen: >-
-      You maintain a Purview repository and want the shared, centrally versioned build and release
-      conventions used across the organisation.
-    avoidWhen: >-
-      Your repository is outside that convention set or needs a substantially different pipeline
-      whose lifecycle should remain independent.
-    repository: purview-dev/build
-    category: build-tooling
-    status: stable
-    order: 60
-    docs:
-      source: github-path
-      path: docs/wiki
-      rootPage: Getting-Started.md
-      exclude:
-        - _Sidebar.md
-        - Home.md
-        - index.md
-    targetFrameworks:
-      - net10.0
-    install: dotnet-tool
-    packages:
-      - id: Purview.Build
-        description: Pinned dotnet tool implementing the shared pipeline.
-        primary: true
-    useCases:
-      - audience: team-lead
-        title: One reusable pipeline for every repository
-        scenario: >-
-          You maintain several repositories that each repeat the same build, test, pack, and release
-          logic, and the copies drift apart.
-        code: |
-          # .github/workflows/pr.yml
-          jobs:
-            build:
-              uses: purview-dev/build/.github/workflows/purview-build.yml@main
-              secrets: inherit
-        language: yaml
-        outcome: >-
-          Consumers reference the reusable workflow or composite action and configure behaviour with
-          purview-build.json instead of owning pipeline source.
-        evidence: >-
-          Pipeline code lives in one repository; a consuming repository is a short workflow file plus
-          configuration.
-        docsPage: repository-ci-cd
-      - audience: contributor
-        title: Dogfood the same pipeline the organisation uses
-        scenario: >-
-          You want local commands, pull-request CI, and releases to run the exact same tool and
-          conventions, rather than three approximations.
-        outcome: >-
-          The pipeline is a Modular Pipelines .NET tool packaged as a pinned dotnet tool, callable from
-          a composite action, reusable workflows, or the local command line.
-        evidence: >-
-          Purview's own repositories use the published pipeline, so the tool is exercised on every
-          build.
-        docsPage: pipeline-modules
-
-  - id: build-sdk
-    name: Build SDK
-    shortDescription: Convention-driven MSBuild SDK for .NET project defaults.
-    description: >-
-      A reusable MSBuild SDK NuGet package that delivers standardised .NET
-      project defaults, code-style enforcement, test-framework wiring, and
-      Central Package Management integration. Install it once per repo; every
-      project beneath the repo root inherits everything automatically.
-    origin: >-
-      Repeating project properties, analyzers, test wiring, and package-management conventions in
-      every repository made a centrally maintained MSBuild SDK the simpler option.
-    useWhen: >-
-      You want Purview's standard .NET project defaults applied consistently across an entire
-      repository from one versioned SDK declaration.
-    avoidWhen: >-
-      Your repository follows different conventions or needs project-by-project control over the
-      settings the SDK intentionally standardises.
-    repository: purview-dev/build-sdk
-    category: build-tooling
-    status: stable
-    order: 70
-    docs:
-      source: github-path
-      path: docs/wiki
-      rootPage: Getting-Started.md
-      exclude:
-        - _Sidebar.md
-        - Home.md
-        - index.md
-    targetFrameworks:
-      - msbuild
-    install: msbuild-sdk
-    packages:
-      - id: Purview.BuildSdk
-        description: MSBuild SDK for standardised project defaults.
-        primary: true
-    useCases:
-      - audience: team-lead
-        title: Apply repository-wide defaults from one declaration
-        scenario: >-
-          You want standard .NET project defaults, code-style enforcement, test wiring, and central
-          package management without repeating the same properties in every project.
-        code: |
-          {
-            "msbuild-sdks": {
-              "Purview.BuildSdk": "1.0.0"
-            }
-          }
-        language: json
-        outcome: >-
-          Install the SDK once via global.json and Directory.Build.props; every project beneath the
-          repository root inherits everything automatically.
-        evidence: >-
-          One versioned SDK declaration replaces per-project property groups, so conventions are
-          upgraded in one place.
-        docsPage: configuration-reference
-      - audience: contributor
-        title: Bootstrap a new repository
-        scenario: >-
-          You are starting a repository and want the organisation's conventions in place before the
-          first project exists.
-        outcome: >-
-          The SDK can bootstrap a global.json at the repository root when one is missing, then applies
-          project-type detection, analyzers, and test wiring.
-        evidence: >-
-          Repository bootstrap, analyzers, and testing wiring are documented and generated, not copied
-          between repos by hand.
-        docsPage: repository-bootstrap
-
-  - id: dotnet-logging-source-generators
-    name: Logging Source Generators
-    shortDescription: Early interface-based logging generation (archived).
-    description: >-
-      The original experiment in interface-based logging generation for .NET.
-      Archived and superseded by the Purview Telemetry SourceGenerator, which
-      generates logging together with Activities and Metrics from the same
-      interfaces.
-    origin: >-
-      This was the original exploration of interface-driven logging generation and established the
-      approach that later grew into the broader Telemetry SourceGenerator.
-    useWhen: >-
-      Use it only when maintaining an existing dependency that cannot yet move to its successor.
-    avoidWhen: >-
-      For new work, use Telemetry SourceGenerator instead; this project is archived and no longer
-      actively developed.
-    repository: purview-dev/dotnet-logging-source-generators
-    category: source-generation
-    status: archived
-    supersededBy: telemetry-sourcegenerator
-    order: 80
-    targetFrameworks:
-      - net6.0
-      - net7.0
-    packages: []
-    useCases:
-      - audience: developer
-        title: Move to the supported successor
-        scenario: >-
-          You depend on the original interface-based logging generator and want logging, activities, and
-          metrics generated together.
-        outcome: >-
-          Telemetry SourceGenerator generates logging alongside Activities and Metrics from the same
-          interfaces, with DI registration and multi-targeting.
-        evidence: >-
-          This project is archived and no longer developed; the successor covers a superset of its
-          behaviour from one interface.
-
-externalProjects:
-  - id: likec4
-    name: LikeC4
-    shortDescription: Visualize, collaborate, and evolve software architecture with live C4 diagrams from your code.
-    description: >-
-      LikeC4 keeps software architecture always actual and live by modelling it
-      with the C4 model in code (TypeScript/React) and rendering interactive
-      diagrams. Purview maintains the AspireC4 integration that links .NET
-      Aspire applications to LikeC4, and contributes to the LikeC4 project
-      itself.
-    url: https://likec4.dev
-    repository: likec4/likec4
-    category: developer-tooling
-    status: stable
-    featured: true
-    order: 10
diff --git a/src/src/data/projects/aspire-resourcekit.yml b/src/src/data/projects/aspire-resourcekit.yml
new file mode 100644
index 0000000..5064cc7
--- /dev/null
+++ b/src/src/data/projects/aspire-resourcekit.yml
@@ -0,0 +1,73 @@
+$schema: ../../lib/manifest/schema.ts
+
+id: aspire-resourcekit
+name: Aspire ResourceKit
+shortDescription: Strongly typed, source-generated resource kits for .NET Aspire.
+description: >-
+  A source-generator-powered framework for structuring .NET Aspire AppHost
+  resource composition as strongly typed, test-friendly classes. Generated
+  host wiring, typed options, and enablement toggles keep large AppHosts
+  maintainable and discoverable.
+origin: >-
+  Large Aspire AppHosts repeatedly accumulated procedural resource wiring and configuration,
+  creating a need for a typed, testable way to package those conventions.
+useWhen: >-
+  Your Aspire AppHost has reusable resource groups, configuration, or enablement rules that
+  should be strongly typed, discoverable, and testable.
+avoidWhen: >-
+  Your AppHost is small and direct resource declarations remain clearer than introducing a
+  resource-kit abstraction.
+repository: purview-dev/aspire-resourcekit
+category: aspire
+status: stable
+order: 50
+docs:
+  source: github-path
+  path: docs/wiki
+  rootPage: Getting-Started.md
+  exclude:
+    - _Sidebar.md
+    - Home.md
+    - index.md
+targetFrameworks:
+  - net10.0
+packages:
+  - id: Purview.Aspire.ResourceKit
+    description: Runtime and source generator for resource kits.
+    primary: true
+useCases:
+  - audience: architect
+    title: Typed, testable resource groups in a large AppHost
+    scenario: >-
+      A large Aspire AppHost accumulates procedural resource wiring and configuration that is hard
+      to test and easy to misconfigure.
+    code: |
+      [HostKit]
+      partial class ShopHostKit;
+
+      [ResourceDefinition<Projects.Example_Service>("api")]
+      partial class ApiResourceKit
+      {
+          protected override IResourceBuilder<ProjectResource> BuildResource(
+              IDistributedApplicationBuilder builder)
+              => builder.AddProject<Projects.Example_Service>(Name);
+      }
+    language: csharp
+    outcome: >-
+      Resource definitions become strongly typed, source-generated classes with generated host
+      wiring and typed options.
+    evidence: >-
+      One [HostKit] plus one [ResourceDefinition] per resource replaces procedural AppHost code, and
+      the analyzer validates the wiring at compile time.
+    docsPage: examples
+  - audience: team-lead
+    title: Configure and toggle resources without editing the AppHost
+    scenario: >-
+      You want enablement rules and configuration to be declarative and discoverable instead of
+      buried in the AppHost entry point.
+    outcome: >-
+      Typed options and enablement toggles are generated for each resource kit, so behaviour is
+      configured rather than coded.
+    evidence: >-
+      Resource kits can be unit tested with the testing helpers, independent of a running AppHost.
+    docsPage: configuration-and-options
diff --git a/src/src/data/projects/aspirec4.yml b/src/src/data/projects/aspirec4.yml
new file mode 100644
index 0000000..1520acc
--- /dev/null
+++ b/src/src/data/projects/aspirec4.yml
@@ -0,0 +1,64 @@
+$schema: ../../lib/manifest/schema.ts
+
+id: aspirec4
+name: AspireC4
+shortDescription: Live LikeC4 architecture diagrams from the Aspire resource graph.
+description: >-
+  An Aspire extension that generates live LikeC4 architectural diagrams
+  from the Aspire resource graph, with a Roslyn source generator for
+  compile-time validation of tags, kinds, groups, and metadata.
+origin: >-
+  Aspire already holds a useful model of a distributed application, so manually maintaining a
+  separate architecture diagram was repetition that could be removed.
+useWhen: >-
+  You use .NET Aspire and want live LikeC4 diagrams derived from the resource graph, with
+  compile-time checks for architectural metadata.
+avoidWhen: >-
+  You do not use Aspire, need a manually curated architecture model, or require diagrams that
+  intentionally differ from the running application topology.
+repository: purview-dev/aspirec4
+category: aspire
+status: stable
+order: 55
+docs:
+  source: github-path
+  path: docs/wiki
+  rootPage: Getting-Started.md
+  exclude:
+    - _Sidebar.md
+    - Home.md
+    - index.md
+packages:
+  - id: AspireC4.Hosting
+    description: Aspire hosting extension for the AspireC4 plugin, generating a dynamic LikeC4 architecture diagram for your Aspire application.
+    primary: true
+useCases:
+  - audience: developer
+    title: A live architecture diagram with three lines of code
+    scenario: >-
+      You already describe your distributed application in Aspire and do not want to maintain a
+      separate architecture diagram that drifts from reality.
+    code: |
+      var builder = DistributedApplication.CreateBuilder(args);
+
+      builder.AddAspireC4();
+
+      builder.Build().Run();
+    language: csharp
+    outcome: >-
+      AspireC4 writes the generated LikeC4 model, starts the LikeC4 sidecar, and refreshes the
+      diagram whenever the Aspire application changes.
+    evidence: >-
+      The diagram is derived from the running resource graph, so it cannot silently fall out of date
+      the way a hand-drawn one can.
+    docsPage: dashboard-integration
+  - audience: architect
+    title: Validate architectural metadata at compile time
+    scenario: >-
+      You want tags, kinds, groups, and metadata in your architecture model checked before the
+      application even runs.
+    outcome: >-
+      A Roslyn source generator validates the architectural metadata while the AppHost compiles.
+    evidence: >-
+      Architectural metadata mistakes fail the build instead of surfacing in a diagram nobody reads.
+    docsPage: generated-output
diff --git a/src/src/data/projects/build-sdk.yml b/src/src/data/projects/build-sdk.yml
new file mode 100644
index 0000000..8f3e048
--- /dev/null
+++ b/src/src/data/projects/build-sdk.yml
@@ -0,0 +1,70 @@
+$schema: ../../lib/manifest/schema.ts
+
+id: build-sdk
+name: Build SDK
+shortDescription: Convention-driven MSBuild SDK for .NET project defaults.
+description: >-
+  A reusable MSBuild SDK NuGet package that delivers standardised .NET
+  project defaults, code-style enforcement, test-framework wiring, and
+  Central Package Management integration. Install it once per repo; every
+  project beneath the repo root inherits everything automatically.
+origin: >-
+  Repeating project properties, analyzers, test wiring, and package-management conventions in
+  every repository made a centrally maintained MSBuild SDK the simpler option.
+useWhen: >-
+  You want Purview's standard .NET project defaults applied consistently across an entire
+  repository from one versioned SDK declaration.
+avoidWhen: >-
+  Your repository follows different conventions or needs project-by-project control over the
+  settings the SDK intentionally standardises.
+repository: purview-dev/build-sdk
+category: build-tooling
+status: stable
+order: 70
+docs:
+  source: github-path
+  path: docs/wiki
+  rootPage: Getting-Started.md
+  exclude:
+    - _Sidebar.md
+    - Home.md
+    - index.md
+targetFrameworks:
+  - msbuild
+install: msbuild-sdk
+packages:
+  - id: Purview.BuildSdk
+    description: MSBuild SDK for standardised project defaults.
+    primary: true
+useCases:
+  - audience: team-lead
+    title: Apply repository-wide defaults from one declaration
+    scenario: >-
+      You want standard .NET project defaults, code-style enforcement, test wiring, and central
+      package management without repeating the same properties in every project.
+    code: |
+      {
+        "msbuild-sdks": {
+          "Purview.BuildSdk": "1.0.0"
+        }
+      }
+    language: json
+    outcome: >-
+      Install the SDK once via global.json and Directory.Build.props; every project beneath the
+      repository root inherits everything automatically.
+    evidence: >-
+      One versioned SDK declaration replaces per-project property groups, so conventions are
+      upgraded in one place.
+    docsPage: configuration-reference
+  - audience: contributor
+    title: Bootstrap a new repository
+    scenario: >-
+      You are starting a repository and want the organisation's conventions in place before the
+      first project exists.
+    outcome: >-
+      The SDK can bootstrap a global.json at the repository root when one is missing, then applies
+      project-type detection, analyzers, and test wiring.
+    evidence: >-
+      Repository bootstrap, analyzers, and testing wiring are documented and generated, not copied
+      between repos by hand.
+    docsPage: repository-bootstrap
diff --git a/src/src/data/projects/build.yml b/src/src/data/projects/build.yml
new file mode 100644
index 0000000..2297981
--- /dev/null
+++ b/src/src/data/projects/build.yml
@@ -0,0 +1,70 @@
+$schema: ../../lib/manifest/schema.ts
+
+id: build
+name: Build
+shortDescription: The shared build, test, and release system for purview-dev.
+description: >-
+  The shared build/test/release system for the purview-dev organisation. A
+  Modular Pipelines based .NET tool packaged as a pinned dotnet tool, exposed
+  through a GitHub composite action and thin reusable workflows. Consuming
+  repositories own configuration; they do not own pipeline source code.
+origin: >-
+  Maintaining near-identical build, test, pack, and release logic across repositories turned
+  the pipeline itself into reusable tooling.
+useWhen: >-
+  You maintain a Purview repository and want the shared, centrally versioned build and release
+  conventions used across the organisation.
+avoidWhen: >-
+  Your repository is outside that convention set or needs a substantially different pipeline
+  whose lifecycle should remain independent.
+repository: purview-dev/build
+category: build-tooling
+status: stable
+order: 60
+docs:
+  source: github-path
+  path: docs/wiki
+  rootPage: Getting-Started.md
+  exclude:
+    - _Sidebar.md
+    - Home.md
+    - index.md
+targetFrameworks:
+  - net10.0
+install: dotnet-tool
+packages:
+  - id: Purview.Build
+    description: Pinned dotnet tool implementing the shared pipeline.
+    primary: true
+useCases:
+  - audience: team-lead
+    title: One reusable pipeline for every repository
+    scenario: >-
+      You maintain several repositories that each repeat the same build, test, pack, and release
+      logic, and the copies drift apart.
+    code: |
+      # .github/workflows/pr.yml
+      jobs:
+        build:
+          uses: purview-dev/build/.github/workflows/purview-build.yml@main
+          secrets: inherit
+    language: yaml
+    outcome: >-
+      Consumers reference the reusable workflow or composite action and configure behaviour with
+      purview-build.json instead of owning pipeline source.
+    evidence: >-
+      Pipeline code lives in one repository; a consuming repository is a short workflow file plus
+      configuration.
+    docsPage: repository-ci-cd
+  - audience: contributor
+    title: Dogfood the same pipeline the organisation uses
+    scenario: >-
+      You want local commands, pull-request CI, and releases to run the exact same tool and
+      conventions, rather than three approximations.
+    outcome: >-
+      The pipeline is a Modular Pipelines .NET tool packaged as a pinned dotnet tool, callable from
+      a composite action, reusable workflows, or the local command line.
+    evidence: >-
+      Purview's own repositories use the published pipeline, so the tool is exercised on every
+      build.
+    docsPage: pipeline-modules
diff --git a/src/src/data/projects/containers.yml b/src/src/data/projects/containers.yml
new file mode 100644
index 0000000..c2ad614
--- /dev/null
+++ b/src/src/data/projects/containers.yml
@@ -0,0 +1,177 @@
+$schema: ../../lib/manifest/schema.ts
+
+id: containers
+name: Containers
+shortDescription: Throwaway Linux containers for .NET integration tests — on WSL Containers with no Docker installation, or on Docker.
+description: >-
+  A Testcontainers-style library for .NET with one API and two interchangeable backends: Microsoft
+  WSL Containers (WSLC) with no Docker installation, or Docker through Testcontainers. Containers are
+  created through backend-neutral abstractions (Purview.Containers.Core) and the backend is resolved at
+  run time, so the same test code runs on WSLC (Purview.Containers.Wsl) or Docker
+  (Purview.Containers.Docker) unchanged. The WSLC backend talks to the WSLC managed C# API directly —
+  no wslc.exe, no docker CLI, no Docker.DotNet.
+  Typed service modules add PostgreSQL, Redis, SQL Server, MySQL, RabbitMQ, Azurite, and NATS, each
+  with its own defaults, configuration, readiness wait strategy, and connection-string helper. The
+  umbrella package Purview.Containers brings the abstractions plus both backends in a single reference.
+origin: >-
+  Integration tests that use real infrastructure on Windows needed a Docker daemon installed and
+  running first. WSL Containers makes the container runtime a Windows feature, so the same
+  throwaway-container workflow could be built straight on its managed API — and the same abstractions
+  could fall back to Docker wherever WSLC is not available, which is why the library grew a portable
+  net10.0 facade and a Docker backend rather than staying Windows-only.
+useWhen: >-
+  You want real PostgreSQL, Redis, SQL Server, MySQL, RabbitMQ, Azurite, or NATS instances in
+  integration tests, and you want the same suite to run on WSL Containers on a Windows developer
+  machine and on Docker in CI without changing a line of test code.
+avoidWhen: >-
+  You need a container runtime other than WSL Containers or Docker, or you require API stability: the
+  public API, defaults, and packaging rules can change between prereleases and there is no production
+  support guarantee.
+repository: purview-dev/containers
+category: developer-tooling
+status: preview
+experimental: true
+order: 90
+docs:
+  source: github-path
+  path: docs/wiki
+  exclude:
+    - _Sidebar.md
+    - Home.md
+targetFrameworks:
+  - net10.0
+packages:
+  - id: Purview.Containers
+    description: The umbrella — references the abstractions and both backends, so one reference runs the same tests on WSLC on Windows and Docker elsewhere.
+    primary: true
+  - id: Purview.Containers.Core
+    description: Backend-neutral abstractions — the container contract, builders, wait strategies, images, mounts, networking, diagnostics, and backend selection.
+  - id: Purview.Containers.Wsl
+    description: WSL Containers backend — sessions, images, ports, mounts, exec, logs, and diagnostics for WSLC; a portable facade plus the Windows implementation.
+    targetFrameworks:
+      - net10.0
+      - net10.0-windows10.0.19041.0
+  - id: Purview.Containers.Docker
+    description: Docker backend — the same containers on any reachable Docker daemon, driven by Testcontainers.
+  - id: Purview.Containers.PostgreSql
+    description: PostgreSQL module — defaults, configuration, pg_isready readiness, and Npgsql connection string.
+  - id: Purview.Containers.Redis
+    description: Redis module — defaults, configuration, redis-cli ping readiness, and connection string.
+  - id: Purview.Containers.MsSql
+    description: SQL Server module — defaults, licence acceptance, configuration, and connection string.
+  - id: Purview.Containers.MySql
+    description: MySQL module — defaults, configuration, readiness wait strategy, and connection string.
+  - id: Purview.Containers.RabbitMq
+    description: RabbitMQ module — defaults, credentials, configuration, and AMQP connection string.
+  - id: Purview.Containers.Azurite
+    description: Azurite module — defaults, account key, and Azure Storage connection string.
+  - id: Purview.Containers.Nats
+    description: NATS module — defaults, configuration, and client endpoint.
+acknowledgments:
+  - name: Testcontainers for .NET
+    url: https://github.com/testcontainers/testcontainers-dotnet
+    description: The Docker backend is driven by Testcontainers and the module connection-string shapes follow it; Purview.Containers is not affiliated with or endorsed by the Testcontainers project.
+  - name: Microsoft WSL Containers
+    url: https://www.nuget.org/packages/Microsoft.WSL.Containers
+    description: The managed C# API behind WSLC that the WSL Containers backend is built against directly, with no wslc.exe or docker CLI.
+useCases:
+  - audience: developer
+    title: The same test on WSL Containers or Docker
+    scenario: >-
+      Your integration suite needs real infrastructure, but the machines it runs on differ: a Windows
+      developer laptop with WSL Containers and a Linux CI runner with a Docker daemon.
+    code: |
+      await using var container = new ContainerBuilder()
+          .WithImage("docker.io/library/redis:latest")
+          .WithPortBinding(6379, assignRandomHostPort: true)
+          .WithWaitStrategy(Wait.ForTcpPort(6379))
+          .Build();
+
+      await container.StartAsync();
+      ushort port = container.GetMappedPublicPort(6379);
+    language: csharp
+    outcome: >-
+      The test never names a backend. Automatic selection prefers WSLC where it is usable and falls
+      through to Docker everywhere else; PURVIEW_CONTAINERS_BACKEND pins one (wsl or docker) when a job
+      should fail loudly instead of falling back.
+    evidence: >-
+      One API, two backends: the same builder, wait strategies, and connection-string helpers run on both
+      Purview.Containers.Wsl and Purview.Containers.Docker with no code change.
+    docsPage: backends
+  - audience: developer
+    title: Zero-config tests that pick a backend themselves
+    scenario: >-
+      You want real PostgreSQL and Redis in your tests and would rather not choose a container runtime,
+      add a backend package explicitly, or write any registration or environment configuration.
+    code: |
+      await using var postgres = new PostgreSqlBuilder().WithDatabase("app").Build();
+      await postgres.StartAsync();                         // waits for pg_isready
+
+      await using var connection = new NpgsqlConnection(postgres.GetConnectionString());
+      await connection.OpenAsync();
+    language: csharp
+    outcome: >-
+      Add the umbrella Purview.Containers to a plain net10.0 project: each backend package's
+      buildTransitive assets generate the registration in your assembly, so WSLC is used on a Windows
+      machine and Docker everywhere else with no code or configuration.
+    evidence: >-
+      Each backend package ships buildTransitive assets that generate a module initializer in the
+      consumer's assembly, so no registration line and no environment variable are required; those
+      assets flow transitively through the umbrella.
+    docsPage: using-in-your-tests
+  - audience: developer
+    title: A typed service module instead of a bare image
+    scenario: >-
+      You need a throwaway PostgreSQL (or Redis, SQL Server, MySQL, RabbitMQ, Azurite, NATS) and do not
+      want to look up its image, port, environment, and readiness probe every time.
+    code: |
+      await using var postgres = new PostgreSqlBuilder()
+          .WithDatabase("tests")
+          .WithPassword("postgres")
+          .Build();
+
+      await postgres.StartAsync();   // returns once pg_isready succeeds
+    language: csharp
+    outcome: >-
+      The module supplies the default image, port mapping, and readiness wait strategy, so StartAsync()
+      returns once the instance is genuinely ready, and GetConnectionString() points at the mapped host
+      port — the same shape Testcontainers modules use.
+    evidence: >-
+      Seven service modules ship (PostgreSQL, Redis, SQL Server, MySQL, RabbitMQ, Azurite, NATS), and a
+      module contributes only its image, ports, environment, wait strategy, and connection string —
+      never the shared runtime.
+    docsPage: modules
+  - audience: architect
+    title: One Windows prerequisite, Docker in CI
+    scenario: >-
+      You want integration tests that use real infrastructure on Windows developer machines and CI
+      agents, without making Docker Desktop a requirement of the minimum Windows toolchain.
+    code: |
+      foreach (var backend in await ContainerBackends.ProbeAllAsync())
+      {
+          Console.WriteLine($"{backend.Name}: usable={backend.IsUsable} version={backend.Version}");
+      }
+    language: csharp
+    outcome: >-
+      The abstractions and modules are portable net10.0, so a platform-neutral project binds the WSLC
+      facade on Windows and behaves as Docker-only everywhere else; ProbeAllAsync() reports exactly
+      which runtime a machine has before a test runs.
+    evidence: >-
+      Purview.Containers.Wsl ships a portable net10.0 facade and a net10.0-windows10.0.19041.0
+      implementation, and the repository builds twenty-one throwaway consumer projects to prove the
+      target-framework contract and the PCC0001/PCC0002 guards.
+    docsPage: consumer-requirements
+  - audience: contributor
+    title: Add a service module
+    scenario: >-
+      You want to add a module for another service, or fix one of the existing seven, and need to know
+      exactly what a module is allowed to contribute.
+    outcome: >-
+      A module supplies only the default image, ports, environment, its own WithXxx configuration, a
+      wait strategy, and connection-string helpers; the generic builder snapshots the accumulated state
+      into an immutable configuration, so modules never duplicate container runtime infrastructure.
+    evidence: >-
+      Every module references Purview.Containers.Core only — never a backend package — which is what lets
+      one module package run on WSLC or Docker, and each module has its own unit and integration test
+      project to prove itself.
+    docsPage: contributing-modules
diff --git a/src/src/data/projects/dotnet-logging-source-generators.yml b/src/src/data/projects/dotnet-logging-source-generators.yml
new file mode 100644
index 0000000..63fece8
--- /dev/null
+++ b/src/src/data/projects/dotnet-logging-source-generators.yml
@@ -0,0 +1,39 @@
+$schema: ../../lib/manifest/schema.ts
+
+id: dotnet-logging-source-generators
+name: Logging Source Generators
+shortDescription: Early interface-based logging generation (archived).
+description: >-
+  The original experiment in interface-based logging generation for .NET.
+  Archived and superseded by the Purview Telemetry SourceGenerator, which
+  generates logging together with Activities and Metrics from the same
+  interfaces.
+origin: >-
+  This was the original exploration of interface-driven logging generation and established the
+  approach that later grew into the broader Telemetry SourceGenerator.
+useWhen: >-
+  Use it only when maintaining an existing dependency that cannot yet move to its successor.
+avoidWhen: >-
+  For new work, use Telemetry SourceGenerator instead; this project is archived and no longer
+  actively developed.
+repository: purview-dev/dotnet-logging-source-generators
+category: source-generation
+status: archived
+supersededBy: telemetry-sourcegenerator
+order: 80
+targetFrameworks:
+  - net6.0
+  - net7.0
+packages: []
+useCases:
+  - audience: developer
+    title: Move to the supported successor
+    scenario: >-
+      You depend on the original interface-based logging generator and want logging, activities, and
+      metrics generated together.
+    outcome: >-
+      Telemetry SourceGenerator generates logging alongside Activities and Metrics from the same
+      interfaces, with DI registration and multi-targeting.
+    evidence: >-
+      This project is archived and no longer developed; the successor covers a superset of its
+      behaviour from one interface.
diff --git a/src/src/data/projects/event-sourcing.yml b/src/src/data/projects/event-sourcing.yml
new file mode 100644
index 0000000..6108a07
--- /dev/null
+++ b/src/src/data/projects/event-sourcing.yml
@@ -0,0 +1,104 @@
+$schema: ../../lib/manifest/schema.ts
+
+id: event-sourcing
+name: Event Sourcing
+shortDescription: Aggregate-based event sourcing for .NET across any store.
+description: >-
+  A .NET event sourcing framework for building aggregate-based applications.
+  Provider-agnostic store facades, source-generated aggregates and events,
+  transaction coordination for multi-aggregate saves, queryable snapshots
+  and read models, and storage providers for SQL Server, PostgreSQL,
+  MongoDB, Azure Storage, Azure Cosmos DB, and in-memory.
+origin: >-
+  Aggregate, event, persistence, and transaction patterns kept recurring across applications,
+  so the reusable parts were separated from any one storage provider.
+useWhen: >-
+  Your domain benefits from aggregate-based event sourcing and you want storage choices,
+  snapshots, read models, and transactions behind consistent abstractions.
+avoidWhen: >-
+  A conventional state-based model is sufficient, or your application does not need the
+  operational and modelling trade-offs that come with event sourcing.
+repository: purview-dev/event-sourcing
+category: application-framework
+status: preview
+featured: true
+order: 20
+docs:
+  source: github-path
+  path: docs/wiki
+  rootPage: Getting-Started.md
+  exclude:
+    - _Sidebar.md
+    - Home.md
+    - index.md
+targetFrameworks:
+  - net8.0
+  - net9.0
+  - net10.0
+packages:
+  - id: Purview.EventSourcing
+    description: Core abstractions, aggregates, facades, transactions, DI, and source generation.
+    primary: true
+  - id: Purview.EventSourcing.SqlServer
+    description: Azure SQL / SQL Server event stream and queryable snapshot stores.
+  - id: Purview.EventSourcing.Postgres
+    description: PostgreSQL event stream and queryable snapshot stores.
+  - id: Purview.EventSourcing.AzureStorage
+    description: Azure Table / Blob event store.
+  - id: Purview.EventSourcing.MongoDB
+    description: MongoDB event stream and queryable snapshot stores.
+  - id: Purview.EventSourcing.CosmosDb
+    description: Azure Cosmos DB queryable snapshot store.
+  - id: Purview.EventSourcing.InMemory
+    description: In-memory event and snapshot stores for local and test scenarios.
+  - id: Purview.EventSourcing.Validation.FluentValidation
+    description: FluentValidation adapter for aggregate save-time validation.
+  - id: Purview.EventSourcing.Validation.ZodSharp
+    description: Purview.ZodSharp adapter for aggregate save-time validation.
+useCases:
+  - audience: developer
+    title: An aggregate that persists as events
+    scenario: >-
+      You want aggregate-based event sourcing without hand-writing the event stream, snapshot, and
+      transaction plumbing.
+    code: |
+      [Aggregate]
+      public partial class OrderAggregate : AggregateBase
+      {
+          public string CustomerId { get; private set; } = default!;
+          public decimal Total { get; private set; }
+
+          [Event]
+          public partial void CreateOrder(string customerId);
+
+          [Event]
+          public partial void AddLineItem(string productId, string productName, int quantity, decimal unitPrice);
+      }
+    language: csharp
+    outcome: >-
+      The source generator produces the aggregate plumbing; provider packages add stores for SQL
+      Server, PostgreSQL, MongoDB, Azure Storage, Cosmos DB, or in-memory.
+    evidence: >-
+      One [Aggregate] declaration, and switching storage means swapping a provider package rather
+      than rewriting the domain.
+    docsPage: solution-design-guide
+  - audience: architect
+    title: Choose the store late, keep the domain stable
+    scenario: >-
+      You need to start on one database and move providers later, but you do not want persistence
+      choices to leak into the domain model.
+    code: |
+      builder.Services.AddSqlServerEventStore();
+      builder.Services.AddSqlServerSnapshotQueryableEventStore();
+    language: csharp
+    outcome: >-
+      Domain code depends on provider-agnostic facades, while concrete stores live behind separate
+      packages and registration extensions.
+    evidence: >-
+      SQL Server, PostgreSQL, MongoDB, Azure Storage, and Cosmos DB are interchangeable at the
+      registration level, so the domain never references a store.
+    docsPage: sql-server-guide
+related:
+  - zodsharp
+  - value-objects
+discussions: false
diff --git a/src/src/data/projects/results.yml b/src/src/data/projects/results.yml
new file mode 100644
index 0000000..16d19c8
--- /dev/null
+++ b/src/src/data/projects/results.yml
@@ -0,0 +1,133 @@
+$schema: ../../lib/manifest/schema.ts
+
+id: results
+name: Results
+shortDescription: Result for .NET — expected failures as values the caller must handle.
+description: >-
+  A small, dependency-free Result<TValue, TError> for .NET that makes
+  expected failures part of a method's contract: not found, invalid, and
+  conflict are values rather than exceptions. A Roslyn source generator adds
+  C# 15 union ergonomics for the error cases, and companion packages carry
+  the result into ASP.NET Core responses and ZodSharp validation problems.
+origin: >-
+  Services kept re-declaring their own error types and hand-writing the same
+  failure helpers and HTTP mapping, so the result type, the generated
+  helpers, and the adapter packages became one shared package family.
+useWhen: >-
+  Expected failures are part of your domain model and you want them returned
+  as values the caller must handle, with a strongly typed error case that
+  still reaches the client as a standard HTTP problem response.
+avoidWhen: >-
+  You target a runtime below .NET 11 with C# 15 preview, or the failures you
+  are modelling are exceptional circumstances that belong in exceptions.
+repository: purview-dev/results
+category: application-framework
+status: preview
+order: 45
+docs:
+  source: github-path
+  path: docs/wiki
+  rootPage: Getting-Started.md
+  exclude:
+    - _Sidebar.md
+    - Home.md
+    - index.md
+targetFrameworks:
+  - net11.0
+packages:
+  - id: Purview.Results
+    description: The result type, its factories, and IResultValue. No dependencies.
+    primary: true
+  - id: Purview.Results.SourceGenerator
+    description: Incremental generator that emits AsFailure helpers for annotated unions, with a code fix and diagnostic suppression.
+    targetFrameworks:
+      - netstandard2.0
+  - id: Purview.Results.AspNetCore
+    description: Result-to-response mapping, endpoint filter, and dependency-injection registration.
+  - id: Purview.Results.ZodSharp
+    description: Bridges ZodSharp validation results into results.
+  - id: Purview.Results.ZodSharp.AspNetCore
+    description: Renders validation-carrying failures as HttpValidationProblemDetails.
+related:
+  - zodsharp
+  - sourcegenerator-framework
+useCases:
+  - audience: developer
+    title: Return expected failures as values
+    scenario: >-
+      You call a store that can fail in ways you expect — not found, disabled,
+      already exists — and you do not want a thrown exception or a generic error
+      string to be the only way the caller learns what happened.
+    code: |
+      Result<Tenant, TenantError> GetTenant(TenantId tenantId) =>
+          _tenants.TryGet(tenantId, out var tenant)
+              ? Result<Tenant, TenantError>.Success(tenant)
+              : new TenantNotFound(tenantId).AsFailure<Tenant>();
+    language: csharp
+    outcome: >-
+      The caller branches on the error value itself, so TenantNotFound keeps carrying
+      its TenantId instead of being flattened into a message.
+    evidence: >-
+      The core package has no dependencies: it ships the result type, its factories,
+      and IResultValue without pulling anything else in.
+    docsPage: core-concepts
+  - audience: developer
+    title: Generate the failure helper for every union case
+    scenario: >-
+      You model errors as a C# 15 union and need each case to become the failure side
+      of a result without writing one conversion helper per case by hand.
+    code: |
+      [GenerateResult]
+      public readonly union TenantError(TenantNotFound, TenantDisabled, TenantAlreadyExists);
+    language: csharp
+    outcome: >-
+      The generator emits AsFailure<TValue>() for every case of an annotated union,
+      plus a code fix and a CA1815 suppression, so the declaration needs no pragma.
+    evidence: >-
+      C# forbids the implicit conversion a bare case value would need — no operators
+      in static classes, no conversion operators in extension members, one
+      user-defined conversion per sequence — which is why the helper is per case.
+    docsPage: union-errors
+  - audience: architect
+    title: Map one error union onto HTTP responses
+    scenario: >-
+      The same domain error union surfaces from many minimal-API endpoints, and you do
+      not want a hand-written switch deciding the status code at each one.
+    code: |
+      builder.Services.AddResultsHttp(options => options
+          .Map<TenantNotFound>(error => TypedResults.NotFound())
+          .Map<TenantError>(error => TypedResults.Problem(statusCode: StatusCodes.Status409Conflict))
+      );
+
+      app.MapGet("/tenants/{id:int}", (int id) => GetTenant(id)).WithResultsHttp();
+    language: csharp
+    outcome: >-
+      The mapping is declared once at startup, WithResultsHttp() applies it to the
+      endpoints, and a host can replace IResultsHttpMapper when it needs different
+      behaviour.
+    evidence: >-
+      Mappings resolve in declaration order — any mapping or failure mapper the host
+      declared earlier always wins — so the most specific rule is registered first.
+    docsPage: aspnetcore-integration
+  - audience: team-lead
+    title: Let ZodSharp validation failures become validation problems
+    scenario: >-
+      Endpoints validate input with ZodSharp, and a failed validation should reach the
+      client as the standard ASP.NET Core validation-problem payload rather than an
+      error shape the API has to document separately.
+    code: |
+      {
+        "title": "One or more validation errors occurred.",
+        "status": 400,
+        "errors": { "TenantId": ["Required field 'TenantId' is null"] },
+        "issues": [{ "code": "missing_field", "path": ["TenantId"], "message": "Required field 'TenantId' is null" }]
+      }
+    language: json
+    outcome: >-
+      A failure that implements IValidationErrorCarrier becomes
+      HttpValidationProblemDetails without the host mapping it, unless a per-code or
+      per-category rule answers that failure first.
+    evidence: >-
+      The response is ASP.NET Core's own HttpValidationProblemDetails contract, so API
+      clients keep the error shape they already parse.
+    docsPage: zodsharp-problemdetails
diff --git a/src/src/data/projects/sourcegenerator-framework.yml b/src/src/data/projects/sourcegenerator-framework.yml
new file mode 100644
index 0000000..b3a3a37
--- /dev/null
+++ b/src/src/data/projects/sourcegenerator-framework.yml
@@ -0,0 +1,77 @@
+$schema: ../../lib/manifest/schema.ts
+
+id: sourcegenerator-framework
+name: SourceGenerator Framework
+shortDescription: A typed framework for building incremental C# source generators.
+description: >-
+  A strongly typed framework for building, testing, and maintaining
+  incremental C# source generators with Roslyn. Includes structured code
+  generation, attribute data models, type libraries, and a step-cache test
+  runner for verifying incremental behaviour.
+origin: >-
+  Building several incremental generators exposed the same needs for typed models, structured
+  output, testing, and cache verification, so those foundations became a shared framework.
+useWhen: >-
+  You are building a non-trivial incremental C# source generator and want reusable modelling,
+  code-writing, packaging, and testing infrastructure.
+avoidWhen: >-
+  Your generator is small enough for the Roslyn APIs directly, or adopting a framework would
+  hide behaviour your implementation needs to control precisely.
+repository: purview-dev/sourcegenerator-framework
+category: source-generation
+status: preview
+featured: true
+order: 40
+docs:
+  source: github-path
+  path: docs/wiki
+  rootPage: Getting-Started.md
+  exclude:
+    - _Sidebar.md
+    - Home.md
+    - index.md
+targetFrameworks:
+  - net8.0
+  - net9.0
+  - net10.0
+packages:
+  - id: Purview.SourceGeneratorFramework
+    description: Core helpers, models, and MSBuild integration for incremental generators.
+    primary: true
+  - id: Purview.SourceGeneratorFramework.Testing
+    description: Framework-agnostic test runner and assertions for generator tests.
+  - id: Purview.SourceGeneratorFramework.Testing.TUnit
+    description: TUnit-specific test base classes and assertions.
+useCases:
+  - audience: contributor
+    title: Build an incremental generator on typed foundations
+    scenario: >-
+      You are writing a non-trivial incremental C# source generator and need typed attribute
+      models, structured code output, and packaging that Roslyn will actually load.
+    code: |
+      <ProjectReference
+        Include="..\MyGenerator\MyGenerator.csproj"
+        PrivateAssets="all"
+        OutputItemType="Analyzer"
+        ReferenceOutputAssembly="false"
+      />
+    language: xml
+    outcome: >-
+      The framework supplies attribute-data models, a structured code writer, a type library, and
+      packaging helpers so the generator stays focused on its own logic.
+    evidence: >-
+      The Purview generators themselves are built on the framework, so it is exercised by real
+      generators rather than being an untested abstraction.
+    docsPage: guide
+  - audience: contributor
+    title: Verify incremental behaviour in tests
+    scenario: >-
+      You need to prove a generator is incremental and produces the code you expect, without
+      assembling a Roslyn driver by hand in every test.
+    outcome: >-
+      The testing package provides SourceGeneratorTestRunner<TGenerator>, a framework-agnostic test
+      base, and assertions such as AssertSingleGeneratedSource and AssertNoCompilationErrors.
+    evidence: >-
+      Step-cache tests and a TUnit integration ship alongside the runner, so incremental regressions
+      surface in CI.
+    docsPage: testing
diff --git a/src/src/data/projects/telemetry-sourcegenerator.yml b/src/src/data/projects/telemetry-sourcegenerator.yml
new file mode 100644
index 0000000..680482a
--- /dev/null
+++ b/src/src/data/projects/telemetry-sourcegenerator.yml
@@ -0,0 +1,85 @@
+$schema: ../../lib/manifest/schema.ts
+
+id: telemetry-sourcegenerator
+name: Telemetry SourceGenerator
+shortDescription: Interface-based telemetry for .NET with zero boilerplate.
+description: >-
+  A source generator that turns simple interface methods into
+  OpenTelemetry-aligned Activities, structured ILogger logging, and Metrics.
+  Define telemetry once on an interface; the generator emits the
+  implementation, DI registration helpers, and multi-target generation —
+  no runtime reflection, no boilerplate.
+origin: >-
+  Repeating the same logging, activity, and metric wiring across services made telemetry a
+  strong candidate for one interface-driven, compile-time implementation.
+useWhen: >-
+  You want strongly typed OpenTelemetry-aligned telemetry from interfaces, with generated
+  implementations and dependency-injection registration.
+avoidWhen: >-
+  Your telemetry is highly dynamic, cannot be described at compile time, or is already handled
+  consistently by another instrumentation layer.
+repository: purview-dev/telemetry-sourcegenerator
+category: observability
+status: stable
+featured: true
+order: 10
+docs:
+  source: github-path
+  path: docs/wiki
+  rootPage: Getting-Started.md
+  exclude:
+    - _Sidebar.md
+    - Home.md
+    - index.md
+targetFrameworks:
+  - net8.0
+  - net9.0
+  - net10.0
+packages:
+  - id: Purview.Telemetry.SourceGenerator
+    description: Core package with the Roslyn source generator and attribute library.
+    primary: true
+    targetFrameworks:
+      - netstandard2.0
+useCases:
+  - audience: developer
+    title: Tracing, logging, and metrics from a single interface
+    scenario: >-
+      You want OpenTelemetry activities, structured logs, and metrics around an order service, but
+      you do not want to hand-write the ActivitySource, ILogger, and Meter wiring in every class.
+    code: |
+      [ActivitySource]
+      [Logger]
+      [Meter]
+      public interface IOrderServiceTelemetry
+      {
+          [Activity]
+          [Info]
+          [AutoCounter]
+          Activity? PlacingOrder(int orderId, [Baggage] string region);
+      }
+    language: csharp
+    outcome: >-
+      The generator emits the implementation and an AddOrderServiceTelemetry() DI extension; you
+      register it once and inject the interface wherever telemetry is needed.
+    evidence: >-
+      One interface replaces the ActivitySource, ILogger, and Meter boilerplate you would otherwise
+      repeat in every service.
+  - audience: architect
+    title: Standardise telemetry names across services
+    scenario: >-
+      You want consistent OpenTelemetry meter and activity-source names across many services instead
+      of ad-hoc string literals scattered through the codebase.
+    code: |
+      builder.AddServiceDefaults(
+          TelemetryNames.MeterNames,
+          TelemetryNames.ActivitySourceNames);
+    language: csharp
+    outcome: >-
+      A generated TelemetryNames static class holds the names, so registration happens once at
+      startup rather than in every service.
+    evidence: >-
+      Naming conventions are generated, so snake_case tags and hierarchical metrics stay consistent
+      without a review checklist.
+    docsPage: generation
+discussions: false
diff --git a/src/src/data/projects/value-objects.yml b/src/src/data/projects/value-objects.yml
new file mode 100644
index 0000000..460fde3
--- /dev/null
+++ b/src/src/data/projects/value-objects.yml
@@ -0,0 +1,88 @@
+$schema: ../../lib/manifest/schema.ts
+
+id: value-objects
+name: Value Objects
+shortDescription: Source-generated scalar and complex value objects for .NET.
+description: >-
+  F#-style single-case types for C#. Mark a partial struct or class with
+  [Scalar] or [ValueObject] and an incremental source generator produces
+  Create/Hydrate factories with normalization and validation, equality,
+  comparison, implicit conversions, JSON converters, and contextual
+  creation. Value objects serialize as their underlying value, map cleanly
+  onto Entity Framework JSON columns, and can be validated with
+  Purview.ZodSharp schemas.
+origin: >-
+  Hand-writing the same factories, equality rules, conversions, serializers, and persistence
+  integration for domain values made the pattern an obvious source-generation target.
+useWhen: >-
+  Your domain uses meaningful scalar or complex value types and you want their repetitive
+  implementation generated from a small, explicit declaration.
+avoidWhen: >-
+  A primitive or record already expresses the concept clearly, or generated conversion and
+  serialization behaviour would be more machinery than the domain needs.
+repository: purview-dev/value-objects
+category: source-generation
+status: preview
+featured: true
+order: 35
+docs:
+  source: github-path
+  path: docs
+  rootPage: Getting-Started.md
+  exclude:
+    - _Sidebar.md
+    - Home.md
+    - index.md
+targetFrameworks:
+  - net8.0
+  - net9.0
+  - net10.0
+packages:
+  - id: Purview.ValueObjects
+    description: Runtime contracts, source generator, and analyzer for scalar and complex value objects.
+    primary: true
+useCases:
+  - audience: developer
+    title: A domain scalar without the boilerplate
+    scenario: >-
+      You want a strong EmailAddress type with normalisation and validation, without hand-writing
+      factories, equality, conversions, and a JSON converter.
+    code: |
+      [Scalar]
+      public readonly partial record struct EmailAddress
+      {
+          public string Value { get; }
+
+          static partial void OnNormalize(ref string value)
+              => value = value?.Trim().ToLowerInvariant()!;
+      }
+    language: csharp
+    outcome: >-
+      The generator adds Create, Hydrate, TryCreate, and Empty, plus equality, comparison, implicit
+      conversions, and a JSON converter.
+    evidence: >-
+      One declaration replaces the factory, equality, comparison, conversion, and serialization code
+      you would otherwise maintain by hand.
+    docsPage: value-object-design
+  - audience: developer
+    title: Map a value object onto an Entity Framework column
+    scenario: >-
+      You use a value object in your domain and want it to persist transparently instead of writing
+      converters at every mapping site.
+    code: |
+      var email = EmailAddress.Create("  Demo@Example.COM  ");
+      // email.Value == "demo@example.com"
+
+      bool ok = EmailAddress.TryCreate("not-an-email", out _);
+      // ok == false
+    language: csharp
+    outcome: >-
+      Value objects serialize as their underlying value and map onto Entity Framework JSON columns,
+      with optional Purview.ZodSharp validation.
+    evidence: >-
+      Persistence and serialization come from the generated type, so mapping code is not duplicated
+      per entity.
+    docsPage: entity-framework
+related:
+  - zodsharp
+  - event-sourcing
diff --git a/src/src/data/projects/zodsharp.yml b/src/src/data/projects/zodsharp.yml
new file mode 100644
index 0000000..6a3f899
--- /dev/null
+++ b/src/src/data/projects/zodsharp.yml
@@ -0,0 +1,90 @@
+$schema: ../../lib/manifest/schema.ts
+
+id: zodsharp
+name: ZodSharp
+shortDescription: Zero-allocation schema validation for C# — a Zod port.
+description: >-
+  A high-performance schema validation library for C#, ported from
+  TypeScript Zod by way of the guinhx/ZodSharp C# port. Struct-based rules,
+  a fluent API, JSON Schema export and import, source-generated validators,
+  and zero-allocation validation on every valid input path. Integrates with
+  System.Text.Json, Newtonsoft.Json, and ASP.NET Core ProblemDetails.
+origin: >-
+  Schema validation was repeatedly needed at application boundaries, but existing approaches
+  did not combine a fluent Zod-style model with predictable, allocation-conscious execution.
+useWhen: >-
+  You want composable C# schemas, compile-time validator generation, or JSON Schema interop with
+  tight control over validation behaviour and allocations.
+avoidWhen: >-
+  Data annotations or an existing validation library already cover your requirements, or Zod-style
+  schemas would add an unnecessary second validation model.
+repository: purview-dev/zodsharp
+category: validation
+status: stable
+featured: true
+order: 30
+docs:
+  source: github-path
+  path: docs/wiki
+  rootPage: Getting-Started.md
+  exclude:
+    - _Sidebar.md
+    - Home.md
+    - index.md
+targetFrameworks:
+  - net8.0
+  - net9.0
+  - net10.0
+packages:
+  - id: Purview.ZodSharp
+    description: Core validation library and source generator.
+    primary: true
+  - id: Purview.ZodSharp.SystemTextJson
+    description: System.Text.Json integration and JSON Schema import.
+  - id: Purview.ZodSharp.NewtonsoftJson
+    description: Newtonsoft.Json integration and JSON Schema import.
+  - id: Purview.ZodSharp.AspNetCore
+    description: ASP.NET Core ProblemDetails integration.
+related:
+  - value-objects
+acknowledgments:
+  - name: Zod
+    url: https://github.com/colinhacks/zod
+    description: The original JavaScript/TypeScript schema validation library.
+  - name: ZodSharp (guinhx)
+    url: https://github.com/guinhx/ZodSharp
+    description: The C# port of Zod, and the fork this project is based on.
+useCases:
+  - audience: developer
+    title: Validate input without exceptions or allocations
+    scenario: >-
+      You need to validate values at an application boundary and prefer a result you can inspect
+      over exception-driven control flow.
+    code: |
+      var nameSchema = Z.String().Min(3).Max(50);
+      var result = nameSchema.Validate("John");
+
+      if (result.IsSuccess)
+          Console.WriteLine($"Valid name: {result.Value}");
+    language: csharp
+    outcome: >-
+      Validate/SafeParse return a ValidationResult<T> with no exceptions, while Parse still throws
+      ZodException when you want that behaviour.
+    evidence: >-
+      Validation is zero-allocation on every valid input path, so the performance claim is a
+      property of the code rather than an aspiration.
+    docsPage: fluent-schema-api
+  - audience: team-lead
+    title: Return standard ProblemDetails for invalid requests
+    scenario: >-
+      You want failed validation in ASP.NET Core to surface as standard ProblemDetails payloads
+      rather than a bespoke error shape that clients must learn.
+    code: |
+      dotnet add package Purview.ZodSharp.AspNetCore
+    language: bash
+    outcome: >-
+      The AspNetCore adapter converts failed validation results into the standard ProblemDetails /
+      HttpValidationProblemDetails payloads.
+    evidence: >-
+      One adapter package, and API consumers keep the error contract they already expect.
+    docsPage: aspnetcore-integration
diff --git a/src/src/lib/docs/aggregate.ts b/src/src/lib/docs/aggregate.ts
index f4969db..dd0ceb2 100644
--- a/src/src/lib/docs/aggregate.ts
+++ b/src/src/lib/docs/aggregate.ts
@@ -321,6 +321,7 @@ async function buildPage(
     description,
     owners: [OWNER],
     status: project.status,
+    experimental: project.experimental,
     lastReviewed: raw.lastModified,
     sourceProject: project.id,
     sourceRepo: project.repository,
diff --git a/src/src/lib/docs/frontmatter.ts b/src/src/lib/docs/frontmatter.ts
index a7e5e56..a161a0f 100644
--- a/src/src/lib/docs/frontmatter.ts
+++ b/src/src/lib/docs/frontmatter.ts
@@ -1,10 +1,18 @@
+import type { ProjectStatus } from '../manifest/schema';
+
 import { slugifyDocFile } from './links';
 
 export interface DocFrontmatter {
   title: string;
   description: string;
   owners: string[];
-  status: 'stable' | 'preview' | 'archived';
+  status: ProjectStatus;
+  /**
+   * True when the catalogue flags the owning project as experimental
+   * (ADR 0004). The manifest keeps `status` and the flag on separate axes, so
+   * the front matter carries both and the site collapses them for display.
+   */
+  experimental?: boolean;
   lastReviewed: string;
   sourceProject: string;
   sourceRepo: string;
@@ -117,6 +125,9 @@ export function renderFrontmatter(frontmatter: DocFrontmatter): string {
   }
   lines.push(`owners: [${frontmatter.owners.join(', ')}]`);
   lines.push(`status: ${frontmatter.status}`);
+  if (frontmatter.experimental) {
+    lines.push('experimental: true');
+  }
   lines.push(`lastReviewed: ${JSON.stringify(frontmatter.lastReviewed)}`);
   lines.push(`sourceProject: ${quote(frontmatter.sourceProject)}`);
   lines.push(`sourceRepo: ${quote(frontmatter.sourceRepo)}`);
diff --git a/src/src/lib/manifest/load.ts b/src/src/lib/manifest/load.ts
index f9d8759..774610f 100644
--- a/src/src/lib/manifest/load.ts
+++ b/src/src/lib/manifest/load.ts
@@ -1,14 +1,22 @@
 import type { ExternalProjectRecord, ProjectManifest, ProjectRecord } from './schema';
 
-import { readFileSync } from 'node:fs';
-import { resolve } from 'node:path';
+import { existsSync, readdirSync, readFileSync } from 'node:fs';
+import { join, resolve } from 'node:path';
 import { parse } from 'yaml';
 import { z } from 'zod';
 
 import { OWNER } from '../site';
 import { PROJECT_DEFAULTS, manifestSchema } from './schema';
 
-export const DEFAULT_MANIFEST_PATH = resolve('src/data/projects.yml');
+/**
+ * The catalogue is one file per project (ADR 0005): `src/data/projects/<id>.yml`,
+ * plus `src/data/external-projects.yml` for the collaborations the organisation
+ * does not own. One file per project keeps a project's history and review
+ * self-contained, and stops concurrent catalogue pull requests from conflicting
+ * on one growing list.
+ */
+export const DEFAULT_PROJECTS_DIR = resolve('src/data/projects');
+export const DEFAULT_EXTERNAL_PROJECTS_PATH = resolve('src/data/external-projects.yml');
 
 export interface ResolvedProject extends ProjectRecord {
   repoOwner: string;
@@ -19,6 +27,7 @@ export interface ResolvedProject extends ProjectRecord {
   changelogUrl: string;
   releasesUrl: string;
   featured: boolean;
+  experimental: boolean;
   order: number;
   packages: NonNullable<ProjectRecord['packages']>;
   related: NonNullable<ProjectRecord['related']>;
@@ -53,6 +62,7 @@ function withDefaults(record: ProjectRecord): ResolvedProject {
   return {
     ...record,
     featured: record.featured ?? PROJECT_DEFAULTS.featured,
+    experimental: record.experimental ?? PROJECT_DEFAULTS.experimental,
     order: record.order ?? PROJECT_DEFAULTS.order,
     packages: record.packages ?? PROJECT_DEFAULTS.packages,
     related: record.related ?? PROJECT_DEFAULTS.related,
@@ -70,6 +80,24 @@ function withDefaults(record: ProjectRecord): ResolvedProject {
   };
 }
 
+/**
+ * Label an issue with the project id rather than its array index, so a schema
+ * failure names the project whose file is wrong (`projects[containers].name`)
+ * instead of a position the author has to map back to a file.
+ */
+function issuePath(raw: unknown, path: readonly PropertyKey[]): string {
+  const [head, index, ...rest] = path;
+  if (head !== 'projects' || typeof index !== 'number') {
+    return path.join('.');
+  }
+  const entries = (raw as { projects?: unknown[] } | null)?.projects;
+  const entry = Array.isArray(entries) ? entries[index] : undefined;
+  const id =
+    typeof entry === 'object' && entry !== null ? (entry as { id?: unknown }).id : undefined;
+  const label = `projects[${typeof id === 'string' ? id : index}]`;
+  return rest.length > 0 ? `${label}.${rest.join('.')}` : label;
+}
+
 /**
  * Validate a raw manifest object against the typed schema.
  * Throws a ManifestValidationError describing the source file, the invalid
@@ -82,10 +110,7 @@ export function parseManifest(raw: unknown, source: string): ResolvedProject[] {
   } catch (error) {
     if (error instanceof z.ZodError) {
       const issues = error.issues
-        .map((issue) => {
-          const path = issue.path.join('.');
-          return `  ${path}: ${issue.message}`;
-        })
+        .map((issue) => `  ${issuePath(raw, issue.path)}: ${issue.message}`)
         .join('\n');
       throw new ManifestValidationError(
         [
@@ -150,10 +175,64 @@ export function parseManifest(raw: unknown, source: string): ResolvedProject[] {
   return projects.toSorted((a, b) => a.order - b.order);
 }
 
-/** Load, parse and validate the project manifest from disk. */
-export function loadProjects(path = DEFAULT_MANIFEST_PATH): ResolvedProject[] {
-  const sourceText = readFileSync(path, 'utf8');
-  return parseManifest(parse(sourceText), path);
+/**
+ * Files may open with a `$schema` hint for editors. It is a file-level concern
+ * rather than part of the record, so it is dropped before validation and
+ * resolution: `ResolvedProject` stays the domain type it always was.
+ */
+function stripSchemaHint(value: unknown): unknown {
+  if (typeof value !== 'object' || value === null || Array.isArray(value)) {
+    return value;
+  }
+  const record: Record<string, unknown> = {};
+  for (const [key, entry] of Object.entries(value)) {
+    if (key !== '$schema') {
+      record[key] = entry;
+    }
+  }
+  return record;
+}
+
+/**
+ * Read the catalogue from disk into the raw shape `manifestSchema` validates:
+ * one record per `*.yml` file in the projects directory, sorted by file name so
+ * the result is deterministic whatever order the filesystem reports, plus the
+ * collaborations file. Validation (including every cross-record invariant)
+ * stays in `parseManifest`.
+ */
+export function readRawManifest(
+  projectsDir = DEFAULT_PROJECTS_DIR,
+  externalProjectsPath = DEFAULT_EXTERNAL_PROJECTS_PATH,
+): { projects: unknown[]; externalProjects: unknown[] } {
+  const files = readdirSync(projectsDir)
+    .filter((file) => file.endsWith('.yml') || file.endsWith('.yaml'))
+    .toSorted();
+
+  const projects = files.map((file) => {
+    const text = readFileSync(join(projectsDir, file), 'utf8');
+    try {
+      return stripSchemaHint(parse(text));
+    } catch (error) {
+      throw new ManifestValidationError(
+        `Invalid YAML in ${file}: ${error instanceof Error ? error.message : String(error)}`,
+      );
+    }
+  });
+
+  const externalProjects: unknown[] = [];
+  if (existsSync(externalProjectsPath)) {
+    const parsed = (parse(readFileSync(externalProjectsPath, 'utf8')) ?? {}) as {
+      externalProjects?: unknown[];
+    };
+    externalProjects.push(...(parsed.externalProjects ?? []));
+  }
+
+  return { projects, externalProjects };
+}
+
+/** Load, parse and validate the catalogue (one file per project) from disk. */
+export function loadProjects(): ResolvedProject[] {
+  return parseManifest(readRawManifest(), DEFAULT_PROJECTS_DIR);
 }
 
 function withExternalDefaults(record: ExternalProjectRecord): ResolvedExternalProject {
@@ -172,11 +251,10 @@ function withExternalDefaults(record: ExternalProjectRecord): ResolvedExternalPr
  * projects the organisation collaborates on but does not own; they link to
  * their own site/repository rather than the Purview-Dev catalogue.
  */
-export function loadExternalProjects(path = DEFAULT_MANIFEST_PATH): ResolvedExternalProject[] {
-  const sourceText = readFileSync(path, 'utf8');
+export function loadExternalProjects(): ResolvedExternalProject[] {
   let parsed: ProjectManifest;
   try {
-    parsed = manifestSchema.parse(parse(sourceText));
+    parsed = manifestSchema.parse(readRawManifest());
   } catch (error) {
     if (error instanceof z.ZodError) {
       const issues = error.issues
@@ -187,7 +265,7 @@ export function loadExternalProjects(path = DEFAULT_MANIFEST_PATH): ResolvedExte
         .join('\n');
       throw new ManifestValidationError(
         [
-          `Invalid project manifest: ${path}`,
+          `Invalid project manifest: ${DEFAULT_EXTERNAL_PROJECTS_PATH}`,
           issues,
           '',
           'Remediation: fix the reported property on the external project record.',
diff --git a/src/src/lib/manifest/schema.ts b/src/src/lib/manifest/schema.ts
index 3668ab9..00ded56 100644
--- a/src/src/lib/manifest/schema.ts
+++ b/src/src/lib/manifest/schema.ts
@@ -12,6 +12,9 @@ export const CATEGORIES = [
 
 export const STATUSES = ['stable', 'preview', 'archived'] as const;
 
+/** The lifecycle/release channel a project publishes on. */
+export type ProjectStatus = (typeof STATUSES)[number];
+
 /** How the primary NuGet package is consumed, which drives the Install options. */
 export const INSTALL_KINDS = ['nuget', 'msbuild-sdk', 'dotnet-tool'] as const;
 
@@ -99,32 +102,46 @@ const acknowledgmentSchema = z.object({
   description: z.string().optional(),
 });
 
-const projectSchema = z.object({
-  id: z.string().regex(/^[a-z0-9-]+$/, 'must be a lowercase slug using [a-z0-9-] only'),
-  name: z.string().min(1, 'must be a non-empty display name'),
-  shortDescription: z.string().min(1, 'must be a non-empty short description'),
-  description: z.string().min(1, 'must be a non-empty long description'),
-  origin: z.string().min(1, 'must explain why the project became reusable tooling'),
-  useWhen: z.string().min(1, 'must explain when the project is a good fit'),
-  avoidWhen: z.string().min(1, 'must explain when the project is not a good fit'),
-  repository: z
-    .string()
-    .regex(/^[a-zA-Z0-9-]+\/[a-zA-Z0-9._-]+$/, 'must be in "owner/repository" form'),
-  category: z.enum(CATEGORIES),
-  status: z.enum(STATUSES),
-  featured: z.boolean().optional(),
-  order: z.number().int().nonnegative().optional(),
-  docs: docsSchema.optional(),
-  install: z.enum(INSTALL_KINDS).optional(),
-  targetFrameworks: z.array(z.string()).optional(),
-  packages: z.array(packageSchema).optional(),
-  related: z.array(z.string()).optional(),
-  useCases: z.array(useCaseSchema).optional(),
-  acknowledgments: z.array(acknowledgmentSchema).optional(),
-  supersedes: z.string().optional(),
-  supersededBy: z.string().optional(),
-  discussions: z.boolean().optional(),
-});
+const projectSchema = z
+  .object({
+    /** Editor hint; stripped by the loader and never part of a resolved record. */
+    $schema: z.string().optional(),
+    id: z.string().regex(/^[a-z0-9-]+$/, 'must be a lowercase slug using [a-z0-9-] only'),
+    name: z.string().min(1, 'must be a non-empty display name'),
+    shortDescription: z.string().min(1, 'must be a non-empty short description'),
+    description: z.string().min(1, 'must be a non-empty long description'),
+    origin: z.string().min(1, 'must explain why the project became reusable tooling'),
+    useWhen: z.string().min(1, 'must explain when the project is a good fit'),
+    avoidWhen: z.string().min(1, 'must explain when the project is not a good fit'),
+    repository: z
+      .string()
+      .regex(/^[a-zA-Z0-9-]+\/[a-zA-Z0-9._-]+$/, 'must be in "owner/repository" form'),
+    category: z.enum(CATEGORIES),
+    status: z.enum(STATUSES),
+    /**
+     * Marks an exploratory project: the API, defaults and packaging may change
+     * between prereleases and there is no production support guarantee. This is
+     * deliberately orthogonal to `status`, which stays the project's release
+     * channel (ADR 0004). Only valid on `projects[]`.
+     */
+    experimental: z.boolean().optional(),
+    featured: z.boolean().optional(),
+    order: z.number().int().nonnegative().optional(),
+    docs: docsSchema.optional(),
+    install: z.enum(INSTALL_KINDS).optional(),
+    targetFrameworks: z.array(z.string()).optional(),
+    packages: z.array(packageSchema).optional(),
+    related: z.array(z.string()).optional(),
+    useCases: z.array(useCaseSchema).optional(),
+    acknowledgments: z.array(acknowledgmentSchema).optional(),
+    supersedes: z.string().optional(),
+    supersededBy: z.string().optional(),
+    discussions: z.boolean().optional(),
+  })
+  .refine((value) => !(value.experimental === true && value.status === 'archived'), {
+    message: 'cannot be true when `status` is archived: an archived project is not an experiment',
+    path: ['experimental'],
+  });
 
 const externalProjectSchema = z.object({
   id: z.string().regex(/^[a-z0-9-]+$/, 'must be a lowercase slug using [a-z0-9-] only'),
@@ -144,7 +161,9 @@ const externalProjectSchema = z.object({
 
 export const manifestSchema = z.object({
   $schema: z.string().optional(),
-  projects: z.array(projectSchema),
+  // Defaulted so the collaborations file, which legitimately declares no
+  // `projects`, is valid on its own (ADR 0005).
+  projects: z.array(projectSchema).default([]),
   externalProjects: z.array(externalProjectSchema).default([]),
 });
 
@@ -157,6 +176,7 @@ export type ProjectAcknowledgment = z.infer<typeof acknowledgmentSchema>;
 export type ProjectUseCase = z.infer<typeof useCaseSchema>;
 
 export const PROJECT_DEFAULTS = {
+  experimental: false,
   featured: false,
   order: 1000,
   packages: [] as ProjectPackage[],
@@ -166,6 +186,7 @@ export const PROJECT_DEFAULTS = {
   discussions: false,
   install: 'nuget',
 } satisfies {
+  experimental: boolean;
   featured: boolean;
   order: number;
   packages: ProjectPackage[];
diff --git a/src/src/lib/releases/transform.ts b/src/src/lib/releases/transform.ts
index 0451bc6..72e240f 100644
--- a/src/src/lib/releases/transform.ts
+++ b/src/src/lib/releases/transform.ts
@@ -1,4 +1,5 @@
 import type { ResolvedProject } from '../manifest/load';
+import type { DisplayStatus } from '../status';
 import type {
   GitHubReleaseInfo,
   PackageReleaseSummary,
@@ -7,6 +8,7 @@ import type {
 } from './types';
 
 import { compareNuGetVersions, formatNuGetVersion } from '../nuget-version';
+import { displayStatus } from '../status';
 import { nugetPackageUrl } from '../urls';
 import {
   isPrereleaseRelease,
@@ -156,7 +158,7 @@ export function flattenReleases(summaries: ProjectReleaseSummary[]): ReleaseEntr
 export interface ProjectVersionRollup {
   projectId: string;
   projectName: string;
-  status: ResolvedProject['status'];
+  status: DisplayStatus;
   /** Number of NuGet packages the project publishes. */
   packageCount: number;
   /** Highest stable version across the project's packages, when one exists. */
@@ -215,7 +217,7 @@ export function projectVersionRollup(
   return {
     projectId: project.id,
     projectName: project.name,
-    status: project.status,
+    status: displayStatus(project),
     packageCount: summary.packages.length,
     stableVersion,
     prereleaseVersion: prereleaseOutranks ? highestPrerelease : null,
diff --git a/src/src/lib/status.ts b/src/src/lib/status.ts
new file mode 100644
index 0000000..52e2438
--- /dev/null
+++ b/src/src/lib/status.ts
@@ -0,0 +1,43 @@
+import type { ResolvedProject } from './manifest/load';
+
+/**
+ * The status a *reader* is shown.
+ *
+ * The manifest models two independent axes (ADR 0004): `status`, the
+ * release/lifecycle channel, and `experimental`, the intent flag that says
+ * "exploratory: the API and packaging may change and there is no support
+ * promise". Presentation collapses them into one value, and this module is the
+ * only place that resolution happens so the catalogue card, project page,
+ * home-page version snapshot, documentation page, docs sidebar topic and the
+ * catalogue filter can never disagree.
+ */
+export const DISPLAY_STATUSES = ['stable', 'preview', 'experimental', 'archived'] as const;
+
+/** The single value every status badge and status filter renders. */
+export type DisplayStatus = (typeof DISPLAY_STATUSES)[number];
+
+/** Human-facing labels, used by `StatusBadge`. */
+export const DISPLAY_STATUS_LABELS: Record<DisplayStatus, string> = {
+  stable: 'Stable',
+  preview: 'Preview',
+  experimental: 'Experimental',
+  archived: 'Archived',
+};
+
+/**
+ * Collapse the manifest's two axes into the displayed status.
+ *
+ * `archived` wins over everything — an archived project is never presented as
+ * an experiment — and otherwise the `experimental` flag wins over the release
+ * channel, because the warning is the whole point of the flag. The schema
+ * already rejects `experimental` on an archived project; handling it here as
+ * well keeps the precedence total and the function total.
+ */
+export function displayStatus(
+  project: Pick<ResolvedProject, 'status' | 'experimental'>,
+): DisplayStatus {
+  if (project.status === 'archived') {
+    return 'archived';
+  }
+  return project.experimental ? 'experimental' : project.status;
+}
diff --git a/src/src/pages/projects/[project].astro b/src/src/pages/projects/[project].astro
index fdc1132..c8b2f6e 100644
--- a/src/src/pages/projects/[project].astro
+++ b/src/src/pages/projects/[project].astro
@@ -12,6 +12,8 @@ import { projectRepoEnrichment } from '~/lib/releases/repo';
 import { projectReleaseSummary } from '~/lib/releases/transform';
 import { getReleaseIndex } from '~/lib/releases/runtime';
 import { SITE } from '~/lib/site';
+import { displayStatus } from '~/lib/status';
+
 import { nugetPackageUrl, withBase } from '~/lib/urls';
 
 export function getStaticPaths() {
@@ -26,6 +28,8 @@ interface Props {
 }
 
 const { project } = Astro.props;
+const status = displayStatus(project);
+
 const releaseIndex = getReleaseIndex();
 const releases = projectReleaseSummary(project, releaseIndex.data, releaseIndex.source);
 const { tags, repoDescription } = projectRepoEnrichment(project, releaseIndex.data);
@@ -51,7 +55,7 @@ const docsPath = project.docs ? withBase(`/docs/${project.id}/`) : null;
 const llmsPath = project.docs ? withBase(`/_llms-txt/${project.id}.txt`) : null;
 const targetFrameworks = project.targetFrameworks ?? [];
 const installSections =
-  project.status !== 'archived' ?
+  status !== 'archived' ?
     project.packages.map((pkg) => {
       const release = releases.packages.find((candidate) => candidate.packageId === pkg.id);
       return {
@@ -92,7 +96,7 @@ const packageRows: PackageRow[] = releases.packages.map((pkg) => ({
     <div class="max-w-3xl">
       <div class="flex flex-wrap items-center gap-3">
         <h1 class="text-3xl font-bold tracking-tight md:text-4xl">{project.name}</h1>
-        <StatusBadge status={project.status} />
+        <StatusBadge status={status} />
       </div>
       <p class="mt-4 text-lg text-muted">{project.shortDescription}</p>
 
@@ -109,7 +113,7 @@ const packageRows: PackageRow[] = releases.packages.map((pkg) => ({
       }
 
       {
-        project.status === 'archived' && (
+        status === 'archived' && (
           <div class="mt-6 rounded-lg border border-error/40 bg-error/10 p-4 text-sm">
             <strong>Archived.</strong> This project is no longer actively developed.
             {supersededBy && (
@@ -126,6 +130,16 @@ const packageRows: PackageRow[] = releases.packages.map((pkg) => ({
         )
       }
 
+      {
+        status === 'experimental' && (
+          <div class="mt-6 rounded-lg border border-error/40 bg-error/10 p-4 text-sm">
+            <strong>Experimental.</strong> This project is an experiment: the public API, defaults and
+            packaging can change between prereleases, and there is no production support guarantee.
+            Read the documentation before adopting it.
+          </div>
+        )
+      }
+
       <div class="mt-8 flex flex-wrap gap-2">
         <a
           href={project.sourceUrl}
@@ -370,7 +384,7 @@ const packageRows: PackageRow[] = releases.packages.map((pkg) => ({
           <dl class="mt-4 space-y-3 text-sm">
             <div class="flex justify-between gap-3">
               <dt class="text-muted">Status</dt>
-              <dd><StatusBadge status={project.status} /></dd>
+              <dd><StatusBadge status={status} /></dd>
             </div>
             <div class="flex justify-between gap-3">
               <dt class="text-muted">Category</dt>
diff --git a/src/src/pages/projects/index.astro b/src/src/pages/projects/index.astro
index 0782ce8..9b727f7 100644
--- a/src/src/pages/projects/index.astro
+++ b/src/src/pages/projects/index.astro
@@ -7,12 +7,14 @@ import { loadExternalProjects, loadProjects } from '~/lib/manifest/load';
 import { projectRepoEnrichment } from '~/lib/releases/repo';
 import { getReleaseIndex } from '~/lib/releases/runtime';
 import { SITE } from '~/lib/site';
+import { displayStatus } from '~/lib/status';
+
 
 const projects = loadProjects();
 const externalProjects = loadExternalProjects();
 const releaseIndex = getReleaseIndex();
 const categories = [...new Set(projects.map((project) => project.category))].toSorted();
-const statuses = ['stable', 'preview'];
+const statuses = ['stable', 'preview', 'experimental'];
 ---
 
 <SiteLayout
@@ -41,8 +43,8 @@ const statuses = ['stable', 'preview'];
             <div
               data-project-id={project.id}
               data-category={project.category}
-              data-status={project.status}
-              data-search={`${project.name} ${project.shortDescription} ${tags.join(' ')} ${project.category} ${project.status}`.toLowerCase()}
+              data-status={displayStatus(project)}
+              data-search={`${project.name} ${project.shortDescription} ${tags.join(' ')} ${project.category} ${displayStatus(project)}`.toLowerCase()}
             >
               <ProjectCard project={project} />
             </div>
diff --git a/src/src/styles/global.css b/src/src/styles/global.css
index 2def925..ab2ba26 100644
--- a/src/src/styles/global.css
+++ b/src/src/styles/global.css
@@ -294,6 +294,12 @@
     background-color: color-mix(in oklab, var(--color-warning) 8%, var(--color-surface));
   }
 
+  .pv-status-experimental {
+    color: var(--color-error);
+    border-color: color-mix(in oklab, var(--color-error) 40%, var(--color-border));
+    background-color: color-mix(in oklab, var(--color-error) 8%, var(--color-surface));
+  }
+
   .pv-status-archived {
     color: var(--color-muted);
     border-color: var(--color-border);
diff --git a/src/tests/unit/docs.test.ts b/src/tests/unit/docs.test.ts
index 83a4440..4c051a7 100644
--- a/src/tests/unit/docs.test.ts
+++ b/src/tests/unit/docs.test.ts
@@ -141,6 +141,28 @@ describe('front matter', () => {
     expect(rendered.startsWith('---')).toBe(true);
   });
 
+  test('marks experimental documentation with the injected flag only', () => {
+    const frontmatter: DocFrontmatter = {
+      title: 'Getting Started',
+      description: 'Intro',
+      owners: ['purview-dev'],
+      status: 'preview',
+      experimental: true,
+      lastReviewed: '2026-09-15',
+      sourceProject: 'containers',
+      sourceRepo: 'purview-dev/containers',
+      sourcePath: 'docs/wiki/Getting-Started.md',
+      editUrl: 'https://github.com/purview-dev/containers/edit/main/docs/wiki/Getting-Started.md',
+    };
+    const rendered = renderFrontmatter(frontmatter);
+    expect(rendered).toContain('status: preview');
+    expect(rendered).toContain('experimental: true');
+
+    // Ordinary projects keep the three-value status vocabulary untouched.
+    const plain = renderFrontmatter({ ...frontmatter, experimental: undefined });
+    expect(plain).not.toContain('experimental:');
+  });
+
   test('renders repository tags when present', () => {
     const frontmatter: DocFrontmatter = {
       title: 'Getting Started',
diff --git a/src/tests/unit/manifest.test.ts b/src/tests/unit/manifest.test.ts
index 7fd670e..6017e26 100644
--- a/src/tests/unit/manifest.test.ts
+++ b/src/tests/unit/manifest.test.ts
@@ -1,9 +1,31 @@
 import { describe, expect, test } from 'bun:test';
 
 import { loadExternalProjects, loadProjects, parseManifest } from '../../src/lib/manifest/load';
-import { ManifestValidationError } from '../../src/lib/manifest/load';
+import { ManifestValidationError, readRawManifest } from '../../src/lib/manifest/load';
 import { AUDIENCES } from '../../src/lib/manifest/schema';
 
+describe('catalogue records', () => {
+  test('reads one file per project, sorted and free of the editor hint', () => {
+    const raw = readRawManifest();
+    expect(raw.projects.length).toBe(loadProjects().length);
+    expect(raw.projects.length).toBeGreaterThanOrEqual(8);
+    expect(raw.externalProjects.length).toBeGreaterThan(0);
+
+    for (const record of raw.projects) {
+      // Each file holds the record itself, so the id is always present...
+      expect(typeof (record as { id?: unknown }).id).toBe('string');
+      // ...and the `$schema` hint is a file-level concern, not part of the record.
+      expect(Object.hasOwn(record as object, '$schema')).toBe(false);
+    }
+  });
+
+  test('names the project, rather than its position, in a schema failure', () => {
+    expect(() =>
+      parseManifest({ projects: [{ ...makeProject('broken'), name: '' }] }, 'fixture.yml'),
+    ).toThrow(/projects\[broken\]\.name/);
+  });
+});
+
 describe('project manifest', () => {
   test('loads and validates the real manifest', () => {
     const projects = loadProjects();
@@ -135,6 +157,28 @@ describe('project manifest', () => {
     ).toThrow(/does-not-exist/);
   });
 
+  test('defaults the experimental flag to false', () => {
+    const projects = parseManifest({ projects: [makeProject('a')] }, 'fixture.yml');
+    expect(projects[0]?.experimental).toBe(false);
+  });
+
+  test('accepts a project flagged experimental', () => {
+    const projects = parseManifest(
+      { projects: [{ ...makeProject('a'), experimental: true }] },
+      'fixture.yml',
+    );
+    expect(projects[0]?.experimental).toBe(true);
+  });
+
+  test('rejects an experimental project whose status is archived', () => {
+    expect(() =>
+      parseManifest(
+        { projects: [{ ...makeProject('a'), status: 'archived', experimental: true }] },
+        'fixture.yml',
+      ),
+    ).toThrow(/not an experiment/);
+  });
+
   test('rejects duplicate package ids across projects', () => {
     expect(() =>
       parseManifest({ projects: [makeProject('a'), makeProject('b')] }, 'fixture.yml'),
diff --git a/src/tests/unit/status.test.ts b/src/tests/unit/status.test.ts
new file mode 100644
index 0000000..8f457c2
--- /dev/null
+++ b/src/tests/unit/status.test.ts
@@ -0,0 +1,29 @@
+import { describe, expect, test } from 'bun:test';
+
+import { DISPLAY_STATUSES, displayStatus } from '../../src/lib/status';
+
+describe('display status', () => {
+  test('keeps the lifecycle status when a project is not experimental', () => {
+    expect(displayStatus({ status: 'stable', experimental: false })).toBe('stable');
+    expect(displayStatus({ status: 'preview', experimental: false })).toBe('preview');
+  });
+
+  test('reports an experimental project as experimental', () => {
+    expect(displayStatus({ status: 'preview', experimental: true })).toBe('experimental');
+    expect(displayStatus({ status: 'stable', experimental: true })).toBe('experimental');
+  });
+
+  test('never reports an archived project as experimental', () => {
+    expect(displayStatus({ status: 'archived', experimental: true })).toBe('archived');
+  });
+
+  test('every display status is reachable from the two manifest axes', () => {
+    const reachable = new Set([
+      displayStatus({ status: 'stable', experimental: false }),
+      displayStatus({ status: 'preview', experimental: false }),
+      displayStatus({ status: 'preview', experimental: true }),
+      displayStatus({ status: 'archived', experimental: false }),
+    ]);
+    expect([...reachable].toSorted()).toEqual([...DISPLAY_STATUSES].toSorted());
+  });
+});