Understanding Feature Status
How to tell current HeartBadge behavior from rolling-out or future capabilities.
HeartBadge documentation distinguishes durable production behavior from capabilities that are still rolling out or remain on the horizon. A feature should not be treated as available merely because it appears in a concept, architecture, or roadmap page.
Status meanings
- Current. Available in the production product for the eligible account or workflow described. The dashboard may still apply account-specific requirements or limits.
- Conditionally available. Shown only when enabled for the purchase, program, account, region, or operator configuration.
- Rolling out. Being introduced in stages. Not every member, device, program, or operator should expect access yet.
- Coming soon. Planned and actively described, but not a dependable production capability today.
- Horizon. Directional research or longer-term product intent. Details can change substantially before release.
How to verify availability
Use the action, payment method, setting, or status shown in HeartDash or the official checkout. For example, checkout displays only the payment methods currently enabled for that purchase. A roadmap page does not override the options shown in the live product.
Documentation rules
- Current guides should describe observable user behavior, not internal implementation promises.
- Fixed timing should be documented only when it is a dependable product or policy commitment.
- Conditional features should say what determines whether they appear.
- Rolling-out and future features should not be mixed into current setup instructions.
- When the product and an older guide disagree, the live record and supported action take precedence.
Report a mismatch
Send documentation mismatches to docs@heartbadge.com. Include the page, the production screen or workflow involved, and the wording that appears inaccurate. Do not include verification codes, backup codes, private keys, full claim links, or banking credentials.