# Progress

**Last Updated:** harness seed (no deliverable produced yet)
**Current Objective:** stand up the harness and prove the anti-theater gate holds.
**Recommended Next Step:** pick the first feature (any of the six deliverable types
have no dependency blockers except `journey-map`, which depends on `automation-spec`)
and produce a real artifact into `workspace/`.

## Master
**crm-automator** — CRM Automation & Orchestration
Manual: `MANUAL.md` (10 sections, 6 rubric'd deliverable types, 9 playbooks)
Workspace: `workspace/`

## Feature sequence
automation-spec, lead-scoring-model, segmentation-plan, pipeline-audit,
integration-runbook → (no deps, any order) → journey-map (needs at least one
automation-spec to reference in its trigger inventory).

## Last verified
`./init.sh` — **PASS**. Anti-theater gate holds: all 6 files in `samples/good/`
(one per deliverable type) pass `verify_crm_automation.py`; all 6 files in
`samples/bad/` (deliberately broken, one per type) fail it on the named checks.
Verified 2026-07-12 via `./init.sh` (exit 0).

## Next step
1. Choose a feature (`automation-spec` is the natural first pick — it's also a
   dependency of `journey-map`).
2. Read the relevant playbook(s) in `playbooks/` for the named school/style.
3. Write `workspace/<feature-id>-<name>.md` with `Deliverable-Type: <id>` on line 1.
4. Run `python3 verify_crm_automation.py workspace/<file>.md` until it exits 0.
5. Re-run `./init.sh` to confirm no regression.
6. Mark the feature `done` in `feature_list.json` with the exact verify command as
   `evidence`, then update this file.

## Blockers
None. Harness is scaffolded and gate-verified; no deliverable work started yet.

## Log
- (seed) Harness built: AGENTS.md, feature_list.json (6 features = 6 deliverable
  types), init.sh, verify_crm_automation.py (full rubric linter, all 6 types),
  samples/good/*.md (6, one per type, all pass), samples/bad/*.md (6, one per
  type, each deliberately broken on named checks, all fail). `./init.sh` verified
  green. 9 playbooks written under `playbooks/` per MANUAL.md §6.