@cynodia/axiom 0.14.0-alpha.2 → 0.14.0-alpha.3

package/README.md

@@ -33,7 +33,7 @@ Shorter forms of the same routing: [`AGENTS.md`](AGENTS.md) and [`llms.txt`](llm
 at this package's root.
 
 **Status: experimental / alpha.** The API may change between alpha releases. The
-documentation in `docs/` describes this exact version, `0.14.0-alpha.2`.
+documentation in `docs/` describes this exact version, `0.14.0-alpha.3`.
 
 ## Installation
 
@@ -47,7 +47,7 @@ Every release of this project is a pre-release and npm's `latest` tag points at
 plain command above installs the current version. **There is no `alpha` dist-tag** — the tag
 was removed once it stopped tracking releases, and `npm install @cynodia/axiom@alpha` now
 fails with a 404. Pin the exact version instead when one is needed:
-`npm install @cynodia/axiom@0.14.0-alpha.2`.
+`npm install @cynodia/axiom@0.14.0-alpha.3`.
 
 These are ES modules compiled to ES2022; import them with `import`, not `require`. There is
 no published Axiom CLI. `@cynodia/axiom-server`'s SQLite persistence adapter additionally

package/docs/ACTIONS_TRANSACTIONS.md

@@ -1,6 +1,6 @@
 # Actions and transactions
 
-Axiom 0.14.0-alpha.2. An action is behavior expressed as data, executed as a transaction.
+Axiom 0.14.0-alpha.3. An action is behavior expressed as data, executed as a transaction.
 
 ```ts
 {

package/docs/AGENT_API.md

@@ -1,6 +1,6 @@
 # Agent API
 
-Axiom 0.14.0-alpha.2. The machine-facing interface. Agents query semantics and apply
+Axiom 0.14.0-alpha.3. The machine-facing interface. Agents query semantics and apply
 structural transformations; they never edit generated code.
 
 ```ts

package/docs/AGENT_REFERENCE.md

@@ -1,6 +1,6 @@
 # Agent reference
 
-Axiom 0.14.0-alpha.2. Compressed operational contract. Read this plus the `.d.ts`
+Axiom 0.14.0-alpha.3. Compressed operational contract. Read this plus the `.d.ts`
 declarations before authoring or modifying an Axiom application.
 
 Formal guarantees: [`SEMANTIC_CONTRACT.md`](SEMANTIC_CONTRACT.md). Mistakes that compile:
@@ -1195,9 +1195,18 @@ semantic step — no transition, no `ActionDef` invoke, no event/timer/branch, n
 auto-failed or auto-cancelled, and `cancelWorkflow` from an incompatible build is refused.
 Presentation-only changes (`name` / `description` / `label`) and step declaration order are
 **not** semantic. A semantically identical fresh process recovers instances normally. There
-is no workflow instance migration in 0.14. Structurally invalid workflow IR is refused at
-`createAxiomServer` (`WorkflowIRError`); a malformed step reaches `validateGraph` as a
-`WORKFLOW_INVALID_STEP` diagnostic, never a native error.
+is no workflow instance migration in 0.14.
+
+Totality: every surface that inspects / validates / compiles / admits / executes a
+`WorkflowDef` is total over malformed input. `validateGraph` / `AgentAPI.validate` /
+`AgentAPI.analyzeWorkflow` / `compileToServerIR` produce a structured diagnostic (or
+structured `Error`), never a native `TypeError`, for a `null` / non-object step, a
+non-array `steps` / `inputs` / `bindings`, or an unknown step kind. A hand-tampered Server
+IR is refused at admission — `createAxiomServer` / `createWorkflowEngine` throw
+`WorkflowIRError` (`WORKFLOW_INVALID_IR`) — for those container shapes **and** for broken
+references (a `bind` to an undeclared binding, a `producedBy` to a non-step, a `ref` outside
+the closed workflow scope, a `now`/`uuid`/`random` call). Unknown references are invalid,
+never silently dropped; an admitted workflow can never wedge permanently `running` on one.
 
 Inspection: `server.getWorkflow(instanceId)` / `inspectWorkflows(limit)` — `status`,
 `currentStepId`, `activationId`, `attempt`, `waitingReason`, `nextEligibleAt`,

package/docs/ANTI_PATTERNS.md

@@ -1,6 +1,6 @@
 # Anti-patterns
 
-Axiom 0.14.0-alpha.2. Each of these compiles. Each is wrong. Each is followed by the correct
+Axiom 0.14.0-alpha.3. Each of these compiles. Each is wrong. Each is followed by the correct
 alternative.
 
 ## 1. Field names as entity runtime keys

package/docs/AUTHORITY.md

@@ -1,6 +1,6 @@
 # Authority
 
-Axiom 0.14.0-alpha.2. How an application crosses the trust boundary.
+Axiom 0.14.0-alpha.3. How an application crosses the trust boundary.
 
 Until 0.5.x an Axiom application executed locally. 0.6 adds an **authority**: a generic
 runtime that owns state, decides mutations and persists them. The same semantic graph

package/docs/CONSTRAINTS.md

@@ -1,6 +1,6 @@
 # Constraints
 
-Axiom 0.14.0-alpha.2. Two constructs, answering different questions. They are not
+Axiom 0.14.0-alpha.3. Two constructs, answering different questions. They are not
 interchangeable.
 
 | | Question | Sees |

package/docs/DISTRIBUTED_AUTHORITY.md

@@ -1,6 +1,6 @@
 # Distributed authority
 
-*This document describes Axiom `0.14.0-alpha.2`.*
+*This document describes Axiom `0.14.0-alpha.3`.*
 
 The authoritative runtime (`docs/AUTHORITY.md`) may run as **more than one process at the
 same time**, over one shared persistence provider, without any change to the

package/docs/EFFECTS.md

@@ -1,6 +1,6 @@
 # Effects
 
-Axiom 0.14.0-alpha.2. External effects are not rollback-capable state mutations. This file
+Axiom 0.14.0-alpha.3. External effects are not rollback-capable state mutations. This file
 is the delivery model; [`AUTHORITY.md`](AUTHORITY.md#external-effects) is the load-bearing
 statement of why, and [`INTEGRATIONS.md`](INTEGRATIONS.md) is the operation vocabulary this
 builds on.

package/docs/EVENTS.md

@@ -1,6 +1,6 @@
 # Events
 
-Axiom 0.14.0-alpha.2. An event is a typed fact — something that happened — never work
+Axiom 0.14.0-alpha.3. An event is a typed fact — something that happened — never work
 itself. [`AUTHORITY.md`](AUTHORITY.md#external-events) is the load-bearing statement;
 this file is the vocabulary and the webhook delivery mechanism. A **subscription** is the
 other way an external fact becomes an `EventDef` payload — see

package/docs/EXPRESSIONS.md

@@ -1,6 +1,6 @@
 # Expressions
 
-Axiom 0.14.0-alpha.2. An expression describes **what value is computed**. It is a tree of
+Axiom 0.14.0-alpha.3. An expression describes **what value is computed**. It is a tree of
 plain data, never source text and never a callback. Evaluation is pure: an expression MUST
 NOT change state.
 

package/docs/GRAPH_MODEL.md

@@ -1,6 +1,6 @@
 # Graph model
 
-Axiom 0.14.0-alpha.2. The `ApplicationGraph` is the authoritative representation of an
+Axiom 0.14.0-alpha.3. The `ApplicationGraph` is the authoritative representation of an
 application. Everything else — the IR, the page, the DOM — is derived from it and is never
 edited.
 

package/docs/INTEGRATIONS.md

@@ -1,6 +1,6 @@
 # Integrations
 
-Axiom 0.14.0-alpha.2. How an application declares and calls an external system, without
+Axiom 0.14.0-alpha.3. How an application declares and calls an external system, without
 embedding a transport, an SDK or a secret in the graph. The authority boundary this
 depends on is [`AUTHORITY.md`](AUTHORITY.md#external-systems); this file is the vocabulary.
 

package/docs/LIVE_QUERIES.md

@@ -1,6 +1,6 @@
 # Realtime — live canonical queries
 
-Axiom 0.14.0-alpha.2. The operational contract for **observing a `QueryDef` result over
+Axiom 0.14.0-alpha.3. The operational contract for **observing a `QueryDef` result over
 time**: subscribe once, receive an initial coherent result, then receive canonical changes
 as authoritative committed state moves — through any compatible authority, across
 reconnects. `axiom.server.v7` (0.13 adds no IR vocabulary).

package/docs/LOCATIONS.md

@@ -1,6 +1,6 @@
 # Locations
 
-Axiom 0.14.0-alpha.2.
+Axiom 0.14.0-alpha.3.
 
 ```text
 Expression = a value

package/docs/MIGRATIONS.md

@@ -1,6 +1,6 @@
 # Schema evolution & semantic migrations
 
-Axiom 0.14.0-alpha.2. The operational contract for evolving a deployed application's
+Axiom 0.14.0-alpha.3. The operational contract for evolving a deployed application's
 semantic model and its persisted canonical data over time — adding a required field,
 splitting one field into two, removing an obsolete one, migrating millions of
 provider-backed rows — **without** an application-authored SQL migration, an ORM migration,

package/docs/PRESENTATION.md

@@ -1,6 +1,6 @@
 # Presentation
 
-Axiom 0.14.0-alpha.2. Presentation is **semantic UX intent**, expressed as data on a UI
+Axiom 0.14.0-alpha.3. Presentation is **semantic UX intent**, expressed as data on a UI
 node. It names roles, tokens and device classes. It never names a colour, a length, a media
 query or a CSS property.
 

package/docs/QUERIES.md

@@ -1,6 +1,6 @@
 # Semantic data access & the query layer
 
-Axiom 0.14.0-alpha.2. The operational contract for demand-driven reads over authoritative
+Axiom 0.14.0-alpha.3. The operational contract for demand-driven reads over authoritative
 data that is too large to materialize as a `StateDef` — 500,000 orders, 5,000,000 order
 lines, years of audit rows. `axiom.server.v6`.
 

package/docs/RUNTIME.md

@@ -1,6 +1,6 @@
 # Runtime
 
-Axiom 0.14.0-alpha.2. The runtime executes an `ApplicationIR`. It is domain-independent: it
+Axiom 0.14.0-alpha.3. The runtime executes an `ApplicationIR`. It is domain-independent: it
 contains no knowledge of any application.
 
 ## Constructing

package/docs/SEMANTIC_CONTRACT.md

@@ -1,6 +1,6 @@
 # Semantic contract
 
-Axiom 0.14.0-alpha.2. Runtime guarantees, stated formally. This file defines behavior; it
+Axiom 0.14.0-alpha.3. Runtime guarantees, stated formally. This file defines behavior; it
 does not teach. Where this file and any specification in `../specs/` disagree, this file
 describes the implementation and is authoritative.
 

package/docs/STATE.md

@@ -1,6 +1,6 @@
 # State
 
-Axiom 0.14.0-alpha.2. A `StateDef` is a named application value: stored, or computed from
+Axiom 0.14.0-alpha.3. A `StateDef` is a named application value: stored, or computed from
 other state.
 
 ```ts

package/docs/STORAGE.md

@@ -1,6 +1,6 @@
 # Storage and blobs
 
-Axiom 0.14.0-alpha.2. How an application stores, references, serves and deletes binary data —
+Axiom 0.14.0-alpha.3. How an application stores, references, serves and deletes binary data —
 an attachment, a document, a photograph, a diagnostic log — with no filesystem path, no
 upload route and no download route anywhere in it.
 

package/docs/SUBSCRIPTIONS.md

@@ -1,6 +1,6 @@
 # Subscriptions
 
-Axiom 0.14.0-alpha.2. How an application receives a stream of external events — an MQTT
+Axiom 0.14.0-alpha.3. How an application receives a stream of external events — an MQTT
 topic, a WebSocket feed, a queue consumer, a filesystem watcher, a serial port — without a
 client, a socket or a callback anywhere in the graph.
 

package/docs/TRIGGERS.md

@@ -1,6 +1,6 @@
 # Triggers
 
-Axiom 0.14.0-alpha.2. A `TriggerDef` says **when** an action should be invoked, without
+Axiom 0.14.0-alpha.3. A `TriggerDef` says **when** an action should be invoked, without
 embedding callback code. `docs/AUTHORITY.md`
 [§ Triggers](AUTHORITY.md#triggers) is the load-bearing statement of the execution model;
 this file is the vocabulary.

package/docs/UI.md

@@ -1,6 +1,6 @@
 # UI
 
-Axiom 0.14.0-alpha.2. Eleven semantic UI node kinds describe **what exists and what it does**.
+Axiom 0.14.0-alpha.3. Eleven semantic UI node kinds describe **what exists and what it does**.
 How it looks is [presentation](PRESENTATION.md).
 
 All eleven share `UIBase`:

package/docs/VALIDATION.md

@@ -1,6 +1,6 @@
 # Validation
 
-Axiom 0.14.0-alpha.2. Validation is authoring-time structural checking. It is not the same
+Axiom 0.14.0-alpha.3. Validation is authoring-time structural checking. It is not the same
 as runtime constraint evaluation — see [`CONSTRAINTS.md`](CONSTRAINTS.md) for the four
 layers of correctness.
 
@@ -197,6 +197,20 @@ connect schema 1 to it. A migration transform reads the old record through the r
 to `axiom.server.v8` or executed. Every failure is a structured diagnostic — never a thrown
 `TypeError` on a malformed step.
 
+**Totality (spec14pt4).** Every public surface that inspects, validates, compiles, admits or
+executes a `WorkflowDef` is total over *malformed* input: `validateGraph`,
+`compileToServerIR`, `AgentAPI.validate` and `AgentAPI.analyzeWorkflow` all produce a
+structured diagnostic (or a structured `Error`, for `analyzeWorkflow`) — never a native
+`TypeError` — for a `null` / non-object step, a `steps` / `inputs` / `bindings` that is not
+an array, or an unknown step kind. A hand-tampered Server IR (a stored / transported IR that
+never passed `validateGraph`) is rejected at **admission** — `createAxiomServer` /
+`createWorkflowEngine` throw `WorkflowIRError` (`WORKFLOW_INVALID_IR`) — for the same
+malformed container shapes and for broken references: a `bind` to an undeclared
+`WorkflowBinding`, a `WorkflowBinding.producedBy` that is not a step, an expression `ref`
+outside the closed workflow scope, or a `now`/`uuid`/`random` call. Unknown binding /
+reference semantics are **invalid**, never silently dropped, and can never produce a
+permanently `running` workflow.
+
 | Code | Raised when |
 | --- | --- |
 | `WORKFLOW_ENTRY_NOT_FOUND` | `WorkflowDef.entry` does not name a step of that workflow. |

package/docs/WORKFLOWS.md

@@ -1,6 +1,6 @@
 # Durable workflows
 
-Axiom 0.14.0-alpha.2. The operational contract for **long-running semantic computations with
+Axiom 0.14.0-alpha.3. The operational contract for **long-running semantic computations with
 a durable control position** — orchestration that survives process death, authority
 failover, retries, timer delivery, event delivery and ordinary distributed contention
 without application-owned infrastructure. `axiom.server.v8`.
@@ -246,7 +246,7 @@ step's argument expressions / `retry` policy, a `wait-event` step's `where` / `b
   or binding migration, and none is inferred ("closest step" recovery never happens).
 - A graph with **no** `WorkflowDef` compiles to the byte-identical `axiom.server.v1`–`v7`
   document it always did, and its `semanticFingerprint` / `schemaFingerprint` are unchanged.
-- Pre-`0.14.0-alpha.2` instances carry a compatibility key computed before `WorkflowDef`
+- Pre-`0.14.0-alpha.3` instances carry a compatibility key computed before `WorkflowDef`
   participated; a corrected authority treats them as incompatible and fails closed (these
   are pre-freeze alpha releases — silent reinterpretation is the only unacceptable
   outcome).

package/llms.txt

@@ -1,6 +1,6 @@
 # Axiom
 
-> AI-native semantic application framework, version 0.14.0-alpha.2. An Axiom application is a
+> AI-native semantic application framework, version 0.14.0-alpha.3. An Axiom application is a
 > typed semantic graph — state, behavior, constraints, UI structure, presentation and
 > authority as structured data — executed by generic runtimes. The JavaScript, HTML and CSS
 > that reach a browser are compiler output and are never authored or edited. The primary

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cynodia/axiom",
-  "version": "0.14.0-alpha.2",
+  "version": "0.14.0-alpha.3",
   "description": "AI-native semantic web application framework.",
   "license": "MIT",
   "author": "AskTech AS",
@@ -34,10 +34,10 @@
     }
   },
   "dependencies": {
-    "@cynodia/axiom-core": "0.14.0-alpha.2",
-    "@cynodia/axiom-runtime": "0.14.0-alpha.2",
-    "@cynodia/axiom-compiler": "0.14.0-alpha.2",
-    "@cynodia/axiom-agent-api": "0.14.0-alpha.2"
+    "@cynodia/axiom-core": "0.14.0-alpha.3",
+    "@cynodia/axiom-runtime": "0.14.0-alpha.3",
+    "@cynodia/axiom-compiler": "0.14.0-alpha.3",
+    "@cynodia/axiom-agent-api": "0.14.0-alpha.3"
   },
   "scripts": {
     "build": "tsc -b tsconfig.json"