Core Data Model

Purpose

Entities and relationships that form the dependency graph data model — content units, test items, dependency edges, and run history.

The store SHALL identify each content unit by the tuple (component, path, symbol?).

The store SHALL record, for each content unit, a content fingerprint computed from the normalized unit content.

The store SHALL classify each content unit by kind ∈ {source, config, fixture, lockfile, external}.

GIVEN a content unit being inserted
WHEN the store records it
THEN it SHALL be classified as one of: source, config, fixture, lockfile, or external

The store SHALL identify each test item by the tuple (component, adapter, node_id).

The store SHALL record each dependency edge as (test_item, content_unit, environment, origin, K-value).

GIVEN a dependency between a test and a content unit
WHEN the dependency is recorded
THEN it SHALL include test_item, content_unit, environment, origin, and K-value

The store SHALL permit static, runtime, and manual edges to coexist for the same (test_item, content_unit, environment) triple.

GIVEN a test_item, content_unit, and environment triple
WHEN edges of different origins exist
THEN the store SHALL permit all three origins (static, runtime, manual) to coexist

The store SHALL maintain a reverse index from content unit to dependent test items.

GIVEN a content unit
WHEN querying for dependent tests
THEN the store SHALL return all test items that depend on it via the reverse index

The store SHALL partition all edges and statistics by environment fingerprint.

GIVEN multiple environments with different fingerprints
WHEN querying edges or statistics
THEN the store SHALL return results scoped to the specified environment fingerprint

The store SHALL record per-test run history including outcome, attempt count, duration, and error signature.

GIVEN a completed test run
WHEN results are ingested
THEN the store SHALL record the outcome, attempt count, duration, and error signature for each test