The workbench

Things I’m building, questions I’m testing, and work you can inspect.

Independent project · public repository

NOID — making digital work inspectable.

A human-readable design language for digital work, with a public contract and a synthetic example you can inspect.

This is early-stage independent work—not a deployed customer system.

Explore the public project

Questions behind the work

01Building / Models / prototyping

Agent-to-agent trust

Exploring what trust means when one agent discovers, delegates to or relies on another: identity, scope, evidence, bounded autonomy, challenge and containment.

TrustIdentityMulti-agent

QUESTION

What evidence should one agent require before accepting another agent’s identity, delegated authority or result?

EVIDENCE STATUSPublic-safe summary

Trust-boundary models, lifecycle controls, prototypes and documented experiments are in active development. Public artefacts will be linked when cleared.

RECORD REVIEWED 27 July 2026 / BUILD → OBSERVE → CHALLENGE → REFINE

02Building / Specified / prototyped

Hybrid enterprise

Designing the operating model around people, AI agents, automation platforms and managed services: where work lands, how accountability moves and how capability grows rather than hollows out.

PeopleAgentsOperations

QUESTION

What must change when software becomes a participant in work?

EVIDENCE STATUSPublic-safe summary

Operating patterns and control-surface prototypes exist; implementation detail remains private while the thesis is refined.

RECORD REVIEWED 27 July 2026 / BUILD → OBSERVE → CHALLENGE → REFINE

03Iterating / Active design practice

POC to production

Turning emerging capability into something an enterprise can buy, own and operate: product architecture, service design, economics, readiness and lifecycle.

InnovationProductManaged services

QUESTION

What has to exist around a prototype before anyone can depend on it?

EVIDENCE STATUSMethod / public summary

This is a repeatable method rather than a single project: readiness frameworks, service-design patterns and explicit maturity states.

RECORD REVIEWED 27 July 2026 / BUILD → OBSERVE → CHALLENGE → REFINE

04Iterating / Built / iterating

Research intelligence

Repeatable ways to move from a question to evidence, challenge and a human-owned decision. Less confident theatre; more traceable judgement.

EvidenceChallengeDecisions

QUESTION

How do we make reasoning inspectable without outsourcing judgement?

EVIDENCE STATUSBuilt / public-safe summary

A method was built, its first pilot was rejected for product fit, and a narrower prototype was retained. Detailed artefacts remain private.

RECORD REVIEWED 27 July 2026 / BUILD → OBSERVE → CHALLENGE → REFINE

The work behind the claims

Some work is public; some remains private. Each entry says what can be inspected and what it does—and does not—demonstrate.