1. Model one complete job
Use an outcome guide to identify inputs, operations and the useful result. Avoid treating a list of supported data shapes as proof of a complete workflow.
Technical guides
A clear route into the architecture.
Start with the part of 8DB you need to understand, then follow it to operations, worked examples and supporting evidence. These are product and architecture guides; SDK access and integration details are agreed for your evaluation.
01 / The practical advantage
Choose your entry point.
Each guide answers a different engineering question. Model breadth, protected exchange and transaction behavior become useful when you connect them to one workload.
01
Represent and query
The model directory links to 17 permanent references with operations, examples, distinct capabilities and performance evidence where available.
Open model references →02Protect and govern
Read the cryptographic reference, migration evidence and qualification boundaries alongside the lifecycle questions in Security.
Read the encryption reference →03Execute and verify
Understand programmable transactions, then connect execution to proofs and the evidence your application needs to retain.
Explore transaction behavior →02 / Scope and evidence
A practical evaluation sequence.
Public API and SDK documentation will expand with qualified releases. This directory links to the substantive references available today.
Open the evidence library →2. Inspect the implementation evidence
Read linked fixtures, articles and qualification notes. Keep build, hardware, dataset, cryptographic profile and excluded work with the result.
3. Confirm integration access
Discuss your platform, language or binding, deployment and recovery requirements. Agree on the exact artifact and instructions before planning implementation around an assumed SDK.
Keep moving