# Lets Litepaper 2026 Lets is a new kind of social network. It starts with familiar activity: posts, profiles, messages, communities, support for people, and clear rules. The ambition is larger than another feed: make contribution visible, give communities a calm way to express direction, and build an accountability contour where decisions, rules, and team actions can be explained publicly. The Litepaper is the short version. It does not replace the White Paper, community rules, support, or legal disclosures. Its job is to explain what Lets is building now, what the mobile beta tests, and which ideas belong to the longer-term project direction. ## 1. Social Network First People do not join Lets to read architecture documents. They join to post, talk, find people, support creators, take part in discussions, and feel that useful contribution does not disappear after a few hours. That is why the mobile beta starts with a clear product: feed, profiles, replies, messages, privacy controls, reports, and support. If the social foundation does not work, the larger ideas do not matter yet. The beta tests onboarding, interface clarity, conversation quality, safety, and the understandability of new features. A person should understand Lets as a social app before they meet words like DAO, LEC, or protocol. ## 2. Contribution Should Be Visible In many social products, useful actions sink quickly. Someone helps a newcomer, explains a conflict carefully, reports a real issue, suggests a community idea, or gathers people around a useful topic, and a day later that work is hard to see. Lets is built around a different idea. Contribution is not only posting. It includes discussion, support, responsible reports, Decision participation, practical help, community building, and a willingness to stand behind actions. Visible contribution helps separate real participation from noise, while rules, support, and human review still handle difficult situations. ## 3. Glints: Recognition Inside The App Glints are an internal Lets feature for support and recognition. A Glint can say thanks, recognize useful contribution, support a creator, or show that a person's action was noticed. For an everyday user, it should feel like a clear social signal inside the app. Glints are not money, crypto, or an entitlement to LEC. Glints do not change Decision vote weight, replace moderation, create a special review path, or promise abilities outside the current product. In beta, Glints remain part of the Lets social experience, and their rules can be refined as the product is tested. ## 4. Decisions: One Account, One Voice Decisions give the community a simple way to express views on product direction, rules, and priorities. In the mobile beta, the principle is one account, one voice. That matters because voice should not depend on Glints, status, activity volume, or closeness to the team. A Decision does not have to change the product immediately. It can lead to a plan, experiment, human review, public report, or an explanation for why the team is not acting now. The main value is follow-up: people should see that the signal was heard and the next step was explained. ## 5. Safety, Reports, And Moderation Lets cannot be a strong product if people do not feel safe using it. The app needs reporting, blocking, support, appeals, community rules, and protection from pressure around Decisions. Private reports and report materials should not become public arguments. Moderation needs context. The team has to consider repeated accounts, spam, manipulation, harassment, impersonation, exposure of personal information, and pressure on participants. Public rules explain boundaries before problems happen, while private review protects people in specific situations. ## 6. Creators And Communities Lets matters for creators, groups, and local communities that build trust around themselves. They need discussion, feedback, visible support, clear participation rules, and a transparent explanation of what happens after important Decisions. Advanced creator tools, partnerships, and separate programs should launch separately from the basic mobile beta. They need review, rules, and abuse protection. The beta first proves that ordinary social flows are understandable and safe. ## 7. DAO Accountability Contour The long-term Lets idea is a social network with a DAO accountability contour. This does not mean that a mobile beta user has to operate a complex system. It means a direction: public rules, understandable Decisions, follow-up reports, responsible roles, and a verifiable relationship between contribution, trust, and product development. DAO accountability is not a slogan. It is a way to make community power more explainable. Who proposed a change, what signal the question received, what the team did next, and why a decision was made or delayed should become part of the product culture. ## 8. AI Direction Lets should grow with AI features, but not as a replacement for people. AI can help find important discussions, explain rules in plain language, surface related questions, reduce noise, assist support, and make public reports easier to understand. Safety decisions, sensitive reports, restrictions, and important product changes should not become invisible automation. The AI direction should improve clarity and quality while keeping responsibility visible. ## 9. LEC, Protocol, And The Mobile Beta Boundary LEC and the protocol layer belong to long-term architecture and project documentation. They are not required mechanics in the mobile beta. A person does not need external technical setup to post, talk, support people with Glints, or participate in Decisions. This separation protects Lets from confusion. The mobile beta tests social value, trust, rule clarity, and product quality. Protocol direction needs separate review, constraints, public documents, and decisions before anything expands beyond the ordinary mobile experience. ## 10. What The Beta Tests The beta needs practical answers. Do people understand that Lets is a social network? Are Glints clear as recognition inside the app? Do participants understand that Decisions use one account, one voice? Are reports, support, privacy, rules, and beta boundaries clear enough? The beta also tests trust in the project direction. Do people see the difference between product, Litepaper, and White Paper? Do they avoid confusing Glints with influence? Is it clear that DAO, LEC, and protocol are a long-term documentation and accountability contour, not a requirement for participating in the mobile beta? ## 11. Where To Read Next - Product: core app flows, Glints, Decisions, safety, and beta access. - Litepaper: a short explanation of the Lets idea, boundaries, and direction. - White Paper: the full project description, long-term architecture, and accountability contour. - Safety and support: rules, reports, blocking, appeals, and help with specific situations. Lets can be ambitious only if the simple parts stay simple. The mobile beta should be an understandable social network, while the bigger ideas are explained separately, honestly, and in a way people can verify.