Phase 1: content source of truth — 40 documents across six areas

Satisfies the Phase 1 Definition of Done:

- content/ validates cleanly against the frozen schema. `make validate`
  reports OK: 40 document(s) validated, 0 violations.
- Six areas exist, each with an L1 entry: ai-overview, platform-overview,
  edge-overview, products-overview, history-overview, about-overview.
- All six areas have an L2 entry: ai-systems, platform-estate, edge-fleet,
  products-business, history-engagements, about-narrative.
- 28 L3 artefact stubs under content/<area>/l3/. Every artefacts[].url in
  every document resolves to one of them; the validator proves there are no
  dangling references (and a deliberately broken copy exits 1).
- Every metric value traces to a source line in the evidence notes or the
  approved metric set in reference/content-map.md (per-metric citations are
  recorded in the AUD-131 completion comment).
- Every document carries confidence and last_verified=2026-10-26; the
  validator rejects a missing or non-canonical value.
- docs/content-redaction.md records the redaction pass: identifiers, third
  party personal data, credentials and infrastructure detail excluded, with
  reasons, plus the two numbers that are reported rather than smoothed.

Honesty positions held: 3 businesses active (12 adoptions over time),
Where-Woof deployed and pre-market, failures kept in (edge-failures), no
promotion of in-progress work to delivered.

No site code, no templates, no CSS, no rendering (Phase 2).

content/ai/l3/ai-omniroute-routing.md

@@ -0,0 +1,31 @@
+---
+id: ai-omniroute-routing
+area: ai
+level: 3
+title: "Artefact — Model routing and cost control"
+claim: "Every model call is classified first and sent to the cheapest capable provider — six providers behind one gateway with no direct SDK calls anywhere in the estate."
+confidence: running
+period: "2020–"
+tech: [OmniRoute, JEV, DeepSeek, MiniMax, OpenRouter, Gemini, OpenAI]
+metrics: [{label: "providers in rotation", value: 6}, {label: "gateways", value: 1}]
+artefacts: []
+public: true
+last_verified: 2026-10-26
+tags: [ai, routing, cost, artefact]
+---
+
+# Artefact — Model routing and cost control
+
+**Status: stub.** The routing decision path and a redacted cost table land in Phase 7. No keys or account identifiers are ever published.
+
+## What the artefact is
+
+The decision path: request arrives, a prompt-analysis step classifies it, the gateway selects a provider and model, and the response returns with its cost recorded. Plus the comparison that demoted local inference for heavy flows — local Ollama measured slower and more expensive under the available hardware than partitioned remote calls.
+
+## What it proves
+
+Cost control implemented as routing and measurement rather than as a monthly promise, and a single chokepoint where provider access can be audited.
+
+## When it is delivered
+
+Phase 7. The evidence for the provider list and the local-versus-remote decision is in the evidence notes, section 2 and section 4.