# How Code Factory Works

## Concept illustrations

These owner-supplied concept illustrations explain the proof-first workflow.
They are not UI screenshots or measured outcome evidence. For the literal
product demonstration, use the [exact shipped UI quick start](https://github.com/zrk222/code-factory/releases/download/v0.17.1/code-factory-quickstart-v0171.mp4).

### 1. From idea to blueprint

![Developer sends an application blueprint through a small factory into code, data, interface, and server components.](assets/how-it-works/01-idea-to-blueprint.png)

Turn intent into an explicit, reviewable product blueprint before implementation begins.

### 2. Shape the product

![Developer turns an application blueprint into folders, a database, a web interface, and servers.](assets/how-it-works/02-prd-to-product-shape.png)

Bind requirements to a concrete product shape, target, and dependency order.

### 3. Compile recurring decisions

![An illustrated stack links an AI brain to Python gears and a locked execution box.](assets/how-it-works/03-ai-compiler-stack.png)

Move repeated decision logic into deterministic, inspectable code with explicit boundaries.

### 4. Apply security contracts

![Robotic arms inspect and stamp shields onto contract documents.](assets/how-it-works/04-security-contracts.png)

Make trust, identity, and release-policy expectations explicit and reviewable.

### 5. Keep authority bounded

![A robotic arm places keyhole plates onto identity cards moving along a conveyor.](assets/how-it-works/05-governed-access.png)

Separate workflow evidence from credentials, deployment, publication, and approval authority.

### 6. Challenge the gate

![Robotic magnifiers inspect green checks and a deliberately broken check.](assets/how-it-works/06-proof-by-sabotage.png)

Deliberately break the control and require the validator to catch the failure.

### 7. Route failures back

![Robotic drills break a mobile interface while failed test samples collect beside it.](assets/how-it-works/07-failure-feedback.png)

Attribute failures to the earliest responsible stage and preserve concrete evidence.

### 8. Link signed proof

![Signed receipts move through a glowing chain and split into accepted and rejected paths.](assets/how-it-works/08-signed-proof-chain.png)

Hash-link reviewed artifacts and receipts while failed evidence remains visibly rejected.

### 9. Release after proof

![A team celebrates as a verified rocket, green check, and secured folder leave the factory.](assets/how-it-works/09-verified-release.png)

Ship only after the required gates pass and the human-controlled release boundary is satisfied.

The ordered filenames, dimensions, SHA-256 digests, alt text, and captions are
bound in [`manifest.json`](assets/how-it-works/manifest.json).
