AD Competitive Intelligence policy
policy artifact · for AD Competitive Intelligence · status draft
policy artifact · for AD Competitive Intelligence · status draft
No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.
- repo: name: string, ownership: string, local_path: string, relationship_to_redkey: string
- project: AD Competitive Intelligence
- hard rules: 13 items
- review gates: 3 items
- allowed paths: 2 items
- product suite: name: string, products: object, repo_path: string, migration_source: object
- schema version: 1.0
- disallowed actions: 3 items
Machine-readable source fields
KnowledgeVault
Standalone production AD suite repo. It should contain KnowledgeVault core, the production KV app, Executive SEO, AD Competitive Intelligence/analytics, and Ask AD integration. RedKey remains platform/orchestration, not the product implementation home.
/Users/justinking/Vaults/Projects/KnowledgeVault
RedKey stores Studio artifacts, agent orchestration, and shared platform infrastructure; product code should graduate into this standalone KnowledgeVault repo.
AD Competitive Intelligence
- This is a production product intended to sell to AD, not a prototype, demo, or art-of-the-possible page.
- Do not publish uncited competitive claims.
- Do not scrape behind logins or violate robots/access controls without explicit approval.
- Label source authority in every observation and signal.
- Keep production V1 focused on Grainger and Fastenal unless Justin explicitly adds competitors; MSC is the next expansion candidate.
- Use public information only. Do not store personal applicant data beyond what is already public in job postings.
- Do not create automated outreach or sales emails in V1.
- Any AI-generated inference must be stored separately from observed facts.
- AD-facing views must show approved material only.
- The AD-facing product must not open on unexplained charts, tables, or raw feeds; the first screen must explain what was done, why, and the value to AD.
- The opening narrative must be product-specific to AD, Grainger, Fastenal, and industrial distribution intelligence.
- Implementation must live in the standalone KnowledgeVault repository at /Users/justinking/Vaults/Projects/KnowledgeVault unless Justin explicitly changes repository strategy.
- Do not treat AD Competitive Intelligence as an isolated app; it belongs in the standalone KnowledgeVault AD suite repo alongside KV, SEO, KV app, and Ask AD.
| gate | requirement |
|---|---|
| source_gate | Source config must identify authority and access method before collection. |
| signal_gate | Signal cannot be approved without source_refs and confidence. |
| brief_gate | Executive brief cannot publish if any included signal is draft or missing citations. |
- /Users/justinking/Vaults/Projects/KnowledgeVault
- RedKey supabase/migrations only if shared platform schema is explicitly needed
KnowledgeVault AD Suite
| id | name | purpose |
|---|---|---|
| knowledgevault-core | KnowledgeVault Core | Capture retiring expert and product knowledge into governed, searchable assets. |
| knowledgevault-app | KnowledgeVault App | Production application surface for capture, search, dashboards, admin, and AD/member workflows. |
| executive-seo | Executive SEO | Distributor digital visibility intelligence and CEO-level opportunity prioritization. |
| competitive-intelligence | AD Competitive Intelligence | Monitor Grainger and Fastenal public signals, produce reviewed analytics/briefs, and feed Ask AD. |
| ask-ad | Ask AD | Suite-level cited advisor across KnowledgeVault, SEO, and Competitive Intelligence. |
/Users/justinking/Vaults/Projects/KnowledgeVault
AD SEO app implementation/artifacts currently live outside this repo and should be migrated or integrated as a product module before production packaging.
/Users/justinking/Vaults/Projects/redk3y/apps/knowledgevault
1.0
- Credentialed LinkedIn scraping
- Automated member communications
- Claims of competitor intent without inference label