TODO
pillar one
TODO: e.g. tooling & workflow design — the registries, scripts, and conventions that make the factory repeatable.
Capability / Software Factory
TODO: 1-2 sentence pitch on what a "software factory" engagement gets a client — a repeatable, AI-assisted system for shipping software, not a one-off build.
File a feature request, get a ticket and an ETA, and come back to a deployed test environment — on loop.
What it is
From raw idea to shipped software, every time.
A feature request, bug report, or new idea comes in.
Scoped into bounded units of work with clear acceptance criteria.
AI agents write the code in isolated, parallel work lanes.
Automated tests and deterministic gates check every change.
Merged, deployed, and live — ready to use.
TODO: define "software factory" in MeshCrawler's own words.
TODO: paragraph on the problem this solves — e.g. teams that ship AI prototypes but can't turn them into a durable, repeatable engineering practice.
TODO: paragraph connecting this to Yesod, the software factory Stephen built and runs at yesod.work, as the reference implementation clients can learn from or adapt.
See Yesod in actionThe pillars
TODO: one-line framing for how these pillars fit together.
TODO: e.g. tooling & workflow design — the registries, scripts, and conventions that make the factory repeatable.
TODO: e.g. agent orchestration — how AI agents are put to work inside the practice, safely and consistently.
TODO: e.g. knowledge capture — turning tribal knowledge into durable, queryable memory for the team and its agents.
TODO: e.g. governance & guardrails — the review, security, and quality practices that keep speed from becoming risk.
How it works
TODO: short paragraph on the engagement shape (timeline, format, who's involved).
Talk through your setupTODO: audit current tooling, workflows, and team practices.
TODO: stand up the factory's tooling, agents, and conventions.
TODO: train the team and leave a self-sustaining practice behind.