alelyon.com 0.17.0
- Friends chat on the website computes its message chain, its warnings and safety codes with the same Rust code the app uses, compiled to WebAssembly and fetched only with the Friends panel; nothing a person sees changes. The site's security header now lets its own scripts compile WebAssembly ('wasm-unsafe-eval' in script-src); it names no other origin.
- Pages: Check signature, in every post's menu, checks the post in your browser against its page's key and says whether it is what the page published, unchanged. My page's Privacy tab downloads your page's signed repository as one file. The Privacy Notice of 23 October 2026 describes the signed records.
- Friends chat on the website checks every message's place: each device's messages are numbered and linked, so the chat says when the service left one out, showed one twice, reordered or swapped one. A friend's new device waits until you accept it, and a safety code you compare in person can be marked verified; if it changes, sending waits until you compare again. The Privacy Notice of 23 October 2026 says what stays on your device.
- Links in Friends chat and in Pages posts, and a product's website and source, open only after a check in this browser: pressing one shows the site it really goes to, the address in full, and anything about it that deserves a second look, with Open, Copy address and Cancel. The check is the app's own, built into the Friends WebAssembly module (now 121,106 B, also fetched as Pages starts), and nothing about a link leaves the browser before it opens.
- The Friends chat's WebAssembly module is rebuilt from the shared core, which gained the app's signed-record checker; the website's build leaves that checker out, so the module keeps its size (100,852 B) and nothing a person sees changes.
- The developer console's findings say a quiet stretch's usual pace correctly: "usually 50 calls an hour", no longer "a hour". Nothing else a person sees changes. The console's analytics are now also written once in Rust (the app's), and held to give the same words and findings as the website's.
- The developer console's Dashboards and SLOs panel: make and read SLOs with their error budget and burn rates, and build dashboards of live widgets; switched on by site.config DASHBOARDS_READY after the identity service serves it.
- The Privacy Notice (2026-10-23.3) says what dashboards and SLOs keep.
- A status page at /status/: each part of Alelyon checked from outside, its uptime over 90 days, incidents and notices; until the live checks run (site.config STATUS_PAGE_READY), it shows the service's notices and says the checks start soon. Linked from the footer.
- The developer console's Endpoint checks panel: turn on health checks of your webhook endpoints and read their results; switched on by site.config WEBHOOK_CHECKS_READY after the identity service serves it.
- The console lets a webhook endpoint take monitor.alert and monitor.recovered, and a monitor watch one endpoint.
- The Privacy Notice (2026-10-23.3) says what endpoint checks keep.
- The developer console is an app at /console/: a side bar of products in groups that folds and pins products to Home, a top bar with search over products and the API reference (press /), the service's status and an alerts bell, the account menu, and Home with getting started, pinned products, the 7-day overview and recent activity. Each product has its own address (/console/#/keys). /developers/ keeps the documentation and sends old console links to their product.
- The Audit log shows every change made in the console beside the keys' own audit, downloadable as CSV.
- An Agents view: how the agents built on your apps use Alelyon (their MCP tool calls and API calls, failures, speed, busiest tools and latest failed tool calls), and an organization's usage by service account in Service accounts.
- The API reference and OpenAPI list the console routes a key with console:read may read.
- The Privacy Notice (2026-10-23.3) says what the console's change record keeps.
- The developer console's Explore and Home add charts to a board of your own: Explore's Add to a board (beside Pin to Home) puts the chart shown on a board, as a line set against what it is compared with, a number for a table, or bars by route when split by route; Home's pinned charts have Add to a board beside them, with a choice of which. Pick one of your boards or a new one, named; a chart a board already holds is not added twice, a full board says how much room it has, and the board opens from the confirmation. The made-up account's boards stay in this browser. Loaded only when pressed.
- The developer console's Boards, ready for the console to open: boards of your own, kept with your account while you are signed in (in this browser otherwise). Each board has a name, the time it shows and what every tile on it is narrowed to; a tile is added in three questions (what to watch, for which calls, shown as a number, a line, bars by route or bars by answer), with what to set it against (the time before, or a week before) and a mark to warn at, the tile following the answers as you choose. Tiles are arranged with buttons, changed, duplicated and removed (with undo); boards are renamed, duplicated, linked and deleted; At a glance names the tiles past their marks. The charts pinned to Home in a browser become a board of their own at the first sign-in there. Loaded only when Boards is first opened.
- The Privacy Notice (2026-10-23.2) says what the developer console's Boards keep with your account: each board's name, time and narrowing and its charts' settings, never a call or a figure; and that a browser's pinned charts are added once to a board of their own at sign-in.
- release as usual; the new header comes with the site's own Firebase Hosting and Cloudflare Pages configuration.
- release before the identity deploy that switches signed repositories on (SIGNED_REPOSITORIES="on"), which records Privacy version 2026-10-23.2 (the second text of 23 October 2026, after the short links' 2026-10-23).
- release as usual.
- Ready for the console to open, with Boards: publish www by www/DEPLOYMENT_RUNBOOK.md on the owner's word.
- Deploy the identity service carrying the console boards' routes (identity next: platform-console-boards) before this release; publish www by www/DEPLOYMENT_RUNBOOK.md on the owner's word. The Privacy Notice 2026-10-23.2 (the owner approved its Boards paragraph on 2026-10-23) ships with it: deploy the identity service with PRIVACY_VERSION 2026-10-23.2 after this release.