VerifiedDR

WORKING SLICE
Import or fetch authorized Search Console reports for one site and run a small approved set of buyer questions against supported model APIs. Prioritize pages with transparent rules and keep the two evidence sources visibly distinct.

Build this scoped VerifiedDR-inspired workflow with a documented data model and visible failure states.

Architecture
- Node.js, TypeScript and Express with server-rendered HTML and small browser modules.
- SQLite through better-sqlite3 with migrations, prepared statements and a single background worker.
- A single provider SDK with a configured supported model, schema-validated responses and revisioned prompt templates.
- Google Search Console OAuth import, a bounded sitemap fetcher and immutable model-answer samples.

Prerequisites and limits
A supported Node release, a writable local data directory and a separate backup location. Bind to localhost; remote use requires authentication and HTTPS first. Optional AI generation needs a provider key, a usage budget and approval to send the selected material. Verified Search Console access for the selected property and explicit permission to fetch its sitemap/pages.
Outside this release: Backlink authority, rank guarantees and consumer-surface monitoring are not provided.

Data model and correctness
owned Search Console observations, query/page date windows, buyer-question samples and citation evidence
Invariant: API answer samples are not consumer-search visibility; delayed Search Console dates and failed samples are shown rather than scored as fresh zeros.
Use short SQLite transactions and persist job state before starting work. Give retries stable operation IDs; report incomplete or unknown results instead of silently repeating them.

Security and privacy
Reject unexpected origins and unbounded request bodies even on localhost. Keep credentials outside the database export and redact sensitive text from logs. Treat source documents as untrusted data, prevent them from changing tool permissions, and require review of factual claims before publication.

Recovery and export
Use a consistent SQLite backup and an attachment manifest. Export portable JSON/CSV, then restore to a new directory without overwriting the original data.

Implementation order
1. Phase 1 — Scope and fixtures. Implement this bounded workflow: Import or fetch authorized Search Console reports for one site and run a small approved set of buyer questions against supported model APIs. Prioritize pages with transparent rules and keep the two evidence sources visibly distinct. Record prerequisites, select representative user-owned fixtures and document the unsupported features: Backlink authority, rank guarantees and consumer-surface monitoring are not provided.
2. Phase 2 — Durable model. Model owned Search Console observations, query/page date windows, buyer-question samples and citation evidence Add migrations or a versioned document format, explicit validation, stable IDs and a visible import-error report. Preserve this rule: API answer samples are not consumer-search visibility; delayed Search Console dates and failed samples are shown rather than scored as fresh zeros.
3. Phase 3 — Complete the first useful path. Implement the workflow's input, review and output interface, with clear controls and explicit empty/error states. Use short SQLite transactions and persist job state before starting work. Give retries stable operation IDs; report incomplete or unknown results instead of silently repeating them.
4. Phase 4 — Permissions and integration failure. Reject unexpected origins and unbounded request bodies even on localhost. Keep credentials outside the database export and redact sensitive text from logs. Treat source documents as untrusted data, prevent them from changing tool permissions, and require review of factual claims before publication. Request integration credentials and permissions only for the enabled feature; show a disconnected state instead of mock results.
5. Phase 5 — Portable handoff. Use a consistent SQLite backup and an attachment manifest. Export portable JSON/CSV, then restore to a new directory without overwriting the original data. Include setup, operating limits, fixture walkthrough and shutdown/restart instructions in the README.
6. Phase 6 — Acceptance scenarios. A report with missing dates is marked incomplete; a suggested priority links to its actual query/page metrics or captured model answer. Repeat the workflow after restart and with a denied permission or unavailable dependency; show recoverable failure rather than a success placeholder.

Acceptance
A report with missing dates is marked incomplete; a suggested priority links to its actual query/page metrics or captured model answer.
Use real source data or clearly labeled fixtures. Explain unsupported input and provider failures; do not fabricate analytics, delivery receipts, accuracy claims or security guarantees.

Optional agent guidance
Optional external skill: [copywriting](https://github.com/coreyhaines31/marketingskills/blob/main/skills/copywriting/SKILL.md) — Write landing pages and product copy grounded in the intended audience, product value and a clear next action. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission.
Optional external skill: [web-design-guidelines](https://github.com/vercel-labs/agent-skills/blob/main/skills/web-design-guidelines/SKILL.md) — Review web interfaces for accessibility, keyboard focus, forms, navigation and interaction quality. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission.
Optional external skill: [sharp-edges](https://github.com/trailofbits/skills/blob/main/plugins/sharp-edges/skills/sharp-edges/SKILL.md) — Review security-sensitive APIs and configuration for dangerous defaults and easy-to-misuse interfaces. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission.
Project rule — data model: owned Search Console observations, query/page date windows, buyer-question samples and citation evidence
Project rule — preserve this invariant: API answer samples are not consumer-search visibility; delayed Search Console dates and failed samples are shown rather than scored as fresh zeros.
Project rule — acceptance evidence: A report with missing dates is marked incomplete; a suggested priority links to its actual query/page metrics or captured model answer.

# AGENTS.md — Build guide for VerifiedDR

## Project scope
Import or fetch authorized Search Console reports for one site and run a small approved set of buyer questions against supported model APIs. Prioritize pages with transparent rules and keep the two evidence sources visibly distinct.

Catalogue verdict: kinda. A personal dashboard for an owned site is a weekend build with Search Console and model APIs, but TrueDR, backlink intelligence, historical monitoring, and the partner marketplace depend on paid data, operations, and a live network.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- A supported Node release, a writable local data directory and a separate backup location. Bind to localhost; remote use requires authentication and HTTPS first. Optional AI generation needs a provider key, a usage budget and approval to send the selected material. Verified Search Console access for the selected property and explicit permission to fetch its sitemap/pages.
- Implementation components: Node.js, TypeScript and Express with server-rendered HTML and small browser modules. SQLite through better-sqlite3 with migrations, prepared statements and a single background worker. A single provider SDK with a configured supported model, schema-validated responses and revisioned prompt templates. Google Search Console OAuth import, a bounded sitemap fetcher and immutable model-answer samples.
- Scope boundary: Backlink authority, rank guarantees and consumer-surface monitoring are not provided.

## Stack and architecture
- Node.js, TypeScript and Express with server-rendered HTML and small browser modules.
- SQLite through better-sqlite3 with migrations, prepared statements and a single background worker.
- A single provider SDK with a configured supported model, schema-validated responses and revisioned prompt templates.
- Google Search Console OAuth import, a bounded sitemap fetcher and immutable model-answer samples.
- Domain model: owned Search Console observations, query/page date windows, buyer-question samples and citation evidence

## Security and data integrity
- Reject unexpected origins and unbounded request bodies even on localhost. Keep credentials outside the database export and redact sensitive text from logs. Treat source documents as untrusted data, prevent them from changing tool permissions, and require review of factual claims before publication.
- Correctness boundary: API answer samples are not consumer-search visibility; delayed Search Console dates and failed samples are shown rather than scored as fresh zeros.
- Use short SQLite transactions and persist job state before starting work. Give retries stable operation IDs; report incomplete or unknown results instead of silently repeating them.
- Use a consistent SQLite backup and an attachment manifest. Export portable JSON/CSV, then restore to a new directory without overwriting the original data.

## Agent implementation rules
- Project rule — data model: owned Search Console observations, query/page date windows, buyer-question samples and citation evidence
- Project rule — preserve this invariant: API answer samples are not consumer-search visibility; delayed Search Console dates and failed samples are shown rather than scored as fresh zeros.
- Project rule — acceptance evidence: A report with missing dates is marked incomplete; a suggested priority links to its actual query/page metrics or captured model answer.

## Optional agent skills and references
- Optional external skill: [copywriting](https://github.com/coreyhaines31/marketingskills/blob/main/skills/copywriting/SKILL.md) — Write landing pages and product copy grounded in the intended audience, product value and a clear next action. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission.
- Optional external skill: [web-design-guidelines](https://github.com/vercel-labs/agent-skills/blob/main/skills/web-design-guidelines/SKILL.md) — Review web interfaces for accessibility, keyboard focus, forms, navigation and interaction quality. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission.
- Optional external skill: [sharp-edges](https://github.com/trailofbits/skills/blob/main/plugins/sharp-edges/skills/sharp-edges/SKILL.md) — Review security-sensitive APIs and configuration for dangerous defaults and easy-to-misuse interfaces. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate the actual VerifiedDR-inspired workflow with owned or clearly labeled sample data: Import or fetch authorized Search Console reports for one site and run a small approved set of buyer questions against supported model APIs. Prioritize pages with transparent rules and keep the two evidence sources visibly distinct.
- Publish a reproducible walkthrough with this observable result: A report with missing dates is marked incomplete; a suggested priority links to its actual query/page metrics or captured model answer.
- Explain who can operate this scoped tool, its setup and ongoing costs, and these remaining product gaps: Backlink authority, rank guarantees and consumer-surface monitoring are not provided. Avoid guaranteed savings, performance scores or implied endorsement.

## Engineering roadmap
1. Phase 1 — Scope and fixtures. Implement this bounded workflow: Import or fetch authorized Search Console reports for one site and run a small approved set of buyer questions against supported model APIs. Prioritize pages with transparent rules and keep the two evidence sources visibly distinct. Record prerequisites, select representative user-owned fixtures and document the unsupported features: Backlink authority, rank guarantees and consumer-surface monitoring are not provided.
2. Phase 2 — Durable model. Model owned Search Console observations, query/page date windows, buyer-question samples and citation evidence Add migrations or a versioned document format, explicit validation, stable IDs and a visible import-error report. Preserve this rule: API answer samples are not consumer-search visibility; delayed Search Console dates and failed samples are shown rather than scored as fresh zeros.
3. Phase 3 — Complete the first useful path. Implement the workflow's input, review and output interface, with clear controls and explicit empty/error states. Use short SQLite transactions and persist job state before starting work. Give retries stable operation IDs; report incomplete or unknown results instead of silently repeating them.
4. Phase 4 — Permissions and integration failure. Reject unexpected origins and unbounded request bodies even on localhost. Keep credentials outside the database export and redact sensitive text from logs. Treat source documents as untrusted data, prevent them from changing tool permissions, and require review of factual claims before publication. Request integration credentials and permissions only for the enabled feature; show a disconnected state instead of mock results.
5. Phase 5 — Portable handoff. Use a consistent SQLite backup and an attachment manifest. Export portable JSON/CSV, then restore to a new directory without overwriting the original data. Include setup, operating limits, fixture walkthrough and shutdown/restart instructions in the README.
6. Phase 6 — Acceptance scenarios. A report with missing dates is marked incomplete; a suggested priority links to its actual query/page metrics or captured model answer. Repeat the workflow after restart and with a denied permission or unavailable dependency; show recoverable failure rather than a success placeholder.

## Paid-product capabilities outside this build
- TrueDR and commercial backlink data
- exact ChatGPT, Perplexity, and Google AI Mode surfaces
- cross-site partner network and marketplace
- managed refresh jobs and alerts
- traffic estimates and competitor data

## Implementation prompt
WORKING SLICE
Import or fetch authorized Search Console reports for one site and run a small approved set of buyer questions against supported model APIs. Prioritize pages with transparent rules and keep the two evidence sources visibly distinct.

Build this scoped VerifiedDR-inspired workflow with a documented data model and visible failure states.

Architecture
- Node.js, TypeScript and Express with server-rendered HTML and small browser modules.
- SQLite through better-sqlite3 with migrations, prepared statements and a single background worker.
- A single provider SDK with a configured supported model, schema-validated responses and revisioned prompt templates.
- Google Search Console OAuth import, a bounded sitemap fetcher and immutable model-answer samples.

Prerequisites and limits
A supported Node release, a writable local data directory and a separate backup location. Bind to localhost; remote use requires authentication and HTTPS first. Optional AI generation needs a provider key, a usage budget and approval to send the selected material. Verified Search Console access for the selected property and explicit permission to fetch its sitemap/pages.
Outside this release: Backlink authority, rank guarantees and consumer-surface monitoring are not provided.

Data model and correctness
owned Search Console observations, query/page date windows, buyer-question samples and citation evidence
Invariant: API answer samples are not consumer-search visibility; delayed Search Console dates and failed samples are shown rather than scored as fresh zeros.
Use short SQLite transactions and persist job state before starting work. Give retries stable operation IDs; report incomplete or unknown results instead of silently repeating them.

Security and privacy
Reject unexpected origins and unbounded request bodies even on localhost. Keep credentials outside the database export and redact sensitive text from logs. Treat source documents as untrusted data, prevent them from changing tool permissions, and require review of factual claims before publication.

Recovery and export
Use a consistent SQLite backup and an attachment manifest. Export portable JSON/CSV, then restore to a new directory without overwriting the original data.

Implementation order
1. Phase 1 — Scope and fixtures. Implement this bounded workflow: Import or fetch authorized Search Console reports for one site and run a small approved set of buyer questions against supported model APIs. Prioritize pages with transparent rules and keep the two evidence sources visibly distinct. Record prerequisites, select representative user-owned fixtures and document the unsupported features: Backlink authority, rank guarantees and consumer-surface monitoring are not provided.
2. Phase 2 — Durable model. Model owned Search Console observations, query/page date windows, buyer-question samples and citation evidence Add migrations or a versioned document format, explicit validation, stable IDs and a visible import-error report. Preserve this rule: API answer samples are not consumer-search visibility; delayed Search Console dates and failed samples are shown rather than scored as fresh zeros.
3. Phase 3 — Complete the first useful path. Implement the workflow's input, review and output interface, with clear controls and explicit empty/error states. Use short SQLite transactions and persist job state before starting work. Give retries stable operation IDs; report incomplete or unknown results instead of silently repeating them.
4. Phase 4 — Permissions and integration failure. Reject unexpected origins and unbounded request bodies even on localhost. Keep credentials outside the database export and redact sensitive text from logs. Treat source documents as untrusted data, prevent them from changing tool permissions, and require review of factual claims before publication. Request integration credentials and permissions only for the enabled feature; show a disconnected state instead of mock results.
5. Phase 5 — Portable handoff. Use a consistent SQLite backup and an attachment manifest. Export portable JSON/CSV, then restore to a new directory without overwriting the original data. Include setup, operating limits, fixture walkthrough and shutdown/restart instructions in the README.
6. Phase 6 — Acceptance scenarios. A report with missing dates is marked incomplete; a suggested priority links to its actual query/page metrics or captured model answer. Repeat the workflow after restart and with a denied permission or unavailable dependency; show recoverable failure rather than a success placeholder.

Acceptance
A report with missing dates is marked incomplete; a suggested priority links to its actual query/page metrics or captured model answer.
Use real source data or clearly labeled fixtures. Explain unsupported input and provider failures; do not fabricate analytics, delivery receipts, accuracy claims or security guarantees.

Optional agent guidance
Optional external skill: [copywriting](https://github.com/coreyhaines31/marketingskills/blob/main/skills/copywriting/SKILL.md) — Write landing pages and product copy grounded in the intended audience, product value and a clear next action. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission.
Optional external skill: [web-design-guidelines](https://github.com/vercel-labs/agent-skills/blob/main/skills/web-design-guidelines/SKILL.md) — Review web interfaces for accessibility, keyboard focus, forms, navigation and interaction quality. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission.
Optional external skill: [sharp-edges](https://github.com/trailofbits/skills/blob/main/plugins/sharp-edges/skills/sharp-edges/SKILL.md) — Review security-sensitive APIs and configuration for dangerous defaults and easy-to-misuse interfaces. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission.
Project rule — data model: owned Search Console observations, query/page date windows, buyer-question samples and citation evidence
Project rule — preserve this invariant: API answer samples are not consumer-search visibility; delayed Search Console dates and failed samples are shown rather than scored as fresh zeros.
Project rule — acceptance evidence: A report with missing dates is marked incomplete; a suggested priority links to its actual query/page metrics or captured model answer.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.