Operating Map

The Agent Hub organizes preparation, reference, validation, and handoff artifacts. It does not prove downstream execution.

What this hub is

The Price Right Digital Agent Hub is an agent utility layer at https://agent.pricerightdigital.com/ for contracts, schemas, guides, policies, status vocabularies, and evidence rules.

What this hub is not

It is not the customer website, CRM, CMS, email platform, Google Sheet, Apps Script, webhook system, inventory feed, review platform, social scheduler, paid media account, or alerting system.

Official customer destination

The official customer-facing destination is https://www.pricerightrv.com/. Shopper-facing CTAs must route there or to exact official shopper pages.

Core policies

Start with /master-index.json, /agent-policy.json, /source-policy.md, and /evidence-policy.md.

Verified facts

Use /pricerightrv-facts.json, /verified-sources.md, and /dealership-reference.md. Do not invent dealership facts.

Lead routing lane

Use lead packet files to prepare handoff packets only. Do not claim CRM mutation, form submission, message send, appointment creation, or routing completion.

Inventory reference lane

Use inventory reference files for preparation and routing. Do not claim availability, pricing, payment, discounts, condition, feed status, or finance outcomes without current approved evidence.

Review and reputation lane

Use review files only with moderation and approved reuse status. Unmoderated reviews are planning-only.

Campaign and content reuse lane

Use campaign and content reuse files to draft channel variants and handoffs. Do not claim launch, posting, boost, send, CMS update, conversion, or performance.

Newsletter lane

Use newsletter files to prepare issue plans and distribution handoff notes. Do not claim send, schedule, delivery, open, click, audience membership, segmentation, or completion.

Automation and routing QA lane

Use automation and routing incident files to document evidence, risks, and handoffs. Do not infer routing success from a page load.

Machine-readable trust layer

Use /site-manifest.json, /health.json, /contract-registry.json, /status-vocabulary.json, and /master-index.json.

Status and evidence rules

Status labels do not prove live system state. Evidence must match the exact claim.

Downstream completion rules

Downstream completion requires confirmation from the destination system. Draft packets and handoffs are not completion.

Recommended agent workflow

  1. Start with master index and evidence policy.
  2. Choose the narrowest lane-specific contract.
  3. Check verified sources and required validators.
  4. Prepare packet or guide output.
  5. Stop before live execution unless explicitly approved and evidenced.

Last updated

2026-06-11T11:09:15Z

# Operating Map

The Agent Hub organizes preparation, reference, validation, and handoff artifacts. It does not prove downstream execution.

## What this hub is

The Price Right Digital Agent Hub is an agent utility layer at https://agent.pricerightdigital.com/ for contracts, schemas, guides, policies, status vocabularies, and evidence rules.

## What this hub is not

It is not the customer website, CRM, CMS, email platform, Google Sheet, Apps Script, webhook system, inventory feed, review platform, social scheduler, paid media account, or alerting system.

## Official customer destination

The official customer-facing destination is https://www.pricerightrv.com/. Shopper-facing CTAs must route there or to exact official shopper pages.

## Core policies

Start with `/master-index.json`, `/agent-policy.json`, `/source-policy.md`, and `/evidence-policy.md`.

## Verified facts

Use `/pricerightrv-facts.json`, `/verified-sources.md`, and `/dealership-reference.md`. Do not invent dealership facts.

## Lead routing lane

Use lead packet files to prepare handoff packets only. Do not claim CRM mutation, form submission, message send, appointment creation, or routing completion.

## Inventory reference lane

Use inventory reference files for preparation and routing. Do not claim availability, pricing, payment, discounts, condition, feed status, or finance outcomes without current approved evidence.

## Review and reputation lane

Use review files only with moderation and approved reuse status. Unmoderated reviews are planning-only.

## Campaign and content reuse lane

Use campaign and content reuse files to draft channel variants and handoffs. Do not claim launch, posting, boost, send, CMS update, conversion, or performance.

## Newsletter lane

Use newsletter files to prepare issue plans and distribution handoff notes. Do not claim send, schedule, delivery, open, click, audience membership, segmentation, or completion.

## Automation and routing QA lane

Use automation and routing incident files to document evidence, risks, and handoffs. Do not infer routing success from a page load.

## Machine-readable trust layer

Use `/site-manifest.json`, `/health.json`, `/contract-registry.json`, `/status-vocabulary.json`, and `/master-index.json`.

## Status and evidence rules

Status labels do not prove live system state. Evidence must match the exact claim.

## Downstream completion rules

Downstream completion requires confirmation from the destination system. Draft packets and handoffs are not completion.

## Recommended agent workflow

1. Start with master index and evidence policy.
2. Choose the narrowest lane-specific contract.
3. Check verified sources and required validators.
4. Prepare packet or guide output.
5. Stop before live execution unless explicitly approved and evidenced.

## Last updated

2026-06-11T11:09:15Z