The public standard / version 1.0
How we keep the claim smaller than the evidence.
These are the public rules behind the stage labels, product boundaries, and release language across the Mythril Devs portfolio.
1. Evidence outranks ambition.
Planned, implemented, demonstrated, externally observed, and measured are different states. Public copy names the strongest state the evidence supports—never the state we hope to reach next.
2. Stage changes require gates.
“Alpha” means a primary path works end to end in a controlled environment. “Beta” requires a bounded release that external testers can use. “Pilot” means a time-boxed external engagement is active with named objectives. “Production” requires a monitored, supported release with rollback and incident handling.
3. Owner control is architecture.
Identity, authorization, budgets, tenant scope, revocation, retention, and human approval are not paperwork outside the product. They are product surfaces that must remain visible, testable, and recoverable.
4. Human judgment stays at consequential gates.
AI can extract, compare, summarize, and assemble evidence. It does not validate its own findings or quietly promote a suggestion into durable truth. A named human approves consequential publication, access, or action.
5. Privacy begins with less data.
Products collect and move only what their purpose requires. Demonstrations use synthetic or explicitly approved data. Secrets, raw customer evidence, private identifiers, and confidential screenshots do not enter public artifacts.
6. Cloudflare services follow the access pattern.
Workers execute edge logic; D1 holds relational state; R2 holds objects; Durable Objects coordinate strongly consistent entities; KV carries configuration and short-lived state; Queues move retriable work off the request path. Bindings are preferred over unnecessary public service hops.
7. A release leaves a record.
A meaningful release records the commit, environment, checks, deployment, smoke evidence, known limitations, rollback path, and post-release verification. A green build is useful evidence, not the entire acceptance case.
8. Products stay independently accountable.
Mythril Devs supplies the shared thesis and operating standards. Each product keeps its own customer, data boundary, architecture, next gate, cost model, and public claims. Shared infrastructure is extracted only after reuse is demonstrated.
9. Accessibility and performance are release behavior.
Public surfaces are built with semantic HTML, complete keyboard paths, visible focus, sufficient contrast, reduced-motion support, and useful content without client JavaScript. Performance and accessibility regressions are defects, not polish work.
10. The next gate is always public.
A product page names not only what is deployed, but what remains unproven. This keeps partners, investors, testers, and the product team oriented around the same reality.