The trustworthy empty state
A dashboard full of polished sample numbers can look more complete than a truthful empty state. It can also destroy the evidence standard before the first real measurement arrives.
Sam Foundry starts with one verified fact: the public Vitals feed is not activated.
What is implemented
The repository contains a schema-validated machine record dated August 7, 2026. Its status is foundation, its feed status is not-activated, its evidence commit is null, and its message states that no operating metrics are being fabricated.
That record is an implemented unavailable state. It is not an implemented telemetry pipeline.
What comes later
A future metric needs an owner, definition, method, date, and source. Stale data must be visibly stale, methodology changes must be recorded, and private operations must stay private.
Useful families may include public release freshness, content evidence coverage, Council cases, accepted contributions, documentation gaps, and reproducible public benchmarks.
Limit
Nothing in this entry supports a claim about traffic, cost savings, autonomy, accepted-outcome rate, or local-versus-cloud work share. Unavailable remains better than invented.
Evidence and limits
Sources
- Sam Foundry Initial Decision Register v0.1 (primary-documentation) — docs/decisions/SamFoundry-Initial-Decision-Register-v0.1.md
- Sam Foundry Metrics, Analytics, and CostOS v0.1 (primary-documentation) — docs/business/SamFoundry-Metrics-Analytics-and-CostOS-v0.1.md
