Sources and exact editions
Link observations and claims to the document revision they came from. Keep time, context and alternative interpretations visible.
E7 Ecosystem /Keep the record.
EVIDENCE / RECORDS / CONTROLLED RELIANCE
Keep the record.
Explain the history.
Declare the boundary.
E7DB and E7 Boundary explore connected document records, inspectable decisions and controlled reliance. Start with one office workflow and a concrete evaluation question.
01 / THE OFFICE WORKFLOW
Keep the history behind the current record.
A document changes. An interpretation changes with it. Someone approves a new use. E7DB explores how to preserve these events as connected evidence rather than flattening them into a latest-value record.
Review and decision history
Connect evidence, rule applications and reviewer decisions. Inspect which conclusion depended on which source or interpretation.
Authority and disclosure
E7 Boundary develops explicit identity, authority and permitted-use conditions at consequential transitions between people and systems.
02 / A WORKFLOW EVALUATION
Test one path through the office.
Choose a document flow
Select one administrative or legal-document workflow with a defined owner, source and review handoff.
Map the record
Identify sources, observations, interpretations, claims, reviewers and decisions. Declare what access and reliance should be permitted.
Evaluate a bounded scenario
Use synthetic or agreed anonymised material to inspect a source-to-decision path and one revision or correction.
Record the gaps
Produce a workflow map, evaluation record and integration-gap list. Agree what further implementation or deployment evidence would be needed.
03 / THE SHARED RECORD
See what a revision changes.
The goal is to preserve an inspectable chain across source revisions, interpretations and decisions. A proposed office interface would make this record easier to review; a finished office deployment is not currently offered.
- Source identity and exact-revision references.
- Evidence, claims, context and alternatives.
- Time-aware histories and inspectable paths.
- Declared reviewer authority and reliance scope.
04 / CURRENT BOUNDARIES
Prototype evidence is a starting point.
Production security and suitability need their own evidence.
E7DB has executable semantic and append-only storage-contract work. A durable XTDB integration and selected security and recovery experiments remain in an open draft. Reported synthetic checks do not establish operational deployment or customer adoption.
Full E7 Boundary conformance has not been achieved. Complete host activation, independent anchors, repair and deployment coverage remain open, along with independent review and operational hardening.
Legal and healthcare examples are document-workflow evaluations. The system does not provide autonomous legal or clinical decisions, and preserving history does not establish correct input or an appropriate permitted use.
A CONCRETE NEXT STEP
Define the question.
Keep the scope clear.
Start with the workflow, intended use and an example of a useful result. Agree the material, review responsibility and evaluation criteria before work begins.