T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:17- Finding
Cross-Workspace Collection and Persistence of Sensitive Operational Data
- Content
View full analysis
datetime('now', '-24 hours') AND bu IN ('{bu}', 'portfolio') ORDER BY ts DESC" ``` Replace `{bu}` with your BU. Events override memory files on contradiction. Bobina: skip — sandboxed. Read from memory files and reports where results are already captured; do not query external APIs (Supabase, PostHog, GSC, Notion, Hashnode, Agent Commune). ``` `SKILL.md:37-43`: ```markdown **Peer Compression:** Information from outside your own workspace (peer HIPPOCAMPUS files, BU captures, cross-workspace reads) compresses to one line per item in your output. If you can't say it in one line, you're absorbing detail that belongs to the owning agent. Your hippocampus carries your domain at depth; peer state is directional context only. **Source Priority:** 1. **Own workspace** (memory, artifacts, data) — full fidelity. 2. **Activity feed** (events.db) — full fidelity for your BU events matching your Track list. 3. **Peer HIPPOCAMPUS** (where listed in Sources) — read for state awareness, compress to 1 line per peer. 4. **BU captures** (where listed) — filter entries to tags matching your domain. See per-agent capture filters in registry. ``` `SKILL.md:58-62`: ```markdown `memory/YYYY-MM-DD*.md` — filter by filename, don't read all files. ### Step 4: Read domain-specific sources Per registry. Rules: 14d window by filename, cross-workspace is read-only, CRM hubs selective (Bobo only for Open Thread entities), cron logs last 20 lines. Cross-workspace reads are context, not content. Extract only what maps to your T ...[truncated 5409 chars]- Remediation
View remediation
