Axiomancer
Changelog

May 5, 2026

Encounter extraction reliability fix restores hourly pairwise data, hardened webhook URL validation, and a coordinated mobile and SEO polish pass across every Axiom site.

May 5, 2026OverwatchFix

Pairwise encounter extraction reliable again

Resolved a silent failure in the pairwise encounter extraction pipeline. The hourly job was timing out on every run for ~24 hours after duplicate indexes on the encounter table pushed write batches past the database statement timeout. The duplicate indexes have been dropped and upsert batches halved as a safety margin. Encounter geometry — CPA, TCPA, range, closing speed, COLREGS rule and role posteriors, and Rule 17 deviation flags — is flowing into the Risk and Investigations APIs again with full hourly freshness. No action is required on your part; backfill of the gap window is in progress.

May 5, 2026OverwatchFix

Hardened webhook URL validation

Webhook URL validation on alert channels is now stricter — only https:// destinations on the public internet are accepted, with explicit rejection of internal hostnames, link-local ranges, and other non-routable addresses. Existing webhook subscriptions are unaffected; new and updated subscriptions return a clear error message when an invalid URL is submitted instead of silently accepting it.

May 5, 2026OverwatchUpdate

Better error details on the public positions endpoint

The public /api/v1/positions/latest endpoint now preserves and returns underlying error details when an upstream component fails, instead of collapsing to a generic 500. API consumers building live maps and dashboards on top of the endpoint can now distinguish between transient upstream issues and request-side problems without having to retry blindly.

May 5, 2026OverwatchUpdate

Tightened security headers and cron authentication

Hardened the security headers served on every axiomoverwatch.io response, and tightened authentication on the internal cron endpoints that drive ingestion, archival, alert delivery, and Locus portfolio refresh. No user-facing behavior changes; browsers benefit from the stricter Content-Security-Policy and related headers automatically.

May 4, 2026OverwatchLayerLocusCodexPlatformUpdate

Coordinated mobile polish across every Axiom site

axiomoverwatch.io, axiomlayer.io, locus.axiomancer.io, axiomcodex.io, and axiomancer.io all received a coordinated mobile polish pass — landing pages, ticker rows, marketing sections, and the cross-product navigation bar no longer overflow the viewport, introduce horizontal scroll, or clip on small breakpoints. The Rogue Stack mobile landing nav also lands in this pass.

May 4, 2026OverwatchLayerLocusCodexPlatformUpdate

The RouteShift entry in the cross-product navigation bar across axiomoverwatch.io, axiomlayer.io, locus.axiomancer.io, axiomcodex.io, and axiomancer.io now points to routeshift.io — the canonical live domain — so clicks from anywhere in the platform reach the LLM proxy gateway directly instead of dead-ending at an unowned domain.

May 5, 2026OverwatchAxiomancerUpdate

SEO, sitemap, and analytics polish on Overwatch and Axiomancer

axiomoverwatch.io and axiomancer.io both received a professionalization pass — branded OpenGraph and Twitter summary_large_image social previews, a robots.txt and sitemap.xml at site root, refreshed alt text on marketing imagery, and analytics gating so PostHog and Amplitude only initialize on consent. Links unfurl with full-bleed branded previews on Slack, X, LinkedIn, and any embed-friendly surface, and search engines can index the public marketing surface without relying on link traversal.

May 3, 2026AxiomancerUpdate

Faster Axiomancer hero video

The hero video on axiomancer.io is now optimized for first paint — the heavier Mux player has been replaced on the homepage with a leaner asset path, mobile rendering of the hero is sharper, and the optimized hero is wired through to the rest of the marketing surface. First-time visitors on mobile see the hero noticeably sooner.

On this page