Expand description
Graph data structures for the spatial browser.
Core structures:
Graph: Main graph container backed by petgraph::StableGraphNode: Webpage node with a transient projected position and metadataEdgePayload: Edge semantics and traversal events between nodes
This module is WASM-clean: it must compile to wasm32-unknown-unknown.
Re-exports§
pub use cross_graph::ComponentCopy;pub use identity::EdgeKey;pub use identity::GraphDirection;pub use identity::GraphIndex;pub use identity::GraphViewId;pub use identity::NodeKey;pub use node::Node;pub use node_facets::NodeFacetStore;pub use node_facets::VisitHistoryFacet;pub use history::NodeHistoryBranchAlternative;pub use history::NodeHistoryBranchProjection;pub use history::NodeHistoryBranchVisit;pub use history::NodeHistoryOwner;pub use history::NodeHistoryProjection;pub use history::NodeHistorySemanticSummary;pub use history::RecentVisit;pub use capture::CapturedDelta;pub use capture::GraphTableStats;pub use capture::replay_captured_deltas;pub use capture::replay_captured_deltas_onto;pub use capture::set_captured_delta_hook;pub use journal::AttributedDelta;pub use journal::GraphJournal;pub use journal::USER_AUTHOR;pub use journal::journal_capture_hook;pub use source_time::SourceExtent;pub use source_time::SourceTime;pub use edge_data::ArrangementData;pub use edge_data::ContainmentData;pub use edge_data::EdgeMetrics;pub use edge_data::ImportedData;pub use edge_data::ProvenanceData;pub use edge_data::REL_VOCAB;pub use edge_data::SemanticData;pub use edge_data::SemanticStatement;pub use edge_data::SemanticStatementSpec;pub use edge_data::StatementAssert;pub use edge_data::Traversal;pub use edge_data::TraversalData;pub use edge_data::all_semantic_sub_kinds;pub use edge_data::predicate_iri;pub use edge_data::sub_kind_from_iri;pub use edge_payload::EdgePayload;pub use edge_taxonomy::ArrangementSubKind;pub use edge_taxonomy::ContainmentSubKind;pub use edge_taxonomy::EdgeAssertion;pub use edge_taxonomy::EdgeFamily;pub use edge_taxonomy::ImportedSubKind;pub use edge_taxonomy::ProvenanceSubKind;pub use edge_taxonomy::RelationDurability;pub use edge_taxonomy::RelationKind;pub use edge_taxonomy::RelationSelector;pub use edge_taxonomy::SemanticSubKind;
Modules§
- apply
- capture
- Stable-id graph-delta capture/replay helpers.
- cross_
graph - Cross-graph node copy (tear-out fork): mints a node in this graph from a donor node in another graph, recording cross-graph derivation provenance. Cross-graph node copy — the kernel half of the tear-out “fork” / cross-graph composability gesture (tear-out brief §7.5; tearout-composability plan C4).
- display
- A human-meaningful display label for a node.
- edge_
data - Per-family edge runtime data structs and semantic IRI mapping.
Extracted from
edge_taxonomy.rsper the 600-LOC ceiling. - edge_
ops - Edge operations — assert, replay, dissolve, retract, traversal recording.
- edge_
payload EdgePayload— the structural + temporal payload carried on every graph edge. Composes the taxonomy types fromsuper::edge_taxonomyinto a single payload struct whose typed sidecars are authoritative:EdgeFamilyis derived from which sidecars are populated, not from a parallel index set.- edge_
taxonomy - Edge taxonomy types — families, kinds, and sub-kinds.
- facet_
projection - PMEST facet projection — computes a queryable facet map from a node + graph context.
- filter
- Faceted filter expression engine.
- history
- Navigation history — one shared visit space for the whole graph.
- identity
- Graph identity types and rkyv archive helpers.
- import_
records - Import-record operations.
- journal
- The edit spine: mere’s captured-delta stream as a
codicillog, replayed into the graph (the substrate’s append-only-log primitive over mere’s own edit vocabulary). Seegraph/journal.rs. The edit spine: mere’s captured-delta stream over the substrate log. - node
- The kernel’s physical node wrapper around chartulary’s neutral Container.
- node_
facets - Typed projections over the graph’s atomic per-node facet store.
- node_
props - Node-property setters and per-node query accessors.
- query
- Graph query + traversal — node / edge lookups, neighbor iteration, BFS / shortest-path / connected-components / SCC, and the derived-edge views (semantic / arrangement / containment).
- snapshot
- Graph snapshot serialization.
- source_
time - Source-time selection, distinct from projected-scene delivery revisions.
Structs§
- Archived
Dissolved Traversal Record - An archived
DissolvedTraversalRecord - Arrangement
Edge View - Containment
Edge View - Coupling
- One coupling rule: identity + target field + selector + response + strength.
- Coupling
Id - Stable identity for a coupling rule.
- Dissolved
Traversal Record - Traversal archive payload emitted when dissolving a node.
- Dissolved
Traversal Record Resolver - The resolver for an archived
DissolvedTraversalRecord - Edge
Path Rule - Per edge-kind path-generation rule.
- Field
- A field as kernel truth: identity + portable definition + extent + lifecycle.
- FieldId
- Stable, federatable field identity. UUID-backed (vs
quint’s original registry-localFieldId(u64)); this is the canonical id for kernel truth. - Graph
- Main graph structure backed by petgraph::StableGraph
- LogId
- A stable identity for a log. Caller-chosen (a name, a URN, a hash you already hold), so identity is deterministic and needs no randomness source.
- Relation
View - Canonical read-side relation view. One row per (from, to,
RelationKind) — a multi-relation node pair yields multiple rows. Replaces theEdgeType-flavouredEdgeViewremoved in stage 4 of the 2026-05-11 relation-taxonomy plan. - Semantic
Edge View - Seq
- The position of an entry in a
Codicil. Zero-based: the first appended entry isSeq(0).
Enums§
- Coupling
Response - How a node responds to a field at its position.
- Edge
Path - How an edge’s path is generated between its two endpoints.
- Falloff
- Falloff shape for spatially-bounded scalar kernels (e.g.
ScalarField::Disk). - Field
Definition - A field’s portable definition: scalar- or vector-valued. The AST is data;
quintevaluates it. - Field
Extent - Where a field applies. (
Regionis an axis-aligned world-space box, kept as four scalars to stay rkyv-friendly at the DTO layer without aBox2Darchive helper.) - Field
Lifecycle - Field lifecycle state. Mirrors the spirit of
NodeLifecycle: a field is authored (Active) and can be retired without losing its definition for history/federation. Richer states (Warm/Cold equivalents) are deferred. - Node
History Transition Kind - How an owner moved to a visit: navigation vocabulary.
- Node
Selector - Selects which nodes a coupling applies to. Tag and kind names are opaque here — they resolve against the node’s tags / classifications.
- Scalar
Field - A scalar field expression. Recursive cases use
Boxto keep the enum sized. - Vector
Field - A vector field expression.
Constants§
- COUPLING_
VOCAB - Base IRI for Mere’s coupling-response vocabulary (the
statements-over-schema
substrate applied to responses). The recognized force core maps to
{COUPLING_VOCAB}{slug}viaCouplingResponse::recognized_iri; the families beyond force name themselves under sub-namespaces, e.g.…/coupling#visual/highlight,nav/focus,selection/member,semantic/assert,trigger/fire. Provisional base; mirrors [crate::graph::edge_taxonomy]’sREL_VOCAB.