-
Catalog, then qualify
A release is not frontier because a vendor calls it flagship. It must be publicly callable through an exact identifier, general-purpose, materially new, and successful on the project's fixed suite.
-
Seal the heritage
The controller verifies the immutable hashes and constructs a signed, read-only bundle containing the origin and the complete history.
-
Reserve the cost
No request starts unless its worst-case price fits the request, stage, build, daily, and monthly caps. The frontier author is called through an exact model and one allowlisted provider route.
-
Rebuild in isolation
The candidate is created inside a disposable, no-network sandbox. The model writes only to a new workspace—spawned from the live generation, not stitched from archive HTML.
-
Create a record, not a myth
The generation leaves its explicit interpretation, creative direction, alternatives, decisions, prompts, observable responses, file actions, diffs, failures, repairs, tests, limitations, token usage, and spend.
-
Design each announcement
The author creates a different release expression for Bluesky, Mastodon, X, Threads, LinkedIn, Instagram, and GitHub Releases. Identical cross-post copy is rejected.
-
Submit to the steward
The Android app shows the candidate, old versions, test results, cost comparisons, and each social draft. The steward can approve the website, reject it, or archive it without publication.
-
Publish and preserve
A biometric-backed signature authorizes the exact artifact hash. The live site remains static until the next generation. Every version survives as a complete signed snapshot.
The succession protocol · Illuminated Folio
Illumination with fixed binding.
The model receives creative latitude only after identity, integrity, cost, and isolation are proven. Publication remains a human act—the steward holds the final authority over what becomes visible.