PRODUCT SHAPE AS DATA
Tiers, entitlements, limits and feature switches are rows, not code paths. Introducing a new tier is authoring a set of keys; it does not touch the client, the functions, or the release calendar.
Composable Behavior is the operations track. Where Composable Development decides what the system is made of, Composable Behavior decides what it does — continuously, in production, without a release.
Working name. This track's branding is under review and may change.
Tiers, entitlements, limits and feature switches are rows, not code paths. Introducing a new tier is authoring a set of keys; it does not touch the client, the functions, or the release calendar.
A change to a key collection propagates to every running client on the refresh cycle. There is no build, no review queue and no store approval between the decision and its effect.
Rate limits, quotas and throttles are expressed as limit keys and enforced by a single governor rather than by bespoke checks scattered through the code. Tightening a limit under load is an edit.
What the system does on a timer — refreshes, sweeps, reconciliations — is declared in lifecycle keys with its own interval. Adding, retiming or suspending a task is a data change.
Transaction keys declare which actions are recorded and at what grain. Turning on measurement for a feature that is suddenly interesting does not require the feature to be modified.
Because behaviour is data, a variation is a scoped key set and a rollback is the previous value. Experiments do not fork the codebase and do not have to be cleaned up out of it afterwards.
Observe what the transaction keys are recording. Decide what should change. Author the key. Watch it take effect within one refresh cycle. Keep or revert. The loop closes in minutes, and it closes without engineering capacity — which is what makes it usable by the people who actually own the product decision.
Configuration that can change the product in minutes is configuration that can break the product in minutes. The track is only safe with the disciplines that go with it.
Key collections are a production surface. Who may author them, and the record of who changed what, matter as much as they do for code.
A missing or malformed key must deny rather than permit, and the client must behave sensibly when a collection cannot be fetched at all.
Anyone operating the system should be able to see the effective configuration at a glance, not reconstruct it from several collections.