Reference22 Reference · 3 of 3

Dating conventions

Stand 29.07.2026

#Why every page carries a date

What

Every route ends with a Stand DD.MM.YYYY stamp, and every volatile claim is anchored to a currency-register key rather than stated loose. A topic that depends on a perishable fact shows it, with the date and a link to the source.

In code, that anchoring is a facts array on the topic. routesForFact(key) then answers the maintenance question directly: change one fact, and it lists every page that needs revisiting. No grep, no memory.

Why

Databricks renamed Asset Bundles, renamed Delta Live Tables, renamed Lakehouse Monitoring and moved ABAC from preview to GA — all within about fifteen months. An undated handbook is not merely stale, it is confidently wrong, which is worse than silent.

The consulting consequence is concrete. Quoting a preview feature as GA to a client, and having their platform team discover it, costs more credibility than saying "this was true in July, let me re-check" ever will.

Doing it

Anchor any platform claim that could move to a currency key rather than asserting it in prose
Re-verify the register against the official docs before reusing this material in a client deliverable
Prefer docs.databricks.com and learn.microsoft.com over blogs — blogs lag renames badly
Mark anything you could not confirm as unverified rather than dropping itA flagged risk is more useful than a silent gap.

Embedding it

Ask the team where a claim came from whenever one appears in a design documentThe habit of citing beats the habit of remembering.
Put the re-verification pass in someone's calendar quarterly, named, before you leave
Model it: when you do not know, say so and check, in front of themThat is the behaviour you are actually transferring.

Defaults

Every platform claim carries a Stand marker or a register cross-reference
Preview and beta features are never load-bearing in a design a client signs
Unverified claims stay, marked unverified, with what you would need to confirm them
The register is data, so the page rendering it cannot drift from the pages depending on it

Gotchas

Copying platform claims out of a blog postBlogs are not updated on rename, so half the internet still says Delta Live Tables and Databricks Asset Bundles — names that are correct history and wrong instruction.
Letting a preview feature become load-bearing in a signed designWhen the preview shape changes, the redesign is not billable and the conversation is not pleasant.
Dating the page but not the claimA page stamped July with a claim from March reads as verified-in-July, and nobody can tell which sentence is the stale one.
Assuming GA on one cloud means GA on all threeFeature availability diverges across AWS, Azure and GCP more often than the marketing implies.