Agent discoverability � root cause analysis runbook
| |
|---|
| Linear | EDEN-1739 |
| Repository artifact | knowledge/clients/eden/governance-martech-delivery-model/eden-agent-discoverability-rca-runbook.md |
| Goal | Explain false negatives (�no tables exist�) when governed marts exist. |
Reproduction checklist
- Clone agent bootstrap: Same repos, branches, env vars, service account JSON path as Eden agents use.
- Document corpus: Which README /
agents.md / beads files were in context for the failing run?
- BigQuery principal: Run inventory queries as the same SA/OAuth used by automation.
- Compare: Human-generated list of canonical marts vs agent-visible datasets.
Likely cause buckets (rank after evidence)
| Rank | Hypothesis | Evidence to collect |
|---|
| A | IAM blind spot � SA cannot see datasets | ACL screenshots / policy binding |
| B | Wrong repos in clone list | Agent config YAML |
| C | Docs not indexed in agent context | Prompt + file list |
| D | Legitimate gap � Ads-specific mart missing | Compare to EDEN-1718 |
Output
- Top 1�3 causes with proof.
- Remediation tickets (catalog link, ACL change, doc pin).
Safety
- No patient row data in notes � dataset and table identifiers only unless approved.