Platform architecture
Service boundaries, module interactions and the event model.
Company
Roadmap
What is built, what is specified and what stands between the two — stated at the level of platform capability rather than dates we cannot commit to.
Built
Working today
Brand and product direction
Positioning, messaging and the principles the platform is built to.
Information architecture
This site — 46 routes, navigation, search, login flow and the dashboard architecture.
UI design system
The component library every page renders through, in a light and a dark theme.
Database schema
103 tables applied to a real PostgreSQL, with 90 invariant checks run against a live server on every verification pass.
API specification
208 operations as a validated OpenAPI 3.1 document, generating a typed SDK surface that compiles.
Reference SDK
A typed TypeScript client over the generated definitions — retries, idempotency, pagination and webhook verification — with its own test suite. Open source at github.com/matinee-ai/sdk; not published to npm.
Sandbox reference server
The quick-start and game-economy loops served locally: the full request conventions, a double-entry ledger, the reward engine and signed webhooks with the specified retry schedule. Driven over real HTTP by the SDK in the integration tests.
Ledger judged by the schema
With its Postgres mirror on, every posting the sandbox accepts is re-posted into the verified database schema, whose own triggers refuse anything unbalanced, imprecise or mutated.
Continuous verification
Every pull request runs the full check suite and the database verification against a live PostgreSQL.
Specified
Designed and checked, not yet running
Product architecture
The twelve products and how they relate.
UX architecture
User types, flows and the dashboard experience.
Technical architecture
Stack, tenancy, identity, wallet architecture and the internal ledger.
Digital asset engine
Issuance, transfer, redemption, expiry and treasury — with a fixed supply enforced by the database rather than by convention.
AI operating system
Gateway, routing, agents, tools and approvals. An agent cannot exceed the authority of whoever invoked it, and that is enforced in the schema.
Workflow engine
Durable automation with human approval built in. A published workflow version cannot be edited, and the person who starts a run cannot approve it.
What is missing
Four things stand between the specification and a platform
None of them is cleared by writing more specification, and each blocks a different set of capabilities:
- No hosted API server. The in-repo sandbox serves the core loop on localhost; nothing answers at api.matinee.ai or sandbox-api.matinee.ai, and the remaining endpoint surface beyond that loop is specification only.
- No AI model provider. No API key, no endpoint, no local model — so no agent has ever run.
- No blockchain connection. No network has been contacted and no contract has been written or deployed.
- No workflow runtime. The queue and workers the design calls for are not part of this system yet, so nothing has executed.
The hosted API server comes first: three of the other four need something to serve their endpoints before they can begin, and the sandbox reference implementation is the path it grows from.
Ready to build your digital economy?
Matinee AI has no public signup. Tell us what you want to launch and we will review the request.