project:atlasRURAL / DATABASEPROTOTYPE IN QUALIFICATION
More dimensions.
One foundation.
Documents tell you what something is. Relationships tell you where it belongs. Time, branches and context tell the rest of the story.
See what exists today01 / DOCUMENTS & MODELSThe shape of
The shape of
everyday work.
Projects, people, products, events. Model real things as documents, with optional schemas and familiar create, read, update and delete operations.
- Nested records and explicit identity
- Optional, versioned schema boundaries
- Atomic changes with a clear transaction boundary
DOCUMENT / ILLUSTRATIVE MODELJSON
{
"id": "project:observatory",
"name": "Observatory",
"kind": "product",
"state": "exploring",
"context": {
"workspace": "main",
"repository": "observatory"
}
}02 / QUERIES & GRAPHSThe connection
The connection
is part of the data.
Relationships deserve more than a field nobody can explain. Connect records with meaning, properties and a source you can trace.
- Explicit relationship types and properties
- Bounded traversal and query plans
- Authorization across edges and endpoints
A CONNECTED MODEL / CONCEPT
REPOSITORYobservatory
produced
DEPLOYMENTrelease-42
observed alongside
BUSINESS EVENTfirst purchase
Correlation is recorded. Causation is not assumed.03 / SNAPSHOTS & BRANCHESA stable past.
A stable past.
An open future.
Read from a committed snapshot. Begin a branch from an existing state. Bring changes back through an explicit merge with visible conflicts.
- Immutable roots and structural sharing
- Recursive branch lineage
- Current permissions across historical views
04 / ANALYTICS & WAREHOUSEFrom what happened
From what happened
to what it means.
Bring product activity and business events into the same context as the work that produced them. Keep raw events, imported reports and derived metrics distinct.
- Event time and ingestion time remain separate
- Explicit correction and deduplication rules
- Coverage and freshness accompany results
THE EVIDENCE CHAINCONCEPT
01
Observe
Raw event · imported report · business record
02
Define
Metric · unit · time window · correction rules
03
Understand
Computed result · source coverage · freshness
05 / ORACLE & MCPGive intelligence
Give intelligence
a sense of place.
A compact interface for discovering context, preparing bounded queries and expanding evidence. Natural-language translation lives outside the database.
- Progressive, authorized discovery
- Aggregation close to the data
- Budgeted answers with inspectable evidence
A SMALL INTERFACE. A LARGER PICTURE.
DISCOVER
Find the relevant, authorized context.
QUERY
Compute a bounded answer.
EVIDENCE
Expand the facts behind it.
CHANGES
Tool contracts are design proposals; see the current docs.Return to what matters next.
CONNECTED RECORDS / INTERACTIVE MODEL
ILLUSTRATIVE DATAFollow a record through its relationships.
Choose a step to see how document identity, a typed edge and branch context combine into one inspectable view.
deploy:atlas:r17source:event-041Atlas is a document with its own stable identity. Relationship details appear as the model expands.
- Select the Atlas project document.
- Follow its typed produced and observed relationships to the deployment and event.
- Read the graph in a named branch view or retained snapshot; permissions still come from the current authority.
CONNECTED DOESN’T MEAN UNBOUNDED.Clear boundaries.
Clear boundaries.
Stronger foundations.
Capabilities matter. So do the rules around them.
The source stays the source.
Repository observations don’t become permission grants. Imported reports don’t become verified business truth.
Trust boundariesEvery request has a limit.
Bytes, work, memory and output belong in the contract. A useful answer should not require unbounded execution.
Protocol boundariesYour data needs an exit.
Recovery, export and verification are part of a database’s responsibility, with explicit delivery gates.
Backup & portabilityDATABASE DEVELOPMENT / RURALStart with the
Start with the
current foundation.
Explore the design.
Check the implementation status.