When to use them
Use an ordinary semantic selection when a stable role and source already describe the intended item. Use a persistent reference when the user selects a specific item interactively or when no unique semantic query can be authored up front.Complete capture, resolution, and explanation workflow
This exact-OCCT module captures a semantically named face, changes the model, resolves the detached evidence against the new snapshot, and inspects the bounded explanation.examples/docs/persistent-topology.ts. Capture first proves the evidence
uniquely identifies the selected item inside the capture snapshot. A symmetric
indistinguishable item is rejected rather than assigned an arbitrary identity.
Evaluation-scoped keys are never stored as durable evidence.
Register captured evidence in a design
bodyRef. A selector cannot consume it
against an ancestor, descendant, unrelated solid, or another design.
Variants and fingerprints
A document entry may contain variants for distinct supported topology protocol and exact kernel-fingerprint combinations. Duplicate fingerprint variants are rejected. Evaluation chooses only an exact compatible variant; it never silently upgrades a stored protocol or loosens a fingerprint.How resolution works
- Validate the stored envelope and operational limits.
- Check the kernel’s signature protocol and fingerprint.
- Normalize one current topology snapshot.
- Prefer authoritative semantic lineage when complete and uniquely anchored.
- Otherwise use bounded toleranced geometry and adjacency evidence.
- Return a current key only for exactly one match.
TOPOLOGY_MATCH_MISSING. Multiple matches produce
TOPOLOGY_MATCH_AMBIGUOUS. A fingerprint mismatch is distinct from both.
Explanations and shared sessions
UseexplainTopologyReference for one detached explanation, or
createTopologyReferenceResolutionSession when resolving/explaining several
references against one snapshot. The session shares normalization, caches, and
a cumulative work budget.
An invalid persistent atom remains fatal inside and, or, not, and
adjacentTo; logical operators cannot hide incompatible stored evidence.
What persistence does not mean
Persistent topology references do not provide:- a cross-run native shape cache
- durable native face indices
- geometric document diffing
- guaranteed identity for symmetric indistinguishable peers
- automatic migration to a new signature protocol