Action Model / Resource rooms / vertical model
checkpoint 003 · inferred
AM-VERTICALS / detailed resource room

Every industry maps to the same operational spine.

Industry → department → job → atom → offer. The lane built the catalogue and crosswalk across all four axes, then held the result at inferred/unverified because catalogue labels are not authenticated Actionist execution.

17 industries12 teams66 use cases72 ideas62 edges
01 / Machine-checked inventory

The four-axis catalogue

Source: catalogue.json + status.json

17industries
12teams / departments
66use cases
72ideas
12reusable atoms
Strongest signal

High-value workflows repeat a low-level loop: intake → extract → decide → act → verify → report.

Finance and CRM have the strongest urgency/value but demand strict approval and read-back gates. Operations scores slightly lower but offers broader atom reuse and a safer first sandbox.

Evidence posture

  • Six use cases have first-party linked recipes; 60 are explicitly “Coming soon.”
  • No authenticated Actionist run or implementation was available to this lane.
  • All crosswalk edges are catalogue/inferred, not live/implemented.
  • No candidate repository is admitted here.
02 / Reusable atom contract

The twelve atoms beneath the verticals

Defined in atoms-001.json; reused across crosswalk batches.

intake

Capture the job

intake_normalize turns a request into a stable shape; triage_route chooses owner, queue, or path.

understand

Make it structured

extract_structure pulls fields from documents/messages; classify_prioritize turns signal into order.

move

Coordinate the work

follow_up_chase and schedule_coordinate keep the process alive across people and systems.

control

Keep state trustworthy

reconcile_audit checks records; monitor_alert watches thresholds and exceptions.

communicate

Close the loop

report_digest makes progress legible; sync_handoff gives the next owner a durable state.

authority

Require the right human

approval_publish gates irreversible outcomes; browser_data_entry handles legacy/UI-only surfaces under explicit authority.

03 / Crosswalk completion

What batch-003 actually added

41 missing idea IDs attached to explicit edges.

EdgesBusiness loopMonetisation eventAtom emphasis
E052–E053Acquire local client/audience → produce/maintain asset → approve → publish/report → renew.Retainer, qualified lead, campaign fee, commission.intake, extract, monitor, report, approval, handoff.
E054–E056Creative brief or reusable product → prepare/list → approve → deliver/support → refresh.Asset order, download purchase, membership, bundle.intake, extract, classify, chase, report, approval.
E057–E058Select niche/asset → research/list → monitor clicks/value → update or resell → reconcile.Affiliate click/sale, product margin, asset sale.extract, monitor, reconcile, report, browser.
E059–E060Acquire brief/file → extract → draft/coordinate → review/sign off → deliver/archive.Document fee, rush fee, concierge fee, referral.intake, extract, approval, chase, handoff, schedule.
E061–E062Capture request/theme → quote/draft → schedule/publish → monitor → repeat.Booked job, referral, royalty, publishing fee.intake, triage, schedule, reconcile, browser, approval.
Important: the crosswalk proves coverage of the catalogue IDs. It does not prove that Actionist currently runs these loops. Every edge is `capability_status: catalog`, `confidence: inferred`, `authenticated_live: false`, and `implemented: false`.
04 / Pilot archetypes

Three places to move from mapping to direct-source review

Scores are prioritisation signals, not customer validation.

28 / 35

Invoice-to-cash control

Finance-heavy document intake, extraction, follow-up, reconciliation, approval, and audit.

  • Strongest finance value.
  • Must define source of truth and allowed writes.
  • No production-write proof before direct review.
27 / 35

Request-to-dispatch desk

Operations intake, triage, schedule, chase, handoff, and exception reporting.

  • Broadest atom reuse.
  • Safest low-risk sandbox.
  • Good first synthetic-fixture candidate.
28 / 35

Lead-to-meeting pipeline

CRM/lead capture, qualification, follow-up, calendar coordination, consent, and read-back.

  • Strong value/frequency.
  • Outbound-send and opt-out controls mandatory.
  • CRM/calendar confirmation must be observed.
05 / Evidence shelf

Open the actual vertical work

Local source links are locked on the public host.

currentAM-VERTICALS current state

Inventory, evidence posture, strongest signal, blockers, and next direct-source gate.

Open CURRENT.md ↗
statusMachine status + counts

Coverage flags, inferred/implemented posture, blockers, and next queue.

Open status.json ↗
catalogueFull four-axis inventory

Industries, teams, use cases, ideas, and IDs used by the crosswalk.

Open catalogue.json ↗
atomsReusable atom definitions

Outcome, trigger, state, decision, side effect, authority, verification, recovery, audit.

Open atoms-001.json ↗
offersPilot offers

Ten candidate offers with job, metric, trigger, entities, blocks, and next gates.

Open pilot offers ↗
queueVertical bounded queue

Direct-source review and synthetic fixture next steps.

Open queue ↗
Local source readerfull text / JSON on demand
Choose a source above. The local reader loads the original artifact.