Compute architecture / capability separate from authority

Four roles. One governor.

Qwen provides local language capability. Grok supplies external high-compute work. EVOKE is the candidate visual-world engine. SAGE remains the sole owner of accepted state, admission, verification, closure and authority.

LocalQwen target
ExternalGrok
VisualEVOKE
GovernorSAGE

Authority allocation

Each component has one bounded job.

Capability does not confer authority, and installation does not prove runtime use.

01 / LOCAL LANGUAGE

Qwen 27B target

Primary local and offline language worker for routine reasoning, coding and tools.

  • Operator-selected target label: qwen3.8:27b.
  • Exact official package identity is not yet verified.
  • No live routing change before shadow qualification.
Target / verify identity
02 / EXTERNAL COMPUTE

Grok

High-compute worker for complex research, architecture, coding and diagnosis.

  • Provider-neutral adapter.
  • Provenance and admission required.
  • No direct SAGE authority.
Authority none
03 / VISUAL WORLD

EVOKE

Local visual-world and simulation candidate for persistent interactive generation.

  • Install in an isolated Python/CUDA environment.
  • Measure memory, speed, power and thermal behavior.
  • No live authority or automatic actuation.
External candidate
04 / GOVERNOR

SAGE

Sole authority over accepted state, decisions, admission, verification and closure.

  • Provider-independent evidence.
  • Capability envelopes and revocation.
  • Operator-visible truth.
Authority unchanged

EVOKE / verified external reference

A world model with state outside the denoiser.

The released EVOKE project describes a 14B, three-step, CFG-free autoregressive world model. It keeps persistent scene geometry in an external camera-indexed world-state bank, so generation context remains bounded while the session continues.

Model14Bpublished parameter count
Sampling3-stepCFG-free student
ReferenceH200not DGX Spark
Output384×64024 fps reference
Chunk1.5 s36 frames
Time2.11 sper chunk on one H200

DGX Spark reality check

Full weights repositoryApproximately 411 GB across released stages and teacher assets.
Shipped stage-3 model directoryApproximately 57.2 GB on disk.
Shared base componentsApproximately 23.3 GB on disk.
Required depth backendViGeo is a separate download and part of the default path.
Runtime fitUnestablished. Disk size is not peak unified-memory use.
Licensing gate: the EVOKE repository is Apache-2.0, while the documented depth backends carry CC-BY-NC-4.0 terms. Commercial use requires a separate licence review.

Execution order

Install capability without silently changing authority.

Every stage is reversible. Model installation, service routing, concurrent residency and live authority are distinct decisions.

  1. Perform a read-only DGX model and service inventory.
  2. Verify the exact Qwen package identity; install without changing live routing.
  3. Shadow-test the local model against existing workloads.
  4. Connect Grok through a provider-neutral governed adapter.
  5. Verify offline, timeout and provider-failure behavior.
  6. Stop but preserve qwen3-coder-next until rollback is proven.
  7. Install EVOKE in an isolated environment.
  8. Benchmark EVOKE and Qwen memory, speed, power and thermals.
  9. Choose simultaneous residency or controlled workload switching from evidence.
  10. Remove retired weights only after dependency and rollback checks.
  11. Connect neither Grok nor EVOKE to live authority until containment closes.

Current programme state

Integration remains held.

LOCAL_PRIMARY_LLM_TARGET = QWEN_27B
EXTERNAL_HIGH_COMPUTE    = GROK
VISUAL_WORLD_CANDIDATE   = EVOKE

GROK_AUTHORITY  = NONE
EVOKE_AUTHORITY = NONE
SAGE_AUTHORITY  = UNCHANGED

MG0_STATUS       = INTERRUPTED_BY_AUTHORITY_DEFECT
LIVE_INTEGRATION = HOLD
ISOLATED_INSTALL_AND_BENCHMARK = ALLOWED

Why this website is not LLM-driven at runtime

The motion on this site is deterministic CSS, SVG and local JavaScript. It makes no model calls, stores no visitor state, and does not depend on Grok, Qwen or EVOKE.

EVOKE-generated media can be added later only after the model is installed, the output has provenance, the licence position is reviewed, and the site can fall back cleanly when the model is absent.