Use cases for Users
See how a person can find a Mission, complete a verified action, and understand the reward that follows.
A Member owns the act stage of one shared program lifecycle — the stage where a funded, distributed Mission becomes a completed action.
Find a Mission worth doing
Scenario. A person wants to contribute to a local cause or community project but needs to know whether the action fits their time, location, and interests.
Problem. A reward headline alone does not explain who runs the activity, what work qualifies, or what proof will be requested.
How ZYNC works. The person can review a Space and its Missions, then check the action, timing, eligibility, proof, verification method, and reward terms before joining. The detailed guides explain how to evaluate a Mission and what it means to join a Space.
Expected outcome. The person can make an informed choice and becomes a Member only within the Space they chose.
Relevant capabilities. Space discovery, Mission terms, eligibility, and scoped membership.
Next step. Read how to find Missions that fit.
Complete an action and follow the decision
Scenario. A Member commits to an event, service task, learning activity, or other clearly defined Mission.
Problem. Proof can be confusing or intrusive when the qualifying rule and review process are unclear.
How ZYNC works. The Mission publishes what counts before work begins. The Member completes the action, provides only the requested evidence, and follows an understandable decision state. Learn the four-part Mission completion flow, how to provide useful proof without oversharing, and what verification means in ZYNC.
Expected outcome. The submission is judged against a visible policy, with a clear state and a challenge path where the policy allows one.
Relevant capabilities. Mission completion, proportionate proof, automated signals, human review, holds, and challenges.
Next step. Review the guide to completing a Mission.
Understand the reward after approval
Scenario. A Member’s completion qualifies and they want to know what was earned, whether it is ready, and what can happen next.
Problem. Points, Credits, funded rewards, and ZYNC serve different purposes; showing them as one balance would mislead people. Beta Credits are test value, while cash backing belongs to the production model.
How ZYNC works. Each value lane keeps its own meaning and state. A funded reward can move through pending or held states before it becomes available, and a completed Mission is not the same as a completed cashout. Use the reward-state reference and the plain-language comparison of Points, Credits, and ZYNC.
Expected outcome. The Member can identify the reward type, source, current state, and next available action without assuming one value converts into another.
Relevant capabilities. Reward state history, separate value lanes, Wallet balances, holds, and staged cashout.
Next step. Learn what the Wallet and cashout flow must show.