Public purpose before technology
Start with the service problem, the people affected and the outcome sought.
Purpose
Public-purpose organisations should be able to improve how work and information flow without losing control of their data, decisions or future to unaffordable or opaque technology.
Build open, trustworthy and demonstrable building blocks that help charities and public services:
Test whether a small team can apply enterprise discipline without enterprise bloat: clear ownership, event contracts, zero-trust boundaries, externalised policy, privacy by design, observable outcomes and repeatable assurance.
Success is not the number of components built. It is whether a demonstrator makes a meaningful organisational problem easier to understand, test and improve—and whether an informed outsider can inspect the evidence and reach their own conclusion.
Founding principles
Start with the service problem, the people affected and the outcome sought.
Publish reusable code and learning without exposing personal, confidential or security-sensitive material.
Assistance never silently acquires authority over consequential decisions.
Separate ideas, demonstrations, measurements and production-ready claims.
Services communicate through explicit commands, events and interfaces.
Purpose, minimisation, consent, retention and auditability belong in the design.
Select Rust, cREXX, Kubernetes and other tools for evidenced value, not identity.
Create the minimum complete path needed to answer a meaningful question.