@adastracomputing/ink 0.2.0 → 0.4.0

package/dist/models/intent.js

@@ -1,5 +1,6 @@
 import { z } from "zod";
 import { ProfileSnapshotSchema } from "./profile.js";
+import { isWithinBounds } from "../crypto/sign.js";
 // --- Intent Types ---
 export const IntentTypeSchema = z.enum([
     "schedule_meeting",
@@ -191,6 +192,14 @@ export const MessageEnvelopeSchema = z.object({
  * Returns the validated message or throws a ZodError.
  */
 export function validateMessage(raw) {
+    // Bound the raw object's complexity BEFORE Zod walks it. A strict-mode parse
+    // must enumerate every key to reject unknowns, so a million-key object would
+    // otherwise burn hundreds of ms of CPU before being rejected. This also
+    // rejects JCS-unsafe numbers so a validated envelope is always one a
+    // canonicalizer can sign unambiguously.
+    if (!isWithinBounds(raw)) {
+        throw new Error("message exceeds complexity bounds");
+    }
     const envelope = MessageEnvelopeSchema.parse(raw);
     const payloadSchema = payloadSchemas[envelope.intent];
     // Validate payload strictly — reject unknown fields

package/docs/maturity.md

@@ -1,8 +1,10 @@
 # Maturity Notice
 
-> INK v0.1 is **experimental**. Wire formats, trust semantics and APIs
-> may change without backward-compatible migration before v1.0. Do not
-> use for load-bearing production traffic without your own review.
+> INK is **experimental**. The current defined wire version is `ink/0.2`, a
+> backward-compatible minor over `ink/0.1` (both major version 0). Wire formats,
+> trust semantics and APIs may change without backward-compatible migration
+> before v1.0. Do not use for load-bearing production traffic without your own
+> review.
 
 ## What "experimental" means here
 
@@ -12,8 +14,8 @@
   agent-card fetch, and DoS-amplification surfaces. Internal review is
   not a substitute for a third-party audit, treat the security
   posture accordingly.
-- Interop vectors (`../test-vectors/`) are authoritative for v0.1 but may
-  be added to or revised between v0.1 patch releases. Mismatched
+- Interop vectors (`../test-vectors/`) are authoritative for the current wire
+  version but may be added to or revised between patch releases. Mismatched
   implementations should report discrepancies as issues.
 - The protocol is in use by one production integrator (Tulpa). That is
   one data point, not a guarantee of robustness at scale.
@@ -22,9 +24,17 @@
   Bun, and edge runtimes. Browser use is feasible but not exercised by
   the maintainers.
 
-## What is stable in v0.1
+## What is stable
 
-- Envelope structure (fields, canonicalization with JCS / RFC 8785)
+These hold across major version 0 (`ink/0.1` and `ink/0.2`):
+
+- Envelope structure (fields, canonicalization with JCS / RFC 8785).
+  Signed bodies are restricted to JSON numbers that every conforming
+  canonicalizer serializes identically: non-finite values, negative zero,
+  and values whose shortest form uses exponential notation (for example
+  `1e21` or `1e-7`) are rejected at sign and verify time. INK payloads
+  carry only small integers and plain decimals, so this keeps the signed
+  bytes unambiguous across implementations.
 - Ed25519 signing base: `ink/0.1\nMETHOD\nPATH\nrecipientDid\nJCS(body)\ntimestamp`
 - Agent Card schema for `keys.signing` and `keys.encryption`
 - Key rotation authority rule (see `key-rotation-rule.md`)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adastracomputing/ink",
-  "version": "0.2.0",
+  "version": "0.4.0",
   "description": "Library and specification for the INK (Inter-agent Networking Kernel) protocol",
   "license": "MIT OR Apache-2.0",
   "author": "Ad Astra Computing Inc.",
@@ -51,7 +51,8 @@
     "check:pack": "./scripts/check-pack.sh",
     "gen:body-vectors": "tsx scripts/gen-body-signature-vectors.ts",
     "prepack": "npm run build",
-    "prepublishOnly": "npm run build"
+    "prepublishOnly": "npm run build",
+    "audit:all": "bash scripts/audit-npm-projects.sh"
   },
   "dependencies": {
     "@noble/curves": "^2.2.0",
@@ -61,14 +62,14 @@
     "zod": "^4.4.3"
   },
   "devDependencies": {
-    "@cloudflare/workers-types": "^4.20260418.1",
-    "@types/node": "^24.12.4",
-    "@typescript-eslint/eslint-plugin": "^8.60.0",
-    "@typescript-eslint/parser": "^8.60.0",
-    "eslint": "^10.4.0",
-    "tsx": "^4.22.3",
+    "@cloudflare/workers-types": "^4.20260610.1",
+    "@types/node": "^24.13.1",
+    "@typescript-eslint/eslint-plugin": "^8.61.0",
+    "@typescript-eslint/parser": "^8.61.0",
+    "eslint": "^10.4.1",
+    "tsx": "^4.22.4",
     "typescript": "^6.0.3",
-    "vitest": "^4.1.7"
+    "vitest": "^4.1.8"
   },
   "keywords": [
     "ink",

package/specs/ink-agent-containment-and-governance-extension-spec.md

@@ -1,7 +1,8 @@
 # INK Agent Containment and Governance Extension v0.1
 
-## Status
-Draft
+**Status:** Draft
+**Authors:** Ad Astra Computing
+**Last updated:** 2026-05-24
 
 ## Purpose
 

package/specs/ink-auditability.md

@@ -2,7 +2,7 @@
 
 **Status:** Draft
 **Authors:** Ad Astra Computing
-**Date:** 2026-03-19
+**Last updated:** 2026-06-01
 
 ## Problem
 

package/specs/ink-authorization-chain.md

@@ -2,7 +2,7 @@
 
 **Status:** Draft
 **Authors:** Ad Astra Computing
-**Date:** 2026-03-19
+**Last updated:** 2026-05-24
 
 ## Problem
 

package/specs/ink-compatibility-policy.md

@@ -1,7 +1,8 @@
 # INK Compatibility and Versioning Policy
 
-## Status
-Draft, v1 stabilization
+**Status:** Draft, v1 stabilization
+**Authors:** Ad Astra Computing
+**Last updated:** 2026-05-24
 
 ## Purpose
 
@@ -15,7 +16,7 @@ This is the normative compatibility contract. Any change to the INK wire format
 
 INK uses a single protocol version string in every message envelope, receipt, audit event and handshake message.
 
-Current version: `ink/0.1`
+Defined versions: `ink/0.1` (default) and `ink/0.2` (negotiated). See [§1.4](#14-defined-wire-versions).
 
 The version string appears in the `protocol` field of every top-level INK object and in the first line of every signature base.
 
@@ -48,6 +49,17 @@ prefix (e.g. `network.ink.*`) and define a transition policy. Until then,
 conforming implementations MUST emit and accept `network.tulpa.*` types as
 specified.
 
+### 1.4 Defined wire versions
+
+Two wire versions are defined:
+
+- `ink/0.1`, the original version. A sender emits it by default unless it has positively negotiated otherwise.
+- `ink/0.2`, a backward-compatible minor that changes only the body-signature domain separator, from the legacy `tulpa/sign\n` to the neutral `ink/sign\n`. Everything else, the transport-auth signature base, the envelope shape, the encryption and audit sub-protocols and every `network.tulpa.*` type, is identical to `ink/0.1`.
+
+`ink/0.2` is receiver-first. A receiver advertises the versions it verifies in its Agent Card `supportedProtocolVersions` array; when that field is absent a sender MUST assume `ink/0.1` only, and a sender MUST NOT emit `ink/0.2` to a receiver that has not advertised it. The negotiation is what keeps the change compatible: an `ink/0.1`-only receiver never receives `ink/0.2` traffic, so it is never asked to verify a domain it does not implement. An `ink/0.2` receiver selects the body-signature domain from the signed `protocol` field and verifies both versions, and because `protocol` is inside the signed body a relabelled message fails verification.
+
+This satisfies §1.1. The minor bump adds a capability without breaking deployed `ink/0.1` implementations, because the body-signature domain is negotiated rather than assumed.
+
 ---
 
 ## 2. Compatibility Rules

package/specs/ink-compliance-checklist.md

@@ -1,7 +1,8 @@
 # INK v0.1 Compliance Checklist and Implementation Matrix
 
-## Status
-Draft, v0.1 alpha conformance
+**Status:** Draft, v0.1 alpha conformance
+**Authors:** Ad Astra Computing
+**Last updated:** 2026-05-27
 
 ## Purpose
 

package/specs/ink-containment-phase1-implementation-spec.md

@@ -1,7 +1,8 @@
 # INK Containment Phase 1, Implementation Spec
 
-## Status
-Draft
+**Status:** Draft
+**Authors:** Ad Astra Computing
+**Last updated:** 2026-06-01
 
 ## Purpose
 

package/specs/ink-introduction-receipts-extension.md

@@ -1,10 +1,8 @@
 # INK Introduction Receipts Extension v0.1
 
-## Status
-Draft
-
-## Last Updated
-23 March 2026
+**Status:** Draft
+**Authors:** Ad Astra Computing
+**Last updated:** 2026-05-24
 
 ## Purpose
 

package/specs/ink-key-rotation-spec.md

@@ -1,7 +1,8 @@
 # INK Key Rotation Specification v0.1
 
-## Status
-Draft
+**Status:** Draft
+**Authors:** Ad Astra Computing
+**Last updated:** 2026-05-24
 
 ## Purpose