Module distributed tensor Architecture

Distributed Tensor Module Architecture

Overview

src/distributed_tensor defines EPIC 3 contracts for portable tensor artifacts, manifest management, shard placement, integrity verification, recovery management, distributed planning, and tensor infrastructure coordination.

Current architecture is implementation-first for Phases 1-3: headers define the public contracts, translation units provide the default runtime behavior, and the focused EPIC 3 regression suite verifies the new failure/degraded-mode semantics.

Component Map

Source files and public headers are now implemented. The table below documents the active ownership map used by the current build.

Component	Active contract	Active implementation
Artifact classes	include/tensor_artifact_classes.h	src/tensor_artifact_classes.cc
Manifest schema	include/artifact_manifest.h	src/artifact_manifest.cc
Shard placement	include/shard_placement.h	src/shard_placement.cc
Integrity verification	include/integrity_verification.h	src/integrity_verification.cc
Recovery manager	include/recovery_manager.h	src/recovery_manager.cc
Distributed planner	include/distributed_planner.h	src/distributed_planner.cc
Tensor infrastructure	include/tensor_infrastructure.h	src/tensor_infrastructure.cc

Boundaries

In scope:

• EPIC 3 contract ownership, sequencing, and default runtime behavior
• integration seams with EPIC 1 retrieval and EPIC 2 evaluation
• phase-gated readiness documentation and focused regression coverage

Out of scope at the current stage:

• finalized scale and fault-injection benchmark outcomes
• default pipeline enablement

Integration Surfaces

• Planning: docs/EPIC3_ARCHITECTURE.md and EPIC 3 sub-issue docs
• Public contracts: include/distributed_tensor/*.h
• Runtime implementation: src/distributed_tensor/*.cc
• Focused verification: tests/epic3_distributed_tensor/test_phase3_failure_semantics.cpp
• Dependency sequencing: docs/EPIC1_2_3_DEPENDENCIES.md

---

ThemisDB 1.9.0-beta · Home · Module-Index · GitHub · Issues