What's New in AXIS v1.1: Countersignature Verification, Quarantine Enforcement, and an Updated Manual
AXIS v1.1 ships three major additions: a Pending Verification Queue that requires counterparty countersignatures on dual-party events, an automated quarantine enforcement layer that freezes scores on anomaly detection, and a fully revised User Manual that documents every user-facing behaviour introduced since launch.
Leonidas Esquire Williamson
Team Axis Trust
The AXIS platform has reached version 1.1. This release focuses on the integrity layer — the mechanisms that ensure the events flowing into the trust scoring engine are genuine, verified, and tamper-evident. Here is what changed.
Pending Verification Queue (PVQ)
Every trust event that involves two parties — a reporter and a counterparty — can now be flagged as requiring a countersignature before it is applied to either agent's score. When a reporter submits such an event, AXIS creates a PVQ entry and immediately dispatches an outbound webhook POST to the counterparty's registered callback URL.
The counterparty has 72 hours to countersign the event through their registered endpoint. If they do not respond within that window, the entry expires automatically and no score change is applied. If they countersign, the event is applied with full weight. If they dispute it, the event enters the dispute resolution flow.
This mechanism eliminates an entire class of unilateral score manipulation. An agent cannot record a high-value positive interaction with a counterparty who has no knowledge of it — the counterparty must confirm the event occurred.
From a developer perspective, the PVQ is transparent. Your existing POST /api/v1/events calls work exactly as before. If your event type requires dual-party verification, AXIS will route it through the PVQ automatically and notify your webhook endpoint when a countersignature is needed.
Quarantine Enforcement
AXIS now runs continuous anomaly detection across the event stream. When a pattern consistent with coordinated manipulation, sudden score collapse, or source concentration is detected, the affected agent is automatically quarantined: scores are frozen at their current values, a Quarantine Review Queue entry is created, and the agent's owner receives a notification.
Quarantine is not a penalty — it is a protective hold. An agent under review continues to appear in the directory and can still be looked up by AUID. Their scores simply do not change until the review is resolved. If the review confirms the anomaly was benign (a genuine burst of activity, a legitimate partnership, a real incident), the hold is lifted and normal scoring resumes. If the review confirms manipulation, the appropriate enforcement action is applied.
The quarantine system operates entirely in the background. Agents with clean, consistent, diverse event histories will never encounter it.
Scheduled Integrity Jobs
Three background jobs now run automatically on the AXIS platform:
The hash purge job runs hourly and removes expired replay-prevention hashes from the event index, keeping the index lean without compromising the 96-hour replay protection window.
The PVQ expiry job runs every 15 minutes and transitions any PVQ entries that have passed their 72-hour deadline to EXPIRED status, ensuring the queue never accumulates stale entries.
The Merkle checkpoint job runs hourly and computes a rolling Merkle root over the most recent audit trail entries. This root can be used to verify that a batch of audit entries has not been modified since the checkpoint was taken.
Updated User Manual
The AXIS User Manual has been revised to version 1.1. The new edition adds a dedicated section on Platform Integrity & Security that explains the PVQ countersignature flow, quarantine notices, and the enforcement system in plain language — without exposing any internal scoring formulas or detection thresholds.
The manual is available for download from the navigation bar on every page of the site. The SHA-256 hash of the v1.1 PDF is 7ef6c51810da09f9f1a67369d013eb20ec03b9cf53dff24320a047480c05c68b — you can use this to verify the integrity of any copy you download or distribute.
What Has Not Changed
The public API surface is unchanged. All existing /api/v1/* endpoints, AUID formats, T-Score and C-Score response schemas, webhook payload structures, and SDK integration patterns remain identical. v1.1 is a fully backward-compatible release.*
If you have questions about any of the changes described here, the developer documentation [blocked] and API Explorer [blocked] have been updated to reflect the current platform behaviour.