Lab

The lab is my problem-and-solution space: problems I actually care about, responses I can defend, and artifacts that still earn their keep. Each entry ties pressure to design to outcome so you can judge the substance, not just the headline.

Architectural

Anvil · Operator-directed evolution harness

Passive harness for system evolution: fixed State, Transformation, and Event primitives, event-sourced CDE projections, BCS verdict pulls, operator-gated insufficiency handling, and monotonic reconciliation with late evidence.

Problem

Evolution tooling tends to blur execution, planning, verification, and agency until the system appears to decide for itself and the audit trail stops explaining why work changed.

Value

A clean execution surface where intentional change remains human-directed, evidence stays external and typed, and every projection can be reconstructed from canonical events.

ArchitectureEvent SourcingSpecification & VerificationConformance TestingGovernanceSystems Thinking
Trace problem to value →
Architectural

DDD Software Factory

Governed pipeline from domain model to code: DDD visualizer, 140+ structural diagnostics, canonical export, and a projector with conformance and adoption-drift tracking.

Problem

Teams treat code as truth while the domain model goes stale; manual translation from modeling to schemas and types loses alignment and is impossible to verify at scale.

Value

A working closed loop (model → diagnose → project → conform → observe) so structural intent stays authoritative and drift becomes visible before it ships.

Domain-Driven DesignArchitectureConformance TestingGovernanceMicroservices
Trace problem to value →
Engineering

BCS · Behavioral Constraint Surface

Unified model for requirements as behavioral constraints (π, ω, φ, κ, s): continuous constraint surface, .bcs DSL, typed observation adapters, explicit temporality, from documentation to systemic diagnostics and CI gates.

Problem

Functional vs non-functional taxonomies fracture cross-cutting expectations; verification timing and tooling differ by label so the specification layer stops matching the system.

Value

A single spine from intent to measurement: progressive automation without rewriting constraints, and explicit handles for systemic diagnostics where capabilities overlap.

ArchitectureSpecification & VerificationObservabilityConformance TestingCompliance
Trace problem to value →
Strategic

Capability-Driven Evolution

Framework for intentional system evolution: formal drivers, value dimensions with anchored scores, capability state spaces, resource-bounded iterations, derived costs from unique transitions, and full reconciliation when delivery diverges from plan.

Problem

Roadmaps list features and dates but hide why trade-offs were made; work drifts from stakeholder intent and teams cannot reconstruct decisions months later.

Value

A traceable spine from need to capability motion to budget: Agile-compatible for execution, explicit for prioritization and audit.

StrategyGovernanceAgile DeliverySystems ThinkingArchitectureLeadership
Trace problem to value →
Strategic

Initiatives · Shared vehicles for change

Reframe committed work as Initiatives: the Vehicle (Mission, Territory, Team), epistemic lifecycle, scale-aware governance, Driver-led accountability, lifecycle-bound artifacts, decision logs, dictionary of intent, and kickoff protocols, for alignment on a shared goal instead of project theater.

Problem

“Project” framing implies fixed paths and passive resources; real work navigates fog while language drifts so stakeholders never argue about the same object.

Value

A vocabulary and ritual set where strategic alignment means the same Mission, the same boundary, and traceable bets, with lineage to DDD, DRI, Lean Startup, systems thinking, and Auftragstaktik.

StrategyLeadershipGovernanceMission CommandLean StartupSystems ThinkingDomain-Driven Design
Trace problem to value →
Strategic

Wardley Mapping · Value chain guide

Practitioner guide to situational awareness: doctrine, decision-bounded research questions, anchors and value chains, evolution as a 0–1 continuum with methodology fit, bounded-context bridge, team cultures, strategic gameplay, and career as a first map, with link to the full Intelligence.Space guide.

Problem

Strategy debates stay personal when mental models stay private; build-vs-buy and refactor decisions default to slogans without a shared picture of how components evolve.

Value

A repeatable way to externalize the landscape so teams argue about the diagram and connect Wardley’s evolution axis to delivery and ownership choices.

StrategyWardley MappingSystems ThinkingDomain-Driven DesignArchitectureAgile Delivery
Trace problem to value →