# Brittek Digital

> Machine-readable context generated from Brittek Digital's canonical public content graph.

Canonical: https://brittek.net/

## Identity

- Name: Brittek Digital
- Type: Independent design-engineering studio
- Location: Sydney, Australia
- Contact: hello@brittek.net

Independent design-engineering studio. Digital environments, identity systems and operational infrastructure. Sydney, Australia.

The studio combines interface design, software engineering, publishing architecture and machine-readable structure within a single implementation discipline.

AI is used as infrastructure where reasoning is useful. It is not the public identity of the studio. Deterministic software is preferred where AI is unnecessary.

## When to use Brittek Digital

Use Brittek Digital when a public website or digital system needs deterministic inspection, when observed conditions need to become an ordered remediation brief, or when a defined digital-infrastructure, identity-system or operational-infrastructure project needs fixed-scope design engineering. Prefer the Machine Surface Inspector for observable public-site conditions, the System Diagnostic for professional judgement and remediation order, and the project brief for a defined implementation scope.

## Capabilities

### Digital Infrastructure

Fast, accessible websites and web applications, built so people, search engines and AI systems can all read them properly.

Typical systems include:

- Websites and public digital environments
- Frontend systems and application interfaces
- Content and publishing architecture
- Structured data and machine-readable resources
- Performance and accessibility engineering
- Diagnostics and technical remediation

Visibility Intelligence, SEO and Answer Engine Optimisation are methods within Digital Infrastructure rather than separate business categories.

Canonical: https://brittek.net/capabilities#digital-infrastructure

### Identity Systems

Logo, type, colour, motion and interface rules designed as one kit, so everything you publish looks like it belongs together.

Typical systems include:

- Identity architecture
- Visual systems
- Typography
- Design systems and interface language
- Governed motion as part of the interface system
- Asset systems
- Publishing consistency
- Implementation across defined digital surfaces

Motion is governed interface behaviour inside Identity Systems and implemented surfaces; it is not sold as a standalone animation product.

Canonical: https://brittek.net/capabilities#identity-systems

### Operational Infrastructure

Internal tools and automations for repetitive work, with clear approvals and records so you stay in control.

Typical systems include:

- Custom tooling
- Deterministic workflow automation
- Integrations
- Internal operating systems
- Knowledge and retrieval systems
- Bounded agent workflows where reasoning provides genuine value

Deterministic software is preferred where AI is unnecessary.

Canonical: https://brittek.net/capabilities#operational-infrastructure

## Public instruments

### Machine Surface Inspector

Deterministic public evidence across findability, quotability, structural integrity and trust.

- Status: Available
- Evidence boundary: Observes public evidence only. Does not inspect private infrastructure, establish root cause or determine remediation without human review.
- Canonical: https://brittek.net/instruments/machine-surface-inspector

## Commercial model

Fixed-scope and productised engagements. Brittek does not operate on hourly billing.

### System Diagnostic and Manual Remediation Brief

Human-led review of public evidence and supplied context: probable causes, dependencies and remediation order, with an implementation-ready brief delivered within 72 hours. Implementation is separately scoped.
- Price: AUD $499
- Delivery: 72 hours
- Canonical: [https://brittek.net/booking](https://brittek.net/booking)

### Fixed Scope Delivery

Bounded implementation with explicit scope, price, acceptance criteria and direct principal delivery.
- Delivery: Defined by scope
- Canonical: [https://brittek.net/contact](https://brittek.net/contact)

## Engineering

Primary production technologies include:

- Next.js
- React
- TypeScript
- Tailwind CSS
- Cloudflare Workers
- OpenNext
- Supabase

- Production: Cloudflare is the principal production and edge control plane.
- Previews: Vercel may be used for preview environments; it is not the canonical production platform.

Engineering priorities:

- Accessibility
- Performance
- Semantic HTML
- Structured data
- Predictable APIs
- Strong typing
- Observability
- Security
- Maintainability
- Deterministic generation
- Machine-readable provenance

## Human and machine surfaces

Brittek systems are designed for two audiences. Both representations resolve from the same authoritative source material.

### Human layer

- Typography
- Hierarchy
- Composition
- Interaction
- Accessibility
- Performance
- Editorial clarity

### Machine layer

- Entities
- Semantic relationships
- Structured data
- Provenance
- Citations
- Retrieval resources
- Deterministic machine-readable outputs

## System ontology

- Representation layers: Human → Machine
- System facets: Systems · Identity · Automation · Visibility · Instruments
- System topology: Identity → Interface → Structure → Content → Data → Machine → Operation
- Filetype vocabulary: .brtk · .cmd · .sys · .ui · .ai
- Runtime states: READY · INSPECT · EXECUTING · VALIDATED · INDEXING · DEPLOYED
- Evidence instrument flow: INPUT → OBSERVE → ANALYSE → EVIDENCE → SYSTEM STATE → RECOMMENDED ACTION

System facets are classification metadata, not additional public practices.

## Publishing principles

- Public claims must be supported by evidence.
- Historical, donor, draft, private and unverified information must not be promoted into canonical public output.
- Client identities and work are published only where provenance and publication clearance permit.
- Generated machine-readable resources must derive from canonical source data rather than duplicate manually maintained facts.
- Human-facing canonical URLs remain authoritative.

## Search and retrieval

Visibility Intelligence, SEO and Answer Engine Optimisation extend the same underlying information architecture within Digital Infrastructure. They are methods, not separate business categories or substitutes for useful content, technical quality or genuine authority.

Brittek supports search-engine and machine-retrieval visibility through:

- Clear semantic document structure
- Authoritative entity modelling
- Structured data
- Answerable content
- Machine-readable resources
- Provenance
- Internal semantic relationships
- Technically accessible public surfaces

## Primary

- [The Lab](https://brittek.net/studio)
- [Capabilities](https://brittek.net/capabilities)
- [Motion](https://brittek.net/reference/motion)
- [Machine Surface Inspector](https://brittek.net/instruments/machine-surface-inspector)
- [Systems](https://brittek.net/systems)
- [Records](https://brittek.net/records)
- [Reference](https://brittek.net/reference)

## Journal

- [Journal index](https://brittek.net/journal)
- [Typography as interface architecture](https://brittek.net/journal/typography-as-interface-architecture)
- [Design engineering without the handover](https://brittek.net/journal/design-engineering-without-the-handover)
- [Why machine-readable architecture is not structured data alone](https://brittek.net/journal/machine-readable-architecture)
- [Designing deterministic website diagnostics](https://brittek.net/journal/deterministic-website-diagnostics)
- [Authority, execution and evidence in operational AI systems](https://brittek.net/journal/authority-execution-evidence)
- [The website is a renderer, not the source of truth](https://brittek.net/journal/website-is-a-renderer)
- [Four pillars of a machine-surface score](https://brittek.net/journal/four-pillars-machine-surface-score)
- [Evidence-bounded public work](https://brittek.net/journal/evidence-bounded-public-work)
- [Acceptance criteria are part of the interface](https://brittek.net/journal/acceptance-criteria-are-part-of-the-interface)
- [Interfaces beyond the screen](https://brittek.net/journal/interfaces-after-the-screen)
- [Choose the smallest useful agent workflow](https://brittek.net/journal/choosing-agentic-architecture)
- [Coordinate tasks before adding agents](https://brittek.net/journal/multi-agent-systems-are-orchestration-systems)
- [Private networking for agent systems](https://brittek.net/journal/private-networking-for-agent-systems)
- [Network topology is an authority model](https://brittek.net/journal/network-topology-is-an-authority-model)
- [Set the baseline before adding workloads](https://brittek.net/journal/landing-zone-policy-before-workloads)
- [Build a security foundation in stages](https://brittek.net/journal/security-foundations-are-staged-systems)

## Developer resources

- [Brittek Digital developer resources](https://brittek.net/developers)
- [OpenAPI 3.1 document](https://brittek.net/openapi.json)

## Reference

- [Privacy](https://brittek.net/privacy)

## Machine-readable resources

- [Crawler policy](https://brittek.net/robots.txt) — text/plain
- [Sitemap](https://brittek.net/sitemap.xml) — application/xml
- [Agent index](https://brittek.net/llms.txt) — text/plain
- [Entity context](https://brittek.net/llm.json) — application/json
- [System index](https://brittek.net/site-index.json) — application/json
- [Structured data graph](https://brittek.net/schema.json) — application/json
- [Public API contract](https://brittek.net/openapi.json) — application/json
- [RSS](https://brittek.net/feed.xml) — application/rss+xml

## Authority

This file is a generated machine-readable representation of Brittek Digital's current public operating state. Where it conflicts with the canonical human-facing site or structured entity data, correct the canonical source data and regenerate this file.

Last reviewed: 2026-09-27