Factory documentation

Start with the root README to run Factory.

Current implementation

• Architecture: system boundaries, flows, contracts, security, limits, and source map.
• Local guide: build, configure, start, delegate, and troubleshoot.
• Worker contract: identity, runtimes, claiming, process safety, and worktree cleanup.
• Remote VM Workers: TLS listener, one-time enrollment, authentication, and reconnect behavior.
• Tasks and Runs: implemented authoring, manual and scheduled Runs across repositories, lifecycle, and migration decisions.
• Release guide: install, verify, upgrade, roll back, reproduce, and publish tagged releases.
• Changelog: user-visible changes and compatibility notes.
• Security policy: reporting and the current trust model.
• Contributing: setup, checks, and pull request standards.

Project operations

• Repository best-practices setup: pasteable prompt for a safe, documented, agent-ready GitHub repository.
• Issue-tracker setup: pasteable prompt for issue forms, labels, and a GitHub Project delivery board.

Active design work

• Agent-directed software factory: proposed work-item queue, repository fleet Runs, agent update capability, and first useful CLI.
• Cloud Run agent backend: proposed elastic, API-backed execution alongside persistent local and VM Workers.
• Software Factory vision: product thesis, scope, principles, and measures of progress.

Design records and superseded proposals

• Scheduled Automations: superseded operator guide for removed Definitions, Automations, and Definition Runs.
• Product model upgrade: completed migration record for converting supported legacy Definitions and Runs into the current model.
• External GitHub ingest: replaced by control-plane typed Automations, then superseded by the target architecture.
• Retired GitHub webhook settings: upgrade note for the webhook listener removed with Definitions and Automations.
• Reusable workflows and automations: design record for the implemented Workflow and typed Automation slices; superseded by Tasks and Runs.
• Coding automation experience: implemented Runbook-first UX record, superseded by Tasks and Runs.
• Unified CLI: useful process-boundary record whose resource names and command contract are superseded by the agent-directed target design.

Current behavior belongs in the root ARCHITECTURE.md. Proposed behavior belongs in a focused design until it is implemented.