Skip to content

Intelligence Database Responsibilities

Why This Exists

This document defines conceptual database responsibilities for the Intelligence Domain.

It does not define SQL implementation, vector store choice, graph database choice, migrations, or physical deployment.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Clear persistence responsibilities make intelligence auditable, explainable, and reusable while respecting source-domain ownership.

Conceptual Tables Or Collections

Conceptual table or collection Responsibility
intelligence_sessions Reasoning session metadata and lifecycle state.
intelligence_agents AI Agent Registry records.
digital_professional_runtimes Runtime mappings for Digital Professionals.
reasoning_steps Ordered reasoning steps and intermediate results.
confidence_assessments Confidence scores, methods, thresholds, and bands.
explainability_records Rationale, evidence references, assumptions, and limitations.
guardrail_decisions Approval requirements, policy results, approvers, and reasons.
execution_requests Governed requests to the Procurement Execution Engine.
ai_memory_entries Intelligence-domain memory records with provenance and scope.
intelligence_event_subscriptions Event Mesh subscription configuration.
intelligence_audit_log Append-only audit records for AI activity.

Memory Storage Responsibilities

AI Memory may require multiple storage patterns over time:

  • Relational records for governance and audit.
  • Search indexes for retrieval.
  • Vector or semantic indexes for memory recall.
  • Graph links to Organization Intelligence Graph references.

Organization-owned facts remain in the Organization Domain. Intelligence memory stores reasoning context, references, and derived intelligence records.

Audit Requirements

Audit records should capture:

  • OrganizationId where applicable.
  • Session ID.
  • Agent ID.
  • Digital Professional ID.
  • Action.
  • Input references.
  • Output references.
  • Confidence score.
  • Guardrail result.
  • Approval status.
  • Timestamp.
  • Correlation ID.

Database Responsibility Diagram

flowchart TD
    Sessions[Intelligence Sessions]
    Agents[AI Agent Registry]
    Reasoning[Reasoning Steps]
    Confidence[Confidence Assessments]
    Explain[Explainability Records]
    Guardrails[Guardrail Decisions]
    Requests[Execution Requests]
    Memory[AI Memory Entries]
    Audit[Intelligence Audit Log]

    Sessions --> Reasoning
    Sessions --> Confidence
    Sessions --> Explain
    Sessions --> Guardrails
    Sessions --> Requests
    Sessions --> Memory
    Agents --> Sessions
    Sessions --> Audit

Indexing Considerations

Future implementation should consider indexes for:

  • OrganizationId.
  • SessionId.
  • AgentId.
  • DigitalProfessionalId.
  • CorrelationId.
  • Event type.
  • Approval status.
  • Confidence band.
  • Timestamp.
  • Memory scope.

Ownership Rule

Intelligence persistence must not become the canonical store for Organization, Compliance, Opportunity, Proposal, Contract, Supplier, Funding, Learning, or Analytics facts.