forge-memory-bridge
Transform Forge export envelopes into projection import batches for semantic-memory.
Usage
use ;
What it does
forge-memory-bridge sits between Forge's export pipeline and
semantic-memory's projection importer. It validates export envelopes,
transforms each record into the import projection format, and preserves
provenance end-to-end.
The bridge does not evaluate comparability, guess missing semantics, act as a query service, or persist any state of its own.
Versioned contracts
The canonical path uses V3 types throughout:
ExportEnvelopeV3 -> transform_envelope_v3() -> ProjectionImportBatchV3
V1 and V2 paths are preserved as deprecated compatibility layers.
Ecosystem
Depends on:
stack-ids-- identity primitives (EnvelopeId,ClaimId,TraceCtx,ContentDigest, etc.)semantic-memory-forge-- export envelope types and validation
Depended on by:
semantic-memoryconstraint-compilerkernel-oracleskernel-conformanceknowledge-runtimeforge-pilotcontract-schema-genforge-engine(living-memory)
stack-ids integration
Uses typed identifiers throughout: EnvelopeId, ClaimId, ClaimVersionId,
EntityId, EpisodeId, RelationId, ContentDigest, TraceCtx, and
ScopeKey from stack-ids for provenance tracking and content addressing.