Files

Documenter 00fa15f98f 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).

2026-10-26 17:30:35 +11:00

1.7 KiB

Raw Blame History

id, area, level, title, claim, confidence, period, tech, metrics, artefacts, public, last_verified, tags

area

level

title

claim

confidence

period

tech

metrics

artefacts

public

last_verified

tags

platform-overview

platform

Platform & Infrastructure

Runs a multi-machine NixOS and Proxmox estate — fifty-plus containers · declarative configuration · encrypted backups with a written restore runbook · and public ingress — sized to the hardware rather than the budget.

running

2020–

NixOS

Proxmox

Docker

Caddy

Tailscale

Borg

Kopia

AWS S3

label	value
containers in the estate	50

label	value
hosts	4

label	value
backup tiers	Borg · Kopia · AWS

type	label	url
doc	Declarative multi-host configuration	content/platform/l3/platform-nixos.md

type	label	url
doc	Backups and restore runbook	content/platform/l3/platform-backups.md

type	label	url
doc	A hand-written Nix package with an exit plan	content/platform/l3/platform-tuios-package.md

true

2026-10-26

platform

devops

nixos

docker

backups

Platform & Infrastructure

Claim. Fifty or more containers across four hosts, configuration declared rather than hand-applied, encrypted backups on three machines with a restore runbook beside them, and one public listener at the edge.

Status. Running. Figures trace to the approved metric set and the infrastructure reference; verified 2026-10-26.

The constraint that shaped it. The runtime host is memory-bound rather than CPU-bound. Every service in this estate carries a memory cap and is bound to loopback, which is why the platform reads as engineering under constraint instead of hardware shopping.

Start here. The capability page covers what runs, where, and what was rejected.

1.7 KiB Raw Blame History Unescape Escape

Platform & Infrastructure

1.7 KiB

Raw Blame History