STILL BEING BUILT, IN PUBLIC
Altineris is not generally available. This is what has changed recently and why it mattered — including the parts that were wrong first. The tracker these entries come from is private while we're in stealth, so there is nothing to link to yet; that changes at general availability.
- 2026-08-20SITE
The site asked to be found — once
Every lore page gained one plain quotable sentence; the entity graph got stable identities that other properties already reference; the sitemap went to Search Console and one IndexNow submission covered all thirty-one pages. The discipline is in the tooling itself: submit once, resubmit only when content genuinely changes.
- 2026-08-20SITE · GUIDES
Every archive became a registry
The guides and this log both grew search, tag filters, honest dates and RSS feeds — server-rendered lists first, enhancement second, one data file each as the single source so the page, the schema and the feed can never disagree.
- 2026-08-20SITE
The planets learned where their pages are
Every body in the scene with a page now carries its route: clicking a planet opens its file on desktop, and the tap-opened dossier sheet grew an open-its-page button on touch. The universe stopped being a map you could only look at.
- 2026-08-20GUIDES · SITE
The research went public as field guides
The material the instruments are built on — publish quotas, near-duplicate detection, originality rules — is now published as citation-backed guides, carrying the same confidence discipline we use internally: documented, inference, or unknown, and never a number without a source.
- 2026-08-20AEGIS · SITE
The Aegis published its manifests
Each publishing instrument now prints its full capability manifest — what has landed with tests, what is still in the yards, and which enforcement gaps we documented against ourselves. Six worlds on four decks, statuses honest in both directions.
- 2026-08-20WAR · SITE
The war got its full bestiary
The documented ways automated publishing dies — from spec rejections to the courts — mapped as five fronts in severity order, each system with its threat file: anatomy of the raid, the shield built against it, the doctrine.
- 2026-08-20SITE
Phones got their own console
The mobile site stopped being a shrunken desktop: tap opens a body’s dossier as a bottom sheet, sideways swipes pan while vertical swipes always scroll, the raid became an explicit chip, the tour became the front door, and the scene runs a lighter profile with an adaptive frame governor. Navigation moved to a thumb-reach dock.
- 2026-08-20SITE
The codex grew into a chart
The reference page stopped being a wall of rows: a drawn map of the whole system with every station pinned — including the four service decks and sighted invaders — over a directory where every line routes to its full page and carries a plain-language reading.
- 2026-08-20SITE
The site became the universe
One live scene, every body real: the engine as a sun, the review queue as the only satellite with launch authority, documented risks as invaders. The treaty underneath: lore is truth in costume, statuses are real, and no number appears without being measured.
- 2026-08-19ENGINE
The deploy stopped trusting itself
A day of hardening the seams: the schema-at-boot guard verified against both of its readings, the CRM output sensor’s configuration seeded and checked in CI, and the deploy token scoped to only the database it deploys — so a leaked credential cannot reach anything else.
- 2026-08-17AEGIS
The validator got a fixture for every way a file fails
Media validation stopped trusting descriptions of bad files and started keeping them: a corpus with a failing case per rule, a recipe that reproduces each capture, box-level checks for the container faults that burn publish attempts, and a record of exactly which rules are enforced versus documented-absent.
- 2026-08-16AEGIS
Rights became a schema that defaults to no
The rights layer landed as data with teeth: grants default to denied, audio rights live separately from video and are never inherited, expired terms sweep already-queued work, credit is provably not a rights basis, and an append-only blocklist remembers a claimed work — including re-encoded copies of it — across every account.
- 2026-08-16ENGINE
A broken sensor now fails its tick instead of looking idle
Three schedulers could break in ways that looked like a quiet day. Fault injection became a shared fixture, and a database fault in any of them now fails the tick loudly — the difference between an outage you see and one you discover from its consequences.
- 2026-08-16SITE
The site went up, honestly unfinished
altineris.com launched on the edge with an access-request form backed by a real database and strict validation — and said in its own footer that the product is in development and not generally available. The honesty rules that later became the universe’s treaty started here.
- 2026-08-15ENGINE
The schema tells you at boot whether it matches the code
A deploy whose database was a migration behind used to fail later, somewhere unrelated, with an error that named the wrong thing. It now refuses to start and says which migration is missing.
- 2026-08-07ENGINE · LEDGER
Even a skipped run reports what it cost
Cost attribution grew past the happy path: runs that end early or get skipped still record their real spend, and CI started gating on a coverage ratchet with its own test database — the numbers the ledger will someday bill from are collected even when nothing shipped.
- 2026-08-02ENGINE
Fetching moved out of the scheduler
Source polling was doing per-client work inside the tick that was only meant to notice work existed. Splitting them stopped one slow client from delaying everyone else’s.
- 2026-08-02ENGINE · LEDGER
Cost is recorded against whoever asked
Render cost used to be computed and thrown away. Every generation now carries a number attributed to a client, which is the precondition for ever having a budget at all.
- 2026-08-02ENGINE · COLONIES
Posts write back into a customer’s CRM
The first end-to-end path where another product asks for content and receives it as a record in its own system, rather than as text somebody has to move by hand.
- 2026-08-01ENGINE
Brand tokens come from a reviewed source, not a stylesheet
Two assets were generated from a CSS file on a branch that predated a customer’s redesign before anyone checked it against the live site. Brand is now recorded data with a provenance, and rendering reads only that.
- 2026-08-01ENGINE
One engine, many clients
The engine stopped modelling everything as one blog. Sources, vocabulary, formats and output paths are per client, which is what makes it something a product can call rather than something one site runs.
NOTHING IN THE RECORD MATCHES — CLEAR THE SEARCH OR PICK ANOTHER AREA.
ENTRIES CORRESPOND TO REAL WORK IN THE REPOSITORIES — IF WE CANNOT POINT AT THE COMMIT, IT DOES NOT GO IN THE LOG. RSS