cognee-promotelisted

# cognee-promote Promote a learning to the correct tier. Promotion is orchestrated, not automatic (noise floods the graph) and not manual (signal gets lost). Blast radius decides. ## Decide the tier Ask: **does this learning affect only me, my team, or everyone?** | Blast radius | Destination | Who decides | When | |---|---|---|---| | agent-private | subagent `MEMORY.md` | the agent | autonomous, anytime | | team-level | team rules + shared topic file | Team Lead | on trigger or at milestone | | cross-harness | Cognee project graph node | Nehemiah + Bezalel | at sprint close (or immediately if high blast radius) | ## Two triggers - **Immediate** — the learning affects another agent's *current* work. The agent flags it to its Team Lead. Team Lead promotes to team-level (topic file) or cross-harness (write to Cognee now). High signal, low volume. - **Milestone** — the Team Reporter collects sprint learning; resolved research and decisions are promoted to Cognee at `/sprint-close`. ## Writing to Cognee Conform to `~/.claude/mishkan/ontology.md`: pick the entity type (ResearchOutput, Decision, CaseNode, SecurityFinding, ADR, Incident…), set `blast_radius`, and add the relationship edges (validated-by, derives-from, supersedes, mitigates…). Only `team-level` and `cross-harness` nodes go to Cognee; `agent-private` stays in MEMORY.md. ## Constraints No fabricated facts. Cross-harness promotion is gated by Nehemiah + Bezalel. English only.