Strings are not people
Visitors, anonymous claims, qualified identities, feature commitments, beta activations, and active users remain separate numbers. Only the declared qualified or committed class enters a threshold.
Live support · capacity · trust · readiness ledger
The network unlocks what it can sustain.
Features do not unlock because a progress bar filled once. They become eligible only when qualified demand, sustainable support, effective capacity, trust quorum, and operational readiness all meet their published requirements—and stay healthy through a proof window.
No pay-to-vote governance. No imaginary capacity. No automatic activation.
Platform-wide truth first
Current network standing
Loading public ledger…Unmeasured values remain blank rather than becoming zero.
STANDINGNOT EVALUATED
Production standing has not been loaded.
One public state machine
Every feature enters—and exits—the same way.
A lifecycle label is an operating statement, not a marketing mood. Threshold changes require a dated explanation. An unlock that falls below its maintenance floor shows the failing requirement and recovery window.
- 01Measuring InterestDefine the use and blockers.
- 02Gathering SupportPublish every applicable gate.
- 03Threshold ReachedHold through the proof window.
- 04ProvisioningPrepare real operations.
- 05Public BetaMeasure actual use and failure.
- 06UnlockedMaintain the public floor.
- 07At RiskShow the gap and grace period.
- 08Graceful SunsetExport, migrate, and close clearly.
Feature ledger
See the weakest gate—not a blended vanity score.
Unpublished thresholds show as unpublished. Missing signed measurements show as unavailable. Neither state produces a fake percentage.
Evaluating published gates…The browser renders only the server-calculated public snapshot.
No feature matches this view.
Public methodology
Capacity is useful only after reality takes a bite out of it.
Advertised disk, bandwidth, compute, or geography never enters an unlock score by itself. Measurements must use privacy-safe signed aggregates and an independently reviewable methodology.
Lifetime is not monthly
Build reserve, recurring support, unrestricted platform reserve, and feature-directed support remain separate pools. A settled donation never silently becomes a subscription or vote.
Promises are not infrastructure
effective = raw × availability × successful jobs × performance × standing
Launch targets then apply a safety margin before any shared allocation is promised.
A live key is not DNS proof
The ledger counts only fresh possession of independently pinned gate keys. Every real domain still requires direct authoritative-DNS observation.
If the pinned witness quorum disappears, new proofs and publication lock. Existing valid domain credentials are not silently revoked.
Popularity cannot ship unsafe code
Security, recovery, abuse controls, redundancy, monitoring, incident response, exit, and required independent review remain hard gates.
Why minimum?
A weighted average would let an enormous donation disguise missing security or capacity. The weakest applicable requirement is the honest result.
Why no automatic release?
The ledger establishes evidence eligibility. Existing signed Daemonet milestone records still require an independent release signature; this public JSON cannot activate a feature.
Maintenance and exit
Unlocked is a responsibility, not a finish line.
The default model launches with 125% recurring-cost and capacity coverage, warns after seven days below the healthy floor, enters At Risk after fourteen days, and begins a sunset review if critical status survives its published recovery window.
Accept normal growth while reserves and operations remain inside policy.
Publish the failing requirement and recovery action.
Pause growth when necessary; show the remaining grace period.
Begin the announced sunset review rather than improvising.
Graceful sunset contract
Advance warning, new-user cutoff, export instructions, final operating date, self-hosting or migration guidance, entitlement behavior, and stored-data disposition must exist before a capacity-backed feature launches.
Audit the promises
The page and the machine read the same ledger.
The catalog is source-controlled and schema-validated. Live public aggregates are calculated server-side. The snapshot contains no individual names, node addresses, topology, fine-grained location, or application activity.
LIVE JSONNetwork unlock snapshotCurrent aggregates, gates, actions, and evidence status →DEPENDENCIESEngineering roadmap manifestPhase ordering and open technical release gates →ROADMAPEngineering evidence viewRepository, verification, and future work →BOUNDARIESTrust and threat modelWhat the system does—and does not—protect →
Help without becoming inventory
Register interest now. Keep every stronger signal honest.
Private-alpha claims count only as top-of-funnel interest. Feature commitment, directed support, and capacity enrollment remain closed until their own cryptographic and operational controls exist.