@cynodia/axiom 0.15.0-alpha.2 → 0.15.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.15.0-alpha.2`.
+documentation in `docs/` describes this exact version, `0.15.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.15.0-alpha.2`.
+`npm install @cynodia/axiom@0.15.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.15.0-alpha.2. An action is behavior expressed as data, executed as a transaction.
+Axiom 0.15.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.15.0-alpha.2. The machine-facing interface. Agents query semantics and apply
+Axiom 0.15.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.15.0-alpha.2. Compressed operational contract. Read this plus the `.d.ts`
+Axiom 0.15.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:
@@ -1263,12 +1263,16 @@ reference is now enforced; `AUTHORIZATION_ENFORCEMENT_UNAVAILABLE` /
 One authorization language. An `AuthorizationPolicyDef` (graph node kind
 `authorization-policy`) is a single boolean `allow` `Expression`. Exactly `true` ⇒ ALLOW;
 `false`, an absent policy, or **any** evaluation error ⇒ DENY (fail closed). **A missing
-PRINCIPAL / RESOURCE field never satisfies a rule** (spec15pt2): the policy evaluator is
+PRINCIPAL / RESOURCE field never satisfies a rule** (spec15pt2 for policies; spec15pt3 for
+the legacy `ActionDef.authorization` expression — one canonical
+`evaluateAuthorizationExpression`, so both surfaces behave the same): the evaluator is
 three-valued (concrete / security-absence / error), so `PRINCIPAL.role != "banned"`,
 `NOT(PRINCIPAL.role == "banned")` and `RESOURCE.ownerId == PRINCIPAL.id` all DENY when the
-named field is absent or the caller is anonymous — `neq` / `not` / `or` cannot turn absence
-into authority. `literal(true)` stays a genuine constant (explicit public still admits
-anonymous). Ordinary `Expression` semantics elsewhere are unchanged. Closed
+named field is absent or the caller is anonymous — `neq` / `not` / `or` / comparison cannot
+turn absence into authority, and an error keeps its provenance through `not`. **Yes,
+`ActionDef.authorization` fails closed if a referenced principal attribute is missing.**
+`literal(true)` stays a genuine constant (explicit public still admits anonymous). Ordinary
+`Expression` semantics elsewhere are unchanged. Closed
 expression scope — the three reserved ids exported from core: `ref(PRINCIPAL)`
 (`'axiom_principal'`, the id `ActionDef.authorization` already uses), `ref(RESOURCE)`
 (`'axiom_resource'` — for `action.invoke`, a `{ id, kind }` descriptor), `ref(OPERATION)`
@@ -1290,6 +1294,13 @@ document it always did. Totality: every validate/compile/analyze surface is tota
 `null` / non-object policy / non-plain `allow` — structured diagnostic, never a native
 `TypeError`.
 
+Runtime evaluator version is authority-compatibility identity, **not** graph identity. The
+`AuthorityCompatibilityKey` carries an `authorizationRuntime` discriminator (`axiom.authz.v3`
+in this build) whenever the IR carries an authorization *decision* — an `AuthorizationPolicyDef`
+reference **or** a legacy `ActionDef.authorization` expression. A cluster mixing evaluator
+versions (`alpha.2` ↔ `alpha.3`) over such a graph is fail-closed incompatible;
+`semanticFingerprint` is unchanged.
+
 Static analysis: `AgentAPI.analyzeAuthorization()` → what protects every action / query /
 workflow surface, per-policy dependencies + a secret-free rule `summary`, the `unprotected`
 list (surfaces with no explicit boundary), and per-workflow `privilegeReviewActions`

package/docs/ANTI_PATTERNS.md

@@ -1,6 +1,6 @@
 # Anti-patterns
 
-Axiom 0.15.0-alpha.2. Each of these compiles. Each is wrong. Each is followed by the correct
+Axiom 0.15.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.15.0-alpha.2. How an application crosses the trust boundary.
+Axiom 0.15.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/AUTHORIZATION.md

@@ -1,6 +1,6 @@
 # Authorization
 
-Axiom 0.15.0-alpha.2. The operational contract for **authorization completeness** — the 0.15
+Axiom 0.15.0-alpha.3. 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`
@@ -11,12 +11,16 @@ prior contract.
 > outside portable application semantics. **Authorization** answers *may this principal
 > perform this semantic operation?* — that is what this document defines.
 
-0.15 landed in nine phases (A–I); `0.15.0-alpha.2` (spec15pt2) is a corrective pass —
-authorization **absent-value safety** (a missing PRINCIPAL / RESOURCE field never grants
-authority), `validateGraph` totality over a malformed `allow` tree, and a fail-closed
-`host.authenticate` exception boundary. This document describes the **model** (stable) and
-marks which phase delivered each surface. External adversarial validation precedes the
-semantic freeze (spec15 §134).
+0.15 landed in nine phases (A–I); `0.15.0-alpha.2` (spec15pt2) and `0.15.0-alpha.3`
+(spec15pt3) are corrective passes. **spec15pt2**: authorization **absent-value safety** (a
+missing PRINCIPAL / RESOURCE field never grants authority), `validateGraph` totality over a
+malformed `allow` tree, a fail-closed `host.authenticate` exception boundary. **spec15pt3**:
+the same fail-closed absent-value semantics now also cover the **legacy
+`ActionDef.authorization` expression** (F1-legacy) — one canonical evaluator for every
+authorization expression, so `PRINCIPAL.role != "banned"` / `NOT(PRINCIPAL.role == "banned")`
+no longer allow an anonymous or attribute-less caller through that surface either. This
+document describes the **model** (stable) and marks which phase delivered each surface.
+External adversarial validation precedes the semantic freeze (spec15 §134).
 
 | Phase | Delivers | State |
 | --- | --- | --- |
@@ -70,16 +74,30 @@ graph.addNode<AuthorizationPolicyDef>({
 - **ALLOW / DENY, fail closed.** `allow` evaluating to exactly `true` is **ALLOW**. `false`,
   an absent policy field, or *any evaluation error* is **DENY** — the safe direction for a
   failed access check is always refusal (spec15 §8, §123).
-- **A missing PRINCIPAL / RESOURCE field never satisfies a rule** (spec15pt2 F1). The policy
-  evaluator is three-valued — a concrete value, **security-scope absence** (a field the
-  scope object does not carry), or an evaluation error. A comparison, `not`, `neq` or `or`
+- **A missing PRINCIPAL / RESOURCE field never satisfies a rule** (spec15pt2 F1,
+  spec15pt3 F1-legacy). The authorization-expression evaluator is three-valued — a concrete
+  value, **security-scope absence** (a field the scope object does not carry), or an
+  evaluation error. A comparison, `not`, `neq`, `lt`, `contains`, `or` or any composition
   whose truth would depend on absence is *not satisfied*, so `PRINCIPAL.role != "banned"` /
   `NOT(PRINCIPAL.role == "banned")` / `RESOURCE.ownerId == PRINCIPAL.id` all **DENY** when
-  the named field is absent or the caller is anonymous. This is authorization-evaluation
-  semantics only; ordinary `Expression` equality/nullish behaviour elsewhere is unchanged
-  (spec15pt2 §4). An `OR` branch that is *concretely* true still allows even if the other
-  branch is absent-dependent. `literal(true)` is a genuine constant — an explicitly public
-  policy still admits an anonymous caller.
+  the named field is absent or the caller is anonymous. An evaluation error keeps its
+  provenance through `not` / `or`, so it can never be negated back to ALLOW. This is
+  authorization-evaluation semantics only; ordinary `Expression` equality / nullish behaviour
+  elsewhere is unchanged (spec15pt2 §4, spec15pt3 §6, §31). An `OR` branch that is
+  *concretely* true still allows even if the other branch is absent-dependent. `literal(true)`
+  is a genuine constant — an explicitly public rule still admits an anonymous caller; the
+  invariant is "missing referenced security fields cannot create authority", **not**
+  "anonymous is forbidden" (spec15pt3 §17).
+- **This applies to both authorization expressions Axiom supports** (spec15pt3 §74, §128):
+  the modern `AuthorizationPolicyDef.allow` **and** the retained legacy
+  `ActionDef.authorization` boolean expression. They share one canonical security-absence
+  primitive (`evaluateAuthorizationExpression`); they differ only in the *final*
+  interpretation applied downstream — a policy allows on exactly `true`, legacy keeps its
+  historical truthiness — never in how absence, boolean composition or errors propagate. So
+  yes: `ActionDef.authorization` **fails closed if a referenced principal attribute is
+  missing.** The legacy expression's historical scope (which could also read an ordinary
+  `StateDef`) is preserved; an unresolvable ref fails closed exactly as a throwing evaluation
+  did before.
 - **Referenced by id.** A protected surface points at a policy:
   - `ActionDef.authorizationPolicy` — `action.invoke`
   - `QueryDef.authorizationPolicy` — `query.read` (distinct from `readPolicyId`, which
@@ -134,13 +152,18 @@ architecture, preserved). Therefore:
 A graph with **no** authorization vocabulary compiles to the byte-identical v1–v8 document
 it always did and its fingerprint is unchanged (spec15 §39, §132).
 
-**Evaluator version.** `0.15.0-alpha.1` and `0.15.0-alpha.2` evaluate the *same* policy
-differently (absent-value safety, spec15pt2 F1), yet the graph — and its
-`semanticFingerprint` — is identical. So the `AuthorityCompatibilityKey` carries an
-`authorizationRuntime` discriminator, present only when the IR uses authorization
-vocabulary: a mixed `alpha.1` / `alpha.2` cluster over an authorization-bearing graph is
-fail-closed **incompatible** (spec15pt2 §35), while a graph with no policy rolls the
-upgrade unaffected.
+**Evaluator version.** Successive builds evaluate the *same* authorization expression
+differently — `alpha.1` → `alpha.2` for policies (spec15pt2 F1), `alpha.2` → `alpha.3` for
+the legacy `ActionDef.authorization` expression (spec15pt3 F1-legacy) — yet the graph, and
+its `semanticFingerprint`, is identical (runtime evaluator version is
+authority-compatibility identity, not graph identity). So the `AuthorityCompatibilityKey`
+carries an `authorizationRuntime` discriminator (`alpha.2` = `axiom.authz.v2`, `alpha.3` =
+`axiom.authz.v3`), present whenever the IR carries an authorization *decision* — an
+`AuthorizationPolicyDef` reference **or** a legacy `ActionDef.authorization` expression. A
+mixed cluster across evaluator versions, over any such graph, is fail-closed
+**incompatible** (present-vs-absent and any string difference are both mismatches;
+spec15pt2 §35, spec15pt3 §37-§42). A graph with **no** authorization decision never carries
+the field and rolls every upgrade unaffected.
 
 ---
 
@@ -153,7 +176,7 @@ effect retry) reconstructs it from durable identity, never a process-local objec
 
 | Operation | Kind | Resource | Effective principal | Pre-0.15 behaviour | 0.15 target |
 | --- | --- | --- | --- | --- | --- |
-| `handle({kind:'invoke'})` / `ActionDef` | execute | `ActionDef` (`{id,kind}`) | caller credential | `ActionDef.authorization` expr, or public | **C ✅** — `action.invoke` policy ∧ legacy expr, re-evaluated on every invocation against current policy |
+| `handle({kind:'invoke'})` / `ActionDef` | execute | `ActionDef` (`{id,kind}`) | caller credential | `ActionDef.authorization` expr, or public | **C ✅** — `action.invoke` policy ∧ legacy expr (both through the one security-absence-aware evaluator, spec15pt3), re-evaluated on every invocation against current policy |
 | workflow `action` step | execute | `ActionDef` | **workflow's start principal** | inherits action's `authorization`, re-evaluated per step (0.14) | **C ✅** — same `authorize()` as a direct call; workflow start never amplifies privilege (§101); denial is terminal not retried (§109) |
 | trigger / scheduler / event → action | execute | `ActionDef` | semantic object that scheduled it (no ambient SYSTEM) | `source: 'system'`, `invocation.allowedSources` | **C ✅** — policy under the canonical effective principal; `'system'` source is not privilege (§26, §102) |
 | `handle({kind:'query'})` / `QueryDef` | read | `QueryDef` | caller credential | `ReadPolicyDef` row filter, or public | **D ✅** — `query.read` policy gates the whole query before any provider call; `ReadPolicyDef` still filters rows, AND-ed into the effective filter so `filter`/`sort`/`limit`/aggregate see the authorized dataset (§18, §81, §82) |
@@ -186,7 +209,9 @@ stream serves no further data. Its `details` carry the canonical `operation`, a
 machine `reason` —
 `policy-denied` (the policy is not exactly `true`), `policy-error` (the policy threw — an
 evaluation error is DENY, never ALLOW, spec15 §123), `legacy-denied` / `legacy-error` (the
-legacy `authorization` expression), or (for workflow instance ops with no policy declared)
+legacy `ActionDef.authorization` expression — `legacy-denied` covers the spec15pt3 case
+where the decision depended on a missing security-scope field), or (for workflow instance
+ops with no policy declared)
 `owner-mismatch`, or (spec15pt2 F3, when `host.authenticate` itself threw)
 `authentication-error` with `operation: 'authentication'` — plus `actionId` / `queryId`
 where applicable. A denied `query` operation

package/docs/CONSTRAINTS.md

@@ -1,6 +1,6 @@
 # Constraints
 
-Axiom 0.15.0-alpha.2. Two constructs, answering different questions. They are not
+Axiom 0.15.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.15.0-alpha.2`.*
+*This document describes Axiom `0.15.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.15.0-alpha.2. External effects are not rollback-capable state mutations. This file
+Axiom 0.15.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.15.0-alpha.2. An event is a typed fact — something that happened — never work
+Axiom 0.15.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.15.0-alpha.2. An expression describes **what value is computed**. It is a tree of
+Axiom 0.15.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.
 
@@ -103,13 +103,16 @@ object([
 - `not` → `!truthy(operand)`.
 - `negate` → `-Number(operand ?? 0)`.
 
-> **Authorization policies evaluate differently for a missing security field.** An
-> `AuthorizationPolicyDef.allow` expression is run by a dedicated three-valued evaluator: a
-> `field(ref(PRINCIPAL) | ref(RESOURCE), F)` read of a field the scope object does not
-> carry is **security-scope absence**, not an ordinary `undefined`. A comparison, `not`,
-> `neq` or `or` whose truth would depend on absence is *not satisfied*, so the policy
-> DENIES (spec15pt2 F1). This is scoped to `allow` evaluation — the general expression
-> semantics above are unchanged everywhere else, including in `ActionDef.authorization`.
+> **An expression evaluated as an authorization decision evaluates differently for a
+> missing security field.** Both `AuthorizationPolicyDef.allow` **and** the legacy
+> `ActionDef.authorization` expression are run by one dedicated three-valued evaluator
+> (`evaluateAuthorizationExpression`): a `field(ref(PRINCIPAL) | ref(RESOURCE), F)` read of a
+> field the scope object does not carry is **security-scope absence**, not an ordinary
+> `undefined`. A comparison, `not`, `neq`, `or` or any composition whose truth would depend
+> on absence is *not satisfied*, so the decision DENIES (spec15pt2 F1, spec15pt3 F1-legacy).
+> This is scoped to authorization evaluation only — the general expression semantics above
+> are unchanged everywhere else, and unchanged for the *ordinary* (non-authorization)
+> evaluation of any expression.
 
 ### `call(fn, ...args)`
 

package/docs/GRAPH_MODEL.md

@@ -1,6 +1,6 @@
 # Graph model
 
-Axiom 0.15.0-alpha.2. The `ApplicationGraph` is the authoritative representation of an
+Axiom 0.15.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.15.0-alpha.2. How an application declares and calls an external system, without
+Axiom 0.15.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.15.0-alpha.2. The operational contract for **observing a `QueryDef` result over
+Axiom 0.15.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.15.0-alpha.2.
+Axiom 0.15.0-alpha.3.
 
 ```text
 Expression = a value

package/docs/MIGRATIONS.md

@@ -1,6 +1,6 @@
 # Schema evolution & semantic migrations
 
-Axiom 0.15.0-alpha.2. The operational contract for evolving a deployed application's
+Axiom 0.15.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.15.0-alpha.2. Presentation is **semantic UX intent**, expressed as data on a UI
+Axiom 0.15.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.15.0-alpha.2. The operational contract for demand-driven reads over authoritative
+Axiom 0.15.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.15.0-alpha.2. The runtime executes an `ApplicationIR`. It is domain-independent: it
+Axiom 0.15.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.15.0-alpha.2. Runtime guarantees, stated formally. This file defines behavior; it
+Axiom 0.15.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.15.0-alpha.2. A `StateDef` is a named application value: stored, or computed from
+Axiom 0.15.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.15.0-alpha.2. How an application stores, references, serves and deletes binary data —
+Axiom 0.15.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.15.0-alpha.2. How an application receives a stream of external events — an MQTT
+Axiom 0.15.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.15.0-alpha.2. A `TriggerDef` says **when** an action should be invoked, without
+Axiom 0.15.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.15.0-alpha.2. Eleven semantic UI node kinds describe **what exists and what it does**.
+Axiom 0.15.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.15.0-alpha.2. Validation is authoring-time structural checking. It is not the same
+Axiom 0.15.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.
 

package/docs/WORKFLOWS.md

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