owner: gmikcon status: active last_reviewed: 2026-10-09 review_interval: 30d confidence: high
Gnexus Book is the canonical infrastructure knowledge base and maintenance API for the personal digital and server infrastructure.
gnbook (192.168.1.170) on hypervisor hp-proliant-dl380-g6 (192.168.1.130).ubuntu on 192.168.1.170 (credentials in gnexus-creds, secret gnauth-gnbook-ssh)./home/ubuntu/gnexus-book (branch master).server/.server/app/mcp_server.py.ui/.gnexus-ui-kit.http://192.168.1.170:8000/ (uvicorn, openapi at /openapi.json).http://192.168.1.170:8001/sse.http://192.168.1.170:80/ (nginx serves the built SPA).user@1000.service: gnexus-book-backend.service (uvicorn :8000) and gnexus-book-mcp.service (MCP server)./home/ubuntu/gnexus-book-backup.sh (700, owner ubuntu) on gnbook./home/ubuntu/gnexus-book as tar.gz (includes .git history, modified 40-inventory/*.yml, and all untracked 90-maintenance/pending-changes/*.json — 271 pending files are NOT in git, so a git-only backup would lose them) + git bundle create --all as a restorable history insurance./opt/backups/gnexus-book/backup.log + cron.log.find -mtime +10 -delete for both gnexus-book-*.tar.gz and gnexus-book-*.bundle).git bundle verify (complete history). Any failure → exit 1, logged.tar xzf gnexus-book-<TS>.tar.gz -C /home/ubuntu restores the full repo including pending changes; or git clone gnexus-book-<TS>.bundle restored for history-only restore (working-tree modifications and untracked pending JSONs are NOT in the bundle — use the tar.gz for full restore).master is ahead of origin/master by 185 commits (origin is stale) — local backups are currently the only copy of recent history. Consider pushing to GitBucket (git.gnexus.space) as an off-host copy.Agents should prefer structured inventory changes, validation, pending changes, and local commits through the maintenance API.
Pending-change queue lives in 90-maintenance/pending-changes/ (untracked JSON files; 11 older ones are git-tracked). Repository-wide validation scans every pending JSON, so a single invalid pending file blocks all applies and commits.
Poisoned-pending protection (since 2026-09-24, commit c77bcb1):
propose_doc_change, propose_inventory_item_change, update_doc): payloads with secret patterns or unsafe doc targets (outside repo root) are rejected BEFORE any file is written — a rejected request leaves no pending file behind.delete_pending_change (MCP) / DELETE /changes/{id} (REST): deletes pending or corrupt records; applied records are refused (409).list_pending_changes tolerates corrupt JSON files and reports them with status corrupt; corrupt records can be deleted but not applied.update_doc cleans up its own pending JSON automatically if apply or commit fails.For agent-facing MCP usage rules, see ../../90-maintenance/agent-mcp-usage.md.
No raw credentials are documented here.