## 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 Neighborhood / structure fidelity 02 Projection / query latency 03 Build & representation cost Include memory, storage, energy and hardware writes # Manifolds | 8DB Product reference. Reviewed 18 September 2026. Implementation and evaluation scope are stated below. Explore the models (https://8braid.com/modalities) / 8DB Manifolds Follow the shape beneath the coordinates. Use supported neighborhood representations and path approximations for data whose local relationships carry useful structure. Explore the capabilities See a complete workload Neighbor · connect · approximate Model / Manifolds Conceptual diagram [Diagram: manifolds representation: conceptual diagram] A curved surface illustrates local neighborhoods and a path along them. The diagram is conceptual. Capabilities What changes Input to value Alternatives Performance Adoption Related articles Reference Start with the operations your question needs. Local chart and declared metric representations Documented geodesic queries Scalar chart-consistency operations Documented product scope, reviewed 17 September 2026. The underlying build and deployment must be qualified for your application. The documented geodesic path uses a neighbourhood graph and shortest-path approximation. Full atlas transitions and arbitrary continuous geometry solvers are separate capabilities; metric suitability requires domain validation. Connected native models Keep the next question within reach. 8DB documents local charts and metric kinds alongside GeoQL operations. An application can make its geometric assumptions explicit and keep the result connected to the observations being compared. [Diagram: spatial representation: conceptual diagram] Spatial data Put the question in its place. Locate · measure · query Explore model ↗ (https://8braid.com/modalities/spatial) [Diagram: graphs representation: conceptual diagram] Graphs Follow the relationship to a better answer. Connect · traverse · follow Explore model ↗ (https://8braid.com/modalities/graphs) [Diagram: tables representation: conceptual diagram] Tables Familiar rows. More context within reach. Filter · sort · project Explore model ↗ (https://8braid.com/modalities/tables) 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 observations along a curved surface 0 1 Receive coordinates → 0 2 Declare the metric → 0 3 Build neighborhoods → 0 4 Follow a path → 0 5 Explain proximity → [Diagram: spatial representation: conceptual diagram] Step 1 / Spatial data Receive observations with their coordinate chart A path passes through a search region. Nearby observations can be connected to their time and source context. Next: Declare the metric 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 Receive observations with their coordinate chart Declare and validate the relevant metric Construct or use the supported neighbourhood representation Compute an approximate path and resolve source records Present proximity with its geometric assumptions Compare approximation error and neighbourhood construction as well as query time. A Euclidean nearest-neighbour result is a different answer when the domain needs surface distance. Compare a realistic alternative. Spatial functions and specialist geometry libraries offer alternative building blocks. Match the geometric question and error contract before comparing speed. PostGIS function reference (https://8braid.com/modalities/https://postgis.net/docs/manual-3.6/reference) 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. Distance/path error against a declared oracle; neighbourhood build time; query latency; metric and chart coverage; memory; input-to-result cost. 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 | What Can Geometry Reveal That Data Points Alone Cannot? (https://8braid.com/journal/one-mathematical-object-six-views-what-a-table-of-samples-can-never-ask) Explore the ideas and implementation context behind this capability. Mechanism & application 8DB | Native Multimodal Data: Connect the Dots Across Graphs, Maps and Time Series (https://8braid.com/journal/modality-is-a-projection) 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) ; PostGIS function reference (https://8braid.com/modalities/https://postgis.net/docs/manual-3.6/reference) ; the related articles above. Internal source leads and outstanding release checks remain in the editorial record. Download this reference (https://8braid.com/modality-reference/manifolds.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)