KINETIC. INTERNAL

Scalable Operating Layer

KINETIC. SOL
CURRENT CANON ONLY
ENGINEERING · CURRENT STATE

Fresh bed. Locked physics. No legacy code.

The current architecture and deployment record for the successor Kinetic Platform. Historical D01–D08 proposals and retired Codex object models are not included.

1PRIVATE MONOREPO
1FRESH NEON PROJECT
3VERCEL PROJECTS
0PRODUCTION CHANGES
CURRENT DEPLOYMENT

One clean codebase, three isolated surfaces

APPS / SITE

Marketing at devsite.kineticdesk.app. Current Frost shell, private and noindex.

APPS / APP

Customer Desk at devapp.kineticdesk.app. Typed synthetic fixtures only while UX contracts are shaped.

APPS / ADMIN

Operator control plane at devadmin.kineticdesk.app. Endpoint availability UI is currently fixture-backed.

SHARED PACKAGES

UI, contracts, and database packages live in one private monorepo so the three surfaces cannot drift.

FRESH DATABASE

Dedicated Neon project initialized with eight foundation tables. No production data or legacy migration chain crossed.

LOCKED PLATFORM PHYSICS

Two engines and one Human Command Layer

LAYERCONTRACTIMMUTABILITY / CONTROL LAW
TaskingQuestion, purpose, scope, rights, expiry, versioned Collection PlanAcquisition begins only under approved Tasking
Actions EngineSubject + authorized Sources and Records → Intelligence ObjectMany Sources in, one governed immutable object out
Operations EngineIntelligence Objects + versioned analytical rules → SignalsSignals preserve support, conflict, class, uncertainty, and limits
DeskHuman review, challenge, composition, activation, sharing, exportHuman judgment never mutates underlying truth
Active FileWatch configuration + independent health + append-only Watch RunsNo Change never means No Run
OutcomeVerified world change or user-supplied dispositionNo causal claim that Kinetic created the outcome
CURRENT BUILD SEQUENCE

Frontend as executable specification

STEPWORKSTATE
01Build every route, screen, drawer, transition, and empty/loading/error/denied state with typed fixturesIN PROGRESS
02Lock routes, interaction rules, and view-model contracts through Mike's scalpel reviewOPEN
03Freeze Endpoint and Intelligence Object contracts in the shared contract packageOPEN
04Implement database, tenancy, auth, billing, Actions, Operations, Files, Watch, and Admin behind frozen contractsNOT STARTED
05Run security, isolation, payment, reproducibility, browser, mobile, and rollback gatesNOT STARTED
06Cut over only with explicit production approvalBLOCKED
ENGINEERING LAW

No legacy source file, schema, migration, or data crosses by default. Locked behavior, regression fixtures, and proven patterns may cross only through explicit review and parity proof.

SOL · ENGINEERING · CURRENT DEPLOYMENT AND ARCHITECTURE ONLY