Overview
Synapsor stores contexts, capabilities, plans, resources, proposals, policies, and migrations in a queryable catalog. That gives agent workflows a versioned database surface instead of loose prompts and tool definitions.
Use SHOW and DESCRIBE for developer inspection, ALTER ... REPLACE for reviewed changes, and ROLLBACK/ACTIVATE when a capability version needs to move between tested states.
READ RESOURCE exposes Synapsor-produced lookup records such as evidence://..., ctx://..., agent-run://..., and wrp://... according to RBAC and redaction policy. last_context, last_evidence, and last_proposal are convenience aliases for the current shell/session; store durable returned ids in app code.
Agent workflow contracts and run graphs are cataloged too. Use EXPLAIN AGENT RUN for the graph-shaped response, and use system views when you need SQL-level inspection.
Developer notes
- Version contexts and capabilities like schema migrations.
- Use READ RESOURCE for handles instead of exposing full inline payloads by default.
- Keep hidden session values redacted unless the caller has an explicit admin/audit role.
- Use system views to debug catalog state without scraping logs.