THE WORKFLOW

Five planes.
One hard boundary.

Nothing that touches the network ever touches a model, and nothing that touches a model ever touches the network. Acquisition and publishing are online, explicit, and human-approved; inference runs in a sandbox that provably cannot reach out. One process is never allowed to do all three.

STATUS: DESIGN STAGE (M0) — this page shows the target workflow. Schemas + docs are shipped; the runtime is roadmap. Full honesty ledger in the repo's EXPERIENCE.md.

THE FIVE PLANES

ACQUIREfetch + hash imagery, labels, modelsrecord licenses + provenanceNETWORK ALLOWEDqukaizen-dacproject.yamlMATERIALIZEimmutable content-addressed bundleno URLs · no credentialsLOCAL ONLYqukaizen-dacgeoai.bundle-manifest/v1alpha1INFERsecure-zero-egress-claw sandboxdeterministic worker · zero networkZERO NETWORKgeoai worker + QueueLLMpredictions.ndjson + receipt.jsonREVIEWevidence · receipt · calibrationapprove / correct / uncertainLOCAL ONLYgeoai review UIreviewed verdictsPUBLISHexplicit, human-approved exportmapswipe-review-packageNETWORK ALLOWEDdac export + geoai adapter

THE WALKTHROUGH ROADMAP

Target CLI shape — a post-cyclone road-obstruction run in Mozambique, end to end. dac commands are the control plane and may use the network in acquire/publish; geoai commands never do.

dac materialize project.yaml        # network may be used to resolve declared assets
dac verify bundle/sha256-87af       # proves all inputs are local and content-addressed
geoai run bundle/sha256-87af --profile secure-zero-egress-claw   # zero egress
geoai review run_01J...             # localhost UI
dac export run_01J... --format mapswipe-review-package           # separate, explicit approval

WHO: PROJECT MANAGER

Declares the run as code: dataset manifest, task, model by digest, sandbox profile. One YAML file in, an auditable pipeline out. No GPU knowledge, no prompt engineering.

WHO: ANALYST-OPERATOR

Runs the five commands, then triages in the review UI. The only human who ever touches this stack — volunteers never see it.

WHO: VOLUNTEERS, ON MAPSWIPE

The exported review package becomes a MapSwipe validation project. Consensus, volunteer experience, and OSM publishing stay upstream where they belong.

THE ANALYST REVIEW UI ROADMAP M2

Evidence-first triage, one candidate per screen

A localhost MapLibre interface reads the immutable result directory and shows, per candidate: before/after imagery, evidence regions drawn on the map, the model observation and its alternative explanations, model and runtime versions, the sandbox receipt, raw vs calibrated confidence, and abstention reason — with three controls: approve, correct, uncertain.

The model cannot operate the UI or approve its own output. The UI talks only to the control plane — never directly to the inference worker. Calibrated confidence is added by the control plane after the run; the sandbox emits raw scores only.

THE CONTRACTS — SCHEMAS SHIPPED TODAY V1ALPHA1 DRAFTS

geoai.bundle-manifest/v1alpha1

The trust boundary. Content-addressed assets, declared model + task + policy. No URLs, no credentials, no symlink escapes.

geoai.prediction/v1alpha1

Label, evidence claims with GeoJSON geometry anchored to an asset, alternative explanations, raw model score only.

geoai.receipt/v1alpha1

What actually executed: bundle/model/task digests, engine build, enforcement level, egress-verification result.

geoai.sandbox-profile/v1alpha1

secure-zero-egress-claw: network none, read-only inputs, write-only output, fail-closed below enforced.

WHAT'S REAL TODAY

BUILT · QUEUELLM

QueueLLM text engine (v0.1.0) and llama.cpp GBNF-constrained verdicts. The engines this stack embeds exist and run.

ROADMAP

Bundle verifier, sandbox enforcement + adversarial egress tests, worker, receipts (M1). Review UI + evaluation kit (M2). Export adapters (M3, gated on maintainer agreement).

UPSTREAM · MAPSWIPE/FAIR

MapSwipe validation ingest, consensus, vote-preserving exports, OSM publishing. Theirs to build and confirm — never assumed deployed.

Dictionary →