@cynodia/axiom 0.16.0-alpha.3 → 0.17.0-alpha.1

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.16.0-alpha.3`.
+documentation in `docs/` describes this exact version, `0.17.0-alpha.1`.
 
 ## 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.16.0-alpha.3`.
+`npm install @cynodia/axiom@0.17.0-alpha.1`.
 
 These are ES modules compiled to ES2022; import them with `import`, not `require`.
 `@cynodia/axiom-cli` (`npm install -g @cynodia/axiom-cli`) publishes the `axiom` executable

package/docs/ACTIONS_TRANSACTIONS.md

@@ -1,6 +1,6 @@
 # Actions and transactions
 
-Axiom 0.16.0-alpha.3. An action is behavior expressed as data, executed as a transaction.
+Axiom 0.17.0-alpha.1. An action is behavior expressed as data, executed as a transaction.
 
 ```ts
 {
@@ -40,6 +40,17 @@ result.diagnostics[0].details  // { preconditionIndex: 2, failureMode: 'insuffic
 
 `actionGuards(action)` returns the conditions however they were written.
 
+**Compilation owns guard lowering, and there is one executable lifecycle.** `guards` is an
+authoring-level representation. `compileToIR` and `compileToServerIR` lower it into aligned
+`preconditions` / `failureModes` preserving meaning and declaration order —
+`meaning(guards) == meaning(lowered preconditions + failureModes)` for every compiled
+action. A runtime — client or authority — evaluates the **normalized** preconditions /
+failure modes; it does **not** also evaluate `guards[]` on top. An authority handed
+serialized Server IR whose guard semantics are not represented in the aligned executable
+form rejects it fail-closed (`SERVER_IR_NOT_NORMALIZED`) rather than lowering at execution
+time or skipping the unmatched check — see
+[Server IR admission](./AUTHORITY.md#server-ir-admission).
+
 ### Guards evaluate in order, and the first failure stops
 
 Declaration order is evaluation order. The first guard that does not hold refuses the

package/docs/AGENT_API.md

@@ -1,6 +1,6 @@
 # Agent API
 
-Axiom 0.16.0-alpha.3. The machine-facing interface. Agents query semantics and apply
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. Compressed operational contract. Read this plus the `.d.ts`
+Axiom 0.17.0-alpha.1. 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:
@@ -285,7 +285,11 @@ Absent `initialValue`, a state starts at the default for its type: `optional`
 
 Prefer `guards: [{ condition, failureMode }]`. The older parallel `preconditions` /
 `failureModes` arrays align **by position** — `failureModes[2]` reports
-`preconditions[2]` — and the compiler normalizes `guards` into them.
+`preconditions[2]` — and the compiler normalizes `guards` into them. Compilation owns that
+lowering: a runtime evaluates the aligned `preconditions` / `failureModes` and does **not**
+also execute `guards[]`. An authority handed serialized Server IR whose guards are not
+represented in the lowered form rejects it fail-closed (`SERVER_IR_NOT_NORMALIZED`) — see
+[`AUTHORITY.md`](AUTHORITY.md#server-ir-admission).
 
 Lifecycle, exactly:
 
@@ -754,6 +758,16 @@ Boundary diagnostics: `UNKNOWN_SERVER_ACTION` `ARGUMENT_TYPE_MISMATCH` `AUTHORIZ
 `AUTHORITY_UNREACHABLE`, plus `SERVER_STATE_WRITE` and `REMOTE_ACTION_UNAVAILABLE` on the
 client.
 
+Serialized Server IR is structurally admitted before any execution (`createAxiomServer`
+throws `ServerIRError`, zero mutation): `SERVER_IR_NOT_OBJECT`,
+`SERVER_IR_INVALID_COLLECTION` (a required collection is not its array/object container),
+`SERVER_IR_INVALID_NODE` (a `null` / primitive where a semantic node or operation belongs —
+a present key does not make an invalid value a node), `SERVER_IR_NOT_NORMALIZED` (guards not
+represented in the lowered `preconditions` / `failureModes`). Total over untrusted input —
+never a native exception. `serverIRStructuralProblems` / `serverIRNormalizationProblems`
+(`@cynodia/axiom-core`) compute the same decision for tooling. `workflows` keep the richer
+`WorkflowIRError` path.
+
 ## SUBSCRIPTIONS AND STORAGE
 
 Full model: [`SUBSCRIPTIONS.md`](SUBSCRIPTIONS.md), [`STORAGE.md`](STORAGE.md). The external

package/docs/ANTI_PATTERNS.md

@@ -1,6 +1,6 @@
 # Anti-patterns
 
-Axiom 0.16.0-alpha.3. Each of these compiles. Each is wrong. Each is followed by the correct
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. How an application crosses the trust boundary.
+Axiom 0.17.0-alpha.1. 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
@@ -40,6 +40,7 @@ describes both halves, so there is no backend to write.
 19. **EVENT** — an event is a typed fact, validated against its declared payload type before any action sees it; an action is where work happens. See [External events](#external-events).
 20. **SECRET** — integration credentials live in host configuration, never in `ApplicationGraph`. See [External systems](#external-systems).
 21. **INVOCATION SOURCE** — a system-originated invocation (trigger, event, effect outcome) and an anonymous client request are distinct authoritative facts; a client cannot forge the former, and an action may restrict which it accepts independently of caller identity. See [Invocation source](#invocation-source).
+22. **ADMISSION** — serialized Server IR is structurally admitted before any semantic execution: a malformed semantic-node entry or a non-normalized guard representation is refused fail-closed with a structured `SERVER_IR_*` diagnostic, never a native exception and never a partial run. See [Server IR admission](#server-ir-admission).
 
 ## Authority and persistence are different questions
 
@@ -151,6 +152,51 @@ document**, computed from the document rather than asserted: see
 
 Guards are normalized into aligned `preconditions` / `failureModes`, exactly as in the
 client IR, so an authority that read one and not the other cannot silently skip a check.
+See [Server IR admission](#server-ir-admission) for the structural and normalization
+requirements an authority enforces before it executes anything.
+
+## Server IR admission
+
+An authority is handed **serialized** Server IR — JSON that a compiler, an agent, a network
+peer or a persisted artifact produced. A TypeScript type is not proof of runtime shape, so
+`createAxiomServer` performs a total structural admission **before any semantic execution**:
+no state is read or written, no provider is touched, no effect is created, no event is
+dispatched, no workflow advances. A malformed document is refused with a thrown
+`ServerIRError` carrying `problems[]` — stable `code` + `path` + `message` — never a native
+`TypeError`, panic or partial start. The codes are `SERVER_IR_ADMISSION_CODES` in
+`@cynodia/axiom-core`, and `serverIRStructuralProblems(ir)` / `serverIRNormalizationProblems(ir)`
+compute them for any tool that needs the same decision without constructing an authority.
+
+### Structural validity
+
+- The document MUST be a JSON object (`SERVER_IR_NOT_OBJECT`).
+- A required collection present but not the container its contract defines — `states`,
+  `entities`, `constraints`, `transitionConstraints`, `observableStateIds` as arrays;
+  `actions`, `fields` as objects — is refused (`SERVER_IR_INVALID_COLLECTION`).
+- Every entry of a semantic-node collection MUST be a JSON object carrying a string `id`. A
+  `null`, a primitive, or an array where a node belongs is refused (`SERVER_IR_INVALID_NODE`)
+  — **a key being present does not make an invalid value a valid node**. This covers the
+  node maps (`actions`, `integrationOperations`, `expressionDefs`), the node arrays
+  (`entities`, `states`, `constraints`, `queries`, `authorizationPolicies`, `readPolicies`,
+  and the rest) and the `operations` array inside an action, at any depth. `workflows` keeps
+  its own richer admission path (`WorkflowIRError` / `WORKFLOW_INVALID_IR`).
+
+### Guard normalization
+
+`ActionDef.guards` is an **authoring-level** representation. Compilation owns lowering it
+into aligned executable `preconditions` / `failureModes`, preserving meaning and declaration
+order: `meaning(guards) == meaning(lowered preconditions + failureModes)` for every
+successfully compiled action. The authority evaluates the **normalized** preconditions /
+failure modes and does **not** independently execute `guards[]` in addition — there is one
+executable action lifecycle, not two.
+
+An authority receiving Server IR in which an action's guard semantics are not represented in
+the aligned executable form — `guards.length` exceeds the lowered `preconditions.length`, or
+`preconditions[i]` is not `guards[i].condition` — MUST reject it fail-closed
+(`SERVER_IR_NOT_NORMALIZED`): no action execution, no mutation, no external effect. It MUST
+NOT lower guards at execution time, drop the unmatched guards, invent a missing failure
+mode, or execute the action while skipping the check. The runtime either executes valid
+normalized semantics or refuses the input.
 
 ## Client IR
 
@@ -470,6 +516,10 @@ does for a local failure.
 | `AUTHORIZATION_DENIED` | The caller may not invoke this action / read this query / start or cancel this workflow, or the rule could not be evaluated. spec15 Phase C covers `ActionDef.authorizationPolicy`, Phase D `QueryDef.authorizationPolicy` (`query.read` — including a live query whose caller is revoked mid-subscription, Phase F, delivered as a live-query error message carrying this code), Phase E `WorkflowDef.startPolicy` / `instanceAccessPolicy` (`workflow.start` / `.cancel`); `details.operation` names the canonical operation and `details.reason` is a non-secret machine reason (`policy-denied` / `policy-error` / `legacy-denied` / `legacy-error` / `owner-mismatch`). A denied `workflow.inspect` / `workflow.history` returns nothing instead (no existence leak). |
 | `CONCURRENCY_CONFLICT` | Another transaction committed the same state first. Nothing was applied. |
 | `MALFORMED_REQUEST` | The request was not an Axiom semantic request, or spoke an unknown protocol. |
+| `SERVER_IR_NOT_OBJECT` | The serialized Server IR handed to `createAxiomServer` is not a JSON object. Thrown as `ServerIRError` at construction, before any semantic execution (spec17 §17). |
+| `SERVER_IR_INVALID_COLLECTION` | A required Server IR collection is present but is not the array / object container its contract defines (e.g. `states` as an object). Refused structurally (spec17 §15, §62). |
+| `SERVER_IR_INVALID_NODE` | An entry of a semantic-node collection — a node map, a node array, or an action's `operations` — is `null`, a primitive or otherwise not a JSON object with a string `id`. A present key does not make an invalid value a valid node (spec17 §16, §80 F1-B). |
+| `SERVER_IR_NOT_NORMALIZED` | An executable action's authoring `guards` are not represented in the aligned, lowered `preconditions` / `failureModes` (`guards.length` exceeds the lowered count, or a lowered precondition does not match its guard's condition). The authority refuses fail-closed rather than execute the action while skipping the unmatched check (spec17 §10-§14, §80 F2). |
 | `AUTHORITY_UNREACHABLE` | The authority could not be reached, timed out, or answered with a transport error. |
 | `EFFECT_FAILED` | An external effect's adapter reported failure after exhausting its retry policy. |
 | `TRIGGER_INVOCATION_FAILED` | A trigger's target action reported failure, or its arguments failed to evaluate. |
@@ -661,6 +711,26 @@ Every fixture is executed against the reference runtime by this repository's own
 and its expectations are exhaustive — a fixture that says which states changed must name all
 of them and no others. No fixture is permitted to disagree with the shipped runtime.
 
+### Runtime-neutral sub-tiers
+
+Later releases add sub-tiers under `conformance/<area>/`, each with its own manifest,
+`conformance` version and reference runner, so a runtime can claim a profile without
+claiming the whole suite:
+
+| Directory | Version | Runner | Covers |
+| --- | --- | --- | --- |
+| `conformance/queries/` | `axiom.conformance.v4` | `runQueryConformanceFixture` | `QueryDef` semantics |
+| `conformance/migrations/` | `axiom.conformance.v5` | `runMigrationConformanceFixture` | schema migrations |
+| `conformance/distributed/` | `axiom.conformance.v6` | `runCoordinationConformanceSuite` | coordination primitives |
+| `conformance/live/` | `axiom.conformance.v7` | `runLiveQueryConformanceFixture` | live queries |
+| `conformance/workflow/` | `axiom.conformance.v8` | `runWorkflowConformanceFixture` | `WorkflowDef` execution |
+| `conformance/authorization/` | `axiom.conformance.v9` | `runAuthorizationConformanceFixture` | authorization decisions |
+| `conformance/normalization/` | `axiom.conformance.v11` | `runNormalizationConformanceFixture` | Server IR structural admission + guard normalization (spec17 §15-§19, §62, §80) |
+
+Each fixture records its **normative provenance** (`semanticRule`) rather than being golden
+against reference-runtime output, so both the reference runtime and an independent runtime
+are tested against the same expectation.
+
 ## Machine-readable contracts
 
 ```

package/docs/AUTHORIZATION.md

@@ -1,6 +1,6 @@
 # Authorization
 
-Axiom 0.16.0-alpha.3. The operational contract for **authorization completeness** — the 0.15
+Axiom 0.17.0-alpha.1. The operational contract for **authorization completeness** — the 0.15
 milestone (spec15). Whether a principal may perform a semantic operation is part of the
 graph's executable meaning — not a runtime concern, not UI visibility, not something that
 varies by transport, provider, process, retry path or authority topology. `axiom.server.v9`

package/docs/CONSTRAINTS.md

@@ -1,6 +1,6 @@
 # Constraints
 
-Axiom 0.16.0-alpha.3. Two constructs, answering different questions. They are not
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3`.*
+*This document describes Axiom `0.17.0-alpha.1`.*
 
 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.16.0-alpha.3. External effects are not rollback-capable state mutations. This file
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. An event is a typed fact — something that happened — never work
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. An expression describes **what value is computed**. It is a tree of
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. The `ApplicationGraph` is the authoritative representation of an
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. How an application declares and calls an external system, without
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. The operational contract for **observing a `QueryDef` result over
+Axiom 0.17.0-alpha.1. 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. 0.13 adds no Server IR vocabulary of its own — current is `axiom.server.v9`.

package/docs/LOCATIONS.md

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

package/docs/MIGRATIONS.md

@@ -1,6 +1,6 @@
 # Schema evolution & semantic migrations
 
-Axiom 0.16.0-alpha.3. The operational contract for evolving a deployed application's
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. Presentation is **semantic UX intent**, expressed as data on a UI
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. The operational contract for demand-driven reads over authoritative
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. The runtime executes an `ApplicationIR`. It is domain-independent: it
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. Runtime guarantees, stated formally. This file defines behavior; it
+Axiom 0.17.0-alpha.1. 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.
 
@@ -204,6 +204,8 @@ Full model: [`AUTHORITY.md`](AUTHORITY.md).
 - `PRINCIPAL` MUST resolve wherever an authority evaluates an expression — authorization, guards, operation values, postconditions and constraints alike — and MUST NOT resolve anywhere a client evaluates.
 - Server IR MUST be serializable, deterministic and free of closures, and MUST declare a contract version a runtime can refuse.
 - `axiom.server.v1` is **frozen**. Its semantics — IEEE-754 binary64 arithmetic, Unicode code-point text ordering, the deterministic host model, and the JSON serialization constraints — are normative and language-independent. An incompatible semantic change requires a new contract identifier.
+- Executable Server IR is **normalized** semantic input. Compilation lowers authoring conveniences into the canonical executable form; an authority evaluates that form and MUST NOT depend on an authoring-only representation the contract defines a normalized form for. `ActionDef.guards` is lowered into aligned `preconditions` / `failureModes` preserving meaning and order, and the authority evaluates the lowered representation only — it does not also execute `guards[]`.
+- A surface that accepts serialized semantic input — deserialized Server IR, a conformance fixture, a persisted or network-provided artifact — MUST perform structural admission before semantic execution, and MUST be **total** over that input: a malformed value inside a semantic-node collection (`null`, a primitive, a non-object), a non-array required collection, a non-object document, or a non-normalized guard representation produces a structured `SERVER_IR_*` diagnostic with zero mutation and zero external effect — never an uncaught host-language exception. A language-level type declaration is not runtime validation. Full model: [`AUTHORITY.md`](AUTHORITY.md#server-ir-admission).
 
 **Not guaranteed in 0.7.0**, and stated so rather than implied: read authorization per caller
 or per record, binding a value generated by one operation in a later one, external side

package/docs/STATE.md

@@ -1,6 +1,6 @@
 # State
 
-Axiom 0.16.0-alpha.3. A `StateDef` is a named application value: stored, or computed from
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. How an application stores, references, serves and deletes binary data —
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. How an application receives a stream of external events — an MQTT
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. A `TriggerDef` says **when** an action should be invoked, without
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. Eleven semantic UI node kinds describe **what exists and what it does**.
+Axiom 0.17.0-alpha.1. 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.16.0-alpha.3. Validation is authoring-time structural checking. It is not the same
+Axiom 0.17.0-alpha.1. 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.
 

package/docs/WORKFLOWS.md

@@ -1,6 +1,6 @@
 # Durable workflows
 
-Axiom 0.16.0-alpha.3. The operational contract for **long-running semantic computations with
+Axiom 0.17.0-alpha.1. 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`.
@@ -255,7 +255,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.16.0-alpha.3` instances carry a compatibility key computed before `WorkflowDef`
+- Pre-`0.17.0-alpha.1` 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.16.0-alpha.3. An Axiom application is a
+> AI-native semantic application framework, version 0.17.0-alpha.1. 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.16.0-alpha.3",
+  "version": "0.17.0-alpha.1",
   "description": "AI-native semantic web application framework.",
   "license": "MIT",
   "author": "AskTech AS",
@@ -34,10 +34,10 @@
     }
   },
   "dependencies": {
-    "@cynodia/axiom-core": "0.16.0-alpha.3",
-    "@cynodia/axiom-runtime": "0.16.0-alpha.3",
-    "@cynodia/axiom-compiler": "0.16.0-alpha.3",
-    "@cynodia/axiom-agent-api": "0.16.0-alpha.3"
+    "@cynodia/axiom-core": "0.17.0-alpha.1",
+    "@cynodia/axiom-runtime": "0.17.0-alpha.1",
+    "@cynodia/axiom-compiler": "0.17.0-alpha.1",
+    "@cynodia/axiom-agent-api": "0.17.0-alpha.1"
   },
   "scripts": {
     "build": "tsc -b tsconfig.json"