# Solo Company OS Delivery Guide

> How the operating model ships work and evidence.

## Delivery Pipeline

```
Request → Intake → Diagnose → Plan → Execute → Verify → Deliver
```

Each phase produces visible, reviewable output. Nothing ships without evidence.

## What Gets Delivered

| Asset | Format | Purpose |
|---|---|---|
| Working code or prototype | Source + build | Functional deliverable |
| Evidence report | Markdown | What changed, why, how it was verified |
| Test results | CLI output | Proof that verification ran |
| Risk register | Markdown | Known issues, blockers, and mitigations |
| Handoff notes | Markdown | Context for continuation or review |

## Delivery Rules

1. **No evidence, no delivery.** Every deliverable includes a verification trail.
2. **Owner review is mandatory.** No automated push to production or client.
3. **Scope is explicit.** What is in scope and what is not, stated in writing before execution begins.
4. **Rollback is defined.** Every delivery includes a way to undo or revert.
5. **Static proof stays live.** Public proof assets remain accessible after delivery.

## How a Typical Engagement Works

### Step 1: Request
The founder or client describes what they need in plain language.

### Step 2: Intake
Scope, constraints, expected deliverables, and timeline are captured in a Markdown task ticket.

### Step 3: Diagnose
Signals, risks, blockers, and dependencies are reviewed before any work begins.

### Step 4: Plan
Work is organized into reviewable steps with clear acceptance criteria.

### Step 5: Execute
Implementation happens locally. Tests, notes, and evidence accumulate alongside code.

### Step 6: Verify
Evidence, reports, and test output confirm what changed and why it works.

### Step 7: Deliver
The client receives the agreed asset pack: code, evidence, test results, and handoff notes.

## Evidence Format

Every delivery includes a closeout report:

```text
Verdict:        PASS / BLOCK
Changed files:  list
Tests run:      count + result
Risks:          list
Rollback:       command or steps
```

## What This Is Not

- Not a project management tool with dashboards and logins
- Not a freelancer marketplace
- Not an automated code generator
- Not a replacement for human judgment

## Contact

Review the public proof site and the delivery assets, then decide whether the operating discipline fits your work.