docs(adr-0036): record the trial end moving from a fixed date to a notice commitment #101
Inga granskare
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-docs!101
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "work/84"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
ADR 0036 described a fixed trial end date. Two things have happened since, and the record now carries both.
§3
What shipped was floor framing, not a fixed date: the trial ended when paid accounts launched, and 31 August 2026 was only the earliest that could happen. Every user-facing surface used it consistently, in both languages. The same fixed-date claim had reached the operator runbook, where it was actively misleading; corrected in bitborg-infra#422, with bitborg-infra#270 recording the decision to hold the downgrade.
The floor is now removed. No public surface states a date at all. The trial ends when paid subscriptions launch for everyone, and users get at least 30 days' notice before it does. That notice, not a date, is the user's protection.
Removing the floor takes nothing from anyone who already signed up. 31 August 2026 has passed and the floor was honoured in full for as long as it stood. The terms text changed, so
TRIAL_TERMS_VERSIONinbitborg-web/src/pages/api/signup.tsand the "Last updated" line insrc/content/{sv,en}/trial-terms.mdmove to 2026-09-21 together.§5
No date is held anywhere. Nothing tracks a date or the launch condition, and an operator runs the downgrade by hand, which is what makes holding it safe.
The 30 days' notice is now an ordering constraint on that procedure, not just copy on a page. The runbook makes sending the notice and letting it elapse a step that must complete before the batch runs, and closes the trial door first so the set of people owed notice stops growing.
Both sections keep the original decision text and record the change as an amendment, because the fixed date genuinely was the decision and the path away from it is worth being able to see.
Companion branches carry the same change in bitborg-web (the public copy) and bitborg-infra (the runbook procedure).
Closes #84
f740b40e53514015ca0f514015ca0f22d2901becdocs(adr-0036): amend the trial-end framing to match the shipped copytill docs(adr-0036): record the trial end moving from a fixed date to a notice commitment