A portfolio you can inspect.
Separate engines. Shared principles. This site uses a modular Next.js application, browser workers, and explicit boundaries between public information and private local files.
One modular application
Public pages, tool shells, and the workspace share navigation and design tokens. Heavy engines are loaded only when their features are used.
Deliberate local processing
Workers keep the interface responsive. Jobs carry IDs, actual stages, results, and errors. Cancellation stops work and stale responses are ignored.
Connected consequences
Domain commands validate actors, versions, idempotency, and invariants. Stock reservations, sales entries, and activity derive from the same transactions.
An assistant with a boundary
Intent routing and weighted retrieval search a public corpus. Sources accompany answers. The assistant does not open the business database or tool files.
Honest runtime labels
Local demos are browser SQL. Roles are simulated. Go and OIDC have separate statuses. Reconstructed workflows are never labelled employer production systems.
Recoverable source
The original code has a Git recovery baseline before the redesign. Preview validation precedes production, and the existing domain remains in place.