Notes from building the platform and from the businesses running on it — the decisions, the things that turned out harder than expected, and the parts worth copying.
An agent that can read the platform underneath your project — the collections, the permissions, the services — instead of guessing at a backend it cannot see.
Michael Chen · Engineering LeadRead itHealth check, sign-in, and a first authenticated read — with the headers that actually matter and the three ways a 200 can still mean you are not signed in.
Sarah JohnsonStaff, customers, servers, terminals and hubs each authenticate differently — and picking the wrong one is how integrations end up sharing a login.
Alex ThompsonThe admin surface over the whole platform — site, content, storefront, CRM, finance, logistics and automation, all against the same records.
Emily RodriguezThere is no CLI and no deploy.yaml. A workspace is zipped, handed to a build plane, and published to a hostname — here is each hop, and what to check when one fails.
James WilsonProducts, carts, checkout and orders on the same records as your CRM, your invoices and your support tickets — so a customer is one customer.
Lisa MartinezLeads, tickets, reservations, campaigns and call history on the same records as your storefront and your invoices — which is why the numbers agree.
David Park