The consumer application
Owns the interaction: the group, journey, show, invitation, check-in, and participant controls. Its experience and business logic fit the people using it.
CONSUMER APPLICATION EXAMPLES
The action happens
in everyday life.
Hytch and Tally make the verified-outcomes approach concrete through consumer applications: coordinating a journey or showing up at an event. Arcus focuses on the shared infrastructure model that connects permissioned participation to program decisions, accountable rewards, and privacy-preserving insight.
Discuss your applicationTWO EXPERIENCES. ONE OUTCOME MODEL.
HytchCoordinate a journey
TallyCheck in at a show
Verified Outcomes EngineEvidence · Policy · Decision
An accountable outcome
Record · Authorized reward · Program insight
Record · Authorized reward · Program insight
Conceptual relationship · Product experiences remain distinct
FROM PARTICIPATION TO A PROGRAM RESULT
Consumer experiences make the infrastructure tangible.
People use an application to coordinate, choose, arrive, or check in. An organization needs to understand which action qualified, why it qualified, and what result or reward the program authorizes.
The Arcus infrastructure model
Organizes authorized evidence, program policy, verification decisions, outcome records, reward controls, and permitted reporting across application contexts.
MOBILITY & GROUP COORDINATION
Hytch
The participant experience
Hytch helps small groups coordinate real-world plans and journeys. Its consumer approach brings trip choices, shared movement, and place-aware coordination into the moment people decide how to get somewhere.
The outcome opportunity
A coordinated journey can become evidence for a qualifying trip or arrival. An eligible program can connect that result to a funded incentive and aggregate reporting on repeat participation or mobility goals.
ILLUSTRATIVE PROGRAM CONNECTION
A shared commute
- A group coordinates a journey in the consumer experience.
- Authorized evidence supports the program's qualifying-trip decision.
- The rule determines eligibility for a campaign reward.
- The organization reviews outcomes and cost within its reporting scope.
LIVE EVENTS & AUDIENCE PARTICIPATION
Tally
The participant experience
Tally connects fans, artists, promoters, and venues around live-event participation. A fan's check-in records arrival; corroborating evidence can strengthen the record's stated confidence.
The outcome opportunity
Verified participation can support a record of turnout, permitted referral attribution, and repeat attendance. An RSVP, ticket purchase, or estimate remains distinct from evidence that a participant arrived.
ILLUSTRATIVE PROGRAM CONNECTION
Participation at a show
- A fan checks in through the application experience.
- The arrival retains its evidence and confidence.
- Program rules govern any eligible incentive or next action.
- Permitted reporting informs the venue or campaign.
A FOUNDATION THAT CAN EXTEND
Keep the experience. Share the accountability model.
Arcus is intended to support partner applications beyond these examples. A business can retain its own participant experience while defining the evidence, policies, outcomes, and permitted effects its program needs.
Verification without a reward
A qualifying result can support a participation record or operational decision on its own.
Rewards when the policy permits
Campaign terms and authorized reward capacity govern issuance after the qualifying decision.
Insight within the privacy boundary
Purpose-bound, aggregate reporting can connect participation to program learning without unrestricted individual histories.
These applications illustrate the verified-outcomes model in consumer contexts. The dedicated external Arcus API and commercial integrations are being developed; availability and readiness are defined for each program.
PRACTICAL ANSWERS
Define the program. Understand the result.
Why show Hytch and Tally on the Arcus website?
They make the verified-outcomes model concrete through consumer participation. Hytch is the mobility and group-coordination example; Tally is the live-event and audience-participation example. Their product experiences remain distinct, while Arcus focuses on the shared infrastructure for evidence, program policies, outcome decisions, reward controls, and privacy-preserving reporting.
Does every verified outcome have to pay a reward?
No. Verification can support a participation record, operational decision, or report without an incentive. When a program attaches a reward, explicit eligibility rules and authorized campaign capacity govern that effect. A qualifying outcome and a reward issuance are connected records, not interchangeable labels.
Can another application use the same infrastructure approach?
Yes, the Arcus model is intended to extend beyond these two applications. A partner can retain its own participant experience and business logic while defining authorized evidence, qualifying program rules, reward conditions where relevant, and permitted reporting. A dedicated external Arcus API is being developed; availability is agreed for each integration.
LET'S DEFINE THE OUTCOME
What could your application make accountable?
Start with the real-world action your users take, the evidence they authorize, and the program decision it should support.
Arcus is a platform initiative in development. Pilot scope, integrations, controls, and readiness are agreed for each deployment.