Join in
Write the story, pick the closest box, and let other people help shape the next step.
Claims App
One connected claim flow.
Claims.promo is the work room and promo.claims is the promotion lane. They are one app state with two routes, tied together by the same proof.
Connected app flow
1ClaimWork starts in claims.promo with sources, needs, and counterclaims.
2ReviewModeration, translation, legal context, and proof bind the claim.
3PromotePromo.claims shows what is allowed to move forward.
4Feed backRegulation.community decides what the app should upgrade next.
Community builds app
Regulation.community decides what promo.claims and claims.promo become. The app domains receive the result after proof.
Proof behind it
Before changes reach users, browser, DNS, node, privacy, rollback, and release proof must pass.
One store app
Apple, Google, Microsoft, and desktop builds use the same account and same app state. The two domains are routes, not two separate user worlds.
Connect to server
The app asks for eligible nodes, chooses a working route, proves TLS, then syncs profile, messages, votes, and flow history.
Store rules gate
Terms, privacy, report, block, moderation, account deletion, and AI safety must pass before a public app release.
AI helper at the bottom
User writes rawNo perfect words needed.
AI asks calmlyProblem, idea, rule, or question?
User approvesThen it enters the public flow.
Rules by place
Country, region, privacy, retention, age, and platform rules can change what a user needs to see.
Fast routes
Apps should receive working nearby endpoints while ns3+ worker nodes upgrade in waves.
Source direction
The project is built toward open source snapshots, while fast AI-generated changes stay attached to proof history.
System statusBrowser TLS is green after proof.
CertificateIssued by Let's Encrypt and served from kernel-owned sector45/profile3.
IPv6AAAA is enabled after IPv6 HTTPS proof.
Release rulePublic copy and app release follow proof and store rules only.
LECertificate issued by Let's Encrypt
This page publishes flow receipts instead of source dumps. It is served from the system authority path; no separate web runtime is required for this surface.