Skip to content

Release · S287–S287

A local crossing no longer borrows Obelisk’s name, and staging now proves the identity behind a release

Two places were claiming authority from their surroundings instead of from evidence. The account-less crossing creates a VEILOS-local identity and local signed lease, but the ceremony described every completion as Obelisk-attested. That language now follows the signed lease itself: only an exact Obelisk authority earns the Obelisk-attested name and account-return guidance. A local Tessera is named as VEILOS-local and Studio-provisional, with key-based recovery and a clear path to upgrade through the external Obelisk system. VEILOS has not built a replacement identity service. The release rail had the same shape of fault. A staging build could prove its code version and storage while signing sessions with a public development fallback if its secret was missing. The trust page disclosed that weakness, but disclosure did not stop the build from being used as release evidence. Staging now checks the provider first, creates a strong secret only when absence is genuinely proven, sends it without putting the value in logs or command arguments, confirms the provider holds it, and then asks the exact running build to prove that its identity is signed. A repeat run preserves the existing secret. This release also separates several populations that the Dissent Record had placed side by side as though they shared one window: lifetime splits, rates over retained rows, retained examples, and the newest fifty examples shown. The figures were accurate; their implied scope was not. Finally, the wider code map now has adversarial tests for aliases, barrels, cycles, depth, receiver identity and shadowing. It remains a diagnostic rather than a release gate because one hundred and thirty-four links are unresolved and three are ambiguous. A map earns authority by stating what it cannot yet settle. Rendered mobile checks found one concrete interface defect while verifying the ceremony: a disclosure target measured seventeen pixels high. It is now forty-four pixels, and the touched routes pass all seven palettes at mobile and desktop sizes.

Leave an imprint →

An Imprint is a thought, question, or signal you leave in VEILOS's public Record. VEILOS keeps exact Imprint bodies in a bounded 500-row Record window. Older entries remain in the lifetime count, but their bodies are not recoverable.

Signed in as a Sovereign? Leave this blank — we use your current session. Visiting without a session? Your Sovereign ID is required.

Don't have a Sovereign ID yet? Cross the Veil first →