{"schema_version":"2.0","record_type":"workflow","canonical_url":"https://marketingwiki.ai/workflows/verify-marketing-ai-tool","id":"workflow-verify-marketing-ai-tool","slug":"verify-marketing-ai-tool","title":"Verify a Marketing AI Tool Profile","description":"A repeatable workflow for separating documented capabilities, observed behavior, editorial inference, stale claims, and unknowns.","dek":"Tool profile should show what evidence supports each capability and what remains untested.","label":"Index maintenance","status":"Published","stages":["Scope","Official docs","Test","Claims","Review"],"topics":["tool index","verification","product claims"],"publishedAt":"2026-08-10","updatedAt":"2026-08-10","lastVerifiedAt":"2026-08-10","readingMinutes":2,"author":"Marketing Wiki Editors","reviewer":"Marketing Wiki Editors","sources":[{"title":"NIST AI Risk Management Framework","url":"https://www.nist.gov/itl/ai-risk-management-framework"},{"title":"Google people-first content guidance","url":"https://developers.google.com/search/docs/fundamentals/creating-helpful-content"}],"wordCount":343,"body":"Tool directory becomes useful when every record shows evidence state. Logo, tagline, and feature list copied from vendor page create marketing inventory, not independent index.\n\n## Inputs\n\n- Canonical product URL\n- Official documentation\n- Public pricing page\n- Public API or integration documentation\n- Maintainer and submitter affiliations\n- Defined test task, when observed evidence is claimed\n\n## 1. Define profile scope\n\nState exact job profile helps evaluate. \"AI marketing platform\" is too broad. \"Turns approved brief into editable email series\" can be checked.\n\nDefine:\n\n- Target user\n- Marketing job\n- Required input\n- Expected output\n- Human approval points\n- Data access and action permissions\n\n## 2. Record official claims\n\nOfficial documentation supports `vendor-documented` status. It does not prove speed, quality, reliability, or superiority.\n\nStore claim with source URL and verification date:\n\n```yaml\nstatement: Product exposes public API\nsource_type: official-documentation\nstatus: vendor-documented\nverified_at: 2026-08-10\n```\n\n## 3. Run bounded test\n\nObserved result requires reproducible task:\n\n- Fixed input\n- Account tier\n- Product or model version\n- Date and region\n- Expected success condition\n- Raw output or trace\n\nDo not turn one successful run into universal capability claim.\n\n## 4. Build claim ledger\n\nUse five visible states:\n\n| State | Meaning |\n| --- | --- |\n| Official | Vendor or publisher documents it |\n| Observed | Dated test produced result |\n| Inferred | Evidence supports conclusion indirectly |\n| Stale | Source or test needs refresh |\n| Unknown | Evidence cannot answer question |\n\n## 5. Review conflicts\n\nDisclose contributor relationship: maker, employee, investor, partner, customer, affiliate, or none. Affiliated profiles use same fields and require unaffiliated review when practical.\n\n## Publish gate\n\nProfile ships only when canonical URL, material claims, source types, verification dates, affiliation, and correction path are present.\n\n## Failure modes\n\n- Vendor marketing copy presented as editorial conclusion\n- Pricing without check date\n- Integration logo treated as working integration\n- Beta access presented as general availability\n- Unpublished test result converted into ranking\n- Maintainer-affiliated product receives featured placement"}