Keep the context behind the code.
A shared structure for project knowledge, durable facts, and the work that happened between sessions.
A place for every piece of context
A wing represents a project or topic. Rooms group related areas such as decisions, backend, and testing. A drawer stores a piece of verbatim text with its metadata. This keeps a specific architectural decision discoverable without turning every query into a search through the entire organization.
The knowledge graph records relationships between entities, including when a fact became valid. Agent diaries capture session continuity: what changed, what was learned, and what the next session needs. These layers complement source files; they preserve the reasons and working history around them.
Recall before repeating
At session start, agents load recent context. Before answering questions about earlier decisions or conventions, they search Palace and check relevant graph facts. Current implementation details still belong in source-code inspection.
Keep the source attached
Search combines keyword matching with local vector similarity. Results carry their wing, room, source file, drawer ID, and score information. Ask an agent to cite that provenance so a teammate can inspect what an answer rests on.
Save what the next person needs
After substantive work, the agent records a diary entry and durable facts. When a decision changes, invalidate the old graph fact and record the replacement. A shared memory is most useful when it preserves both the current answer and its history.
Workspaces and the wings registry
Palace Server keeps a tenant-scoped wings registry: the source of truth for which workspaces exist in your organization. Each wing has a kind (project or topic) and a description. Wings auto-register the first time an agent writes a memory, and existing memories are backfilled lazily per tenant, so upgrading from an earlier release needs no manual setup.
palace_project_statusreports whether the current repo is a known project, a registered-but-unmined wing, or unknown, with a recommendation.palace_create_wingdeclares a topic or project wing on demand, which suits people without a repository such as product or sales. A wing can be promoted from topic to project but never demoted.palace_list_wingsreturns the full registry with per-wing drawer counts.