Commitment · Structural

The loop is law

adopted a build gate proves it

The kernel names the loops the model must close, each a shape whose edges form one cycle over all its roles, and the build holds every one to at least one instance. Two are named: the accountability loop, in which a campaign is measured by a reading whose evidence is the events that move a person out of the state the campaign targets; and the activation loop, in which what a campaign does is read back through an instrument and a metric to a goal the campaign supports.

What goes wrong without it

A measurement approach that runs from goal to question to metric only earns its keep when the metric's evidence comes back to the goal, and a state machine only means something when its moves are the ones somebody can cause and count. The private platform this model learned from declared every one of these roads and never asked whether energy sent along them came back; the first time the question was asked here, the campaign's own email read back to a goal the campaign did not claim, and its reactivation reading counted nothing directly. Holding the loops closed on every build is what makes the gears a fact rather than a drawing.

What proves it — 1

Each is a gate the build runs: a check inside a ring, a whole ring, or an eval beside them. A build stops at the first that refuses.

registry integritythe loops close
Every pattern the kernel names as a loop is a shape whose edges form one cycle over all of its roles, and the model instantiates it: at least one set of rows stands to one another all the way round. A loop is how the model says its gears connect; a loop that does not close is a picture, and one nothing stands in is a promise.

Derived from — 2

Basili, Trendowicz, Kowalczyk, Heidrich, Seaman, Münch and Rombach, Springer, 2014Aligning Organizations Through Measurement: The GQM+Strategies Approach
David Harel, Science of Computer Programming 8(3), 1987Statecharts: a visual formalism for complex systems

Where this model stands

registry/kernel.json `loops` names PTN-037 and PTN-038, both shapes in registry/patterns.json; FND-034 holds each to being a shape whose edges form one cycle over every role and to at least one instance, bound by the same engine that binds every pattern.

The accountability loop closes through the reactivation formula: the Retention campaign is measured by Reactivation Rate, computed from a formula that takes the conversion and lapse instruments as inputs, whose events move a person out of At risk, the state the campaign targets. It stands twice: once for a conversion, once for a lapse.

The activation loop closes on one assertion the law demanded: the Retention campaign supports Engagement, because its win-back email's reading, Email Engagement Rate, serves that goal; a campaign whose action is read to a goal it does not claim is the gap this loop refuses.

The deliverables door reads in the order the loop is walked, plan, activate, observe, move, read and learn: the Measurement Plan, the Campaign Brief, the Instrumentation Plan, the Lifecycle Map and the Evidence Plan, declared in that order and opened as declared, so the surface hands over the loop one stage at a time and every job belongs to a stage.

What it does not claim

Money enters nowhere: cost is read, never allocated. Budget and Allocation are the next phase's kinds, and the loop that runs from an allocation through the readings back to the next allocation is declared with them.

RUL-048