← Agent catalogue
PostgreSQL + Prisma persistence

Preview portrait

Data

PostgreSQL + Prisma persistence

Durable substrate for deterministic workflows — no prompt-held state for meaningful platform facts.

LiveCatalogue status
Execution activeRuntime posture

Canonical storage for tenant data, workflow runs, evidence, jobs, approvals, audit, and outbound dispatch.

Expanded capabilities

  • Provide PostgreSQL/Prisma durable storage for tenant-owned rows
  • Support migrations and inspectable execution state
  • Enforce tenant isolation at the data plane
  • Back WORKFLOW, approvals, audit, and knowledge artifacts
  • Never accept client-supplied tenantId as sole authority

How they learn & improve

Persistence improves through migrations and schema governance — not runtime self-altering tables. Learning applies write rows; it does not rewrite history.

  1. Store tenant-scoped rows with compound keys where required.
  2. Migrate additively under deploy gates.
  3. Expose durable state to observers (WORKFLOW/TERMINUS) for human ops.

Practical benefits

  • State you can migrateSchema changes ship as migrations — not ad-hoc db push in production.
  • Isolation by defaultQueries stay tenant-scoped so one customer never sees another’s jobs.
  • Replay after incidentsDurable rows let ops reconstruct what ran without trusting chat logs.

Learning and improvement stay human-visible: candidates are RECORD_ONLY until an operator reviews and applies them. Sensitive sends, publishes, and approvals never run silently.

PostgreSQL + Prisma persistence — AgentIQ Agent Catalogue · AgentIQ Labs