How synced records stay the same record: the identity cascade, the bind table, deferred relationship resolution, and why deletes are the hardest part of sync. Part 2 of a three-part series.
How synced records stay the same record: the identity cascade, the bind table, deferred relationship resolution, and why deletes are the hardest part of sync. Part 2 of a three-part series.
How we built the sync engine that pulls Shopify orders, Stripe customers, and any REST API into our entity system: streams, recursive mapping trees, and one choke-point writer. Part 1 of a three-part series.
A generic engine is a runtime, not a product. This is how ours becomes Kopilot: page-scoped tools, prompt assembly built for caching, reference cards the model renders into the UI, and autonomous runs. The final part.
A read-only chat loop is easy. An agent that sends emails, mutates records, and can still be replayed deterministically in a test suite is where the engineering lives. Part two of three.
How we built the runtime that powers Kopilot: parts-based messages, async-generator streaming, and the safety valves that keep a model from running away. The first of a three-part deep dive.
Env vars, SST secrets, database overrides, and registry defaults — how we built a unified config service for a monorepo with 8 apps and 100+ variables.
Retry strategies, lock renewal recovery, circuit breakers, queue metrics, and graceful shutdown — keeping 20+ BullMQ workers healthy in production.
A deep dive into the async generator-based agent harness that powers Kopilot — routing, tool execution, streaming, and human-in-the-loop approval.
How we enqueue jobs, build parent-child processing pipelines with FlowProducer, and manage 25+ cron schedules — with real code from our open-source codebase.
How installed apps run inside Auxx.ai at runtime — the surface-based extension system, workflow triggers and blocks, caching strategy, access control, and admin governance.
Queues, workers, and the handler registry pattern — how we structured our BullMQ setup to process email syncs, webhooks, AI jobs, and more.
How we built apps/build — a standalone developer portal with dehydrated state, JWT auth, tRPC routers, version management, OAuth configuration, and team invitations.