## Performance evidence update / 18 September 2026 MODALITY PERFORMANCE / EVIDENCE REVIEWED 18 SEPTEMBER 2026 Define the useful result. Measure the complete job. A modality-specific timing is not yet linked to this guide. There may be supporting engineering measurements in the internal archive. We are reconciling their workload, result quality and comparison conditions before presenting a public chart. A benchmark for an adjacent model does not establish this model’s performance. 01 Crossing-order fidelity 02 Encode & comparison latency 03 Retained history bytes Include memory, storage, energy and hardware writes # Topological braids | 8DB Product reference. Reviewed 18 September 2026. Implementation and evaluation scope are stated below. Explore the models (https://8braid.com/modalities) / 8DB Topological braids Keep the order of an interaction. Represent crossing order in interacting histories so a relationship pattern can retain how it unfolded. Explore the capabilities See a complete workload Order · encode · compare Model / Braids Conceptual diagram [Diagram: braids representation: conceptual diagram] Strands change relative order over time. Crossings retain sequence as well as connection. Capabilities What changes Input to value Alternatives Performance Adoption Related articles Reference Start with the operations your question needs. Braid encoding and strand operations Topology matching on supported paths Declared graph, hypergraph, vector and timeline projections Documented product scope, reviewed 17 September 2026. The underlying build and deployment must be qualified for your application. Not every BraidQL operator is released. Durable semantic-identity ingestion remains gated while its encoding profile is corrected. Fingerprints summarize a representation; projections need not reconstruct the original braid. Connected native models Keep the next question within reach. For a group of time series, rank crossings describe the pattern of co-movement. Braid representations can support topology-based comparison and declared projections into other structures. [Diagram: time series representation: conceptual diagram] Time series Keep the meaning in every observation. Observe · window · analyze Explore model ↗ (https://8braid.com/modalities/time-series) [Diagram: graphs representation: conceptual diagram] Graphs Follow the relationship to a better answer. Connect · traverse · follow Explore model ↗ (https://8braid.com/modalities/graphs) [Diagram: vectors representation: conceptual diagram] Vectors Give a similar result its context. Compare · rank · retrieve Explore model ↗ (https://8braid.com/modalities/vectors) These connections show the models involved in the application design. Compare the supported combination and full workflow with a realistic alternative. Input → usable value / interactive design example Compare the interaction pattern of related signals 0 1 Read signals → 0 2 Define crossings → 0 3 Encode order → 0 4 Compare patterns → 0 5 Inspect the match → [Diagram: time series representation: conceptual diagram] Step 1 / Time series Read a bundle of source-backed time series Measured points, an interval bound and a visible gap retain different meanings along the same timeline. Next: Define crossings Conceptual application workflow. Qualify the supported operations, external tools, protection and persistence for the complete path. These diagrams are explanatory, not measured results. Read the complete workflow and comparison scope Read a bundle of source-backed time series Declare how series become strands and crossings Encode the rank-crossing pattern Compare topology and inspect the source intervals Return a pattern match with its interpretation and limits A static graph and an ordered interaction history preserve different information. Temporal graphs or application-side encodings are legitimate alternatives; compare the exact invariant, query semantics and data preparation. Compare a realistic alternative. A property graph can store events and ordering relationships. 8DB’s case is the implemented braid algebra and its composition paths, not an assertion that another database cannot store ordered data. Neo4j graph concepts (https://neo4j.com/docs/getting-started/appendix/graphdb-concepts/) Compare equivalent outputs and required guarantees, including the simplest single-product alternative where one exists. A specialist may remain the better fit when its operators, ecosystem or operational maturity are decisive. Combining native models becomes valuable when your actual question crosses them. Performance & resources Measure the work that delivers the answer. Encoding invariants and match correctness; strand/crossing count; index/scan complexity; storage/reopen identity; complete source-to-match latency. This draft does not assign a new speed ratio or score to this modality. Existing measurements and source leads are retained in the evidence programme; a qualified public result must identify the particular operation and path tested. Explore the published benchmark evidence (https://8braid.com/benchmarks) What belongs inside the timer and resource budget? For input-to-value testing, declare the input state and the consumer-ready output first. Include parsing, derivation, storage/protection, index readiness, querying, result assembly and delivery as applicable. Identify amortized setup and any work deferred past the finish line. Report database-stage and full-job results separately. Do not add unrelated medians or p95 values, or multiply component speedups into a claimed workflow result. Energy needs measured joules; reduced handoffs alone do not establish a saving. Choose the path that fits your deployment. Verify the supported API/SDK, data format, persistence and indexing behaviour for the release you plan to use. Match the operation-by-modality protection profile and device qualification to the workload. Post-quantum protection (https://8braid.com/pqc) · Plan a workload evaluation (https://8braid.com/build) Related articles Take the next step into the thinking. Mechanism & application 8DB | Beyond Timestamps: Give Interacting Histories a Structure (https://8braid.com/journal/order-is-data-why-some-truths-need-a-braid) Explore the ideas and implementation context behind this capability. Mechanism & application 8DB | Encryption That Remembers How You Got Here (https://8braid.com/journal/when-the-history-becomes-part-of-the-key) Explore the ideas and implementation context behind this capability. Reference / Reviewed 17 September 2026 Readable, shareable and traceable. This reference explains 8DB’s public modality description (https://8braid.com/modalities#explore) with an explicit workload and selection criteria. It is a documentary review, not fresh execution of every operator or platform. Public sources: 8DB modality scope (https://8braid.com/modalities) ; Neo4j graph concepts (https://neo4j.com/docs/getting-started/appendix/graphdb-concepts/) ; the related articles above. Internal source leads and outstanding release checks remain in the editorial record. Download this reference (https://8braid.com/modality-reference/braids.md) Evaluate the question your application needs to answer. Bring the data shapes, input state, expected output and the systems you use today. Define a comparison around that complete job. Discuss your workload (https://8braid.com/build)