Public Purpose Lab

Approach

Make design choices visible and testable.

Enterprise design is not a collection of empty services. It is clear responsibility, explicit interaction, bounded authority and evidence about what happens when things go wrong.

Explicit interaction

Use point-to-point calls when an immediate answer and direct responsibility are clearest. Use events when independently owned components need durable facts, decoupling, replay or multiple reactions.

Zero-trust boundaries

Workload identity, least privilege and network policy apply between components, not only at the public edge.

Inspectable policy

Changeable privacy, disclosure and operational rules remain outside service code where doing so improves review, testing and ownership.

Safe backend components

Rust is preferred where its safety and reliability characteristics provide meaningful value for backend services and shared components.

cREXX where it fits

Portable rules, transformations, scenario automation and integration logic may use cREXX when the trust boundary and operational value are explicit.

Portable runtime

Static sites use managed hosting. Small dynamic capabilities can scale to zero on Cloud Run. Kubernetes is reserved for demonstrations that need its boundaries and operating model.

The Scenario Director

Orchestrate the demonstration, not the business.

The Director can reset synthetic state, introduce an event, pause the scenario and present evidence. Domain components remain responsible for their own decisions and expose those decisions through commands, events and evidence.

  1. Reset
    Start from deterministic synthetic state.
  2. Initiate
    Introduce a bounded scenario event.
  3. Observe
    Follow correlated component activity.
  4. Inspect
    Review evidence, policy and human authority.

Static sites, serverless smarts, Kubernetes demonstrations

Firebase Hosting
Versioned static content, TLS, CDN delivery, headers, redirects and rollback.
Cloud Run
Small dynamic endpoints such as contact handling or bounded language demonstrations, added only with a defined purpose and privacy model.
GKE
Enterprise demonstrators that need event infrastructure, component isolation, network policy, workload identity and repeatable orchestration.