Independent design-engineering practice · Sydney, Australia
Interfaces, infrastructure and machine-readable systems designed as one governed environment.
Brittek Digital works across design, software and infrastructure.
We build clearer, faster and more maintainable digital systems by treating interface, engineering and infrastructure as one system.
|
Semantic, performant and accessible interfaces built as systems rather than isolated pages. |
Typography, interaction, motion and editorial rhythm held as one visual grammar. |
Structured data, retrieval and agent-readable representations beneath the human interface. |
DESIGN ENGINEERING · DIGITAL INFRASTRUCTURE · AUTOMATION · QUALITY SYSTEMS · RETRIEVAL ARCHITECTURE
A small selection of the systems and instruments that represent how Brittek Digital works.
| System | Scope | Role |
|---|---|---|
| Brittek Surface | Design system · frontend architecture · publishing | Production environment |
| Visibility Scanner | Analysis · retrieval · reporting · machine-readable output | Studio instrument |
| Machine Surface | Structured data · entities · schema · retrieval representations | Knowledge infrastructure |
| Profile Infrastructure | Metrics · activity assets · validation · automated link checks | Public-system governance |
Commercial implementation is predominantly private. Public repositories and profile infrastructure show only part of the production system.
Extended technology map
One system from interface through infrastructure, verification and deployment.
| Layer | Production system |
|---|---|
| Interface | Next.js 15 App Router · React 19 · TypeScript · Tailwind CSS v4 |
| Motion | GSAP 3.15 · Lenis |
| Application | Next.js server/runtime primitives · FastAPI · Python 3.12 · Pydantic v2 · Zod |
| Data | PostgreSQL · Supabase |
| Edge runtime | Cloudflare Workers · OpenNext |
| Storage | Cloudflare R2 · KV · D1 where appropriate |
| Commerce | Stripe |
| Messaging | Resend |
| Delivery | GitHub Actions · Wrangler · Cloudflare |
| Preview environments | Vercel |
| Browser verification | Playwright · axe-core |
| Code verification | TypeScript · Vitest · ESLint |
| Performance | Lighthouse CI · Core Web Vitals |
| Observability | Sentry where wired |
| Package management | pnpm only |
INTERFACE
↓
APPLICATION
↓
DATA + SERVICES
↓
EDGE RUNTIME
↓
VERIFICATION
↓
PRODUCTION
STRATEGY → REQUIREMENTS → ARCHITECTURE → DESIGN SYSTEM → IMPLEMENTATION → VERIFICATION → PRODUCTION
Customer impact → Business impact → Engineering simplicity → Long-term maintainability
Systems over pages.
Performance is an aesthetic property.
Constraints define output.
Machine-readable first. Human-legible always.
Motion explains state or it is removed.
Reference informs judgement; it does not become authority.
ENTITIES → CONTENT GRAPH → COMPILE → REPRESENTATIONS → VERIFY → DEPLOY
One governed source should remain legible to both humans and machines.
AI architecture boundary
When AI belongs in a system, define:
model selection · context boundaries · prompt strategy · tool permissions · memory boundaries · structured outputs · evaluation · guardrails · fallbacks · observability · cost controls · human review
Deterministic software remains preferable where deterministic software is sufficient.
Most commercial implementation is private. Public GitHub activity represents only part of the engineering output.
Repository standard
README.md
LICENSE
CONTRIBUTING.md
SECURITY.md
CHANGELOG.md
.github/
├── ISSUE_TEMPLATE/
├── PULL_REQUEST_TEMPLATE.md
└── workflows/
Documentation is implementation infrastructure.
Brittek Digital
Sydney, Australia
brittek.net · hello@brittek.net · github.com/brittek
Built deliberately in Sydney.