QUARK / WAREHOUSE MANAGEMENT METADATA‑GOVERNABLE ARCHITECTURE
QUARK.BUILD

The warehouse
that configures
itself.

A warehouse management system that deploys in days, not years. Because an AI agent configures it — not a consulting team. Built on Metadata‑Governable Architecture: a foundation legacy systems cannot retrofit.

§ 01 — The diagnosis

Traditional WMS
is stuck in 2010.

Manhattan, SAP and Infor are excellent systems — built for an era when warehouse management meant custom code. That era is ending. Their architecture was never designed to be configured at runtime; only customised, by experts, over months, with tribal knowledge trapped in their heads. We respect what they built. We are building what comes next.
Legacy WMS · circa 2010
Customised by experts. Slowly.
12months to go live
×Hardcoded processes you can't touch
×New SKU? File a ticket. Wait 3 weeks.
×Tribal knowledge in consultants' heads
×Every change is a customisation project
×Cannot be audited. Cannot be rolled back.
Quark · 2026
Configured by AI. Live.
1day to go live
Every feature is metadata, addressable by agents
New SKU? Type it in. It's live in seconds.
The system describes itself at runtime
Every mutation is versioned and reversible
Destructive ops require human approval — by design
§ 02 — The day we go live

Describe your warehouse.
Log in tomorrow.

Not a prototype. Not a sandbox demo. Production. Bring a photo of your aisles, a spreadsheet of your SKUs, and a short conversation about how you actually run. By morning, your operators have a working WMS configured to your specific business — RF terminals, picking rules, integrations, the lot.
Day · zero09:00

Tell the AI about your operation.

Upload a photo of your aisles. Drop in your stock list as Excel. Describe — in your own words — what you store, how you receive, who picks. The agent extracts zones, SKUs, lot policies and team structure automatically.

aisle_photo.jpg · 4032×3024
4 zones 12 aisles 3 staging cold chain 12,847 SKUs
Day · zero14:30

Review the diff in the Studio.

The agent generates your full configuration as a draft. You review it visually — every zone, role, picking rule, validation. Approve, fork, edit, or reject. No SQL, no source code, no consultant‑in‑the‑middle.

diff · draft cs_8421+ 48 / ~ 12 / − 1
+zone.cold_chainFEFO · 2–8°C
+role.picker_pharmarf.scan_lot · qc.flag
~strategy.replenishthreshold 20% → 30%
+integration.erp_inwebhook · daily 04:00
rule.legacy_putawayrequires approval
Day · one08:00

Operators log in. The system is live.

RF terminals scan their first pallet. Pickers walk their first wave. Every change you make from this moment forward goes through the same Draft → Validate → Approve → Apply pipeline — including the ones the AI proposes itself.

Quark agent
Proposed: increase replenish threshold for zone A from 20% to 30%. Based on 7 days of stockout events. today · 08:14 ApproveDiffReject
Approved.08:15 · you
Quark agent ✓ Applied to production. Rollback available for 7 days. 08:15
§ 03 — The foundation

Metadata‑Governable
Architecture.

A manifesto for systems that AI agents can safely operate. Not governance bolted on top — governance baked into the data model itself. Five principles. No path around them.
P · 01
Features are data, not code.

Forms, workflows, validation rules, navigation, business objects — all rows in a database. Not source files. An agent issues INSERT/UPDATE statements; not merge requests.

addressability for agents
P · 02
Every capability self‑describes.

Endpoints, objects, UI elements expose machine‑readable schemas through introspection. Agents discover new capabilities the moment they exist — no client update, no integration work.

openrpc · json schema · live
P · 03
Mutations are reversible.

No write goes direct to a live system. Every change passes Draft → Validate → Apply. Diff before promotion. Rollback as a structural property, not a recovery procedure.

draft · validate · apply · fork
P · 04
Dangerous ops require a human.

Deletions, financial transactions, customer‑facing publishes — they cannot reach execution without an approval signal. Not a configurable option. A code path that physically does not exist.

unavoidable · by design
P · 05
Sandboxing is structural.

A field script can read a field. It cannot call the database. It cannot make HTTP. The sandbox isn't a scanner looking for dangerous calls — it's an architecture that refuses to expose the APIs at all.

semantic · not syntactic
P · ∞
A stronger claim — no path around the controls.

External governance is only as strong as its perimeter. Quark embeds governance into the primary data model. Change, validation and rollback are not enforced from outside — they are the only available vocabulary for mutation.

read the full manifesto →
§ 04 — Figure 01

Five layers.
One contract.

Mutation flows top‑down: an agent (or human) drafts a change against the metadata layer, validation runs against the schema, the apply step is gated by approval policy, and the runtime is rebuilt from metadata — no redeploy, no migration, no downtime.

Governance is not a layer on top. It is the only vocabulary for change.

  1. Metadata is the source of truth. The runtime is rebuilt from L1, not the other way around.
  2. Drafts are isolated. A bad agent decision becomes a discarded draft — not a production incident.
  3. Approval is unavoidable. Destructive paths cannot reach execution without a signed signal.
  4. Sandboxes refuse, not detect. The architecture doesn't scan scripts for danger — it never exposes the dangerous APIs.
  5. Introspection is live. Agents read the system the same way the system reads itself.
§ 05 — Who it's for

Two readers.
One economic shift.

Quark transforms two groups simultaneously. The integrators who today bill 6 months on routine config — and the regulated industries that need every change attributable to the record.
A · For integrators

Your business is not threatened.
It is transformed.

Today, implementing Infor or SAP eats six months of your team mapping SKUs, drawing zones and writing printer scripts. Clients consider it "included." Your margin lives in the leftover hours.

With Quark, that work takes two weeks. The remaining 5.5 months become available for the work you actually enjoy — process consulting, ERP integration, operator training, new clients.

More projects per year, same headcount
Higher margin per billable hour
No junior implementer treadmill
"Sell, train, support — the platform handles configuration."
B · For regulated industries

Pharma. 3PL. Food. Electronics.

Compliance does not relax because AI is in the loop — it tightens. Quark's approval hooks, audit logs, and reversible mutations are designed for environments where every change must be justified, attributable, and traceable.

Every mutation logged with actor, timestamp, before / after state
Every deployment is a reviewable diff — see what changed and why
Destructive operations require sign‑off through a channel of your choice
Every user script runs in a sandbox that cannot escape its permissions
If your auditor asks "what did the AI change last Tuesday?" — we show them, to the record, in under a minute.
§ 06 — The Standard Model

A platform of particles.
Each one does one thing well.

Named after the fundamental particles of matter — because warehouses are built from fundamental blocks too. Each module is a quark, gluon, boson, or lepton in a single coherent system. You compose, not integrate.
Core Operations Functional On the roadmap
Q
SHIPPED CORE

Quark

Metadata core. The fundamental particles of warehouse operations — entities, policies, rules.

φ
SHIPPED · BETA VOICE

Phonon

Voice layer over your WMS. The quantum of sound — listens, confirms, scans, posts back. Stays on SAP, Manhattan, Infor, Odoo. Two-week integration, not a rip-and-replace.

+15–25%Picking lift
99%+Accuracy on noise
$700Per‑operator hardware
5×–10×Lower TCO vs proprietary voice
g
Q1 2027iPaaS

Gluon

Binds Quark to ERP, marketplaces, carriers, EDI. The strong force between systems.

B
Q2 2027EVENT BUS

Boson

Carries every state change — receipt, ship, adjust — across modules. Pub/sub with audit.

Q4 2026EDGE / RF

Lepton

Lightweight client for RF scanners, tablets, mobiles. Runs everywhere, weighs nothing.

H
Q3 2026VERTICAL

Hadron

Pre-composed industry templates — 3PL × Pharma, D2C × Fashion. Quarks bound by an industry.

α
Q4 2027VOICE AI

Axion

The intelligence hidden in voice sessions. Per-operator acoustic tuning, slotting hints, fraud signals.

γ
FUTUREAI AGENT

Photon

The onboarding agent. Carries information at the speed of light.

ν
SHIPPEDANALYTICS

Neutrino

Reporting that passes through everything — almost weightless, never blocking.

ƒ
SHIPPEDIDENTITY

Fermion

RBAC and identity. Pauli's principle — every user is unique.

h
FUTURECONFIG ENGINE

Higgs

Gives meaning — the configuration field that makes other particles real.

π
FUTUREMIDDLEWARE

Meson

Composite adapters — bridges between protocols, formats, eras.

A note on the name — Quark is pronounced [kwɔːk], after Gell-Mann's coinage. He took the spelling from a single line in Joyce's Finnegans Wake: "Three quarks for Muster Mark." Mark is also the name of my son. The metaphor and the family — they earn their place.

§ 07 — Early access

Be first when
Quark ships for
your industry.

We're onboarding the first warehouses now. Leave your email and tell us what you run — we'll reach out the moment your industry template is ready.

§ Waitlist — early access

Join the waitlist

One email. No spam. We'll only be in touch when there's something real to show you.

No spam. One email when we launch for your industry.
Thanks — you're on the list. We'll be in touch.