All notable changes to the NEXUS-A2A specification and Python SDK.
Format follows Keep a Changelog. Versioning follows Semantic Versioning.
Found by the four-area battery in tests/battery/. Assessment record:
docs/assessments/2026-10-06-false-assurance/.
/ separators and collapsed slashes before matching. Built-in detectors now run in
addition to blocked_argument_patterns:
CREDENTIAL_PATH: .ssh/, .aws/, .kube/config, .netrc, gcloud, docker
config, /etc/shadow, /etc/sudoersPATH_TRAVERSAL: any .. segmentMETADATA_ENDPOINT: 169.254.0.0/16 in decimal, hex, or octal spellings;
fd00:ec2::254; 100.100.100.200; metadata hostnamesSECRET_IN_ARGUMENTS: private-key headers, cloud and VCS tokensREMOTE_CODE_PIPE: a download piped into an interpreterOf 24 evasions that v0.3 allowed, 24 are now denied. Denials report every rule that fired.
guardian_url was set and
httpx was not installed, NEXUSGuardianClient evaluated the default inline policy.
That bypassed the remote policy and never engaged FAIL_CLOSED. A missing HTTP client is now
an unavailable Guardian, and the configured fail mode applies. Found when the behavioral
nexus-score failover check ran in a clean environment.REASONING_INSUFFICIENT). Previously, "x" satisfied it.NEXUS/opa/nexus-authz.rego):
request label no longer
downgrades a PERMANENT write.allow.deny_reason is populated.verify_chain_integrity() now recomputes each version’s content hash.
Previously it compared stored hashes only, so a component edited inside a stored version
verified as intact. Snapshots now deep-copy components, so a live edit can no longer rewrite
history. Hashes for components that were never quarantined are unchanged from v0.3.AgBOM rug-pull hold. Re-discovering a known MCP server with a different tool-manifest
digest no longer registers a second trusted server. The component is marked quarantined,
its prior digest is kept, and the version reason is mcp_capability_digest_changed. Release
requires approve_capability_change(bom_ref, approver), which is recorded in the chain.
Same-digest rediscovery is idempotent. A first digest on an unpinned server is recorded as
mcp_capability_digest_pinned.
nexus-score --v03-checks tests behavior, not imports. Guardian must deny a hostile
argument, allow a benign one, and reject thin HEAR reasoning. A FAIL_CLOSED Guardian must
deny when unreachable. AgBOM must detect a stored-version edit and hold a rug pull. OPA
policies must pass opa check --strict and opa test; file presence no longer counts.
On main the old checker printed “10/10 verified, all v0.3 controls satisfied”, while
the behavioral checks fail 3 of 10. Missing evidence (no opa binary) is NOT ASSESSED,
never OK. Exit codes: 0 verified, 1 failed, 2 not assessed. Output is labeled an
implementation self-check, not a conformance claim.Memory Vaccine stub honesty. Stub mode scores any text that lacks its test keywords at
drift 0.05, including an explicit exfiltration instruction. Decisions and Guardian exports
now carry drift_method (stub:keyword-fixture, embedding:all-MiniLM-L6-v2, or
not_assessed:request_scope), and constructing a stub-mode vaccine emits a warning.
GuardianPolicy(aim_registry=...):
ACT_TIER_FROM_REGISTRY), so a lower claim cannot skip it.ACT_TIER_EXCEEDS_REGISTERED).AIM_NOT_REGISTERED).AIM_DIGEST_MISMATCH).nexus-authz.rego and nexus-aism-invariants.rego read the tier from data.nexus.aim.agents[<did>]
and expose effective_act_tier. Previously, a config_change that omitted act_tier skipped the
ACT-2+ out-of-band approval, and an agent with no tier passed I-4 without any kill path. Both now
treat a missing tier as ACT-4.AIMRegistry.to_opa_data() produces the OPA document.act_tier: Guardian now treats an undeclared ACT
tier as ACT-4, so HEAR applies (ACT_TIER_UNDECLARED). A tier outside 1-4 is denied
(ACT_TIER_INVALID). To restore v0.3 behavior, pass
GuardianPolicy(treat_undeclared_tier_as=None).schemas/aim-v0.3.schema.json: v0.2 plus required actTier (1-4) and optional maxDelegationDepth,
using v0.2’s camelCase field names. The IETF draft’s example uses snake_case (act_tier); that naming
conflict is recorded here, not resolved. nexus_sdk.aim provides AIMRegistry, which records every
AIM version, and aim_digest. The undeclared-tier-as-ACT-4 floor still applies when no registry is configured.nexus-aism-invariants.rego failed
type-checking on every version. The APay migration is decision-identical on 873
differential inputs.docker/docker-compose.yml mounted ./opa and ./schemas, which resolve under
docker/ and do not exist. It now mounts ../opa and ../schemas. The OPA
healthcheck no longer calls curl, which is absent from the -static image, so the
gateway’s service_healthy dependency can clear..github/workflows/opa.yml watched a non-existent opa/** path. It now checks and
tests NEXUS/opa on OPA 0.65.0 and 1.4.2.v0.5.0 is the Sovereign Payment Gateway release. It composes the
CP.5.APAY/0.4 payment-integrity foundation into a deterministic execution
boundary designed so that compromising an agent process is not sufficient to
obtain a payment key, widen authority, replay authorization, restore spent
capacity, or declare settlement truth.
KeyGuardian): an isolated credential-use boundary with
transaction-bound authorization and no raw-key return path.ai-safe2 package.0.5.0; the distribution remains
nexus-a2a-sdk and the import namespace remains nexus_sdk.full extra now expands to its dependencies directly so package metadata
can be resolved before the first public release exists.nexus-score console entry point because its target
module was not shipped. The source scoring utility remains available for
repository workflows until it is redesigned as a supported SDK command.CP.5.APAY/0.4 schemas, policy IDs, profile IDs, and wire contracts
are intentionally unchanged. Package v0.5.0 adds the gateway without silently
creating a new protocol version.NEXUSPaymentExecutionPlane.readiness().v0.4 is the Agent-to-Payment Release. It adds a fourth enforcement plane, CP.5.APAY (Agentic Payments Integrity Profile), covering the layer no published agent-payment protocol claims: proof that the workload holding a valid credential is still running the software that was approved, at the moment value moves.
AP2 (FIDO, April 2026), x402 (Linux Foundation, April 2026), Visa TAP, Mastercard Agent Pay and KYA-OS answer recognition and authorization well. All of them assume the signing host is trustworthy; none require proof of it. An attacker who owns the agent host inherits its identity, registrations and mandates intact, and every signature they produce verifies correctly.
Two AISM invariants are added: I-7 Runtime-Bound Authority and I-8 Aggregate Economic Containment.
nexus_sdk/payments/objects.py: protocol-independent object model
principal_id, authority_grant_id,
delegation_chain_id, runtime_measurement_id, policy_id,
transaction_intent_id, revocation_epochMoney in exact integer minor units; rejects float construction, excess precision,
and cross-currency comparisonAssuranceLevel (0 none/guest → 4 runtime-bound), SettlementFinality,
ConsequenceClass, 40+ stable PaymentReasonCode valuesAuthorityConstraints.attenuation_violations() across 18 axes; null on a set-valued
axis is treated as the universal set, so an unconstrained child under a constrained
parent is a widening rather than an inheritancenexus_sdk/payments/mandate.py: mandate compiler and trusted rendering surface
Ambiguity objects;
issue() refuses while any remain unresolvedrender() generates from constraints alone, consequence firstnexus_sdk/payments/authority.py: authority graph and revocation plane
RevocationPlane as a monotonic epoch rather than a delete, so revocation does not
race caches, facilitators or child agentsexposure_after_revocation(): measures value that still moved, not API latencynexus_sdk/payments/firewall.py: deterministic policy decision point; no language
model participates; reports every failing rule, not the firstnexus_sdk/payments/broker.py: isolated signing authority
NullCredentialBroker is the bound default and refuses every requestnexus_sdk/payments/evidence.py: Payment Transaction Receipt (PTR)
nexus_sdk/payments/gateway.py: orchestration and conformance metrics
nexus_sdk/payments/opa_input.py: single input contract shared by the Python
firewall and the Rego policynexus_sdk/payments/adapters.py: IdentityNormalizer (implemented) plus AP2,
x402, Visa TAP, Mastercard Agent Pay and KYA-OS bindings as fail-closed contractsopa/nexus-apay.rego: out-of-process payment enforcement, default deny, with a
separate release_credential gateopa/nexus-aism-invariants.rego: invariants I-7 and I-8; aggregate score now /8schemas/apay-authority-grant-v0.4.schema.jsonschemas/apay-ptr-v0.4.schema.jsonpayments/README.md: CP.5.APAY profile, standards landscape, execution sequence,
required metrics, MVP acceptance gates, buyer and standards positioningpayments/THREAT-MODEL.md: adversaries, 14-entry risk register with residual risk,
and an explicit known-limits sectionpayments/CONTROLS.md: APAY-01..20 with AI SAFE² mapping, rationale, test
references, and three conformance levelspayments/CHALLENGE-LAB.md: twelve falsifiable experiments, including one
(EXP-08, catalog poisoning) designed to fail in order to document a stated limittests/test_apay.py: 95 tests. Every control has at least one test proving it
denies what it claims to deny. TestHonesty fails if a fail-closed default is made
permissive.tests/test_apay_opa_contract.py: 7 tests. Parses the Rego, extracts every
input.* path it reads, and fails if anything is not supplied by the shared builder -
because a rule with an absent input path is undefined, and an undefined violation rule
is a control that silently stopped existing.pyproject.toml: build-backend was setuptools.backends.legacy:build, which does
not exist. The package could not be installed from source at all. Corrected to
setuptools.build_meta.opa/nexus-apay.rego is not validated against a live OPA server in this repository’s
CI. Its input contract is test-enforced; its evaluation semantics are not.[project.scripts] nexus-score = "nexus_sdk._cli:main" still points at a module that
does not exist. The console script is non-functional. Not fixed in this release.v0.3 is the ACS Integration Release. It closes the per-call argument inspection gap identified in the NEXUS-vs-ACS analysis, adds OpenTelemetry-native audit export, implements dynamic Agent Bill of Materials, and publishes the first NEXUS-ACS Bridge Specification. AI SAFE2 v3.0 score moves from 24/25 (stub mode) toward 25/25 with full Guardian + OPA + SPIRE deployment.
nexus_sdk/guardian.py: Guardian Integration Profile (ACS-compatible)
GuardianPolicy: inline verdict engine with 8-rule hierarchyGuardianStepContext: AOS JSON-RPC 2.0 compatible step context with NEXUS DID identityNEXUSAgentContext: replaces bare string agent.id with DID + SPIFFE workload attestationNEXUSGuardianClient: three failover modes (FAIL_CLOSED, FAIL_OPEN, FAIL_MANDATE_ONLY)build_tool_call_step(), build_memory_store_step(): factory helpersnexus_sdk/otel.py: OpenTelemetry-native NOR export
NEXUSOutputReceipt (NOR): cryptographic audit receipt for every agent actionInMemoryNORExporter: test utility for NOR span collectionNEXUSNORSpan: production OTel span exporternor_to_otel_attributes(): OCSF event class mapping (deny always maps to POLICY_VIOLATION 6002)OCSFEventClass enum: API_ACTIVITY, POLICY_VIOLATION, DATA_ACTIVITY, AUTHENTICATION_ACTIVITYbuild_tool_call_nor(), build_memory_nor(): factory helpersnexus_sdk/agbom.py: Dynamic Agent Bill of Materials
AgBOMManager: real-time, hash-chained component inventoryAgBOMComponent (CycloneDX v1.6 compatible): 8 component types including mcp_serverAgBOMVersion: hash-chained version history with Ed25519-ready signaturesdiscover_mcp_server(): auto-creates AgBOM version on MCP server discoveryto_cyclonedx(), to_spdx_summary(), to_dict(): multi-format exportverify_chain_integrity(): full chain validationnexus_sdk/bridges/__init__.py (updated):
NEXUSACSBridge: NEXUS-ACS Bridge Specification v0.1
build_tool_call_request(): wraps CAEL tool calls in AOS steps/toolCallRequest formatbuild_memory_store_request(): steps/memoryStore with NEXUS memory provenance extensionbuild_message_request(): steps/message for input/output interceptionparse_verdict(): parses AOS Guardian response into GuardianVerdictResultProtocolBridgeFactory: updated to include “acs” protocol; auto-detects from guardian_urlnexus_sdk/memory.py (updated):
MemoryVaccine.to_acs_guardian_context(): exports provenance metadata for ACS Guardian stepsMemoryVaccine.validate_write_with_guardian(): validates write against external Guardian endpointopa/nexus-aism-invariants.rego: Six AISM invariants as OPA/Rego Guardian policy templates
aism_score (0.0-1.0), aism_verdict (allow/deny), invariant_violations aggregateschemas/nor-v0.3.schema.json: JSON Schema for NEXUS Output Receiptschemas/agbom-v0.3.schema.json: JSON Schema for Agent Bill of Materials (CycloneDX-compatible)schemas/guardian-v0.3.schema.json: JSON Schema for Guardian Integration Profile wire formatdocker/docker-compose.yml: Reference sovereign gateway deployment
docker/.env.example: Configuration template with all environment variables documenteddocker/otel/collector-config.yaml: OTel Collector config for NOR-to-SIEM exportgovernance/GOVERNANCE.md: Multi-sovereign governance charter
governance/ietf-draft-nexus-l1-l2.md: Pre-submission IETF Internet-Draft framing
LICENSE: Apache 2.0CHANGELOG.md: This fileCONTRIBUTING.md: Contribution guide with DCO requirementsSECURITY.md: Vulnerability disclosure policyCODE_OF_CONDUCT.md: Contributor Covenant v2.1pyproject.toml: PEP 517 packaging (installable via pip install nexus-a2a-sdk)examples/: Working examples directorytool_call check fired before deny check,
so a denied tool_call received API_ACTIVITY (6003). Security classification was wrong.| Pillar | v0.2 | v0.3 | Delta |
|---|---|---|---|
| P1 Sanitize and Isolate | 5/5 | 5/5 | Guardian fills S1.3 gap |
| P2 Audit and Inventory | 5/5 | 5/5 | NOR OTel + AgBOM fills A2.3/A2.5 gap |
| P3 Fail-Safe and Recovery | 5/5 | 5/5 | Guardian inline deny fills F3.1 gap |
| P4 Engage and Monitor | 4/5 | 4/5 | Drift via AgBOM unsigned count (full score requires production embeddings) |
| P5 Evolve and Educate | 5/5 | 5/5 | |
| Total | 24/25 | 24/25 (stub) / 25/25 (full) |
Full 25/25 requires OPA + SPIRE + production sentence-transformers in deployment.
Initial public release. Core NEXUS-A2A specification with Python SDK.
nexus_sdk/cael.py: CAEL envelope (CAELEnvelope, CAELSender, Performative, ContextCompartment)nexus_sdk/memory.py: Memory Vaccine (four zones, drift detection, provenance, checkpoints)nexus_sdk/bridges/__init__.py: Protocol bridges (MCP, A2A, OpenAI, LangChain, CrewAI, n8n, REST)opa/nexus-authz.rego: L3 core authorization policyschemas/aim-v0.2.schema.json: Agent Identity Manifest schemacompliance/scoring/nexus-score.py: AI SAFE2 v3.0 compliance checkerREADME.md: Specification overview and quick startMaintained by Cyber Strategy Institute. Contributions welcome via the process in CONTRIBUTING.md.