SOL · ENGINEERING RECORD

The architecture, deployment, and edit map.

A study surface for the One Platform. It separates current infrastructure, ruled physics, and proposed stack choices so the operating record never presents a draft as production fact.

05SYSTEM LAYERS

01TRUTH SEAM

52ACTION CONTRACTS

D01–D08STACK RULINGS OPEN

TARGET ARCHITECTURE · PROPOSED

One direction of truth

The production flow is ruled. Technology selections D01–D08 remain proposed until Mike rules them.

01 · SOURCES

Licensed feeds, official records, public records, and customer-supplied documents. Each source carries rights, provenance class, retrieval time, and retention controls.

02 · ACTION RUNTIME

One dispatch door checks identity, entitlement, meter, scope, idempotency, and effect class. A closed worker fleet invokes source adapters and emits canonical Components.

03 · LEDGER

Append-only events form the record. Typed projections expose Subjects, Runs, Records, Findings, Components, Files, actors, edges, actions, and outcomes without mutating history.

04 · SYNTHESIS

Deterministic-first resolution, relationship edges, patterns, and cross-run enrichment. Observation, derived fact, scored inference, uncertainty, and conflict remain separate.

05 · SURFACES

Desk, API, MCP, webhooks, Files, exports, docs, metering, and invoices read one contract. Surfaces are projections, not independent systems of record.

TRADE STUDY · AWAITING CEO RULING

Proposed technology stack

ID	AREA	PROPOSED CHOICE	WHY	STATE
`D01`	Language	TypeScript end to end	One type system from contract to surface. Hot paths stay isolated for a future Rust worker.	PROPOSED
`D02`	Compute	Vercel surfaces + managed long-lived containers	Edge delivery for thin surfaces. Stateful licensed-source workers do not run as short lambdas.	PROPOSED
`D03`	Ledger	Event-sourced Postgres on Neon	Append-only events, typed projections, RLS, preview branches, and conventional operations.	PROPOSED
`D04`	Graph	Materialized graph tables in Postgres	Graph state stays replayable from the ledger. A dedicated graph database waits for measured traversal pressure.	PROPOSED
`D05`	Queue	Postgres SKIP LOCKED, Temporal-class later	Fewest moving parts now. Workflow engine enters only when durable multi-operation chaining requires it.	PROPOSED
`D06`	Fleet	Per-family managed container services	Blast-radius and licensing isolation without Kubernetes overhead.	PROPOSED
`D07`	Repository	Single workspace monorepo	Contracts, taxonomy, ledger, runtime, design system, and surfaces change together under one QA gate.	PROPOSED
`D08`	Objects	S3-class content-addressed store	Files and source objects are immutable, hash-addressed, and bound to custody manifests.	PROPOSED

CONTRACT MAP

What each package owns

PACKAGE	OWNS	MUST NOT OWN
`contracts`	OpenAPI, JSON Schema, event envelopes, generated types, error vocabulary	Provider logic or UI state
`taxonomy`	Provider-neutral element tree, stable IDs, finding classes, source classes	Vendor names or tenant data
`ledger`	Event append, projections, RLS policy, replay, recall-by-source	Source calls or presentation logic
`runtime`	Registry, dispatch, entitlement, idempotency, metering, worker contract	Direct public exposure of the fleet
`synthesis`	Deterministic resolution, graph edges, patterns, uncertainty, conflicts	Advice or silent fact mutation
`design-system`	Tokens, primitives, native Component renderers, state patterns	Domain decisions
`surfaces/*`	Desk, API, MCP, webhooks, exports, docs, invoice projections	Independent truth stores

DEPLOYMENT DOCTRINE

From edit to production

The Codex itself is currently a static, access-gated Vercel property. The platform deployment below is the proposed production operating model.

STAGE	ACTION	REQUIRED PROOF	ROLLBACK
01 · Branch	One feature branch and one decision-linked scope	No direct commits to main	Delete branch
02 · Preview	Vercel preview plus isolated Neon branch	Clickable URL, migration proof, synthetic tenant	Discard preview and DB branch
03 · Gate	Typecheck, production build, full tests, new edge tests, security review	All checks green and independent diff review	Block PR
04 · Oracle	Shadow-run current and replacement implementations	Canonical output parity at declared threshold	Keep current implementation serving
05 · Approval	Mike approves merge after visual and QA proof	Explicit green light	Do not merge
06 · Production	Main auto-deploys surfaces; workers roll by family	Health, contract, auth, meter, and tenant-isolation smoke	Re-point surface and worker version

CURRENT SOL HOST

Internal source-of-truth deployment

HOST

Vercel static project

Project: verb-codex. Static HTML sections deploy as one immutable release. Custom domain: sol.m1k3d0w.com.

CURRENT

DNS + TLS

Cloudflare to Vercel

DNS-only CNAME at sol.m1k3d0w.com points to Vercel. Vercel owns certificate issuance and renewal.

CURRENT TARGET

ACCESS

Private and noindex

Client-side shared-key gate plus noindex and nofollow metadata. This is an internal study surface, not a public security boundary.

CURRENT

Edit rule: architecture changes begin as a decision in the register. A page update records a ruling. It does not itself authorize a code merge, infrastructure cutover, billing change, or public release.

KINETIC · SCALABLE OPERATING LAYER · PRIVATE WORKING RECORD