Brittek Surface.
The public Brittek design-engineering surface and its governed machine-readable publishing layer.
- State
- Live
- Type
- Public system
- Delivery
- Cloudflare edge
- Verified
- 01 Aug 2026
01 / Context
The website is treated as an operating surface, not a brochure.
The system had to present a restrained design-engineering practice, operate a deterministic visibility instrument, support commercial and private workflows, and publish consistent facts to both people and machines.
The central constraint was cohesion: visual refinement could not compromise scanner state, payments, portal isolation, subdomain routing, accessibility or the canonical content graph.
02 / Architecture
One system, six explicit layers.
- 01
Public surface
Editorial routes, instruments and engagement paths.
- 02
Content graph
Validated entities, relationships and factual records.
- 03
Application layer
Next.js server components and bounded client interactions.
- 04
Operational APIs
Scanner, contact, booking, payment and portal boundaries.
- 05
Edge delivery
OpenNext deployment on Cloudflare Workers.
- 06
Verification
Build, browser, accessibility and production-surface checks.
03 / System language
Editorial outside. Operational underneath.
04 / Operational safeguards
Presentation can change. System guarantees remain fixed.
Canonical integrity
One canonical public host with deliberate product-subdomain behaviour.
Content integrity
Public facts compile from a validated entity graph into human and machine outputs.
Execution boundaries
Scanner, payment, contact and portal operations remain isolated from presentation changes.
Accessible operation
Keyboard navigation, reduced motion, visible focus and touch-safe controls are regression tested.
05 / Public evidence