Skip to content

ARCHITECTURE.md

Latest commit

 

History

History
53 lines (36 loc) · 1.6 KB

ARCHITECTURE.md

File metadata and controls

53 lines (36 loc) · 1.6 KB
Raw

Architecture

Tracebench is organized as a generic observability pipeline.

trace-like input
  → difference frame
  → distinction event
  → trajectory artifact
  → pathology signature
  → artifact registry
  → retrieval / comparison / clustering
  → validation packet

First-class objects

  • trajectory_artifact
  • pathology_signature
  • failure_vector
  • signature_cluster
  • nearest_neighbor_result
  • validation_packet

Core boundary

The public core is intentionally generic. It contains observability primitives, synthetic/test fixtures, and validation packet machinery.

It does not contain private model adapters, DAW instrumentation, production telemetry wiring, proprietary extractors, calibration logic, real traces, tensors, corpora, or deployment-specific provenance mappings.

Separation from admissibility

Tracebench records and compares observations.

It does not decide whether a candidate is admissible, does not issue receipts, and does not mutate authoritative state.

The intended architectural relationship is:

Tracebench
  observation surface / evidence packet

Constitutional Runtime Substrate
  admissibility surface / receipt / lineage / replay

The two are complementary, not interchangeable.

Adapter posture

The public repository may document generic adapter interfaces and synthetic examples.

A real domain adapter should be treated as a separate integration with its own verification boundary. The existence of an adapter interface must not be read as evidence that any private adapter, extractor, or telemetry provenance path is included here.