Skip to content
ScrutableEvidence-native product studioDiscuss a system

Inside Scrutable · Labs/Internal

The Factory

The Factory is Scrutable Labs Internal's recursive meta-product surface for software production: the coordinated people, agents, doctrine, tools, records, runtimes, and release controls used to decide, build, verify, operate, and improve Scrutable work.

Not a fifth arm · not a Works project

The Factory lives in Scrutable Labs Internal. It is not a fifth arm and is not itself a Scrutable Works project. Its named, separable software components may be Works projects, while the aggregate Factory remains a Labs Internal meta-product surface that can support work across Scrutable.

2 operating halves

production

Production — make it

Turn goals and approved work into tested, reviewable, releasable artifacts.

  • plan
  • coordinate
  • build
  • verify
  • integrate
  • promote
  • operate

market-and-iteration

Market and iteration — ship, learn, improve

Publish and deploy work, observe real outcomes, route evidence and opportunities, and deliberately pace the next improvements.

  • publish
  • deploy
  • monetize
  • listen
  • measure
  • prioritize
  • improve

6-step operating cycle

  1. 01 · Direction

    Institutional goals, arm-specific mandates, research, user needs, and observed opportunities define candidate work.

  2. 02 · Selection and pacing

    Canonical goals, evidence, dependencies, authority, risk, and capacity determine what is released from the backlog.

  3. 03 · Production

    Agents and tools execute bounded work through versioned repositories, controlled identities, and explicit coordination.

  4. 04 · Verification

    Logic, regression, and low-context WF testing produce evidence; human or perceptual claims use Auditions when required.

  5. 05 · Promotion

    Accepted changes pass authority and shipping gates before merge, deployment, or live installation.

  6. 06 · Operation and learning

    Live state, incidents, receipts, outcomes, corrections, and user response become durable evidence for the next cycle.

6 Factory planes

desired-state

Desired-state plane

Versioned goals, doctrine, policy, specifications, registries, and build recipes.

evidence-and-context

Evidence and context plane

Durable source records, observed world state, memory, provenance, generated indexes, and read projections.

coordination-and-execution

Coordination and execution plane

Idempotent assignments, outbox/inbox coordination, bounded workers, retries, receipts, and compensations.

authority-and-access

Authority and access plane

Identity isolation, scoped capabilities, standing policy, human gates, secrets boundaries, approvals, and revocation.

verification-and-promotion

Verification and promotion plane

Logic, regression, WF, audit evidence, release gates, merge truth, live artifact identity, and rollback.

read-and-command

Read and command plane

A truthful living map of the Factory plus a small command surface that dispatches work but does not become the worker.

Recursive property

Some Works projects are also Factory machinery. The Factory uses projects such as ExecOS, Antechamber, Codex Agent Link, SwiftRelay, Swift WF Testing, and Auditions to build and improve those projects and other Scrutable work.

Source
registry/factory.json
Schema
v1
Publication status
published
Institutional home
Labs/Internal