All chapters
  1. Start hereA software factory, from first principles
  2. Primitive · 1A factory, before AI: input, transformation, check, output
  3. Primitive · 2From repetition to a pattern: what stays, what varies, what to leave alone
  4. Primitive · 3The specification as an executable contract
  5. Primitive · 4Build the smallest factory: four stations, two specs, one manifest
  6. Primitive · 5Assembly stations: typed contracts, owners and failure handling
  7. Primitive · 6AI enters the factory: what a model adds, and what stays deterministic
  8. WatchAlgo · 7The WatchAlgo production story: what the repository shows
  9. WatchAlgo · 8A problem as a production unit: the files one unit must contain
  10. WatchAlgo · 9Station by station: description, solution, implementations, visualization
  11. WatchAlgo · 10The visualizer factory: from algorithm state to renderable steps
  12. WatchAlgo · 11Three flavors and three languages: two different contracts
  13. WatchAlgo · 12Looping over a large backlog: scheduling, limits and a failed-case queue
  14. WatchAlgo · 13Long-running agent execution: context, checkpoints and token limits
  15. WatchAlgo · 14Evidence of correctness: tests the producer cannot talk its way past
  16. WatchAlgo · 15The factory learning loop: defects change the pattern, not only the unit
  17. Enterprise · 16Classify the enterprise demand before choosing a pattern
  18. Enterprise · 17Reference enterprise patterns and their variation points
  19. Enterprise · 18Platform foundations: golden paths, templates, registries and catalogs
  20. Enterprise · 19Pattern versus configuration versus business logic
  21. Enterprise · 20Insurance factory, part 1: building the intake contract
  22. Enterprise · 21Insurance factory, part 2: building the underwriting workflow
  23. Enterprise · 22Insurance factory, part 3: trust and observability built in
  24. Enterprise · 23Data and integration engineering: contracts that survive change
  25. Enterprise · 24The CI/CD and deployment factory: from pull request to production
  26. Enterprise · 25Enterprise governance: owners, approved patterns and provenance
  27. Enterprise · 26Scaling safely: many teams, many agents, one set of boundaries
  28. Operations · 27Factory quality engineering: measuring accepted output, not activity
  29. Operations · 28Failure and recovery scenarios: what breaks a factory, and what restores it
  30. Operations · 29The landscape: which tool for which job, read from its own documentation
  31. Operations · 30Design an enterprise software factory: the blueprint and the rollout
  32. ReferenceSources and verification
  33. ReferenceGlossary
  34. AboutAbout this site
About

About this site

What this site is and is not, how the WatchAlgo case study was checked, the sister sites, the label convention, and what is original.

This site explains one idea and tests it from three sides. A software factory turns a reusable engineering pattern and an explicit product specification into independently tested software artifacts through governed, repeatable assembly stations. It starts with one function and four deterministic stations, reads the WatchAlgo repositories to see how far a repeated algorithm pattern was scaled, and then builds a synthetic insurance service the way an enterprise factory would, with contracts, authorization, release gates and owners.

What this site is, and what it is not#

IT IS
A map of production systems for software: specs, patterns, stations, gates, run records and feedback.
IT IS NOT
A promise that enterprise software ships in days, or a ranking of tools.
IT CHECKS
Every code claim by running it; every product claim against its own documentation, with a date.

It is a teaching map to adapt, not a standard. The chapter order follows the questions a team meets when it moves from doing one thing by hand to producing many similar things with checks: first the primitive, then a real case at scale, then the enterprise version, then measurement and design. The patterns, station graphs and simulators are the author's teaching reconstruction unless a page labels them otherwise.

How the WatchAlgo case study was checked#

WatchAlgo is the author's own algorithm-learning product, so it can be named and its repositories could be read. They were read, never changed: nothing in them was written, built, installed or deployed for this site. Every WatchAlgo statement on these pages carries one of three labels.

LabelWhat it meansExample
Observed in the repositoryA file, folder, field or commit that anyone with the repository can openthe three files inside each problem folder
Reported by the authorThe author's operational account, not measured here3,246 implemented problems; runs of 30 or more hours until token limits
Teaching reconstructionAn architecture this site proposes to explain the ideathe station map and Example B's toy unit

The full matrix, with paths and commits, is summarized on Sources and told as a story in the WatchAlgo chapter. Where the repository does not show something (for example the prompts or the run logs of the long sessions), the pages say so instead of filling the gap.

The insurance example is synthetic#

The enterprise chapters build a service for an insurer that sells commercial property insurance through brokers. This is an illustrative reconstruction for teaching. It follows the shape of a real project by the author, but the insurer, people, rules, fields and every number are invented, and nothing here reports the quality of a real system or model. In every example the model is a scripted stand-in, so the results show how the factory mechanics work, not how good any model is. Two sentences hold throughout: the factory builds the underwriting software but never makes an underwriting decision, and in the software it builds, the model recommends; a person decides.

The label convention#

Claims of different kinds are kept apart with a bold lead-in, so a reader always knows what kind of statement they are reading.

Lead-inUsed for
Observed in the repositoryWatchAlgo facts with a path and commit
Reported by the authorThe WatchAlgo operational account
Teaching reconstructionThis site's proposed design, toy or simulator
StandardWhat a standard or specification says, with version and date read
ProductWhat a product or open-source project documents, with date read
PatternA common practice that no standard requires
This site's recommendationThe author's advice, never presented as a standard
Simulated, illustrativeAny number from a lab or simulator

Sister sites#

This site is one of a series on AI-native engineering by the same author. Each owns one subject and links the others where they meet, instead of repeating them.

SiteWhat it owns
prompt.sammuthu.comInstructions: how they are written, composed and defended
context.sammuthu.comWhat the model can see now: selection, retrieval, budget
memory.sammuthu.comDurable information and saved execution state
a2a.sammuthu.comMessages between agents; A2A versus MCP
auth.sammuthu.comIdentity, delegation, enforcement and audit for every caller and every hop
guardrails.sammuthu.comEnforceable checks around a probabilistic agent
observe.sammuthu.comLogs, metrics, traces, audit events, replay
tools.sammuthu.comCallable capabilities: schema, execution, MCP tools
mcp.sammuthu.comShared capabilities across teams: when MCP is justified, identity, authorization, governance
rag.sammuthu.comRetrieval from SQL rows to production: embeddings, vector indexes, hybrid search, reranking
schema.sammuthu.comTyped contracts: shape, validation, repair, evolution
orchestrate.sammuthu.comThe control plane: what runs next
reliable.sammuthu.comAcceptable outcomes despite failures and load
harness.sammuthu.comThe runtime around a model call
eval.sammuthu.comMeasurement: graders, golden sets, release gates
factory.sammuthu.com (this site)Specs and reusable patterns turned into independently tested software through governed assembly stations
diff-to-deploy.sammuthu.comShipping a change with coding agents
ask-to-release.sammuthu.comPlanning a change before the first meeting

Three neighbours share the most ground with this site. Harness Engineering explains the controls around one agent's run; this site explains the production system that many such runs feed. Diff to Deploy follows one change from a diff to production; this site creates many products from a pattern and hands each one to that path. Evals for agentic software explains how to measure quality; this site invokes those measurements as gates and decides what advances.

What is original#

The chapter order, the examples, the simulators, the diagrams, the labs and the explanations are original to this site. Standards, product documentation and outside articles are cited and summarized in the site's own words, never copied; the dates they were read are on Sources. The WatchAlgo excerpts in the problem explorer come from the author's own repository and keep their file paths and commits.