Production system

Build systems that build systems.

The sXs factory turns intent into operable software, then retains the capabilities that make the next build stronger.

Definition

A factory is a real operating model, not a speed metaphor.

sXs combines repeatable inputs, composable production, model-driven execution, independent verification, and compounding output.

The factory does not make every product identical. It gives unlike products a disciplined way to move from intention to release while retaining the parts of production knowledge that deserve to travel.

The production rail

Specify. Generate. Verify. Ship. Compound.

Every stage has a concrete output and a visible human responsibility. Models accelerate work; they do not inherit accountability.

  1. 01

    Specify

    What must be true?

    Turn product intent into constraints, interfaces, acceptance criteria, and consequential decisions.

    Output
    Specifications · ADRs · schemas · tests
    Human role
    Set intent and approve irreversible choices.
  2. 02

    Generate

    Where does synthesis help?

    Use models and specialized agents for exploration, implementation, transformation, and documentation.

    Output
    Working changes · options · documentation
    Human role
    Bound the task and select the useful direction.
  3. 03

    Verify

    What evidence decides?

    Build, test, inspect, and review generated work against the intended product behavior.

    Output
    Builds · tests · evals · reviews
    Human role
    Own quality, risk, and release judgment.
  4. 04

    Ship

    Can someone use and own it?

    Release operable software with documentation, deployment, and a clear maintenance path.

    Output
    Products · releases · runbooks
    Human role
    Accept the release and remain accountable for it.
  5. 05

    Compound

    What should the next build inherit?

    Convert repeated knowledge into capabilities, templates, components, and decision patterns.

    Output
    Skills · harnesses · reusable systems
    Human role
    Choose what deserves to become shared infrastructure.

Symbolic

What the system must preserve.

  • Specifications and acceptance criteria
  • Types, schemas, and contracts
  • Tests, builds, and release gates
  • Architecture decisions and ownership
s×s

Subsymbolic

Where synthesis creates leverage.

  • Exploration and alternative generation
  • Bounded implementation work
  • Pattern recognition across a codebase
  • Transformation and draft documentation

symbolic × subsymbolic

The seam is a production decision.

Human judgment places the boundary, defines the evidence, and owns the release. Stable decisions move into deterministic infrastructure; model judgment stays where interpretation is useful.

Factory Ledger

Compounding is recorded only when reuse is visible.

The ledger stays deliberately small. A retained capability earns an entry when a later build or production system demonstrably uses it.

BuildShipped outputCapability retainedReused byEvidence
ADR PowerPortable ADR creation and maintenance capabilityCanonical ADR knowledge artifactKanon / Context BazaarInspect ↗
Byron PowersLiterary and publishing workflow libraryEight domain capability familiesKanon Byron Powers collectionInspect ↗

Anti-promises

What the factory will not pretend.

  • No instant-app claim. Ambitious products still contain decisions, unknowns, and integration work.
  • No unsupported “10×.” Velocity claims require a defined baseline and evidence from comparable work.
  • No unaccountable autonomy. Consequential boundaries and release decisions retain a named human owner.
  • No reuse for its own sake. Unlike products are not forced into a shared platform merely to make the ledger longer.