# E7 ecosystem

Creator and author: **Oleksandr Razinkov**
Website: https://e7gt.com
Contact: oleksandr@e7gt.com
Development snapshot: **10 October 2026**

E7 develops systems that connect sources, transformations, evidence and decisions while retaining context and explicit reliance boundaries.

## Two practical starting points

**E2CI — document and translation assurance:** a bounded offline runtime produces deterministic findings and replayable records from structured evidence. People prepare the input and make professional review decisions. An offline reviewer workspace and explicit reviewer-response workflow remain in open drafts. Explore: https://e7gt.com/e2ci/

**E7DB + E7 Boundary — evidence-native office workflows:** pre-alpha semantic and append-only storage-contract work explores source revisions, interpretations and decision history. Durable storage integration and expanded review/security/recovery experiments remain in an open draft. Full Boundary conformance and production deployment remain open. Explore: https://e7gt.com/e7db-boundary/

## Proposed scoped evaluations

The proposed E2CI assisted pilot covers one source–target batch, language direction and declared use; up to 10,000 source words and 40 named material decisions; one responsible qualified reviewer; and one consolidated correction/reassessment on one revised target. The word allowance supplies context, not a promise of complete word-by-word review or certification.

Deliverables include an agreed decision inventory, exact edition and evidence references, complete machine findings, separately attributed reviewer decisions, revision history and a final scoped report. Completion may retain unsupported claims. Machine checks do not establish semantic correctness, source truth or translation quality.

The proposed E7DB + Boundary evaluation covers one office document workflow and a revision/correction scenario using synthetic or agreed anonymised material. Deliverables are a workflow/boundary map, a scoped evaluation record and an integration-gap list. This is not a production legal or clinical decision service.

Scope, material handling, responsible reviewer, evaluation criteria, fee and delivery date are agreed after intake. Pilot enquiries: https://e7gt.com/pilots/

## Foundation and wider portfolio

- **E7G-T:** geometry-first experimental modelling and constructive calculus. The current canonical reference is v0.15. Bounded executable and formal work has declared scopes; E7C completeness and an all-input Python/IR-to-Lean adequacy bridge remain open.
- **E7 Core:** provisional shared contracts and conformance work within E2CI. A broadly released shared standard/runtime is not established.
- **E7Q:** credential-free v1.0 release candidate rc12, with reference circuits and portable evidence/reporting workflows. Hardware validation and quantum advantage need separate evidence.
- **E7Q-IR:** a core architecture within E7Q with a bounded supplied-QASM/counts demonstrator. It does not execute real hardware or authenticate provider observations.
- **E7FS:** evidence-preserving storage architecture direction; a production file system and recovery guarantee are not established.
- **E7 Fabric:** conditional integration/orchestration direction dependent on independently useful products and validated interfaces.

Consumer projects retain their own pinned profiles and contracts. A new E7G-T reference does not automatically migrate them.

## Inspectable development

Specifications, tests, formal models, deployment evidence and customer outcomes establish different things. Preserve the source, record transformations, identify loss, expose unresolved conditions and state the reliance supported by the evidence.

Current snapshot: https://e7gt.com/development/
Creator: https://e7gt.com/about/
Public E7G-T source: https://github.com/E7GT-Ecosystem/E7G-T
Public E7Q source: https://github.com/E7GT-Ecosystem/E7Q