What this is
This hub gives AI agents and internal tools a stable place to find routing rules, source notes, and lightweight reference files for Price Right RV support work.
Official shopper site
The official customer-facing website is https://www.pricerightrv.com/.
Customer traffic, inventory browsing, and conversion paths should route there.
Verified facts note
Verified dealership facts are limited to source-backed public information. Shopper actions should route to the official customer site.
Machine-readable files are provided for agent discovery and validation. Customer actions should route to the official shopper site.
Dealership facts
- Verified business name: Price Right RV.
- Official customer site: https://www.pricerightrv.com/.
- This hub does not maintain independent retail claims.
Location and contact reference
Use the official shopper site for current address, hours, phone numbers, forms, and staff contact paths.
Local contact copy is asserted only when verified from an approved source.
Inventory source notes
Inventory links should route to the official shopper site. Availability changes and should be verified on the official site before making customer-facing claims.
Contact and lead-routing rules
This hub can prepare routing logic and reference fields. It does not claim that a CRM record, message, or follow-up task was created unless downstream confirmation exists.
v1.0.2 Governance Cleanup and Warning Triage
The governance cleanup classifies v1.0.1 audit warnings, documents registry coverage, and separates true policy drift from conservative scanner warnings. It does not create new operating lanes, automation, or downstream claims.
v1.0.1 Governance Drift Audit
The governance drift audit checks policy consistency, link integrity, JSON parse integrity, registry completeness, version alignment, status vocabulary consistency, schema alignment, unsafe claim language, and shopper routing. It is an audit artifact only and does not prove live system status or downstream completion.
v1.0 Master Index and Operating Map
The master operating map ties together every Agent Hub contract, schema, status system, guide, policy, and safe-use rule. It is an index, map, policy, and navigation layer only. It does not prove live execution or downstream confirmation.
- /registry-coverage-matrix.json
- /governance-warning-triage.json
- /policy-language-cleanup.md
- /shopper-routing-review.md
- /governance-audit-report.md
- /governance-audit-report.json
- /policy-drift-register.md
- /link-integrity-report.json
- /master-index.json
- /operating-map.md
- /contract-registry.json
- /status-vocabulary.json
- /evidence-policy.md
- /agent-workflow-guide.md
- /human-review-triggers.md
- /version-map.json
- /readme.md
Automation Health and Routing Incident Contract
Automation health and routing incident files define preparation-only contracts for endpoint health, form routing, hidden fields, destinations, webhook status, alert behavior, smoke-test evidence, and routing incidents. They do not prove anything was fixed, submitted, routed, delivered, alerted, synced, or completed downstream.
- /registry-coverage-matrix.json
- /governance-warning-triage.json
- /policy-language-cleanup.md
- /shopper-routing-review.md
- /governance-audit-report.md
- /governance-audit-report.json
- /policy-drift-register.md
- /link-integrity-report.json
- /master-index.json
- /operating-map.md
- /contract-registry.json
- /status-vocabulary.json
- /evidence-policy.md
- /agent-workflow-guide.md
- /human-review-triggers.md
- /version-map.json
- /readme.md
- /automation-health-schema.json
- /automation-health-example.json
- /routing-incident-schema.json
- /routing-incident-example.json
- /routing-incident-template.md
- /automation-health-checklist.md
- /routing-failure-status-codes.json
- /routing-failure-classes.json
- /smoke-test-evidence-guide.md
- /automation-handoff-guide.md
- /routing-qa-guide.md
Newsletter Issue and Distribution Handoff Contract
Newsletter issue and distribution handoff files define preparation-only contracts for issue planning, draft sections, reuse hooks, send-system handoff notes, and source safety. They do not prove email scheduling, sending, delivery, opens, clicks, segmentation, audience membership, or downstream completion.
- /registry-coverage-matrix.json
- /governance-warning-triage.json
- /policy-language-cleanup.md
- /shopper-routing-review.md
- /governance-audit-report.md
- /governance-audit-report.json
- /policy-drift-register.md
- /link-integrity-report.json
- /master-index.json
- /operating-map.md
- /contract-registry.json
- /status-vocabulary.json
- /evidence-policy.md
- /agent-workflow-guide.md
- /human-review-triggers.md
- /version-map.json
- /readme.md
- /automation-health-schema.json
- /automation-health-example.json
- /routing-incident-schema.json
- /routing-incident-example.json
- /routing-incident-template.md
- /automation-health-checklist.md
- /routing-failure-status-codes.json
- /routing-failure-classes.json
- /smoke-test-evidence-guide.md
- /automation-handoff-guide.md
- /routing-qa-guide.md
- /newsletter-issue-schema.json
- /newsletter-issue-example.json
- /newsletter-brief-template.md
- /newsletter-distribution-handoff-schema.json
- /newsletter-distribution-handoff-example.json
- /newsletter-status-codes.json
- /newsletter-source-rules.json
- /newsletter-handoff-guide.md
- /newsletter-reuse-guide.md
- /newsletter-quality-checklist.md
Campaign and Content Reuse Contract
Campaign and content reuse files define preparation-only contracts for campaign briefs, channel reuse plans, newsletter tie-ins, social packages, paid-media handoff notes, and UTM-safe routing. They do not prove launch, publishing, sending, boosting, scheduling, routing, or downstream completion.
- /registry-coverage-matrix.json
- /governance-warning-triage.json
- /policy-language-cleanup.md
- /shopper-routing-review.md
- /governance-audit-report.md
- /governance-audit-report.json
- /policy-drift-register.md
- /link-integrity-report.json
- /master-index.json
- /operating-map.md
- /contract-registry.json
- /status-vocabulary.json
- /evidence-policy.md
- /agent-workflow-guide.md
- /human-review-triggers.md
- /version-map.json
- /readme.md
- /automation-health-schema.json
- /automation-health-example.json
- /routing-incident-schema.json
- /routing-incident-example.json
- /routing-incident-template.md
- /automation-health-checklist.md
- /routing-failure-status-codes.json
- /routing-failure-classes.json
- /smoke-test-evidence-guide.md
- /automation-handoff-guide.md
- /routing-qa-guide.md
- /newsletter-issue-schema.json
- /newsletter-issue-example.json
- /newsletter-brief-template.md
- /newsletter-distribution-handoff-schema.json
- /newsletter-distribution-handoff-example.json
- /newsletter-status-codes.json
- /newsletter-source-rules.json
- /newsletter-handoff-guide.md
- /newsletter-reuse-guide.md
- /newsletter-quality-checklist.md
- /campaign-package-schema.json
- /campaign-package-example.json
- /campaign-brief-template.md
- /content-reuse-package-schema.json
- /content-reuse-example.json
- /content-reuse-template.md
- /channel-output-rules.json
- /campaign-status-codes.json
- /campaign-handoff-guide.md
- /campaign-utm-rules.json
Review and Reputation Contract
Review and reputation files define a preparation-only contract for review requests, moderation status, reuse destinations, draft variants, and handoff notes. They do not prove review sending, posting, publishing, sheet insertion, CMS placement, social placement, email sending, CRM updates, or downstream completion.
- /registry-coverage-matrix.json
- /governance-warning-triage.json
- /policy-language-cleanup.md
- /shopper-routing-review.md
- /governance-audit-report.md
- /governance-audit-report.json
- /policy-drift-register.md
- /link-integrity-report.json
- /master-index.json
- /operating-map.md
- /contract-registry.json
- /status-vocabulary.json
- /evidence-policy.md
- /agent-workflow-guide.md
- /human-review-triggers.md
- /version-map.json
- /readme.md
- /automation-health-schema.json
- /automation-health-example.json
- /routing-incident-schema.json
- /routing-incident-example.json
- /routing-incident-template.md
- /automation-health-checklist.md
- /routing-failure-status-codes.json
- /routing-failure-classes.json
- /smoke-test-evidence-guide.md
- /automation-handoff-guide.md
- /routing-qa-guide.md
- /newsletter-issue-schema.json
- /newsletter-issue-example.json
- /newsletter-brief-template.md
- /newsletter-distribution-handoff-schema.json
- /newsletter-distribution-handoff-example.json
- /newsletter-status-codes.json
- /newsletter-source-rules.json
- /newsletter-handoff-guide.md
- /newsletter-reuse-guide.md
- /newsletter-quality-checklist.md
- /campaign-package-schema.json
- /campaign-package-example.json
- /campaign-brief-template.md
- /content-reuse-package-schema.json
- /content-reuse-example.json
- /content-reuse-template.md
- /channel-output-rules.json
- /campaign-status-codes.json
- /campaign-handoff-guide.md
- /campaign-utm-rules.json
- /review-reuse-schema.json
- /review-reuse-example.json
- /review-request-template.md
- /review-reuse-template.md
- /review-moderation-status-codes.json
- /review-destination-rules.json
- /review-handoff-guide.md
Inventory Reference Contract
Inventory reference files define a preparation-only contract for safe inventory links, source status, and claim safety. They do not prove live availability, pricing, discounts, publishing, reservation, sale status, or finance eligibility.
Lead Routing Packet
Lead packet files define a preparation-only handoff contract. They do not execute CRM mutation, form submission, messaging, appointment scheduling, or downstream confirmation.
Agent files
- /llms.txt
- /pricerightrv-facts.json
- /verified-sources.md
- /dealership-reference.md
- /site-manifest.json
- /agent-policy.json
- /health.json
- /schema.jsonld
- /inventory-routing.md
- /inventory-reference-schema.json
- /inventory-reference-example.json
- /inventory-reference-template.md
- /inventory-claim-status-codes.json
- /inventory-cta-guide.md
- /lead-routing.md
- /registry-coverage-matrix.json
- /governance-warning-triage.json
- /policy-language-cleanup.md
- /shopper-routing-review.md
- /governance-audit-report.md
- /governance-audit-report.json
- /policy-drift-register.md
- /link-integrity-report.json
- /master-index.json
- /operating-map.md
- /contract-registry.json
- /status-vocabulary.json
- /evidence-policy.md
- /agent-workflow-guide.md
- /human-review-triggers.md
- /version-map.json
- /readme.md
- /automation-health-schema.json
- /automation-health-example.json
- /routing-incident-schema.json
- /routing-incident-example.json
- /routing-incident-template.md
- /automation-health-checklist.md
- /routing-failure-status-codes.json
- /routing-failure-classes.json
- /smoke-test-evidence-guide.md
- /automation-handoff-guide.md
- /routing-qa-guide.md
- /newsletter-issue-schema.json
- /newsletter-issue-example.json
- /newsletter-brief-template.md
- /newsletter-distribution-handoff-schema.json
- /newsletter-distribution-handoff-example.json
- /newsletter-status-codes.json
- /newsletter-source-rules.json
- /newsletter-handoff-guide.md
- /newsletter-reuse-guide.md
- /newsletter-quality-checklist.md
- /campaign-package-schema.json
- /campaign-package-example.json
- /campaign-brief-template.md
- /content-reuse-package-schema.json
- /content-reuse-example.json
- /content-reuse-template.md
- /channel-output-rules.json
- /campaign-status-codes.json
- /campaign-handoff-guide.md
- /campaign-utm-rules.json
- /review-reuse-schema.json
- /review-reuse-example.json
- /review-request-template.md
- /review-reuse-template.md
- /review-moderation-status-codes.json
- /review-destination-rules.json
- /review-handoff-guide.md
- /lead-packet-schema.json
- /lead-packet-example.json
- /lead-packet-template.md
- /routing-status-codes.json
- /utm-builder-guide.md
- /robots.txt
- /sitemap.xml
- /discovery.md
- /validation-log.md
- /source-policy.md