An observable software factory

Keeping the machinery running.

Eight products. A workforce of software agents. One human operator.

Woodhouse keeps the record. What was built, what was proved, and what reality still has to settle.
An original editorial illustration of a composed steward in an archive looking out to a busy operations floor.Office copy · 01
WOODHOUSE / THE STEWARD'S OFFICEA visual metaphor, not a live view
PORTFOLIO READOUT · reviewed 28 September 2026GITHUB REMAINS THE ENGINEERING SOURCE OF TRUTH
01 / The factory floor

Different work.
Different finish lines.

Eight projects enter the same factory and expose different limits. This is a dated operator-reviewed readout, not a stream of invented Git events.

Enter the factory
What the record saysSource: The shareable factory SITREP supplied for the Woodhouse launch.
“Does it work?” is increasingly not the problem.The hard question is whether it feels finished, survives qualification, reaches production or works in the physical world.
01BubblesGame systems · deterministic playBubbles is a polished arcade game with a serious deterministic core. Its remaining work is concentrated in the connected product experience, broad browser qualification and owner acceptance.Final convergence02FighterGame systems · authored journeysFighter has grown into a deep game with Story, Tournament, Battle, Arcade, Survival, Daily Challenges and progression. The work now is to make the complete experience earn an A+.A+ convergence03SHOALSHOTGame systems · mobile-first presentationSHOALSHOT is a richly developed fishing game whose recent work spans presentation, performance, responsive play and qualification.Release convergence04Protocol 11Game systems · responsive table playProtocol 11 has mature game systems and a substantially recovered frontend, including better mobile, table and tablet composition.Qualification and tracker reconciliation05MAXAssistive technology · software and hardwareMAX is an assistive-technology project with a substantial software platform: PWA, pairing, gateway, offline behaviour, remote FIND and STOP, privacy and device control.Physical proof required06PiratesGame reconstruction · source archaeologyPirates is rebuilding Master of the Secret Sea from original source evidence. The work is deliberately parity-first.Gate B locked07LoftwahFMMusic platform · listener and venue productLoftwahFM is already a substantial working music product. The larger business-music roadmap adds a second, broader product with venue reliability, control and operations still to build.Parked against the larger roadmap08Social ClubHospitality · membership experienceSocial Club has a functional foundation for a private-club and hospitality experience.Parked

Snapshot boundary: reviewed 28 September 2026. The underlying GitHub repositories are private; public entries summarise the shareable factory report and do not expose issue or pull request content.

02 / The operating model

A green build is one kind of proof.

The factory keeps implementation, review, production and physical use as separate observations. The evidence comes back to the record.

PLATE 01THE FACTORY REMEMBERS28.09.26
From intent to evidenceA reviewed request moves through agent work, qualification and release. A separate reality check observes the software in use and returns evidence to the factory.01 / REQUESTHumanIntent & authority02 / DECOMPOSEAgentsBounded work03 / QUALIFYReviewEvidence & judgement04 / RELEASEProductionExact state05 / REALITYUse it. Observe.Physical proof when the work leaves a screen.A SOFTWARE FACTORY IS A SYSTEM FOR TURNING INTENT INTO OBSERVABLE OUTCOMES.EVIDENCE RETURNS TO THE RECORDWOODHOUSE TECHNICAL PLATE · 01NOT ALL PROOF IS SOFTWARE
Every stage makes a different claim.Implementation does not stand in for release. Release does not stand in for physical proof.
  1. 01 · HumanSets intent and authority.
  2. 02 · AgentsComplete bounded work.
  3. 03 · ReviewChallenges the change against evidence and judgement.
  4. 04 · ProductionPublishes the exact qualified state.
  5. 05 · RealityObserves use and returns evidence to the factory.

Founding essay

I Didn't Mean to Build a Software Factory

A practical habit of composing tools grew into a system for directing software agents, checking their work and seeing what survived in the real world.

Read the founding essay
Woodhouse's illustrated archive and operations floor.
Origin recordIllustrative scene

A note from Dean

I didn't mean to build a software factory.

I started by gluing websites together with plugins. The useful skill was knowing what did each job well and not rebuilding capability that already existed.

The tools changed. APIs, cloud services, infrastructure, models, skills and agents started doing more of the work. Then the work spread across several products at once.

Meet the operator
03 / Agent Reception

A public entrance for people and agents.

Project facts are available as a bounded, dated record. The endpoint is designed to answer factual questions without handing an agent private access or write authority.

Report to Agent Reception

Is Pirates ready for its procedural fork?

No. The 28 September report says the parity gate is still locked. Expansion is waiting for source-backed reconstruction.

GET /agents/facts.json

pirates
state: Gate B locked
parity-first: true
procedural-fork: not approved
reviewed: 2026-09-28