Home/Modules/churn

churn

system module churn

Churn — data, dimensions, constraints, and inheritance

Churn organizes five complementary ways to model a magnitude. Each numbered set has a distinct primary dimension, but all sets share provenance and quality rules, the three-domain grouping (math, physics, social), and a constraint layer.

See DATA-CATALOG.md for the cross-dimensional data catalog, shared record contract, import policy, and integration roadmap.

Set index

SetDimensionCore modelQuestion
1 — Longstemporal seriesLong and pairwise relevanceHow do measurements co-vary across periods?
2 — Structuresstanding scalarStructureWhat is the value, unit, and evidence kind?
3 — Facetsobject + selected faceFacetWhich property of which object is described?
4 — Areastwo-dimensional extentAreaWhat extent is occupied, and relative to what?
5 — Linesone-dimensional count/lengthLineHow far does a count or length reach, and what Spark guides its reading?

Organization

Each set keeps its model source and local explanation beside the data it interprets. Sets /2–/5 group inputs under data/ and domain explanations under models/; /1 keeps its annual series in longs.csv and its separate assumptions layer under assumptions/.

Shared data contract and relationships

These are conceptual/data-contract relationships, not claims that SLeeLa currently implements class inheritance between the five model structs.

  1. Shared evidence contract. Factual records should identify their name, value(s), unit or measurement basis, evidence kind (EXACT, MEASURED, or OBSERVED where applicable), source/provenance, and date or period when values can change.
  2. Domain is cross-cutting. Math, physics, and social classify the subject; they do not replace Long/Structure/Facet/Area/Line.
  3. Derived relationships must be explicit. A Facet should identify its source object(s); an Area derived from geometry should identify its formula and inputs; a Line derived from a count or length should retain its unit and source. Do not conflate formulas, measurements, and observations.
  4. Temporal joins need matching periods. Longs should document period, frequency, units, and fiscal/calendar-year differences before series are compared. Correlation is descriptive, not causal.
  5. No speculative imports. Add data only with a verifiable source, retrieval/update date, units, evidence kind, and an explanation of how it enriches the model. Prefer updating a canonical dataset over duplicates.

Build and validation

From the repository root:

make churn
make churn-data-check
make churn-test

Or from this directory: make all, make test, make clean.

The data check parses JSON/XML/CSV/TXT, checks CSV headers and row widths, detects duplicate IDs in supported record arrays/CSV ID columns, validates evidence-kind values, and enforces the opt-in churn-1 JSON contract. It does not establish scientific correctness, unit compatibility, referential integrity, or that sources are still current. Java constraint reports are generated outputs and remain ignored by Git. See DATA-CATALOG.md for the recommended validation roadmap.

Evidence discipline


SLeeLa

<p align="center"><img src="images/sleela/sleela-wordmark.svg" alt="SLeeLa — The Now. The Ingredient." width="560"></p> <p align="center"><img src="https://github.com/mearvk/SLeeLa/blob/master/images/sleela-programming-language-002.jpg" alt="SLeeLa Marketing Logo" width="560"></p>

Files 67