A first-class wings registry organizes drawers into workspaces — backend, frontend, data, infra. Wings auto-register the moment an agent writes a memory, so every workspace inherits its context automatically.
Agents detect whether the current repo is a known project or topic and act on it — palace_project_status reports the state, palace_create_wing declares a topic wing, and palace_list_wings returns the full registry.
The same BM25 + cosine retrieval from palace-rs, now over your whole team's collective memory, with source-grounded provenance on every hit. R@5 = 0.981 on LongMemEval.
Temporal entity relationships across all teammates. Facts written by one agent are queryable by all — architecture decisions, API contracts, team conventions.
Session diary entries in AAAK format — private by default, optionally shared. Any agent can warm-start from the last person's session context.
Fine-grained read/write permissions per workspace per user, backed by Postgres row-level security and admin RBAC. Contractors see what they need; sensitive projects stay scoped.
Every MCP tool call is recorded as a usage event, and every memory write lands in a tenant-scoped audit log. Gain reports and Prometheus metrics show adoption across the team.
Exposes all palace_* MCP tools over the network. Any MCP-compatible agent — Cursor, Claude Code, Codex — connects with zero configuration change.
Single binary, low memory, fast startup. Runs comfortably on a small VM or a Raspberry Pi. No JVM, no Node, no Python runtime needed.
Embeddings run locally via ONNX. License verification is offline-capable. No data ever leaves your network — full air-gap mode supported.
Free and local in two minutes. Shared across your whole team in ten. No cloud, no lock-in.