Radiant
Git and YAML registration, schemas, refs, validation, caching, and provenance for configuration that other primitives can reference.
Composable platform primitives
Build connected software from modular, production-ready building blocks.
LatticeKit gives teams a coherent way to define, validate, compose, and operate the core primitives behind modern systems: configuration, schedules, workflows, resources, audiences, communication, and ledgers.
Git-backed
Schema-first
Observable
AI-ready
The idea
A toolkit for the systems beneath the product.
Most applications eventually rediscover the same hard problems: schedules, policy, configuration, workflows, audiences, notifications, resource allocation, and auditable records. LatticeKit treats those as reusable primitives instead of scattered feature code.
Use LatticeKit to turn business behavior into explicit definitions, contracts, plans, and executions that developers and future AI agents can inspect safely.
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.
Seldon
Schedules, offers, availability projections, and full booking lifecycles. Pending through completed under explicit cancel and modify policies, with deterministic planning and scheduled hand-offs.
Trantor
Physical resources, inventory, capacity, pools, allocation, and constraints for reservable or assignable assets.
Terminus
People, accounts, and ranked groups — households, families, tiers, teams. Consent and entitlement gates that other primitives call before touching customers.
Hardin
Products, variants, modifiers, recipes, categories, and tax classes. The sellable catalog that POS surfaces price and order against.
Hober
Live order tabs for retail and food service. Open, modify, route to kitchen, settle, and close — coupled to Hardin, Payments, and Mallow.
Payments
Processors, payment methods, intents, authorizations, settlements, and disputes — modeled to match how real payment providers actually work.
Mallow
Ledger-style records, sales, hours, payouts, settlements, immutable event history, and auditable financial state.
Speaker
Messages, templates, channels, consent, communication preferences, delivery attempts, provider routing, and conversation history.
Daneel
Actions, workflows, execution records, idempotency, retries, side effects, compensation, and runtime observability.
Palver
WebSocket channels over the audit event outbox. Live, per-channel pushes of the same DTOs the REST endpoints return, auth-gated by 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.
Define
Use schema-first APIs and Git-backed YAML definitions to describe policies, workflows, schedules, resources, and audiences.
Validate
Resolve refs, infer types where appropriate, check relationships, and produce human-readable validation failures before execution.
Plan
Compute offers, actions, allocations, communication targets, and side effects as inspectable plans with deterministic reasoning.
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: seldon.offer_pattern
version: 1
name: weekly-member-window
source:
radiant_ref: schedule-definitions/main
policy:
release: rolling_14_days
quota:
per_audience: member_standard
max_active: 2
hooks:
on_reserved:
action: speaker.send_message
template: reservation.confirmed.v1Use 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.
Scheduling · Allocation
Golf tee sheet
Daily tee sheet with carts, member tiers, front-vs-back dimensional offers, and a Saturday tournament that locks the front nine.
Read →Stays · Folio
Hotel front desk
Multi-night stays, in-room charges that roll into the folio, spa appointments as separate Bookings, housekeeping routing on checkout.
Read →Appointments · Retail
Salon & spa
Variable-duration services, walk-in queues that promote on cancellation, retail add-ons mid-service, tip-on-card with one capture.
Read →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.