BELA65 — Claims Ledger
This is the most important governance document in the Launch Studio. No asset — no video, headline, deck slide, or FAQ — may claim a capability unless that capability appears in this ledger with a sta
The honesty firewall: nothing gets claimed publicly unless it's listed here
This is the most important governance document in the Launch Studio. No asset — no video, headline, deck slide, or FAQ — may claim a capability unless that capability appears in this ledger with a status. This is how we guarantee we never market a future feature as if it exists today.
Executive Summary
Every capability BELA65 might mention falls into one of four honesty tiers. Assets must label capabilities using these tiers whenever there's any doubt, and must never present a lower tier as if it were "Available Today."
The Launch Studio does not have independent, real-time confirmation of the live production state of each stage. Per our operating rules, anything not explicitly confirmed by the Founder as "Available Today" is written conservatively. This ledger starts every claim in a defensible position; the Founder promotes items as they're verified.
The Four Honesty Tiers (reuse these exact labels everywhere)
| Tier | Label | What it means | How assets may phrase it |
|---|---|---|---|
| 1 | Available Today | Works in the product now; a customer can rely on it. | Present tense, confident: "BELA understands your business." |
| 2 | In Progress | Actively being built; partially working. | "is being rolled out," "early access." Never bare present tense. |
| 3 | Planned | Committed on the roadmap; not built. | "on the roadmap," "coming in a future version." Always future tense. |
| 4 | Future Vision | Direction/ambition; not committed to a date. | "our vision," "where we're headed." Clearly aspirational. |
Golden rule: when unsure which tier, drop one tier down (be more conservative), not up.
The Ledger
Status key: ✅ Available Today · 🔧 In Progress · 🗓️ Planned · 🔭 Future Vision · ❓ Needs Founder confirmation (written conservatively until confirmed)
The Claim wording column is the maximum an asset may say. Writers may say less, never more.
Core Pipeline
| Capability | Default status | Claim wording (max allowed) | Confirm? |
|---|---|---|---|
| Business Understanding | ❓ → treat as In Progress publicly | "BELA works to understand your business before building." | Needs Founder |
| Clarification (asks questions) | ❓ → In Progress | "BELA can ask clarifying questions when something's unclear." | Needs Founder |
| Business Reality Model (BRM) | ❓ → In Progress | "BELA builds a model of your business." | Needs Founder |
| Architecture design | ❓ → In Progress | "BELA designs the software's architecture." | Needs Founder |
| Engineering Reality | ❓ → In Progress | "BELA assesses what it takes to build." | Needs Founder |
| Technology Provider Selection | ❓ → In Progress | "BELA selects appropriate technologies (provider-neutral)." | Needs Founder |
| Project Assembly | ❓ → In Progress | "BELA assembles the application." | Needs Founder |
| Testing | ❓ → In Progress | "BELA tests what it builds." | Needs Founder |
| Self Review | ❓ → In Progress | "BELA can review its own work." | Needs Founder |
| Self Repair | ❓ → In Progress | "BELA can repair issues it finds." | Needs Founder |
| Qualification | ❓ → In Progress | "BELA qualifies the result against a standard." | Needs Founder |
| Certification | ❓ → In Progress | "BELA certifies readiness." | Needs Founder |
| Deployment | ❓ → Planned (conservative) | "Deployment is on the roadmap." | Needs Founder |
| Engineering Passport | ❓ → In Progress | "Each application can carry an Engineering Passport of how it was built." | Needs Founder |
Signature Properties
| Capability | Default status | Claim wording (max allowed) | Confirm? |
|---|---|---|---|
| Explains every engineering decision | ❓ → In Progress | "BELA aims to explain its engineering decisions." | Needs Founder |
| Provider-neutral (multi-technology) | ❓ → In Progress | "designed to be provider-neutral." | Needs Founder |
| Fully autonomous end-to-end | ❓ → In Progress | "runs the engineering lifecycle autonomously." | Needs Founder |
| Continuous Evolution (app keeps improving) | ❓ → Planned | "Continuous evolution is planned." | Needs Founder |
Metrics & Numbers
| Claim | Default status | Rule |
|---|---|---|
| Any speed multiple ("10x faster") | 🚫 Do not use | Only permitted once a measured, sourced figure is approved and added here. |
| Any cost-saving figure | 🚫 Do not use | Same — needs a real, cited source. |
| Any "number of apps built / customers" | ❓ | Leave out until Founder provides a verified number. |
| Market size / TAM (investor decks) | 🗓️ Planned/sourced only | Every figure must cite an approved source, or it's marked "illustrative." |
Simple Explanation (for anyone)
We made a promise to never lie or exaggerate. This page is how we keep it. Before anyone writes "BELA does X" on a website or in a video, they check this list. If X isn't marked "Available Today," they either say it's coming, or they don't say it at all. That's the whole system.
Business Explanation (for a business owner)
Trust is our most valuable asset, and the fastest way to lose it is to promise something the product can't do yet. This ledger is our internal contract: it separates what BELA can do today from what's coming. It protects customers from disappointment and protects us from claims we can't stand behind.
Technical Explanation (for a CTO / engineer)
This is a claims-governance artifact. Each publicly stated capability maps to a status tier and a maximum-allowed phrasing. The default posture is conservative: unverified capabilities are written as "In Progress" or "Planned," never as steady-state features. Numerical claims require a cited source before use. Downstream assets are non-compliant if they exceed the ledger's wording — this is checkable in review.
Key Messages
- Nothing is claimed publicly unless it's in this ledger.
- Four tiers: Available Today, In Progress, Planned, Future Vision — and we never promote a claim up a tier.
- When in doubt, we say less, not more.
- Numbers require sources. No exceptions.
How the Founder promotes a claim
When a capability is verified as live, change its status to ✅ Available Today, update the "Claim wording" to confident present tense, remove the ❓, and add a line to Version History. All downstream assets may then use the stronger wording. Until then, the conservative wording stands automatically — no asset is ever blocked waiting on this.
Future Improvements
- Add a per-claim "evidence link" column pointing to the certification report or a demo, once the Founder confirms which internal source is the public-facing proof.
- Add an automated check that flags any asset phrase exceeding the ledger wording.
- Version this ledger alongside product releases so claims and reality never drift.
Version History
| Version | Date | Change | Author |
|---|---|---|---|
| 1.0 | 2026-07-02 | Initial Founder-Ready ledger. All core claims defaulted to conservative tiers pending Founder confirmation; numeric claims blocked until sourced. | Launch Studio |
More in this section
Turn a business need into software.
This document is part of the BELA65 Launch Studio.