Skip to main content

Data Model

Purpose​

helpifyr-fabric persists the shared control-plane state that should not live only in provider runtimes, ad-hoc files, or downstream products.

Core Persisted Entities​

Graph Revisions​

  • canonical topology and graph history references
  • used for sync, rollout, and drift correlation

Topology Sync Records​

  • downstream sync evidence for product-facing integrations

Rollout History​

  • dry-run and guarded rollout planning history

Drift Snapshots​

  • persisted evidence of detected topology/runtime drift

Audit Events​

  • operator and system evidence trail for guarded control-plane actions

Product Adapter Requests​

  • persisted product-facing request records

Event Outbox​

  • durable event publication staging and publish evidence

Capability Registry​

  • registered products and capabilities from manifest-backed intake

Important Keys​

  • tool_key
  • product_key
  • capability_key
  • graph_revision
  • plan_id
  • persisted record IDs per repository layer

Persistence Assumptions​

  • PostgreSQL is the durable backing store
  • Alembic owns migration history
  • persistence bootstrap and readiness are explicit operator-facing concepts

Integration Relevance​

This model supports:

  • rollout-gate and compatibility checks
  • event publishing evidence
  • product registration and capability lookups
  • governance/audit/readiness surfaces
  • future cross-repository operational alignment

License​