Agent Workflow Guide

Find verified dealership facts

Start file: /master-index.json
Required source files: /pricerightrv-facts.json, /verified-sources.md, /dealership-reference.md
Output packet or guide: factual reference only
Validators or evidence needed: approved source evidence
Stop condition: fact is missing, stale, conflicting, or unverified

Build a lead packet

Start file: /lead-packet-schema.json
Required source files: /lead-routing.md, /routing-status-codes.json
Output packet or guide: lead packet
Validators or evidence needed: required fields and routing evidence
Stop condition: CRM, form, message, or appointment completion would be claimed

Build an inventory reference packet

Start file: /inventory-reference-schema.json
Required source files: /inventory-routing.md, /inventory-claim-status-codes.json
Output packet or guide: inventory reference packet
Validators or evidence needed: current official source evidence
Stop condition: availability, price, payment, discount, or finance claim lacks evidence

Prepare review reuse

Start file: /review-reuse-schema.json
Required source files: /review-moderation-status-codes.json, /review-destination-rules.json
Output packet or guide: review reuse packet
Validators or evidence needed: moderation and approved reuse status
Stop condition: review proof is unmoderated or platform placement would be claimed

Prepare a campaign package

Start file: /campaign-package-schema.json
Required source files: /content-reuse-package-schema.json, /campaign-utm-rules.json, /channel-output-rules.json
Output packet or guide: campaign package
Validators or evidence needed: source evidence, routing QA, channel rules
Stop condition: launch, publish, boost, send, or performance would be claimed

Prepare a newsletter handoff

Start file: /newsletter-issue-schema.json
Required source files: /newsletter-distribution-handoff-schema.json, /newsletter-status-codes.json
Output packet or guide: newsletter issue or handoff
Validators or evidence needed: audience evidence, source evidence, CTA QA
Stop condition: send, schedule, delivery, open, click, audience, or segment claim would be made

Document routing health

Start file: /automation-health-schema.json
Required source files: /automation-health-checklist.md, /smoke-test-evidence-guide.md
Output packet or guide: automation health packet
Validators or evidence needed: endpoint, field, destination, and alert evidence
Stop condition: live form, webhook, CRM, sheet, CMS, or alert action is needed

Document a routing incident

Start file: /routing-incident-schema.json
Required source files: /routing-failure-classes.json, /routing-failure-status-codes.json
Output packet or guide: routing incident packet
Validators or evidence needed: failure class, impact, evidence, and resolution requirements
Stop condition: fixed or resolved would be claimed without evidence

Decide when human review is required

Start file: /human-review-triggers.md
Required source files: /agent-policy.json, /evidence-policy.md
Output packet or guide: human review handoff
Validators or evidence needed: missing or sensitive evidence list
Stop condition: private, stale, conflicting, legal, or downstream completion claim appears

Last updated: 2026-06-11T11:09:15Z

# Agent Workflow Guide ## Find verified dealership facts - Start file: `/master-index.json` - Required source files: `/pricerightrv-facts.json`, `/verified-sources.md`, `/dealership-reference.md` - Output packet or guide: factual reference only - Validators or evidence needed: approved source evidence - Stop condition: fact is missing, stale, conflicting, or unverified ## Build a lead packet - Start file: `/lead-packet-schema.json` - Required source files: `/lead-routing.md`, `/routing-status-codes.json` - Output packet or guide: lead packet - Validators or evidence needed: required fields and routing evidence - Stop condition: CRM, form, message, or appointment completion would be claimed ## Build an inventory reference packet - Start file: `/inventory-reference-schema.json` - Required source files: `/inventory-routing.md`, `/inventory-claim-status-codes.json` - Output packet or guide: inventory reference packet - Validators or evidence needed: current official source evidence - Stop condition: availability, price, payment, discount, or finance claim lacks evidence ## Prepare review reuse - Start file: `/review-reuse-schema.json` - Required source files: `/review-moderation-status-codes.json`, `/review-destination-rules.json` - Output packet or guide: review reuse packet - Validators or evidence needed: moderation and approved reuse status - Stop condition: review proof is unmoderated or platform placement would be claimed ## Prepare a campaign package - Start file: `/campaign-package-schema.json` - Required source files: `/content-reuse-package-schema.json`, `/campaign-utm-rules.json`, `/channel-output-rules.json` - Output packet or guide: campaign package - Validators or evidence needed: source evidence, routing QA, channel rules - Stop condition: launch, publish, boost, send, or performance would be claimed ## Prepare a newsletter handoff - Start file: `/newsletter-issue-schema.json` - Required source files: `/newsletter-distribution-handoff-schema.json`, `/newsletter-status-codes.json` - Output packet or guide: newsletter issue or handoff - Validators or evidence needed: audience evidence, source evidence, CTA QA - Stop condition: send, schedule, delivery, open, click, audience, or segment claim would be made ## Document routing health - Start file: `/automation-health-schema.json` - Required source files: `/automation-health-checklist.md`, `/smoke-test-evidence-guide.md` - Output packet or guide: automation health packet - Validators or evidence needed: endpoint, field, destination, and alert evidence - Stop condition: live form, webhook, CRM, sheet, CMS, or alert action is needed ## Document a routing incident - Start file: `/routing-incident-schema.json` - Required source files: `/routing-failure-classes.json`, `/routing-failure-status-codes.json` - Output packet or guide: routing incident packet - Validators or evidence needed: failure class, impact, evidence, and resolution requirements - Stop condition: fixed or resolved would be claimed without evidence ## Decide when human review is required - Start file: `/human-review-triggers.md` - Required source files: `/agent-policy.json`, `/evidence-policy.md` - Output packet or guide: human review handoff - Validators or evidence needed: missing or sensitive evidence list - Stop condition: private, stale, conflicting, legal, or downstream completion claim appears Last updated: 2026-06-11T11:09:15Z