anymorph 0.4.0 → 0.6.0

package/dist/skillpacks/geo/skills/seo-technical-diagnosis/references/checks.md

@@ -1,58 +0,0 @@
-# Technical Checks
-
-## Crawlability
-
-- `robots.txt` exists, parses, references sitemap, and does not block important
-  resources.
-- Search crawlers and AI crawlers are distinguished:
-  - Googlebot and Bingbot affect search indexing.
-  - GPTBot, ClaudeBot, PerplexityBot, ChatGPT-User, CCBot, Google-Extended, and
-    Bytespider affect AI discovery/training/browsing differently.
-- Key pages must be reachable within reasonable crawl depth.
-
-## Indexability
-
-- status code is 200 for canonical pages.
-- no accidental `noindex`.
-- canonical is present, stable, and not contradictory.
-- raw HTML and rendered DOM agree on canonical and robots directives.
-- duplicate or parameter URLs should resolve to canonical pages.
-
-## Sitemap
-
-- sitemap index and nested sitemaps parse.
-- only canonical, indexable, 200 URLs are included.
-- stale or orphan URLs are flagged.
-
-## JavaScript Rendering
-
-- title, meta description, canonical, robots, H1, primary content, and JSON-LD
-  should exist in initial HTML when possible.
-- non-200 pages must not rely on JS-injected SEO elements.
-- raw/rendered conflicts are high risk.
-
-## Structured Data
-
-- detect JSON-LD first, then microdata/RDFa when needed.
-- Organization, WebSite, BreadcrumbList, Article, Product, Offer, LocalBusiness,
-  and SoftwareApplication are common valid opportunities.
-- Do not recommend deprecated or ineligible rich-result schema for Google value.
-- Ecommerce Product schema belongs to ecommerce opportunity when product evidence
-  is needed.
-
-## Performance and Mobile
-
-- use INP, not FID.
-- LCP target: under 2.5s.
-- INP target: under 200ms.
-- CLS target: under 0.1.
-- field data beats lab data; absent field data is a limitation, not a failure.
-
-## Security and URL Structure
-
-- HTTPS enforced.
-- no mixed content.
-- no long redirect chains.
-- consistent trailing slash and host canonicalization.
-- descriptive URLs without unnecessary content query params.
-

package/dist/skillpacks/geo/skills/third-party-diagnosis/SKILL.md

@@ -1,54 +0,0 @@
----
-name: third-party-diagnosis
-description: Use when diagnosing third-party citation surfaces, external authority gaps, competitor presence on external sources, profile/listing opportunities, reviews, or social sentiment risks.
----
-
-# Third-Party Diagnosis
-
-Use this skill for directly callable Earn / third-party diagnosis.
-
-The output is a compact diagnosis plus action candidates for `assetType="third_party"`.
-
-## Scope
-
-Diagnose:
-
-- Cited third-party domains.
-- Competitor presence on external sources.
-- Tenant-owned third-party profiles.
-- Submission, listing, review, and inclusion opportunities.
-- External sentiment risk on social or community surfaces.
-
-Do not recommend third-party work just because a domain is frequently cited. Prefer no action when the path is speculative.
-
-## Workflow
-
-Read these references before producing proposals:
-
-- `references/workflow.md` for the full third-party product workflow, actionability boundaries, candidate types, evidence gates, social handling, and no-action cases.
-- `references/diagnosis-contract.md` for the exact runtime diagnosis contract and artifact submission shape.
-
-1. Read shared run context and the third-party candidate slice.
-2. Use `get_citation_intelligence` before lower-level citation calls.
-3. Use `list_third_party_candidates` for actionable domain slices.
-4. Use `get_geo_intent_diagnostic` when intent-level citation behavior matters.
-5. Use `social_analyze` for YouTube, Reddit, TikTok, Instagram, or LinkedIn URLs.
-6. Use `web_scrape` only for specific non-social pages where feasibility or profile quality must be checked.
-7. Use `web_search` only to find an official submission/profile path or verify actionability.
-
-## Output Contract
-
-Each proposal should include:
-
-- exact third-party source domain.
-- exact publish surface URL when known.
-- content format and content angle.
-- 2-4 concrete execution steps.
-- expected outcome.
-- root cause, priority, confidence, risks, and evidence.
-
-Allowed no-action outcomes:
-
-- external path is not actionable.
-- citation signal exists but no credible submission/profile/update path exists.
-- owned or generated page coverage is the clearer bottleneck.

package/dist/skillpacks/geo/skills/third-party-diagnosis/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "Third-Party Diagnosis"
-  short_description: "Diagnose external citation and Earn opportunities."
-  default_prompt: "Use $third-party-diagnosis to diagnose third-party GEO opportunities for this workspace."

package/dist/skillpacks/geo/skills/third-party-diagnosis/references/diagnosis-contract.md

@@ -1,111 +0,0 @@
-# GEO Strategy: Third-Party Diagnosis
-
-You diagnose external citation surfaces.
-
-Do not force proposals. Return no proposal when the external path is only speculative or not plausibly actionable.
-
-## Scope
-
-Work on:
-
-- cited third-party domains
-- competitor presence on cited sources
-- tenant-owned third-party profiles
-- submission/listing/review opportunities with evidence of feasibility
-- negative or risky external sentiment
-
-Do not recommend outreach only because a domain is frequently cited.
-
-## Evidence Order
-
-Use the cheapest sufficient evidence.
-
-1. Common run context and routed candidates.
-2. `list_third_party_candidates` for the first third-party domain slice.
-3. `get_geo_intent_diagnostic` when an intent-level citation pattern needs explanation.
-4. `get_citation_intelligence` first, then `list_citations`, `get_citation_domains`, and `get_citation_timeseries` for citation evidence.
-5. `list_ai_responses` for answer excerpts and recommendation reasons.
-6. `social_analyze` for YouTube, Reddit, TikTok, Instagram, or LinkedIn URLs; do not use `web_scrape` for these platforms.
-7. `web_scrape` only for a specific non-social external page where feasibility or profile quality must be checked.
-8. `web_search` only to find an official submission/profile path or verify third-party actionability.
-
-## Candidate Types
-
-- `competitor_cited_surface_gap`
-- `owned_3p_profile_gap`
-- `submission_target`
-- `owned_3p_refresh`
-- `authority_source_monitor`
-- `negative_or_risk_domain`
-- `not_actionable`
-
-## Root Cause Buckets
-
-Allowed buckets:
-
-- `third_party_presence_gap`
-- `external_authority_gap`
-- `owned_3p_entity_gap`
-- `submission_feasibility_gap`
-- `sentiment_risk`
-- `not_actionable`
-- `insufficient_evidence`
-
-## Action Families
-
-Allowed families:
-
-- `refresh_owned_3p_profile`
-- `publish_owned_3p_content`
-- `request_submission_inclusion`
-- `update_listing_or_profile`
-- `collect_reviews`
-- `monitor_only`
-- `no_action`
-
-Prefer a concrete action when there is a plausible evidence-backed path. Use `monitor_only` or `no_action` when feasibility is too speculative.
-
-When `list_third_party_candidates` returns `competitor_presence`, `tenant_presence`, and `actionability`, use those fields as the primary planning frame:
-
-- Propose action for `competitor_cited_surface_gap` when competitors are present, tenant presence is missing or weak, and `actionability.actionable=true`.
-- Propose `owned_3p_profile_gap` when the tenant has an owned profile URL but the cited surface shows weak tenant presence.
-- Keep editorial, forum, unknown, or `actionability.actionable=false` cases as `monitor_only` or rejected unless additional evidence proves a direct path.
-
-## Output
-
-Produce one `third_party` diagnosis object in this shape.
-
-Do not write intermediate diagnosis JSON files directly.
-
-Do not include `workspaceId`, `runId`, `channel`, final action id, or final `assetType`; the orchestrator can derive them.
-
-Use this shape:
-
-```json
-{
-  "summary": "Short diagnosis.",
-  "proposals": [
-    {
-      "intentId": "intent_123",
-      "candidateType": "submission_target",
-      "target": { "domain": "example.com", "url": "https://example.com/vendor-list" },
-      "rootCauses": [
-        { "bucket": "third_party_presence_gap", "confidence": 0.68, "evidence": ["Competitors appear on a repeatedly cited list; tenant is absent."] }
-      ],
-      "actionFamily": "request_submission_inclusion",
-      "operations": ["Prepare human-reviewed inclusion request"],
-      "priority": "medium",
-      "confidence": "medium",
-      "evidence": [
-        { "type": "source", "ref": "citation_domain:example.com", "summary": "Repeatedly cited for weak intent." }
-      ],
-      "whyNow": "Why this matters this week.",
-      "risks": ["External owner may not accept submissions."]
-    }
-  ],
-  "rejected": [
-    { "ref": "example.org", "reason": "Frequently cited but no action path found." }
-  ],
-  "noActionRationale": "Use when proposals is empty."
-}
-```

package/dist/skillpacks/geo/skills/third-party-diagnosis/references/workflow.md

@@ -1,174 +0,0 @@
-# Third-Party Diagnosis Workflow
-
-## Role
-
-The `third_party` channel diagnosis reviews external citation surfaces and decides whether third-party action is warranted.
-
-It always participates in the orchestrated run, but it should not force proposals when evidence is not actionable.
-
-It covers two action channels:
-
-- `owned_3p`: tenant-controlled third-party profiles or channels
-- `submission_3p`: external domains where inclusion, listing, outreach, or profile updates may be possible
-
-## Non-Goals
-
-- Do not recommend outreach only because a domain is frequently cited.
-- Do not assume a domain is actionable without category or feasibility evidence.
-- Do not replace brand-owned or GEO page fixes with third-party work unless evidence shows the bottleneck is external authority or third-party presence.
-
-## Inputs
-
-- common run context from the orchestrator
-- tenant `agent/BRAND.md`
-- tenant `agent/STRATEGY.md`
-- tenant `agent/LEARNINGS.md`
-- relevant rows from:
-  - `geo_recommendation_quadrants`
-  - `geo_intent_citations`
-  - `geo_third_party_domains`
-  - `geo_competitor_citations`
-  - `geo_third_party_sentiment`
-- `geo_strategy_actions_recent`
-- brand social profiles
-- competitor/domain evidence when available
-- social evidence from the scraper SocialAnalyzer for YouTube, Reddit, TikTok, Instagram, and LinkedIn
-- submission/contact feasibility scrape only when needed for non-social pages
-
-## Workflow
-
-### 1. Review External Citation Pattern
-
-Look for:
-
-- domains repeatedly cited for weak intents
-- competitor presence on cited domains
-- tenant absence on cited domains
-- negative or weak sentiment on external sources
-- owned third-party profiles that are cited but under-optimized
-
-Do not treat citation count alone as actionability.
-
-### 2. Classify Candidate Type
-
-#### A. Submission Target
-
-Use when:
-
-- competitors are present on a cited third-party domain
-- tenant brand is absent or weak
-- domain category is directory, review site, marketplace, partner page, or open listicle
-- there is evidence of submission/contact feasibility
-
-Potential action:
-
-- create listing
-- update profile
-- request inclusion
-- collect reviews
-
-#### B. Competitor-Cited Surface Gap
-
-Use when `list_third_party_candidates` reports:
-
-- `candidate_type=competitor_cited_surface_gap`
-- `competitor_presence.status=present`
-- `tenant_presence.status=missing` or `weak`
-- `actionability.actionable=true`
-
-Potential action:
-
-- request inclusion
-- create or update listing
-- collect reviews on the cited surface
-
-#### C. Owned 3P Profile Gap
-
-Use when:
-
-- `candidate_type=owned_3p_profile_gap`
-- `tenant_presence.owned_profile_url` is present
-- owned third-party page is cited, competitor-cited, or likely relevant
-- tenant messaging, category terms, proof, or content coverage is weak
-
-Potential action:
-
-- update owned profile
-- publish owned-channel post
-- add category keywords and proof
-
-For YouTube, Reddit, TikTok, Instagram, and LinkedIn URLs, inspect the content with `social_analyze`.
-Do not use generic web scraping for those platforms.
-
-#### D. Authority Source Monitor
-
-Use when:
-
-- domain is highly cited
-- source is not directly controllable
-- no clear submission path exists
-
-Potential action:
-
-- `no_action`
-- monitor only
-- PR/analyst relations note in `rationale.md`
-
-#### E. Negative Or Risk Domain
-
-Use when:
-
-- sentiment is negative
-- domain appears repeatedly
-- factual correction or review response may be needed
-
-Potential action:
-
-- monitor sentiment
-- prepare factual correction
-- flag for human review
-
-### 3. Pick Root Cause Buckets
-
-Allowed buckets:
-
-- `third_party_presence_gap`
-- `external_authority_gap`
-- `owned_3p_entity_gap`
-- `submission_feasibility_gap`
-- `sentiment_risk`
-- `not_actionable`
-- `insufficient_evidence`
-
-### 4. Route Action
-
-Allowed action families:
-
-- `refresh_owned_3p_profile`
-- `publish_owned_3p_content`
-- `request_submission_inclusion`
-- `update_listing_or_profile`
-- `collect_reviews`
-- `monitor_only`
-- `no_action`
-
-Prefer a concrete action when the candidate carries a plausible evidence-backed path. Use `monitor_only` or `no_action` when feasibility is speculative.
-
-### 5. Output JSON
-
-Return:
-
-- channel summary
-- proposals
-- rejected candidates
-- no-action rationale
-
-If no third-party action is warranted, return an empty `proposals` array and explain why.
-
-## Guardrails
-
-- Frequency is not actionability.
-- Citation count alone does not justify outreach.
-- Prefer `monitor_only` when feasibility is unknown.
-- Require evidence before labeling a domain as submission-friendly.
-- Do not emit third-party actions that the product cannot execute or review.

package/dist/skillpacks/geo/skills/third-party-execution-planning/SKILL.md

@@ -1,64 +0,0 @@
----
-name: third-party-execution-planning
-description: Use when turning a selected third-party GEO Earn action into a concrete human execution plan for social platforms, directories, review sites, marketplaces, partner pages, open listicles, or owned third-party profiles.
----
-
-# Third-Party Execution Planning
-
-Use this skill after a `third_party` GEO action has already been selected.
-
-This skill does not diagnose whether an Earn action should exist. It enriches one approved third-party action into an operator-ready work order for a human operator.
-
-## Scope
-
-Plan execution for:
-
-- Reddit posts or comment replies.
-- YouTube creator outreach.
-- TikTok creator briefs.
-- Instagram Reel or carousel briefs.
-- LinkedIn posts, comments, or outreach.
-- Directory, marketplace, and partner listing submissions.
-- Review-site profile refreshes and review collection motions.
-- Open listicle or editorial inclusion requests.
-- Tenant-owned third-party profile updates.
-
-Do not recommend automated posting, fake engagement, vote/comment coordination, review manipulation, undisclosed paid promotion, spam, or impersonation.
-
-## Workflow
-
-Read these references before producing a plan:
-
-- `references/execution-contract.md` for the exact output contract.
-- `references/reddit-rules.md` for Reddit rule checks and draft format.
-- `references/social-platform-playbooks.md` for social platform planning guidance.
-- `references/non-social-surface-playbooks.md` for directory, review, listing, marketplace, partner, and editorial inclusion planning guidance.
-
-1. Start from the provided `third_party` action, policy snapshot, and backend execution context.
-2. Prefer backend-provided cited threads, URLs, creator profiles, and candidate surfaces before broad discovery.
-3. Use `firecrawl_search` for search and discovery.
-4. Use `social_analyze` for Reddit, YouTube, TikTok, Instagram, and LinkedIn URLs.
-5. Use specific non-social URLs, submission pages, listing pages, or profile pages when the action targets directories, review sites, marketplaces, partner pages, or open listicles.
-6. Select one best execution surface when evidence is sufficient.
-7. Produce a dashboard-ready work order with surfaces, execution type, required assets, draft, policy checks, execution steps, completion signal, impact signal, and fallback.
-8. If evidence is thin, platform rules block execution, or a non-social submission path is not verifiable, return a conservative plan with open questions or a do-not-post/no-submit path.
-
-## Output Contract
-
-Return a third-party work order:
-
-- `assetType`: always `third_party`.
-- `surfaces`: exact publish, reply, creator, or discovery surfaces.
-- `executionType`: one specific execution pattern.
-- `requiredAssets`: what the operator needs before executing.
-- `draft.format`: concrete content type.
-- `draft.angle`: audience-facing angle.
-- `draft.body`: concise execution brief or copy-paste-ready Reddit block.
-- `draft.tone`: human operator tone.
-- `policyChecks`: platform, review, disclosure, editorial, or evidence constraints.
-- `executionSteps`: 2-5 ordered manual steps.
-- `completionSignal`: how the operator knows the work was completed.
-- `impactSignal`: how the team should observe GEO/business impact.
-- `fallback`: what to do if the main execution path is blocked.
-
-Keep the output executable by a human operator.

package/dist/skillpacks/geo/skills/third-party-execution-planning/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "Third-Party Execution Planning"
-  short_description: "Turn one Earn action into a human execution plan."
-  default_prompt: "Use $third-party-execution-planning to enrich this third-party GEO action into a human execution plan."

package/dist/skillpacks/geo/skills/third-party-execution-planning/references/execution-contract.md

@@ -1,90 +0,0 @@
-# Third-Party Execution Contract
-
-Use this contract when enriching one selected `assetType="third_party"` GEO action into an operator-ready work order.
-
-## Inputs
-
-- `workspaceId`
-- optional `runId`
-- one `GeoStrategyAction`
-- optional policy snapshot
-- optional backend execution context
-
-The action is already selected. Do not re-run third-party diagnosis.
-
-## Tools
-
-Use:
-
-1. `firecrawl_search` for search and discovery.
-2. `social_analyze` for Reddit, YouTube, TikTok, Instagram, and LinkedIn URLs.
-3. `web_scrape` or equivalent page reading only for specific non-social pages where submission feasibility, listing quality, or profile quality must be checked.
-
-Do not use social scraping as a substitute for platform rule checks when Reddit posting or replying is proposed.
-
-## Output
-
-Return JSON with:
-
-```json
-{
-  "assetType": "third_party",
-  "executionType": "claim_profile | update_profile | request_inclusion | ethical_review_motion | factual_correction | editorial_pitch | owned_profile_refresh | owned_channel_content | social_reply | social_creator_outreach | social_post | no_submit",
-  "surfaces": [
-    {
-      "name": "string",
-      "url": "string | null",
-      "searchQueries": ["string"]
-    }
-  ],
-  "whyThisSurface": "string",
-  "requiredAssets": ["string"],
-  "draft": {
-    "format": "string",
-    "angle": "string",
-    "body": "string | null",
-    "tone": "string | null"
-  },
-  "policyChecks": [
-    {
-      "name": "string",
-      "status": "clear | blocked | unknown",
-      "reason": "string"
-    }
-  ],
-  "executionSteps": ["string"],
-  "completionSignal": "string | null",
-  "impactSignal": "string | null",
-  "fallback": "string | null"
-}
-```
-
-## Requirements
-
-- `surfaces` must include at least one exact surface or a rerunnable discovery surface.
-- Prefer exact URLs over discovery queries. Use the URL selection hierarchy in `non-social-surface-playbooks.md` for non-social actions.
-- `executionType` must match the selected surface and action family.
-- `requiredAssets` must name concrete inputs the operator needs, such as product category, logo, screenshots, proof points, customer list, policy URL, or evidence packet.
-- `policyChecks` must include review, disclosure, platform, editorial, or evidence constraints when relevant. Use `unknown` rather than inventing policies.
-- `executionSteps` must contain 2-5 ordered manual steps.
-- `completionSignal` must describe the immediate operational completion state.
-- `impactSignal` must describe the downstream GEO/business signal and time window when possible.
-- `fallback` must say what to do if the surface cannot be submitted, claimed, updated, or contacted.
-- Do not invent platform rules, creator contacts, submission forms, review policies, metrics, brand claims, or user experiences.
-- If evidence is thin, lower confidence in the draft body and list open questions.
-
-## Safety Boundaries
-
-Never recommend:
-
-- automated posting.
-- fake engagement.
-- vote/comment brigading.
-- review manipulation.
-- undisclosed paid promotion.
-- undisclosed incentivized reviews.
-- review gating or sentiment-conditioned review requests.
-- employee, family, or insider reviews without clear relationship disclosure.
-- spam.
-- hiding AI assistance to evade moderation.
-- impersonation or fabricated personal experience.

package/dist/skillpacks/geo/skills/third-party-execution-planning/references/non-social-surface-playbooks.md

@@ -1,123 +0,0 @@
-# Non-Social Third-Party Surface Playbooks
-
-Use these playbooks for `third_party` actions outside Reddit, YouTube, TikTok, Instagram, or LinkedIn.
-
-The goal is an operator-ready work order: a human should know exactly where to go, what to prepare, what to submit or change, what not to do, and how to judge completion.
-
-## URL Selection Hierarchy
-
-Choose the most actionable URL available:
-
-1. Existing owned profile or listing URL.
-2. Claim, edit, submission, or partner application URL.
-3. Category, directory, review, marketplace, or list page where the tenant should appear.
-4. Contact, corrections, editorial guidelines, or pitch URL.
-5. Rerunnable discovery query only when no exact URL is available.
-
-If the URL is only a broad homepage, explain the missing surface in `fallback`.
-
-## Decision Matrix
-
-- Tenant absent and a claim/submission path exists: `executionType=claim_profile` or `request_inclusion`; final action usually uses `operation=create`.
-- Tenant profile exists but is stale, thin, miscategorized, or missing proof: `executionType=update_profile`; final action usually uses `operation=update`.
-- Review-site profile exists and real customers can be asked neutrally: `executionType=ethical_review_motion`; final action usually uses `operation=create`.
-- Article/list has a factual error or outdated tenant fact: `executionType=factual_correction`; final action usually uses `operation=update`.
-- Article/list lacks the tenant, criteria fit is credible, and contact/editorial path exists: `executionType=editorial_pitch`; final action usually uses `operation=create`.
-- Tenant controls the external profile/channel: `executionType=owned_profile_refresh` or `owned_channel_content`.
-- No visible execution path, no proof, or policy risk is unresolved: `executionType=no_submit`; do not turn it into a final action unless the product explicitly supports open-question tasks.
-
-## Claim Or Create Profile
-
-Use for directory, marketplace, partner, vendor catalog, integration list, or agency directory surfaces where the tenant is missing.
-
-Work order must include:
-
-- target category/list page and claim/submission/contact URL when known.
-- evidence that the tenant fits the category.
-- required assets: product or company name, objective description, category, logo, destination URL, screenshots or media, proof points, pricing/integration facts only when verified.
-- draft body written as a concise submission or partner/contact request, not marketing copy.
-- completion signal: profile submitted, claim requested, partner application sent, or owner acknowledged.
-- impact signal: listing live, profile indexed, referral traffic, external mention, or AI citation movement in 30-90 days.
-
-Quality bar:
-
-- Use objective category/audience/use-case language.
-- Avoid first-person copy, superlatives, unsupported comparisons, CTAs inside descriptions, and unverifiable claims.
-- Do not recommend submission if the product is not publicly available or category fit is unclear.
-
-## Improve Existing Profile
-
-Use when a third-party listing/profile exists but is weak, stale, incomplete, miscategorized, or missing proof.
-
-Work order must include:
-
-- exact profile URL.
-- fields to update: category, description, screenshots, video, pricing, FAQ, proof points, integrations, product links, or discussion responses.
-- required assets for each field.
-- draft body with replacement copy or concise edit instructions.
-- completion signal: update submitted, profile edited, correction approved, or profile completeness improved.
-- impact signal: indexed update, profile traffic, category visibility, review-site visibility, or AI citation movement.
-
-Quality bar:
-
-- Favor objective definitions, category terms, audience, and use cases.
-- Keep profile copy factual and scannable.
-- Screenshots should show the real product/interface when relevant.
-- Do not claim "best", "fastest", or similar unless the source evidence proves it and the platform permits it.
-
-## Ethical Review Motion
-
-Use when review volume, recency, profile trust, or competitor review advantage is a credible bottleneck.
-
-Work order must include:
-
-- exact review profile/category URL.
-- platform review policy URL or `unknown` policy check.
-- neutral customer segment to ask, such as recent active customers or completed implementation cohort.
-- draft request that asks for honest feedback from all eligible customers, not only happy customers.
-- completion signal: neutral review request launched or review program checklist created.
-- impact signal: authentic review count/recency movement, profile trust movement, rating distribution, or AI citation movement in 30-90 days.
-
-Never recommend:
-
-- incentives conditioned on review sentiment.
-- asking only happy customers.
-- discouraging negative reviews.
-- asking customers to include specific phrases, employees, ratings, or keywords.
-- employee, family, fake, AI-generated, or insider reviews without clear relationship disclosure.
-- payment or benefits for changing or removing a negative review.
-
-## Editorial Inclusion Or Correction
-
-Use for open listicles, buyer guides, analyst-style pages, comparison articles, or editorial pages.
-
-Work order must include:
-
-- exact article/list URL and contact/corrections/editorial URL when known.
-- whether the motion is correction, inclusion, expert quote, or evidence packet.
-- why the ask serves the publisher's audience, not only the tenant.
-- evidence packet: factual proof, category fit, original data, customer proof, quote, or concise source links.
-- draft body under 300 words unless the operator needs a longer evidence packet.
-- completion signal: correction request sent, editor acknowledged, pitch sent, or evidence packet delivered.
-- impact signal: article updated, new mention/backlink, editorial reply, or AI citation movement.
-
-Quality bar:
-
-- Lead with the factual gap or reader value.
-- Keep the pitch short, specific, and evidence-led.
-- Do not pitch weak stories, generic inclusion requests, or pages with no contact/correction path.
-- Respect "not interested" responses and stop after a small number of polite follow-ups.
-
-## Owned Third-Party Profile Refresh
-
-Use when the tenant controls the external profile or channel.
-
-Work order must include:
-
-- exact owned profile URL.
-- weak fields or stale surfaces to update.
-- required assets: current positioning, proof points, links, media, category terms, product/service coverage, or post brief.
-- completion signal: profile update live or owned-channel post published.
-- impact signal: indexed profile/post, external engagement, profile completeness, referral traffic, or AI citation movement.
-
-Do not use this playbook for the tenant's own website. Website work belongs to `brand_owned` or `geo_page`.