Plan transitions
A release reaches new subscriptions; existing subscriptions keep their pins and follow their pricing binding.
A release reaches new subscriptions; existing subscriptions keep their pins and follow their pricing binding.
Publishing a new commercial release never edits a subscription in place. Each subscription carries two pins, and every change is classified by what those pins say.
| Pin | Set at | Moves when |
|---|---|---|
| Recurring-price pin | subscription start | Never silently. Only an explicit (post-launch, deferred) move-to-latest operation repoints it. |
| Usage-pricing binding | plan declaration | pricing.current() — follows every activated catalog forward. withContractTerms() — follows activated catalogs while terms change only on agreement amendment. fixedVersion(n) — never. |
current() — applies from the activation of the new
release, forward. Usage already admitted under the old release is rated
under the old release. Nothing is rerated retroactively.NewMeterPolicy / NewMeasurePolicy: adopt_at_current_rate,
exclude_until_renewal, or require_amendment.farthershore build
farthershore commercial-release diff <from-release.json> <to-release.json>
git push
farthershore apply-timeline inspect <business> <commit-sha> \
--env production \
--format json
Review every changed compiled plan and every added or removed rating-context
version. For an active repository-managed business, create a GitHub Release
for the exact reviewed commit only after approval. The initial DRAFT
activation is the sole repository-managed state that uses
farthershore business publish; active businesses reject that command,
including dry-run, with MANAGED_BY_CODE.
A negotiated discount, floor, cap, or pinned catalog version for one customer
is an economic agreement created through the confirm-gated CLI. Releases carry
the public catalog; agreements bind a subject to it with terms. Fixed-version
agreements are require_amendment by definition and never move with a release.
A rollback appends a release-log entry that points at an older immutable release. Requests already admitted under the rolled-back release complete and are rated under it. Business A's rollback never touches business B.