The grammar

How the volume is built.

Every endpoint in this API is a view onto one structure: a system described as a sentence, and a coordinate space of ways that sentence can change. This page is the vocabulary; the reference is the calling convention.

Axis one

Five change levels

How far the transformation is allowed to reach. C0 is not a change — it is the baseline you must establish before proposing any of the others.

The five change levels
Code	Level	Definition	Typical operators
`C0`	Baseline	Describe, preserve, measure, or standardize the current system.	Observe, map, maintain, measure.
`C1`	Minor Change	Tune parameters without changing the system’s identity.	Increase, decrease, simplify, speed up.
`C2`	Major Change	Introduce a functionally distinct mechanism while retaining the overall system.	Replace, automate, invert, split, merge.
`C3`	Structural Change	Change relationships, flows, roles, dependencies, or control architecture.	Rewire, redistribute, decentralize, modularize.
`C4`	Paradigm Change	Change assumptions, purpose, category, object, or the definition of value.	Redefine, eliminate, dematerialize, universalize.

Axis two

Ten internal variables

The clauses of the system sentence. Together they say who does what to which object, under what conditions, with what, producing what, and how it breaks.

The ten internal variables
Code	Variable	Question it answers	Grammar role
`I01`	Object	What is being acted upon?	The subject: what is being acted upon.
`I02`	Conditions	Under what circumstances does the system operate?	Contextual clause: when, where, and under what circumstances.
`I03`	Actions	What does the system do?	Verb: what the system does.
`I04`	Tools	What mechanisms carry out the actions?	Instrument: what directly carries out the action.
`I05`	Resources	What information, assets, energy, people, or capital are required?	Inputs: what enables or supplies the action.
`I06`	Outcomes	What does the system produce?	Result clause: what observable state is produced.
`I07`	Feedback	How does the outcome change the system?	Recursive clause: how results alter the next cycle.
`I08`	Constraints	What limits performance or adoption?	Boundary clause: what limits valid operation.
`I09`	Value	For whom is value created, and what kind?	Meaning clause: who benefits and why it matters.
`I10`	Failure mode	How does the system fail at this level?	Break clause: how the sentence becomes invalid.

Axis three

Fourteen meta-variables

How any one clause can vary. The illustrative states are vocabularies for describing a direction of travel — they are not calibrated scales.

The fourteen meta-variables
Code	Meta-variable	Question it answers
`M01`	Magnitude	How much change?
`M02`	Rate	How quickly?
`M03`	Direction	Moving toward what?
`M04`	Scope	How broadly?
`M05`	Depth	How fundamentally?
`M06`	Duration	For how long?
`M07`	Frequency	How often?
`M08`	Acceleration	Is the rate increasing or decreasing?
`M09`	Variability	How consistent or unpredictable?
`M10`	Detectability	How visible or measurable?
`M11`	Reversibility	Can it be undone?
`M12`	Propagation	How does it spread?
`M13`	Amplification	What makes it stronger?
`M14`	Accumulation	How does it build over time?

Reading a coordinate

LAKA-C3-I07-M08

C3 Structural Change × I07 Feedback × M08 Acceleration — “how might the rate of change of the system's feedback loops be restructured?”

The 50-cell grid pairs each change level with each internal variable and names the intent of that pairing. The meta-variable then selects which property of the clause is in play. Fetch any single coordinate from GET /v1/coordinates/{code}.

Grid intents for the C0 and C4 rows
Change level	Internal variable	Intent
`C0` Baseline	`I01` Object	Same object and category
`C0` Baseline	`I02` Conditions	Accept current environment
`C0` Baseline	`I03` Actions	Repeat current action
`C0` Baseline	`I04` Tools	Use current tool
`C0` Baseline	`I05` Resources	Use existing inputs
`C0` Baseline	`I06` Outcomes	Preserve current result and metric
`C0` Baseline	`I07` Feedback	Manual, delayed, or periodic
`C0` Baseline	`I08` Constraints	Treat boundary as fixed
`C0` Baseline	`I09` Value	Same beneficiary and value type
`C0` Baseline	`I10` Failure mode	Observe known failure
`C4` Paradigm Change	`I01` Object	Eliminate the old object or create a new object category
`C4` Paradigm Change	`I02` Conditions	Remove dependence on the condition or redefine the context
`C4` Paradigm Change	`I03` Actions	Eliminate the action or achieve the outcome through different logic
`C4` Paradigm Change	`I04` Tools	Make the tool ambient, invisible, autonomous, or unnecessary
`C4` Paradigm Change	`I05` Resources	Make the system generate its own resource or convert scarcity into abundance
`C4` Paradigm Change	`I06` Outcomes	Redefine the purpose, desired result, or meaning of success
`C4` Paradigm Change	`I07` Feedback	Anticipatory or self-governing feedback that can redefine targets
`C4` Paradigm Change	`I08` Constraints	Reframe the system so the old constraint is no longer relevant
`C4` Paradigm Change	`I09` Value	Establish a new unit, source, exchange, or philosophy of value
`C4` Paradigm Change	`I10` Failure mode	Transform failure into information, resources, adaptation, or another valid state

Showing the C0 and C4 rows. All 50 cells: GET /v1/grid

Operators

17 moves through the volume

Operators are how you get from one coordinate to another. Each one carries a guardrail — the condition under which applying it would be invalid.

Navigation

SHIFT, ROTATE, RECURSE

Move something to another change level.

Transformation

INVERT, TRANSFER, SUBSTITUTE, SPLIT, MERGE

Reverse an assumption, direction, object, action, or outcome.

Relationship

COUPLE, DECOUPLE

Make variables affect each other.

Control

STABILIZE, DESTABILIZE

Preserve or return to a desired state.

Composition

SEQUENCE, PARALLELIZE, COMPOSE

Arrange alternatives into an implementation path.

Comparison

OVERLAY

Compare systems, competitors, users, scenarios, or periods.

Selection

PRUNE

Remove alternatives that violate observable Outcomes.

Full definitions, inputs, outputs and guardrails: GET /v1/operators

Modes

Six ways to read the same volume

The coordinate space does not change; the question you bring to it does.

The six operating modes
Mode	How it reads the volume
`GENERATE`	Produce candidate transformations from unfilled coordinates.
`SOLVE`	Move a specific failing clause to an acceptable state.
`DECODE`	Explain an existing system by locating it in the volume.
`PREDICT`	Project how meta-variables carry a clause forward.
`PLAN`	Sequence transformations into a feasible order.
`POSITION`	Compare your system sentence against alternatives.

Each mode ships a full playbook: GET /v1/modes/{id}