Successor: new method and setup work is maintained in arcitai/factory, using T3 Code, native harnesses and GitHub. This repository and its releases remain available for existing installations and historical evidence. Installation cutover is qualified separately; this notice does not migrate or stop a running service.
Software & Defence. A method, a project Inbox, and your native coding agent.
Factory connects a repository's issues to a separately configured native coding agent. Keep the familiar list, Kanban, filters and issue detail; let the native agent run the work and GitHub handle issues, pull requests and CI. Published by Arcitai.
- Foundation: guidance to prepare a project, its execution host and access.
- ADLC skills: portable triage, specification, implementation, review, security and evaluation instructions, adopted under the project's own vision.
- Inbox: repository issues, explicit Start and Continue, native status/results and issue creation using the repository's templates. Harness usage shows native account limits without turning token estimates into charges.
- Small CLI and bridge: setup, native login, diagnostics, the same operations as the Inbox, and pinned Linux user-service startup.
Factory does not run another agent loop, queue, execution database or scheduler. The supported integrations are Codex and Claude Code on Linux with GitHub. Other harnesses and hosts need their own qualified integration; the method can be used independently.
Install the native-only 0.18 release through its explicit migration channel:
npm install --global factory-software-defence@next
factory help
factory foundationFor occasional use, npm exec --package=factory-software-defence@next -- factory help.
The package name is factory-software-defence; its commands include factory
and factory-software-defence. If the former npm package owns a global factory
command, follow the explicit package switch
before installing. Do not overwrite that command with --force.
Follow setup to select a native harness and prepare a project Inbox.
Existing installations must follow migration; old histories
stay outside the current package and are never automatically converted into work.
For method-only use, run factory kit --output ./factory-kit and review
adoption before merging any files into an application.
The dashboard and CLI share one small bridge. It delegates to the selected harness and issue provider, keeping their protocols out of the UI. Native history is the execution record; Factory retains only issue associations and operation receipts needed to avoid duplicate work. There is no Factory transcript database.
The versioned ADLC lifecycle catalog is the single source for default repository phases, label identities and semantic presentation. The bridge and Inbox share a pure projection; GitHub source phase and native execution state remain separate.
A completed agent turn needs checks and independent review. It is not automatic acceptance, merge or deployment. The project vision bounds improvements.
| Path | Responsibility |
|---|---|
.agents/skills/ |
Contributor/setup guidance, including Factory Foundation |
adlc/ |
Portable method and six canonical skills |
bin/ |
Small operator CLI and composition of supported integrations |
factory/ |
Native bridge, issue integration and packaged UI assets |
dashboard/ |
Inbox source and interaction tests |
docs/ |
Setup, architecture, interfaces, migration and recovery |
scripts/, tests/ |
Package checks and focused behavioral regressions |
Documentation · Contributing · Security · Current work
MIT for original code and method. Retained components and fonts are covered by third-party notices.