Capabilities
Three practices, delivered directly.
Digital infrastructure, identity systems and operational infrastructure. Each is scoped in writing, delivered by the principal, and accepted against criteria agreed before the work starts.
A website is infrastructure or it is a liability.
Architecture, performance, accessibility and edge delivery, engineered so the system stays maintainable after the launch it was built for.
Implementation is bounded by a written scope. Ranking, traffic and revenue are not predicted, and no engagement is priced against them.
Response policy · asserted at the edge
- strict-transport-security
- max-age=63072000; includeSubDomains; preload
- content-security-policy
- default-src 'self'; frame-ancestors 'none'; object-src 'none'
- x-content-type-options
- nosniff
- referrer-policy
- strict-origin-when-cross-origin
- Web and application architecture
- Next.js and TypeScript implementation
- Cloudflare edge deployment
- Performance and accessibility remediation
- Machine-readable publishing layer
An identity is a system, not a mark.
Typography, colour, design tokens and interface foundations, documented so the identity survives contact with a second implementer.
Delivered as production tokens and documentation, not as static artwork. Naming, positioning and messaging strategy are outside this scope.
- Inter Tight
- Display
- Inter
- Reading
- Geist
- Interface
- Geist Mono
- Evidence
- Canvas
- Muted
- Ink
- Terracotta
- Signal
- Identity and typographic systems
- Design tokens and interface foundations
- Component and pattern documentation
- Motion and interaction principles
Turn intent into work that can be shown to be finished.
Workflows, internal tools, approvals and evidence records, with authority held outside the runtime that executes.
Deterministic functions are the default. Constrained agents and isolated runtimes are introduced only where the workload requires them.
- Authority01
- Capability02
- Runtime03
- Evidence04
- Workflow and approval architecture
- Internal tools and typed integrations
- Publishing and document pipelines
- Execution and completion records
System Diagnostic and Manual Remediation Brief
The entry point to every engagement. A manual assessment of the current system, delivered as a prioritised remediation brief that names the implementation path and the verification method for each finding.
- Fee
- AUD $499 net
- Delivery
- 72 hours
- Model
- Fixed scope · Direct principal delivery · Retained engagements by qualification
Questions worth asking first.
Hourly billing makes the studio’s efficiency your cost. Engagements are scoped and priced in writing against acceptance criteria, so the investment is known before work begins.
Yes, and most engagements begin that way. The diagnostic establishes what is failing on the current system before anything is proposed; remediation in place is preferred to re-platforming where the evidence supports it.
It is the diagnostic method inside digital infrastructure: whether a public system can be found, parsed, attributed and trusted by retrieval and answer systems. The Machine Surface Inspector measures the public conditions; the principal assesses the rest.
Yes, as bounded systems. Authority, capability scope and evidence are kept outside the execution runtime, so an agent cannot expand its own permissions or verify its own work.