Updated
Rendering and content
Next.js App Router with strict TypeScript. Reading pages render on the server from version-controlled content. Narrow interactive components handle preferences, forms and demonstrations. Private evidence is excluded from public imports and deployment.
An explicit native boundary
Legacy Bridge validates JSON, produces fixed-width ASCII records and invokes a fixed GnuCOBOL executable without a shell. Output is validated before it is returned. The program timeout is two seconds. Missing dependencies return an explicit unavailable error.
Local state and external effects
Quote and replay records use IndexedDB transactions with version checks. Demonstrations send no payments, messages or requests to external sites. The only possible email delivery is the contact form after authorized configuration.
Validation and documents
Validation covers schemas, deterministic calculations, state transitions, failures and Chromium/WebKit journeys. Fictional quotes, invoices, receipts and replay summaries are generated in the browser from demonstration records. Transaction documents are marked as not valid for payment.
Deployment trade-offs
A local build, a hosted preview and publication are separate milestones. Native execution must be verified in the target runtime. Contact requires an authorized recipient and checked receipt. The intended domain is not represented as active.
Performance and privacy
Locally hosted Manrope font under the SIL OFL, no advertising tools and deferred document generators. No production performance statistics are invented. Reading pages remain available when contact or native execution is unavailable.