{"slug": "competitive-intelligence-digest-agent", "title": "Competitive Intelligence Digest Agent", "summary": "AgentKit released the Competitive Intelligence Digest Agent, an open-source AI agent that compiles competitor digests from public sources while labeling items as confirmed facts or unverified rumors. The agent includes an AgentAz governance specification for security review, defining trust levels, tool boundaries, and human handoff triggers. The release aims to provide a safe, auditable framework for competitive research without fabricating data.", "body_md": "## Overview\n\nCompiles a competitor digest — product, pricing, positioning, news — with every item cited and dated.\n\nLabels each item as confirmed fact or unverified rumor, so nothing reads as more certain than it is.\n\nDraws only from public, ethical sources — no leaks, no non-public data, no fabricated moves.\n\nDefensive: flags low-confidence items, notes recency, and marks assumptions rather than guessing.\n\n## AgentAz™ specification\n\nA lightweight, design-time governance spec for security review. It documents what this agent is authorized to do — and why — and pairs with whatever policy engine you already run. It does not enforce anything at runtime.\n\nMachine-readable contract (`agentaz.json`\n\n), validated against the open AgentAz™ JSON Schema — bundled for offline use and published at a permanent URL:\n\n```\n{\n  \"$schema\": \"./agentaz.schema.json\",\n  \"version\": \"2.0.0\",\n  \"last_reviewed\": \"2026-06-24\",\n  \"agent_id\": \"competitive-intel-agent\",\n  \"trust_level\": \"A1\",\n  \"dna_pattern\": \"Research\",\n  \"worst_case_action\": \"Includes a stale fact in a digest for human review. Never publishes or acts.\",\n  \"authority_boundary\": \"Gathers and cites competitive intel; never fabricates; publish/send tools absent.\",\n  \"tags\": [\n    \"research\",\n    \"competitive-intel\",\n    \"read-only\",\n    \"cited\"\n  ],\n  \"tool_boundary\": {\n    \"allowed_tools\": [\n      \"search_sources\",\n      \"gather_signals\",\n      \"cite_source\",\n      \"flag_stale\"\n    ],\n    \"execution_tools_absent\": true,\n    \"read_only\": true\n  },\n  \"output_boundary\": {\n    \"format\": \"structured_json\",\n    \"never_emits\": [\n      \"publish\",\n      \"send\"\n    ],\n    \"never_fabricates\": true\n  },\n  \"cost_boundary\": {\n    \"max_usd_per_trace_loop\": 0.3,\n    \"alert_threshold_usd\": 0.2\n  },\n  \"loop_boundary\": {\n    \"max_reasoning_turns\": 10\n  },\n  \"human_handoff\": {\n    \"triggers\": [\n      \"stale_data\",\n      \"conflicting_sources\"\n    ],\n    \"destination\": \"analyst\"\n  },\n  \"audit\": {\n    \"append_only\": true,\n    \"logs\": [\n      \"sources\",\n      \"citations\"\n    ]\n  }\n}\n```\n\nNew to this? Read the [AgentAz specification guide](/agentaz-specifications) — Trust Levels, DNA patterns, and how it complements your runtime.\n\nAgentAz™ is open source under [Apache-2.0](https://www.apache.org/licenses/LICENSE-2.0) — schema (frozen v1.0.0) and source on [GitHub](https://github.com/agent-kits/agentaz).\n\n## Governance matrix\n\nA scannable summary of this blueprint's governance coverage, derived from its AgentAz™ specification. It documents the boundaries that already ship — not new functionality.\n\n| Agent goal | Bounded by the authority spec above |\n|---|---|\n| Trust Level | A1 — Research |\n| Tool access | Least privilege — execution tools absent (read-only) |\n| Context handling | Grounded in provided inputs; cites or flags rather than guessing |\n| Memory strategy | Task-scoped; no persistent cross-session memory |\n| Human approval | Required on stale data, conflicting sources → analyst |\n| Audit trail | Append-only log (sources, citations) |\n| Cost & loop bounds | ≤ $0.3 per loop · ≤ 10 reasoning turns |\n| Recovery / escalation | Escalates to analyst |\n\n## Agent component mapping\n\nA framework-neutral view of how this blueprint maps to standard agent-architecture components (the vocabulary common to ADK-style frameworks). It describes structure for clarity — not an official integration or certified compatibility.\n\n| Agent | Primary reasoner — Research authority (A1) |\n|---|---|\n| Tools | search sources, gather signals, cite source, flag stale — execution tools absent (read-only) |\n| Memory | Task-scoped working context; no persistent cross-session memory |\n| Guardrails | Worst-case classified (A1); no execution tools; ≤ $0.3/loop · ≤ 10 turns |\n| Evaluator | Confidence and authority-boundary checks; low-confidence or out-of-bounds results are flagged, not actioned |\n| Handoff | Escalates to analyst on stale data, conflicting sources |\n\n## Failure modes\n\nSpecific ways this blueprint can fail, and how it is designed to detect, contain, and recover from each — the boundaries that make it safe to run, stated plainly.\n\nIncludes a stale or wrong fact in the digest that a reader acts on.\n\n- Detection\n- Every claim is cited and stale or unverifiable items are flagged.\n- Mitigation\n- It gathers and cites public information only; it never publishes or acts.\n- Recovery\n- The reader verifies against the citation and discards the bad item.\n\nFabricates a competitor claim or metric.\n\n- Detection\n- Uncited claims are withheld rather than asserted.\n- Mitigation\n- It never invents a competitor claim or figure.\n- Recovery\n- The analyst confirms against the source.\n\nPresents a single source as settled fact despite conflicts.\n\n- Detection\n- Conflicting sources are flagged.\n- Mitigation\n- It surfaces the conflict rather than resolving it silently.\n- Recovery\n- The analyst reconciles the sources.\n\n## Evaluation\n\nFactual accuracy with citations is primary — a stale or fabricated competitor fact that a reader acts on is the failure.\n\n| Fact accuracy | Share of digest claims that are correct and current versus verified sources. |\n|---|---|\n| Citation rate | Share of claims that cite a source, with uncited claims withheld. |\n| Fabrication rate | Frequency of invented competitor claims or metrics — should be near zero. |\n| Conflict surfacing | Share of conflicting sources flagged rather than silently resolved. |\n| Latency | Time to compile a digest. |\n\n**Recommended approach.** Use a set of digests with verified reference facts; measure accuracy and citation rate and audit for fabrication. Include topics with conflicting sources to confirm conflicts are surfaced, not smoothed over.\n\n## When to use\n\nUse it when\n\n- You track competitors and want a regular, cited digest instead of scattered notes.\n- You have public sources (sites, news, filings, changelogs) the agent can monitor and cite.\n- You want confirmed facts clearly separated from rumor and speculation.\n- You want an ethical, defensible intel process with sources attached.\n\nAvoid it when\n\n- You want it to obtain or use non-public, leaked, or illicitly sourced information — it won't.\n- You expect it to predict a competitor's roadmap as fact (it labels inference as inference).\n- You have no sources for it to ground claims in.\n- You need legal/strategic decisions made for you (it informs; humans decide).\n\n## System prompt\n\n```\nYou are a Competitive Intelligence Digest Agent. You compile a digest of competitor activity (product, pricing, positioning, news) from PUBLIC sources, for an internal team. You are judged on a useful, accurate, source-cited, ethically-sourced digest and on never fabricating competitor moves or presenting rumor as fact.\n\n== CORE PRINCIPLES ==\n1. Cite or don't claim. Every item must cite a public source you actually consulted, with a date. No source = it doesn't go in as fact.\n2. Fact vs. rumor vs. inference. Clearly label each item: confirmed (sourced fact), unconfirmed (rumor/unverified report), or inference (your hypothesis). Never blur these. A rumor stays a rumor.\n3. Ethical sourcing only. Use public information (websites, news, filings, changelogs, public social posts). Never use, request, or speculate from non-public, leaked, confidential, or illicitly obtained information.\n\n== HARD RULES (NON-NEGOTIABLE) ==\n- NO FABRICATION: Never invent a competitor launch, price, hire, or statement. If you can't source it, it's not in the digest (or it's clearly an inference).\n- NO NON-PUBLIC DATA: Do not use or seek trade secrets, leaked docs, private communications, or anything obtained unethically. Public sources only.\n- LABEL CONFIDENCE: Mark each item confirmed / unconfirmed / inference, with a source and date. Flag stale data.\n- NO DECISIONS: You inform strategy; you don't make competitive or legal decisions. Avoid legal-risk framing (e.g. don't advise on anti-competitive actions).\n- RECENCY: Note how recent each item is and flag when something may be outdated.\n\n== METHOD ==\n- For each competitor, gather from public sources. Classify each finding (confirmed/unconfirmed/inference), cite and date it, and assess significance. Surface what changed since the last digest.\n\n== OUTPUT FORMAT (return ONE JSON object) ==\n{\n  \"period\": \"<digest window>\",\n  \"competitors\": [\n    {\n      \"name\": \"<competitor>\",\n      \"items\": [\n        { \"category\": \"product|pricing|positioning|news|hiring\", \"finding\": \"<what>\", \"status\": \"confirmed|unconfirmed|inference\", \"source\": \"<public source>\", \"date\": \"<when>\", \"significance\": \"high|medium|low\" }\n      ]\n    }\n  ],\n  \"notable_changes\": [\"<biggest confirmed shifts since last digest>\"],\n  \"rumors_to_watch\": [\"<unconfirmed items, clearly labeled>\"],\n  \"gaps\": [\"<what couldn't be verified>\"],\n  \"ethics_note\": \"Public sources only; no non-public or leaked information used.\"\n}\nNever present an unconfirmed item as confirmed. Never fabricate or use non-public data.\n```\n\n## Simulate run\n\nTry the agent with a sample task. This is a frontend-only preview that shows how the kit would plan and execute — no API calls, nothing leaves your browser.\n\nFrontend preview only — no data leaves your browser. Tip: press `⌘/Ctrl` + `Enter` to run.\n\n## Setup guide\n\nInstall and connect public sources\n\nInstall the agent and connect public monitoring sources.\n\n```\npipx install compintel-agent\ncompintel-agent connect --sources news-api,changelogs,rss\ncompintel-agent doctor\n```\n\nConfigure ethics & confidence guardrails\n\nPublic-only sourcing and confidence labeling are enforced here.\n\n```\ncp .env.example .env\nANTHROPIC_API_KEY=sk-ant-...\nPUBLIC_SOURCES_ONLY=true\nLABEL_CONFIDENCE=true\nFLAG_STALE_AFTER_DAYS=30\n```\n\nDefine competitors & sources\n\nList who to track and which public sources to watch.\n\n```\n# compintel.yml\ncompetitors: [Acme, Globex, Initech]\nsources: { Acme: [acme.com/blog, acme.com/pricing], news: [techcrunch, theverge] }\ncategories: [product, pricing, positioning, news, hiring]\n```\n\nGenerate a digest\n\nRun a digest and review citations and confidence labels.\n\n```\ncompintel-agent run --period 7d --explain\n# prints items with status/source/date + notable changes + rumors\n```\n\nWire into your cadence\n\nSchedule a recurring digest to your strategy channel.\n\n``` php\n# weekly job -> cited digest to #competitive-intel (public sources only)\n```\n\n## Architecture\n\n## Tools required\n\n## Workflow\n\n1. Set competitors & sources\n\nTake the competitor list and the public sources to monitor.\n\n2. Gather from public sources\n\nCollect findings, recording a public source and date for each.\n\n3. Classify each finding\n\nLabel confirmed, unconfirmed, or inference — keeping them strictly distinct.\n\n4. Apply the ethics guard\n\nUse only public sources; exclude any non-public, leaked, or illicit information.\n\n5. Detect changes\n\nCompare to prior digests to surface genuine shifts since last time.\n\n6. Weight & date\n\nRate significance and flag stale items so the digest reflects current intel.\n\n7. Assemble the digest\n\nOutput cited items, notable confirmed changes, labeled rumors, and verification gaps.\n\n## Examples\n\nSourced competitor launch → confirmed item with citation\n\nA competitor announced a feature via press release. The agent records it as a confirmed, dated, sourced item.\n\nInput\n\n```\nAcme published a press release announcing a new analytics dashboard, dated this week.\n```\n\nOutput\n\n```\n{\n  \"period\": \"Last 7 days\",\n  \"competitors\": [\n    {\n      \"name\": \"Acme\",\n      \"items\": [\n        { \"category\": \"product\", \"finding\": \"Launched a new analytics dashboard\", \"status\": \"confirmed\", \"source\": \"Acme press release (acme.com/news)\", \"date\": \"2026-06-18\", \"significance\": \"high\" }\n      ]\n    }\n  ],\n  \"notable_changes\": [\"Acme entered analytics with a dashboard launch (confirmed)\"],\n  \"rumors_to_watch\": [],\n  \"gaps\": [\"Pricing for the new dashboard not yet disclosed\"],\n  \"ethics_note\": \"Public sources only; no non-public or leaked information used.\"\n}\n```\n\n**Note:** A clean confirmed item: sourced to a public press release, dated, and rated for significance. Note it also flags a gap (pricing not disclosed) rather than guessing it.\n\nUnverified rumor → included but clearly labeled, not as fact\n\nThere's chatter that a competitor will raise prices, but nothing official. The agent labels it a rumor.\n\nInput\n\n```\nA few social posts and a forum thread claim Globex is about to raise prices 20%. No official source.\n```\n\nOutput\n\n```\n{\n  \"period\": \"Last 7 days\",\n  \"competitors\": [\n    {\n      \"name\": \"Globex\",\n      \"items\": [\n        { \"category\": \"pricing\", \"finding\": \"Possible ~20% price increase\", \"status\": \"unconfirmed\", \"source\": \"Social posts + forum thread (public, but unofficial)\", \"date\": \"2026-06-19\", \"significance\": \"medium\" }\n      ]\n    }\n  ],\n  \"notable_changes\": [],\n  \"rumors_to_watch\": [\"Globex possible ~20% price increase — UNCONFIRMED; only unofficial chatter, no official source. Watch their pricing page.\"],\n  \"gaps\": [\"No official confirmation of any Globex price change\"],\n  \"ethics_note\": \"Public sources only; no non-public or leaked information used.\"\n}\n```\n\n**Note:** The agent surfaces the signal (useful to watch) but labels it clearly as unconfirmed and puts it under 'rumors to watch,' never in notable confirmed changes. It cites the unofficial nature and recommends watching the official page. Rumor stays rumor.\n\nAsked to infer a roadmap / use a leaked doc → refuse, stay public + labeled\n\nThe team wants a confident roadmap prediction and offers a leaked internal doc. The agent declines both.\n\nInput\n\n```\nRequest: 'state what Acme will ship next quarter as fact, and here's a leaked internal roadmap doc someone shared.'\n```\n\nOutput\n\n```\n{\n  \"period\": \"Last 7 days\",\n  \"competitors\": [\n    {\n      \"name\": \"Acme\",\n      \"items\": [\n        { \"category\": \"product\", \"finding\": \"May continue investing in analytics given the recent dashboard launch\", \"status\": \"inference\", \"source\": \"Inference from public launch (acme.com/news)\", \"date\": \"2026-06-18\", \"significance\": \"low\" }\n      ]\n    }\n  ],\n  \"notable_changes\": [],\n  \"rumors_to_watch\": [],\n  \"gaps\": [\"Acme's actual next-quarter roadmap is not publicly known\"],\n  \"ethics_note\": \"I won't use the leaked internal document — it's non-public/confidential, and using it would be unethical and a legal risk. I also won't state Acme's roadmap as fact; their plans aren't public. I've included only a clearly-labeled inference from public information.\"\n}\n```\n\n**Note:** The defining defensive case: asked to (1) present speculation as fact and (2) use a leaked internal doc. The agent refuses both — it excludes the leaked document on ethics/legal grounds, declines to state an unknowable roadmap as fact, and offers only a clearly-labeled low-confidence inference from public info. Ethical sourcing and honest confidence over a confident, tainted answer.\n\n## Implementation notes\n\n- Require a public, cited source for every confirmed item; an uncited competitor 'fact' a team acts on is a strategic risk.\n- Keep confirmed / unconfirmed / inference strictly separate and labeled — blurring rumor into fact is the most common and damaging intel failure.\n- Hard-exclude non-public, leaked, or illicitly obtained information; using it is an ethical and legal liability, not a shortcut.\n- Label recency and flag stale items, since competitive facts (pricing, positioning) change quickly.\n- Frame the agent as informing strategy, not making competitive or legal decisions, and avoid anti-competitive advice.\n- Surface verification gaps explicitly so the team knows what's unknown rather than assuming silence means nothing changed.\n- A cheaper model is usually enough to gather and structure public findings, so keep the strong model for fact/rumor classification and significance.\n\n## Variations\n\nBasic\n\nCited competitor snapshot\n\nCompiles a cited, labeled snapshot of recent competitor activity from public sources. On demand.\n\nAdvanced\n\nConfidence-graded digest\n\nAdds fact/rumor/inference labeling, ethical-sourcing guards, change detection, significance rating, and gap flagging.\n\nEnterprise\n\nContinuous competitive monitoring\n\nAdds scheduled multi-competitor monitoring, source governance, trend tracking, battlecard inputs, and integration with strategy workflows — public sources only.\n\nDownload the Agent Blueprint\n\n[Download Blueprint (.zip)](/downloads/competitive-intel-digest.zip)\n\nExport\n\n[View the source on GitHub](https://github.com/agent-kits/agentaz/tree/main/kits/competitive-intel-digest)\n\nThis blueprint and the AgentAz™ specification live in the central AgentKits registry — open source under Apache-2.0 (code & schema) and CC‑BY‑4.0 (text).\n\n## Frequently asked questions\n\nNo — that's its core constraint. Every confirmed item must cite a public source with a date; anything it can't source is excluded or clearly labeled as a rumor or an inference, never presented as fact.\n\nIt includes them only under 'rumors to watch,' clearly labeled unconfirmed with their (unofficial) source, and never lets them appear among confirmed changes. A rumor stays a rumor until there's an official source.\n\nNever. It uses only public, ethical sources — websites, news, filings, changelogs, public posts. It will refuse to use leaked documents or any non-public data, which is both an ethical and a legal safeguard.\n\nOnly as a clearly-labeled inference from public signals, never as fact. If their plans aren't public, it says so and flags the gap rather than stating a confident prediction.\n\nEach item is dated and rated, and stale data is flagged, so you can weight recent confirmed moves over older or unverified ones.\n\nNo. It compiles cited, confidence-graded intelligence to inform your strategy; the decisions stay with your team.", "url": "https://wpnews.pro/news/competitive-intelligence-digest-agent", "canonical_source": "https://www.agent-kits.com/kit/competitive-intel-digest", "published_at": "2026-06-21 00:00:00+00:00", "updated_at": "2026-06-26 22:04:37.591385+00:00", "lang": "en", "topics": ["ai-agents", "ai-safety", "ai-research", "ai-tools", "ai-ethics"], "entities": ["AgentKit", "Competitive Intelligence Digest Agent", "AgentAz", "GitHub"], "alternates": {"html": "https://wpnews.pro/news/competitive-intelligence-digest-agent", "markdown": "https://wpnews.pro/news/competitive-intelligence-digest-agent.md", "text": "https://wpnews.pro/news/competitive-intelligence-digest-agent.txt", "jsonld": "https://wpnews.pro/news/competitive-intelligence-digest-agent.jsonld"}}