team-skill-name

name	{"[object Object]":null}
description	Read and reason over this repository's company AI Brain using source-first search, date and alias checks, contradiction handling, original-file citations, and explicit uncertainty. Use when answering company-context questions, preparing internal decisions, or grounding another task in the organization's private knowledge base.

Use the {{COMPANY_NAME}} Brain

Ground company work in this repository without treating summaries as ground truth.

Orient

1. Read AGENTS.md and README.md.
2. Read data/overview.md, data/public-research.md, data/team-and-roles.md, data/tools-and-sources.md, and data/source-manifest.yml for broad questions.
3. Read task-specific original evidence before making factual claims.

Retrieve and verify

1. Identify the entities, aliases, product, customer, metric, geography, decision, and time period involved.
2. Search data/ with rg for exact terms plus aliases and alternate spellings.
3. Open the matching original sources and verify dates, roles, visibility, and context.
4. Compare relevant sources. Prefer direct, current, and claim-specific evidence.
5. Preserve contradictions and label inferences, stale data, and confidence.
6. Cite original repository paths. Do not cite this skill as evidence for company facts.

Respect knowledge and access boundaries

• Treat data/sources/ and data/interviews/ as evidence.
• Treat orientation files as interpretation.
• Treat registries and decisions as canonical only when their status and approval support that use.
• Apply visibility and allowed-role restrictions even when a file is technically readable.
• Honor the approved task scope recorded for each connector or source even when the app's technical permission footprint is broader.
• Do not expose private employee, customer, board, finance, legal, or security information outside its authorized audience.
• Do not infer reporting lines, authority, performance, productivity, influence, or sentiment from chat or calendar activity.
• Require explicit approval before external messages, publishing, system changes, scheduling, commits, pushes, access grants, or other consequential actions.

Answer contract

Lead with the answer. Cite the original files used. State conflicts, freshness limits, and missing context. If the Brain cannot answer, say so and list the closest sources checked.