Valhalla Control Surface
The Valhalla suite is the Valkyr product stack working as one system:
For subsystem relationship charts, code anchors, and breakout maps, see the Valhalla Suite Atlas.
Print and reference assets:
-
Valhalla api-0 is the suite backend platform for generated APIs, RBAC, billing, admin/control surfaces, deployments, GrayMatter control, and SWARM coordination.
-
ValkyrAI is the workflow engine for tasks, ExecModules, agentic orchestration, and reviewable automation.
-
GrayMatter is the durable memory and RBAC-scoped object-graph layer.
-
ValorIDE is the agentic coding and application-generation client. It is both a GrayMatter client and a SWARM agent.
-
Valor is the agentic chat/work interface that can advise, create workflows, navigate the web app, operate against system inputs, and coordinate agents.
-
SwarmOps is the live agent registration, discovery, command, graph, and telemetry layer. It is not the GrayMatter memory primitive.
-
Gridheim Runes are OpenAPI extension-defined calculated fields generated by ThorAPI as
@Runemodel fields and evaluated by ValkyrAI/OpenXLS with no calculated-value persistence. -
Sheetster Grid is the workbook/table UX for operating generated objects, cells, formulas, charts, and actions.
Runtime Discovery
Current Valhalla api-0 exposes a GrayMatter control document for clients and agents:
GET /v1/graymatter/control
GET /v1/graymatter/admin/control
The response describes the authenticated principal's GrayMatter contract:
| Section | Purpose |
|---|---|
suite | Names the Valhalla suite and the participating products. |
memory | Lists memory primitives, entry types, entitlements, usage, and admin actions. |
semantic | Reports semantic index health and reindex guidance. |
objectGraph | Declares that the full RBAC-visible api-0 schema is the object graph. |
swarm | Points to SwarmOps registration and graph endpoints, with coordination-only policy. |
clients | Profiles ValorIDE, Valor, CODEX, OpenClaw, Claude, Sheetster Grid, and other SWARM clients. |
endpoints | Provides the canonical endpoint map for memory, schema, SwarmOps, Agent, and GrayMatter surfaces. |
Clients should load this document before falling back to direct /v1/api-docs capability inference.
Boundary Rules
GrayMatter memory operations use these primitives:
MemoryEntryGrayMatterSemanticIndexEntry
The live object graph may include any RBAC-visible api-0 model, including Agent, Workflow, Task, Application, Workbook, Customer, Opportunity, Product, FileRecord, and other generated ThorAPI entities. Gridheim Runes attach formula rules to generated object properties; Sheetster Grid presents the workbook/table operating surface over them.
SwarmOps is intentionally separate:
- Use
POST /v1/swarm-ops/registerto register or refresh a live agent instance. - Use
/v1/swarm-ops/discover,/v1/swarm-ops/agents, and/v1/swarm-ops/graphfor presence and coordination views. - Do not treat SwarmOps rows or graph snapshots as durable GrayMatter memory entries.
Agent Startup Pattern
Agentic clients should follow this order:
- Authenticate against api-0.
- Load
/v1/graymatter/control. - Create or refresh a durable
Agentrecord when required. - Register live presence through
/v1/swarm-ops/register. - Sync
/v1/api-docsand use it as the RBAC-scoped object graph. - Query GrayMatter memory before meaningful work.
- Write only durable decisions, preferences, todos, artifacts, configuration, or compact context.
- Publish SWARM events for coordination, acknowledgements, task state, and audit proof.
Related: