recon_gen.common.spine.generator
ViolationGenerator Protocol — the producer.
A ViolationGenerator claims to manufacture a specific Violation by emitting base-table rows. Producer ≠ thing-produced: the generator is not the violation; it CAUSES one. The spine link is
Invariant[T].detect(ViolationGenerator[T].emit()) ⊇ {intended}
— pinned in-process by tests/unit/test_ap3_invariant_self_validation.py and threaded end-to-end through the spine for drift by tests/unit/test_as0_drift_full_spine.py.
The Protocol is minimal: intended (the Violation the generator claims to cause) + emit(conn) (writing the rows). Concrete generators specialize freely:
Single-shot row emitters for trivial cases (the AP.3 spike’s first pass — adequate for ad-hoc tests).
Stateful folds (the AP.2 shape: State -> (flows, State’) over days, carrying the running balance forward; AS.3 lands the base class for this).
Cross-account vector folds (AS.4 — same Protocol, state generalizes from scalar balance to dict[account_id, balance]).
Promoted from tests/unit/test_as0_drift_full_spine.py by AS.1.
Classes
|
A producer of base-table rows intended to manifest intended. |
- class recon_gen.common.spine.generator.ViolationGenerator(*args, **kwargs)[source]
Bases:
ProtocolA producer of base-table rows intended to manifest intended.
intended is a @property (not a bare attribute) so concrete generators can derive it from their construction params — e.g., a DriftGenerator whose intended Violation includes its anchor day and resolved account_id, computed at access time.
AY.2.a — intended is typed Violation | None. The None case is the AP.2 non-violating shape: FanInChainGenerator(expected_ kind=’healthy’) plants parent_count = expected, so the fan_in_disagreement matview’s CASE produces no row, so the generator claims no Violation. AY.2.b’s CoverageObservation layering may flip the healthy variant to return a non-None CoverageObservation (signalling “I planted a chain firing”), but the Protocol stays widened to accommodate either shape.
emit(conn) writes the rows. Generators MAY also commit or refresh matviews internally, but most leave that to the caller so a single scenario can compose multiple generators against ONE connection and refresh once at the end (the AP.3 _assert_self_validates pattern).