Concepts for reading product boundaries.

Use these pages when product names, storage words, replay words, or maturity labels overlap. Concepts explain how to reason about the system before moving into product hubs, references, compatibility matrices, or limits pages.

Concept Index

Stornamics system map
Available: DOCS-044
See how ObjectDB, Message Broker, Concordia, and LogDB relate without turning likely integration paths into current runtime guarantees.
Product mental models
Available: DOCS-045
Object/version/manifest, stream/queue/replay, placement/gateway/storage, and envelope/segment/query concepts.
Durability and evidence levels
Available: DOCS-046
Local, durable, committed, replicated, preview, and verification-required language for docs claims.
Tenancy and security concepts
Available: DOCS-047
Tenant, dataset, stream visibility, auth modes, bearer tokens, trusted headers, and current review gates.
Diagram accessibility review
Available: DOCS-048
Architecture diagram surfaces, text equivalents, clear labels, semantic reading order, and owner review routing.

Concept Guardrails

Separate Role From Runtime Support

A product can have an obvious architectural role without every integration path being implemented or reviewed as supported.

Use Evidence Before Promotion

Compatibility matrices, known-limits pages, and evidence indexes decide whether a concept can be stated as live, alpha, preview, future, or verification-required behavior.