{
  "gnexus-book": {
    "transport": "sse",
    "url": "http://192.168.1.170:8001/sse",
    "groups": {
      "read": [
        "search_docs",
        "read_doc",
        "list_docs",
        "list_inventory",
        "get_inventory_item",
        "get_relationships",
        "check_freshness"
      ],
      "write": [
        "propose_doc_change",
        "propose_inventory_item_change",
        "apply_pending_change",
        "commit_changes",
        "update_doc"
      ],
      "admin": [
        "validate_repository",
        "git_status",
        "git_diff",
        "list_pending_changes"
      ]
    },
    "instructions": "MANDATORY: Before answering ANY question about infrastructure, servers, services, networks, documentation, or system inventory — you MUST call gnexus-book tools first.\n\nQuery mapping:\n- 'server X not working / status' → search_docs, get_inventory_item\n- 'what services run where' → list_inventory, get_relationships\n- 'update docs / fix documentation' → read_doc, propose_doc_change, commit_changes\n- 'is X up to date / freshness' → check_freshness\n- 'validate repository / repo state' → validate_repository, git_status\n\nDo NOT rely on memory or NAVI.md for infrastructure facts — they may be stale. Always pull current state from gnexus-book.\n\nAlways validate the repository before making changes. Do not store raw secrets in documentation.\n\nWhen you discover new infrastructure facts, service configurations, or relationships during tool execution, consider whether they should be persisted. For stable facts about servers, services, or network topology, use gnexus-book write tools (propose_doc_change, propose_inventory_item_change). For user-specific facts, use the memory tool instead. Choose the target based on scope, not habit."
  }
}