What this desk publishes, and what it does not

An operating record is only useful if you can tell what is measured, what is recalled, and what is missing.

Every figure carries a date

Not a preference. There is a test in this repo that reads every content file and fails the build when a figure appears in prose without a date, an "as of", or a fact id beside it:

npm test

An undated number has a short and predictable life. It is true when written, it is quoted a month later, and by then nobody can tell whether it was ever checked. A date makes a stale figure obviously stale, which is the most useful thing a stale figure can be.

Internal identifiers stay out

My notes carry hosting project and deployment identifiers for every verified host. They are not on these pages.

They would add nothing a reader can act on, and they are exactly the sort of detail that is boring until it is not. The commit sha is published instead: it is already public in the repository, and it is the identifier that actually answers "which version is this".

What is hand-kept

The status page is a record of checks I ran on the dates shown. It is not a monitor. The distinction is on the page itself, in the section that says so.

The intent is that Signal exports that page and the same pipeline deploys it. Until that happens the table is hand-kept and labelled hand-kept. A status page that implies freshness it does not have is the one kind of status page worse than none.

What is missing today, as of 2026-09-21

Cost and volume figures are not supplied. None reproduce from a repo or report in scope. (N-1, source: company/product-facts.md, section 3, verified 2026-09-21)

No cost figures, no deployment counts, no request volumes. Those would be the most quotable numbers on this desk, which is exactly why they are not being estimated.

The DNS provider and domain registrar for bryancalabro.com are not confirmed. (V-1, source: company/product-facts.md, section 4, verified 2026-09-21)

The DNS provider and registrar are unconfirmed. Naming one from memory on an operating record would be the opposite of the job.

Why the gaps are on the page

A record that only shows what it knows reads as complete. Over time, the gaps stop being gaps and start being things nobody thought to ask about.

Listing them keeps them uncomfortable, which is where they belong until they are filled.