You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Public opt-in: free-tier beta enrollment into amicissimo (spec-first) #849
Problem — Amicissimo ships first to beta testers, and free-tier users must be able to opt in easily. The entitlement resolves via PREMIUM_ENTITLEMENT("amicissimo") today, but there is no opt-in SURFACE: no public command/setting that enrolls an install, no beta-grant story, no update/revocation story for beta testers. Approach — SPEC FIRST (deliberate, two-lens review) before any code. Open questions the spec must settle: (1) what the opt-in grants — a local beta flag vs an account-level entitlement (license machinery is settled: entitlement, never keys); (2) where the opt-in surface lives (a public amicode command/setting — the flow is base, what it unlocks is premium); (3) how beta entitlements expire/rotate and how revocation reaches the client (Slice B's read-only-with-pointer is the client-side landing); (4) the honesty rules — what the user is told they're enabling, and the guaranteed exit (off = byte-identical base, already enforced by H3). Boundary (settled) — the opt-in flow is PUBLIC amicode; the content it stages is premium amicissimo; ADR-0004 + the freeze validator govern what staging may carry.
Important
Problem — Amicissimo ships first to beta testers, and free-tier users must be able to opt in easily. The entitlement resolves via PREMIUM_ENTITLEMENT("amicissimo") today, but there is no opt-in SURFACE: no public command/setting that enrolls an install, no beta-grant story, no update/revocation story for beta testers.
Approach — SPEC FIRST (deliberate, two-lens review) before any code. Open questions the spec must settle: (1) what the opt-in grants — a local beta flag vs an account-level entitlement (license machinery is settled: entitlement, never keys); (2) where the opt-in surface lives (a public amicode command/setting — the flow is base, what it unlocks is premium); (3) how beta entitlements expire/rotate and how revocation reaches the client (Slice B's read-only-with-pointer is the client-side landing); (4) the honesty rules — what the user is told they're enabling, and the guaranteed exit (off = byte-identical base, already enforced by H3).
Boundary (settled) — the opt-in flow is PUBLIC amicode; the content it stages is premium amicissimo; ADR-0004 + the freeze validator govern what staging may carry.