@cynodia/axiom 0.16.0-alpha.1 → 0.16.0-alpha.2

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.1`.
+documentation in `docs/` describes this exact version, `0.16.0-alpha.2`.
 
 ## Installation
 
@@ -47,10 +47,12 @@ 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.1`.
+`npm install @cynodia/axiom@0.16.0-alpha.2`.
 
-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
+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
+— `explain` / `analyze` / `diff` over `AgentAPI`, plus `inspect` / `validate` / `build` /
+`serve` — see that package's README. `@cynodia/axiom-server`'s SQLite persistence adapter additionally
 needs a Node build that provides `node:sqlite` (Node 22 or newer); `isSqliteAvailable()`
 reports its absence rather than failing at import.
 

package/docs/ACTIONS_TRANSACTIONS.md

@@ -1,6 +1,6 @@
 # Actions and transactions
 
-Axiom 0.16.0-alpha.1. An action is behavior expressed as data, executed as a transaction.
+Axiom 0.16.0-alpha.2. 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.16.0-alpha.1. The machine-facing interface. Agents query semantics and apply
+Axiom 0.16.0-alpha.2. The machine-facing interface. Agents query semantics and apply
 structural transformations; they never edit generated code.
 
 ```ts
@@ -31,6 +31,15 @@ agent.referencedBy(expression)         // ids an expression references
 Edge kinds: `contains` `reads` `writes` `invokes` `renders` `binds` `depends-on`
 `derives-from` `constrains` `routes-to` `references`.
 
+`getDependencies`/`getDependents` return **dependency edges resolved to nodes, not a
+deduplicated node set**: if two distinct edges of the requested kinds connect the same pair
+of nodes — an action that both reads and writes the same state, with no `kinds` filter
+narrowing it to one — the target node appears once per edge (spec16pt2 §112, intentional:
+provenance would otherwise be lost). De-duplicate by `id` where a unique node set is what
+you actually want. `getTransitiveDependencies`/`Dependents` (spec16) are the exception —
+they return a deduplicated id set by construction, since "reachable at all" is what a
+transitive closure answers.
+
 ## Dependency queries
 
 ```ts

package/docs/AGENT_REFERENCE.md

@@ -1,6 +1,6 @@
 # Agent reference
 
-Axiom 0.16.0-alpha.1. Compressed operational contract. Read this plus the `.d.ts`
+Axiom 0.16.0-alpha.2. 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:
@@ -663,9 +663,9 @@ await serveAxiomApplication({
 ```
 
 `GET /` is the page, `POST /axiom` the semantic endpoint. No route, controller, handler, SQL
-or client JavaScript is authored. **There is no published Axiom CLI.** The halves also run
-separately: `serveOverHttp({ server, port })` is the bare authority, and
-`createDirectTransport(server)` drives one in-process for tests.
+or client JavaScript is authored. `@cynodia/axiom-cli`'s `axiom serve` runs this same path
+ad hoc. The halves also run separately: `serveOverHttp({ server, port })` is the bare
+authority, and `createDirectTransport(server)` drives one in-process for tests.
 
 A remote invocation returns `{ ok: false, pending: true }` and its outcome arrives later,
 through the same action-outcome lifecycle a local refusal uses — so a `diagnostic` node
@@ -949,12 +949,12 @@ Providers: `createMemoryRowStore` + `createMemoryMigrationStore` (deterministic
 `runMigrationConformanceFixture` over the `axiom.conformance.v5` fixtures in
 `conformance/migrations/`.
 
-There is **no published Axiom CLI**. Every schema/migration operation is a public library
-function — `inspectSchema`, `diffSchema`, `explainSchemaDiff`, `migrationImpact` (from
+Every schema/migration operation is also a public library function —
+`inspectSchema`, `diffSchema`, `explainSchemaDiff`, `migrationImpact` (from
 `@cynodia/axiom-agent-api`); `planMigration`, `explainMigration`, `executeMigration`,
-`getMigrationStatus` (from `@cynodia/axiom-server`). A host builds its own command around
-them. (The Axiom repository has a private, unpublished CLI over the same functions for
-maintainer use.)
+`getMigrationStatus` (from `@cynodia/axiom-server`) — for a host that builds its own
+command around them. `@cynodia/axiom-cli` publishes `axiom schema status` / `schema diff` /
+`migrate plan` / `migrate` / `migrate status` over the same functions.
 
 Diagnostics: `SCHEMA_MIGRATION_REQUIRED` `SCHEMA_INCOMPATIBLE` `MIGRATION_IN_PROGRESS`
 `MIGRATION_STATE_CORRUPTED` `MIGRATION_PATH_NOT_FOUND` `MIGRATION_APPROVAL_REQUIRED`

package/docs/ANTI_PATTERNS.md

@@ -1,6 +1,6 @@
 # Anti-patterns
 
-Axiom 0.16.0-alpha.1. Each of these compiles. Each is wrong. Each is followed by the correct
+Axiom 0.16.0-alpha.2. 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.1. How an application crosses the trust boundary.
+Axiom 0.16.0-alpha.2. 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
@@ -596,8 +596,8 @@ The two halves also run separately. `serveOverHttp({ server, port })` is the bar
 and `createAxiomServer({ ir, persistence, host })` is the authority with no transport at all —
 which is what `createDirectTransport` drives in tests.
 
-**There is no published Axiom CLI.** `packages/cli` is a private development tool of this
-repository and is not on npm; the API above is the supported way to run an application.
+`@cynodia/axiom-cli` publishes an `axiom serve` command over this same API for ad hoc use;
+the API above remains the supported way to run an application from your own Node process.
 
 ## Conformance
 

package/docs/AUTHORIZATION.md

@@ -1,6 +1,6 @@
 # Authorization
 
-Axiom 0.16.0-alpha.1. The operational contract for **authorization completeness** — the 0.15
+Axiom 0.16.0-alpha.2. 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.1. Two constructs, answering different questions. They are not
+Axiom 0.16.0-alpha.2. 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.1`.*
+*This document describes Axiom `0.16.0-alpha.2`.*
 
 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.1. External effects are not rollback-capable state mutations. This file
+Axiom 0.16.0-alpha.2. 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.1. An event is a typed fact — something that happened — never work
+Axiom 0.16.0-alpha.2. 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.1. An expression describes **what value is computed**. It is a tree of
+Axiom 0.16.0-alpha.2. 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.1. The `ApplicationGraph` is the authoritative representation of an
+Axiom 0.16.0-alpha.2. 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.1. How an application declares and calls an external system, without
+Axiom 0.16.0-alpha.2. 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.1. The operational contract for **observing a `QueryDef` result over
+Axiom 0.16.0-alpha.2. 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.16.0-alpha.1.
+Axiom 0.16.0-alpha.2.
 
 ```text
 Expression = a value

package/docs/MIGRATIONS.md

@@ -1,6 +1,6 @@
 # Schema evolution & semantic migrations
 
-Axiom 0.16.0-alpha.1. The operational contract for evolving a deployed application's
+Axiom 0.16.0-alpha.2. 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.1. Presentation is **semantic UX intent**, expressed as data on a UI
+Axiom 0.16.0-alpha.2. 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.1. The operational contract for demand-driven reads over authoritative
+Axiom 0.16.0-alpha.2. 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.1. The runtime executes an `ApplicationIR`. It is domain-independent: it
+Axiom 0.16.0-alpha.2. 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.1. Runtime guarantees, stated formally. This file defines behavior; it
+Axiom 0.16.0-alpha.2. 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.16.0-alpha.1. A `StateDef` is a named application value: stored, or computed from
+Axiom 0.16.0-alpha.2. 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.1. How an application stores, references, serves and deletes binary data —
+Axiom 0.16.0-alpha.2. 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.1. How an application receives a stream of external events — an MQTT
+Axiom 0.16.0-alpha.2. 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.1. A `TriggerDef` says **when** an action should be invoked, without
+Axiom 0.16.0-alpha.2. 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.1. Eleven semantic UI node kinds describe **what exists and what it does**.
+Axiom 0.16.0-alpha.2. 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.1. Validation is authoring-time structural checking. It is not the same
+Axiom 0.16.0-alpha.2. 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.
 
@@ -70,7 +70,7 @@ non-numeric collections, and obviously incompatible assignments.
 
 | Code | Raised when |
 | --- | --- |
-| `UNKNOWN_STATE_REF` | A location naming a state that does not exist, or an unknown location kind. |
+| `UNKNOWN_STATE_REF` | A location naming a state that does not exist, an unknown location kind, or a location/selector that is not even a plain object (spec16pt2 F2). |
 | `DERIVED_STATE_WRITE` | A write target rooted in derived state. |
 | `FIELD_ON_NON_ENTITY` | A field selected on a value that has no fields. |
 | `FIELD_NOT_ON_ENTITY` | A field that belongs to a different entity than the one addressed. |
@@ -107,6 +107,15 @@ Recursive, with a `path` naming the position.
 | `UNSUPPORTED_OPERATION` | An operation kind outside `OPERATION_KINDS`, or a `for-each` containing something other than a mutation. |
 | `INVALID_ACTION_REF` | A button or form naming something that is not an action. |
 | `INVALID_STATE_REF` | A reference that must be a state but is not. |
+| `INVALID_OPERATION_COLLECTION` | `ActionDef.operations`, or a `for-each`'s nested `operations`, is present but not an array (spec16pt2 F1). |
+| `INVALID_OPERATION` | An operation array entry that is not a plain object with a recognized `kind` — `null`, a primitive, or a malformed object (spec16pt2 F1/F2). |
+
+A candidate graph can arrive from AI generation, deserialization or hand-tampering, so
+`validateGraph` establishes shape before it ever traverses an action's operations or a
+location — `{}` where `operations` should be an array, or `null` where a `set`/`insert`/
+`remove` target should be a `Location`, is a structured diagnostic (`INVALID_OPERATION_COLLECTION`,
+`INVALID_OPERATION`, or `UNKNOWN_STATE_REF` for a malformed location/selector), never a
+native exception.
 
 ### Constraints
 

package/docs/WORKFLOWS.md

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