knowledge-graphlisted

# Knowledge Graph ## What It Is The knowledge graph is shared institutional memory across all agents. It is backed by PostgreSQL — full-text search is the canonical default backend, with Apache AGE as an optional graph backend (`UNITARES_KNOWLEDGE_BACKEND=age`). Every agent can search, contribute, and update entries. Discoveries persist across sessions and are available to all agents in the system. ## Search Before Creating Always search before adding new entries: ``` knowledge( action: "search", query: "description of what you're looking for", tags: ["relevant", "tags"], limit: 10 ) ``` `search_shared_memory(query=...)` is the discoverable workflow alias for this same read path. Use either it or the unified router; duplicate entries fragment knowledge and make search less effective. You may omit `query` entirely when filtering by tags, type, severity, dates, or status. A supplied-but-blank query is rejected so a caller mistake cannot turn into an accidental broad scan. Omit `include_details` to let the server expand a small result set automatically; pass `include_details=false` when summaries only are intentional. ## Quick Contribution For low-friction contributions, use the unified note action: ``` knowledge( action: "note", summary: "What you discovered or observed", tags: ["domain", "type", "context"] ) ``` Notes are automatically shared with all agents. Use this when you find something useful, spot a bug, or have an insight that others should kno