## 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 Order / join correctness 02 Meet, join & traversal latency 03 Update & retained-state cost Include memory, storage, energy and hardware writes # Lattices | 8DB Product reference. Reviewed 18 September 2026. Implementation and evaluation scope are stated below. Explore the models (https://8braid.com/modalities) / 8DB Lattices Preserve what can be compared. Represent partial order, joins and meets when the relationships among values matter to the application. Explore the capabilities See a complete workload Order · join · meet Model / Lattices Conceptual diagram [Diagram: lattices representation: conceptual diagram] Some values share an order; others remain incomparable. Connections show a partial-order structure. Capabilities What changes Input to value Alternatives Performance Adoption Related articles Reference Start with the operations your question needs. Dominance and partial-order comparison Joins and meets on declared carriers Incomparable frontiers Documented product scope, reviewed 17 September 2026. The underlying build and deployment must be qualified for your application. Each carrier has a different algebra. A confidence join is not automatically a calibrated probability, and a security-label primitive does not prove enforcement on every access path. Connected native models Keep the next question within reach. Typed joins, meets and frontiers give applications operations over bounds and alternatives. The documented time-series path uses interval enclosures, while other carriers represent confidence, labels and clocks with their own rules. [Diagram: graphs representation: conceptual diagram] Graphs Follow the relationship to a better answer. Connect · traverse · follow Explore model ↗ (https://8braid.com/modalities/graphs) [Diagram: hypergraphs representation: conceptual diagram] Hypergraphs Give a shared event its full cast. Group · relate · intersect Explore model ↗ (https://8braid.com/modalities/hypergraphs) [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) 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 Choose what evidence to gather next 0 1 Record candidates → 0 2 Declare the order → 0 3 Keep alternatives → 0 4 Plan an observation → 0 5 Choose the next step → [Diagram: documents representation: conceptual diagram] Step 1 / Documents Record candidate explanations and supporting observations A document is represented through its sections and passages, with a route back to the source. Next: Declare the order 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 Record candidate explanations and supporting observations Represent the relevant order or set relationships Compute which alternatives remain incomparable Relate proposed observations to those alternatives Present an evidence-gathering choice with explicit assumptions The comparison is about preserving distinctions and applying the right algebra. A conventional database can store fields representing these objects; the work to define, validate and apply their semantics still belongs in the evaluation. Compare a realistic alternative. Property graphs and application-side algebra are plausible alternatives. Compare the complete representation and operator contract rather than assuming SQL rows or graph nodes cannot encode the values. 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. Algebra-law and semantic correctness; frontier size; join/meet cost; update behaviour; result explainability; complete planning-response 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 | Eight Explanations. How Can a New Kind of Database Help You Tell Them Apart? (https://8braid.com/journal/when-the-answer-is-more-than-yes-or-no) Explore the ideas and implementation context behind this capability. Mechanism & application When Evidence Changes, Know Which Decisions Need Review (https://8braid.com/journal/a-proof-is-a-graph-where-confidence-only-flows-downhill) 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/lattices.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)