# DigitalStemCell API The LAKA Volumetric Grammar as a REST service. Every GET below is public and needs no key. Corpus version: 1.0-draft OpenAPI: https://api.digitalstemcell.bowtiekreative.com/v1/openapi.json Documentation: https://digitalstemcell.bowtiekreative.com ## What the grammar is Five change levels (C0 Baseline -> C4 Paradigm) x ten internal variables (I01 Object .. I10 Failure mode) x fourteen meta-variables (M01 Magnitude .. M14 Accumulation) = 700 base coordinates. A coordinate is a question slot, not a guaranteed distinct, feasible, novel or valuable innovation. A coordinate id looks like LAKA-C3-I07-M08 = Structural Change x Feedback x Acceleration. ## Endpoints GET /v1/axes The three axes and their vocabularies GET /v1/axes/{axis} One axis: change-levels, internal-variables or meta-variables GET /v1/grid The 50-cell change x internal intent grid GET /v1/coordinates/{code} Resolve a coordinate such as LAKA-C3-I07-M08 GET /v1/prompts Search and page the 700 prompt stems GET /v1/prompts/{id} One prompt stem by coordinate id GET /v1/modes The six operating modes GET /v1/modes/{id} One mode playbook GET /v1/operators The seventeen navigation and transformation operators GET /v1/operators/{name} One operator with guardrail and example GET /v1/core The seven core framework extracts GET /v1/core/{id} One core extract as Markdown GET /v1/templates Run, worksheet, concept card, forecast ledger, positioning GET /v1/templates/{id} One template as Markdown GET /v1/schema/run JSON Schema for a LAKA run GET /v1/schema/blank-run An empty run document to fill in GET /v1/scoring The proposed scoring rubric and hard gates POST /v1/score Compute the comparison index from ratings POST /v1/validate Validate a run document against the schema GET /v1/health Service health ## Typical agent flow 1. GET /v1/modes and pick a mode (GENERATE, SOLVE, DECODE, PREDICT, PLAN, POSITION). 2. GET /v1/templates/run-laka for the master run template. 3. Establish the baseline before proposing any change. 4. GET /v1/prompts?change=C2&internal=I07 to pull a focused coordinate subset. 5. Record answers as observation, assumption, hypothesis, transformation or not-applicable. 6. POST /v1/validate with the run document to check it against the schema. 7. POST /v1/score to produce a comparison index across concepts. ## Limits This is a specification and working toolkit, not a validated forecasting system. State ladders are illustrative vocabularies, not calibrated numerical scales. An unfilled cell does not establish novelty or demand. A decoded explanation is not proof of intent or wrongdoing.