BloomSpec
Entities

Source Document

The raw artefact pulled from a connected external system — a wiki page, a Slack message, a ticket, a file — before or independent of any curation. May never become a Knowledge Item at all.

Volume

Very high; scales with the number and size of connected sources

Retention

Tied to the source system's own retention, mirrored rather than owned

Entity attributes8
  • source_document_id
  • tenant_id
  • source_system
  • Connector failure must be visibly surfaced to content owners and search-quality monitoring, not only retried silently, since a silently-degrading connector produces a quietly shrinking index rather than a loud error.
  • Enforcement must be evaluated at query time against live claims for any source with volatile membership (e.g. project- or engagement-based access), with a bounded, documented resync SLA for index-time-baked permission metadata elsewhere.
  • source_native_id
  • raw_content
  • last_synced_at
Entity relationships1
Entity relationships1
Capability entities1
Entity lifecycle

Not yet researched

Only the control-bearing entities were modelled for lifecycle. Defensible as a starting point, but it does leave the entity model uneven, and this is incompleteness rather than a finding.

Implementation risks1
Capability operations7