Operational platform primitives

The platform layer for real-world operations.

LatticeKit composes the primitives operations-heavy products always end up rebuilding — scheduling, identity, payments, ledger, workflow, comms, real-time, marketing, reporting, experimentation, logistics. Wire the primitives; ship the business logic on top.

Git-backed Schema-first Observable AI-ready
A bright pastel modular lattice network connecting software primitives.
The idea

A toolkit for the systems beneath the product.

Most operations-heavy products end up rebuilding the same wheels: scheduling and resources, identity and consent, payments and ledger, workflow and comms, audiences and audit history. LatticeKit ships them as reusable primitives so teams compose them instead of reinventing them.

LatticeKit turns business behavior into explicit definitions, contracts, plans, and executions — auditable by developers and AI agents alike.

Primitive library

Named building blocks with clear ownership.

Each primitive owns a real architectural concern. Together they form a lattice of reusable capabilities instead of a monolith of accidental coupling.

Live
R

Radiant

Git and YAML registration, schemas, refs, validation, caching, provenance — plus pull-request-style review on every asset change. Employees and AI agents propose; operators approve and merge.

Live
S

Seldon

Schedules, offers, availability projections, and full booking lifecycles — now including travel-aware field-service scheduling. Pending through completed under explicit cancel and modify policies, with deterministic planning and scheduled hand-offs.

Live
T

Trantor

Physical resources, inventory, capacity, pools, allocation, and constraints for reservable or assignable assets.

Live
Te

Terminus

People, accounts, and ranked groups — households, families, tiers, teams. Consent and entitlement gates that other primitives call before touching customers, plus typed custom attributes that add per-tenant fields without a migration.

Live
Ha

Hardin

The sellable catalog: products, variants, modifiers, recipes, tax classes, and a real dynamic-pricing engine — tier and channel scopes, CEL fallback, yield / surge, cart promotions, bundles, and customer-redeemable promo codes.

Live
Ho

Hober

Live order tabs for retail and food service. Open, modify, route to kitchen, settle, and close — coupled to Hardin, Payments, and Mallow.

Live
Pa

Payments

Processors, payment methods, intents, authorizations, settlements, and disputes — modeled to match how real payment providers actually work, now including card-present (EMV) terminals.

Live
M

Mallow

Ledger-style records, sales, hours, payouts, settlements, immutable event history, and auditable financial state — plus stored value (gift cards, store credit, loyalty) on the same ledger.

Live
Sp

Speaker

Messages, templates, channels, consent, communication preferences, delivery attempts, provider routing, and conversation history — across email, SMS, and Web/mobile push.

Live
D

Daneel

DAG-based workflow engine. Branch, switch, parallel, sleep, wait-for-event, and loop nodes; CEL triggers; three-backend executor (sync, sqs, temporal).

Live
De

Demerzel

The operator console. Mannix-backed sign-in (passkeys + MFA), AI chat with an MCP tool registry over every primitive, visual asset editor, multi-page tenant sites.

Live
Ko

Korell

Bulk data-import primitive. Upload a CSV, XLSX, or a whole ZIP export; AI proposes the mapping, a dry run previews it, and rows import through each primitive's normal validation.

Live
Ma

Magnifico

Marketing primitive: audiences, campaigns, attribution, and conversions. Sits on top of Speaker, Daneel, and Terminus.

Live
Pe

Pelorat

Reporting-fork data plane plus authored reports with scheduled runs. Forks operational writes into a query-shaped read plane with backfill, so reports never touch the hot path.

Live
Pv

Palver

Live channels over the audit event outbox, deployed over Centrifugo. Twelve per-primitive channel derivers, out-of-transaction fan-out, and a Live Activity stream in Demerzel; subscription auth defers to Terminus.

Live
Br

Branno

Experimentation: multi-armed bandit experiments over prices, ui_views, and offers. Wired live into Hober pricing — cohort-stable allocation, revenue attribution at order close, hourly auto-convergence, and a Radiant handoff that merges the winning variant.

Live
El

Elliot

Logistics: parcel, last-mile own-fleet, and recurring B2B freight behind one mode-agnostic carrier-driver seam. Real carriers (EasyPost, Shippo, UPS, FedEx, DoorDash, Uber Direct, freight brokers), an X12 EDI freight layer, tracking webhooks, and auto-shipments from a closed Hober order.

Live
Md

Media

The media store: files and images uploaded straight to S3 over a presigned URL, served from CloudFront, and referenced by opaque id so no other primitive ever proxies a byte.

Live
Mx

Mannix

Authentication for customers, operators, and machines: one global principal with password, passkeys, TOTP, social, and OIDC. RS256 tokens every primitive verifies offline; reuse one login across businesses with no cross-business visibility.

In progress
Sg

Sign

E-signature: envelopes, signers, and the signing lifecycle, with the real vendor (DocuSign, Dropbox Sign, Adobe) behind one provider-driver seam. Documents live in Media; signers in Terminus.

Common runtime

Shared IDs, tenancy boundaries, contracts, error models, metadata, events, CLI flows, and OpenAPI-ready DTOs.

Architecture

Definition, planning, execution, and feedback.

LatticeKit is built around a simple loop: define behavior in versioned contracts, validate it before runtime, execute it through observable primitives, then improve it safely.

01

Define

Use schema-first APIs and Git-backed YAML definitions to describe policies, workflows, schedules, resources, and audiences.

02

Validate

Resolve refs, infer types where appropriate, check relationships, and produce human-readable validation failures before execution.

03

Plan

Compute offers, actions, allocations, communication targets, and side effects as inspectable plans with deterministic reasoning.

04

Execute

Run workflows and I/O through idempotent handlers, retries, compensation, audit records, and observable runtime boundaries.

Developer experience

Built for humans and agents.

LatticeKit favors explicit contracts, strong names, stable APIs, and clear error models so developers can reason about change. The same properties make it safer for AI tools to assist without guessing.

  • OpenAPI 3.1-friendly contracts
  • Git-backed configuration and provenance
  • Validate, plan, apply workflows
  • Observable execution and audit history
_type: daneel.action
version: 1
name: booking-reminder-24h
trigger:
  event: seldon.booking.confirmed
  filter: "event.startsAt - now > 24h"
dag:
  entryNodeId: send
  nodes:
    send:
      type: speaker.send_message
      config:
        templateAlias: reservation.reminder.v1
        recipientPersonId: "{{ event.party.members[0].terminusPersonId }}"
        urgency: transactional
      next: done
    done:
      type: end
Use cases

Concrete walk-throughs.

One primitive set, very different products. Click any of these for a full end-to-end narrative naming the primitives at each step.

See all use cases →

Early access

Start with one primitive, then connect the lattice.

LatticeKit is still being built in the open with a small group. Join the waitlist to follow along and get access as primitives mature.