Axiomancer
Changelog

April 20, 2026

Slack credential encryption, NYC council decisions and zoning variances populated, faster kinematic processing, and improved loitering detection accuracy.

April 20, 2026LayerFix

Slack integration credentials fully encrypted

Slack bot tokens stored by Layer are now exclusively encrypted at rest. A previous migration encrypted all existing tokens, and the final plaintext column has now been removed — so there is no path for credentials to be stored unencrypted going forward. No action is required on your part.

April 20, 2026LayerFix

Stricter virtual card ownership checks

Virtual card operations now verify that the cardholder belongs to the requesting organization before issuing or modifying a card. This prevents any possibility of cross-tenant card creation. If you use virtual cards, no changes are needed — the check applies automatically.

April 20, 2026LocusCodexUpdate

NYC council decisions and zoning variances now populated

New York City uses a non-standard Legistar layout that was missing several expected fields, causing council decision and zoning variance records to come back incomplete or empty. Locus now handles NYC's field variations — including committee names, enactment dates, and introduction dates — by trying multiple fallback identifiers for each field. Vote history for council decisions and action history for zoning variances are also now scraped directly from meeting detail pages when the JSON API is unavailable. If you query NYC council decisions or zoning data through the Locus API or MCP server, you should now see complete records with vote tallies and action history.

April 20, 2026CodexLocusUpdate

Federal environmental reviews now available

The previous changelog entry noted that EPA EIS environmental reviews were not yet available. They now are — Locus pulls federal NEPA environmental impact statements from the Federal Register public API, replacing the retired EPA endpoint. Environmental review records flow into cell scores and the Civic Intelligence dataset alongside the existing California CEQA reviews. No action is required on your part.

April 20, 2026OverwatchUpdate

Faster kinematic fingerprint processing

Kinematic fingerprint computation now processes vessel visits in parallel batches instead of sequentially, so vessels with large visit histories no longer risk timing out. If you use risk scoring or behavioral analytics, fingerprint profiles now update more reliably for high-traffic vessels. No action is required on your part.

April 20, 2026OverwatchUpdate

Faster AIS data retention queries

Added a dedicated index on AIS position timestamps that speeds up the downsampling queries used by the data retention system. Retention tier transitions now run faster, especially as position data grows.

April 20, 2026OverwatchFix

Improved loitering detection accuracy

Fixed an incorrect column reference in the vessel loitering feature extraction that could cause loitering behavior detection to return inaccurate results. Loitering signals now use the correct timestamps, improving the accuracy of behavioral anomaly scoring.

April 20, 2026OverwatchFix

AIS ingestion no longer logs false errors on rate limits

Fixed an issue where rate-limited AIS data requests were logged as failures instead of being handled gracefully. Overlapping data requests that receive a "too frequent" response are now correctly treated as skipped rather than failed, reducing false error noise in pipeline monitoring.

April 20, 2026CodexFix

More complete council decision data for New York City

The Civic Intelligence HTML collection path now resolves more fields for New York City council decisions. Previously, records from NYC could have missing introduction dates, committee names, and enactment dates because the city's Legistar pages use different field labels than most other jurisdictions. The collector now tries multiple label variants per field, so NYC records have significantly fewer null values for MatterIntroDate, MatterBodyName, and MatterEnactmentDate. If you query council decisions for NYC through the Locus API or the Civic Intelligence schema, you should see more complete date and committee information. No action is required on your part.

April 20, 2026LocusFix

More complete vote tallies for council decisions

Fixed an issue where vote history for council decisions could be missing even when the HTML fallback was available. When a city's Legistar JSON API partially responded — returning meeting history but failing on the vote detail request — the system incorrectly treated the partial response as complete and skipped the HTML scraping fallback. Vote tallies are now captured reliably for all Legistar-powered cities, including New York City. If you query council decisions through the Locus API or the Civic Intelligence schema, you should see more complete vote results. No action is required on your part.

On this page