Declared context creates possible relevance—not automatic truth.
Core module · Pulino
Relevance can create value. Trust decides when it moves.
Pulino connects explicit user context, business relevance, rewarded participation, trust rules and wallet states. It is not simply a wallet—and not a system that pays for arbitrary data.
Why it had to exist
User context can create real value, but unqualified context can destroy it. Pulino exists to decide when a user and a business are relevant enough for an economic interaction to make sense.
Primary job
Turn declared context into a qualified, user-chosen relationship while keeping eligibility, verification and value state separate.
Historical Story 3 supports interests, traits, tastes and skills. Later architecture broadens the explanatory set; the page keeps those source levels separate.
Core mechanism
From friction to a usable product flow.
Eligibility determines whether that context applies to a specific opportunity.
The user chooses whether to Follow, participate or continue.
Later interaction and commerce signals can reinforce—or challenge—the declaration.
Context architecture
The questions are not the product. The relevance created from them is.
One person can be relevant to many markets for different reasons. Pulino preserves the reason, confidence level and applicable opportunity instead of flattening every answer into a generic profile.
Explicit context
Interests, traits, tastes and skills create explainable relevance signals. Occupation, vehicle, housing and lifestyle are useful later explanatory examples, not proof of one historical questionnaire.
Eligibility filter
Not every user should qualify for every business relationship. Declared context opens a possibility; applicable rules decide whether the opportunity should be shown.
Qualified opportunity
Only after eligibility should the system expose a matched business, campaign, Follow path or participation event.
Trust economics
Once rewards exist, verification becomes part of the economics.
Historical materials describe participation limits, identity checks at withdrawal and purchase-based reinforcement. They are incentive architecture—not a claim of modern compliance certification.
Declared is not verified
A self-declared trait, an eligibility decision, a behaviorally reinforced trait and a downstream outcome are distinct confidence states.
Limits protect relevance
Unlimited qualification weakens the business value of relevance and increases the incentive to over-claim eligibility.
False qualification matters
The source describes stronger identity boundaries and refund logic where rewarded qualification proved false; exact implementation remains version-sensitive.
Value mechanisms
Different economic events must remain distinguishable.
Pulino can connect context to Follow, Board and commerce-linked value, but each produces a different signal and should not be collapsed into one generic reward claim.
Follow
Business-funded value may attach to a qualified relationship action where configured. Follow is not ownership of the user and not proof of purchase.
Board
Qualified users can learn about a product, answer campaign questions and complete an interaction. That is stronger than an impression and narrower than expertise.
Cashback
An eligible purchase can create a commerce-linked value event and outcome signal. Transaction, validation and settlement conditions remain separate.
Wallet states
The wallet makes value visible. It does not prove qualification by itself.
A qualifying event, validation state and settlement state are separate objects. Main Pulino therefore explains the architecture without presenting an illustrative balance as measured production evidence.
Recorded
The applicable relationship, campaign or commerce event is recorded.
Pending
Qualification, identity, campaign or transaction conditions may still apply.
Available
Value becomes available only after the relevant release and settlement conditions are satisfied.
System interpretation
Pulino creates context. Analytics tests whether the signals agree.
Declared context, qualification, Follow, Board participation, commerce outcome and wallet state stay distinguishable evidence types. Pulino qualifies context; Board qualifies interaction; commerce can qualify outcome; Analytics interprets their relationships.
Product view · 01
Match context to relevant businesses.
Declared context → possible relevance → eligibility filter → qualified opportunity. The breadth of examples explains the architecture without claiming one universal questionnaire.
Product view · 02
The user earns from legitimate participation. The business pays for relevance.
The business is not paying to own the user, and the user is not paid merely for claiming an identity. Value is attached to defined, qualified interactions.
Product view · 03
Keep event, validation and settlement separate.
The wallet is the visible state layer. Exact reward amounts, withdrawal rules and settlement behavior belong to versioned evidence and the separate Earn demonstration.
What the page can establish
Mechanism first.
Performance requires evidence.
- A trust-aware qualification architecture with explicit confidence stages.
- A user-choice model in which relevance can lead to Follow or participation.
- Distinct Follow, Board, commerce and wallet event types.
- A clear connection from context and outcomes to Analytics.
- An economic principle: fund qualified relationships, not ownership of users.
Connected systemContext→Eligibility→Interaction→Verification→Value state→Analytics
Claim boundary
The architecture is source-supported; exact live rules remain evidence-mapped and version-sensitive. Follow is not purchase, arbitrary data payment, universal income or permanent truth. Reward, withdrawal and settlement rules require their applicable source and period.