Every future capsule must preserve linked source records, references, claims, scores, duplicate clusters, conflict maps, and receipts.
No orphan capsules.No source trail, no capsule.
A read-only preservation gate that defines what must survive before any intelligence capsule can be compressed, stored, reactivated, visualized, or routed to agents.
Every TheoB pathway can move through Past, Present, and Future without losing context.
Read current signals, conditions, and live context.
Voice ready
Preserve the trail before you capsule the truth.
Capsule Source Preservation Gate protects TheoB from creating elegant but empty memory. Every future capsule must preserve source trail, provenance, claims, scoring, dedupe, conflict, rights, redaction, and modality boundaries before compression can ever begin.
Capsule Source Preservation Gate is active as a non-destructive readiness gate. TheoB can define what must survive before capsule compression, but it cannot preserve live candidates, store capsules, compress records, process files, route to agents, or mutate production yet.
Every capsule must know where its intelligence came from and which transformations shaped it.
Compression without provenance becomes mythology.Capsules must preserve extracted claims and the source trail behind those claims.
Do not convert claims into unsupported facts.Capsules must preserve confidence, source quality, and review state where available.
A capsule is not a truth verdict.Capsules must preserve whether evidence is independently corroborated or repeated from the same source cluster.
Do not compress repetition into false certainty.Capsules must preserve unresolved conflict, severity, and review state.
Do not make disagreement disappear by compressing it.Capsules must preserve rights status, attribution requirements, retention policy, and redaction state.
Do not turn restricted content into permanent memory.Images, diagrams, CAD, schematics, maps, PDFs, datasets, and composite records need file provenance and modality-specific preservation.
Files are not text blobs.Future capsule reactivation must preserve what was expanded, compared, visualized, simulated, or routed to agents.
Compressed memory needs a use-history when it influences action.High-impact capsules require human review before storage, compression, reactivation, or agent handoff.
Do not automate irreversible trust decisions.Links to Vault records, references, claims, scores, duplicate clusters, conflict maps, and receipts.
Records provider, retrieval, normalization, scoring, deduplication, conflict, redaction, and transformation steps.
Preserves whether the source is metadata-only, review-required, or full-storage-allowed.
Preserves whether the capsule candidate is redacted-safe or needs review.
Preserves whether citation, link, provider label, or publisher attribution must remain attached.
Preserves how long and how deeply the record may be retained.
Preserves source quality, confidence band, review state, and scoring explanation.
Preserves conflict severity, unresolved disagreements, and review requirements.
Preserves repetition count, independence score, and duplicate cluster identity.
Preserves file format, derived formats, validation state, visual uncertainty, and modality-specific source details.
A capsule cannot be compressed until source trail, rights, redaction, confidence, dedupe, and conflict context are present.
Compression must reduce size, not truth.Every capsule must be traceable back to Vault-safe source records or approved source pointers.
No source trail, no capsule.Conflict maps, unresolved disagreement, and uncertainty must remain attached to capsule candidates.
Do not preserve a clean lie.Rights, attribution, retention, and redaction policy must follow the capsule forever.
The memory layer cannot launder restricted content.Visual, schematic, CAD, map, and dataset capsules need specialized provenance fields.
Do not flatten visual intelligence into text-only memory.This gate defines preservation readiness only and does not preserve, store, or compress capsule records.
No Vault writes, no capsule writes, no file processing, no production mutation.Future capsule use should create receipts when capsules are expanded, compared, routed, visualized, simulated, or handed to agents.
Memory that influences action needs an audit trail.Turning on capsule preservation, storage, or compression must require explicit approval.
No accidental permanent memory.