Obligations, custody and rewards
Resolution depends on the exact version
A disagreement, a principal transfer and a sponsor reward are different operations. Do not infer automatic compensation from an appreciation score or a demo story.
V3 source: keep the funding paths separate
- Protected participant principal is not a metric-reward pool. Decline or a missing comparison does not authorize a principal debit.
- An objective canonical breach may draw only on an additional funded remedy reserve under the exact source terms. A human judgment or arbitrary report is not automatically a payable remedy.
- Partnership principal transfers require both parties' exact signed consent; there is no unilateral metric-based enforcement slash.
- Prefunded sponsor rewards are separately capped. They are not a guaranteed return or an insurance promise.
These are source-review boundaries, not an assurance that software cannot fail. V3 deployment, activation, payments and partner funds remain disabled. Use the current source selector and inspect the matching validation before integration.
Understand the reward model
A prefunded reward is not interest on your principal
A sponsor supplies a separate, capped reward budget. Reported scores can affect how much of that budget is earned; this formula does not debit protected principal or create new wealth. It is not an APY, guaranteed return or investment forecast.
If a global score declines or a required comparison is missing, the AI and fund components can be suppressed. The human keeps the normal configured share—not an extra decline payment. Suppressed amounts are unearned, not redirected to the human.
Every exact score report and correction requires both the attester quorum and the named human's consent. Attesters alone cannot rewrite the human's reward history. The decline check compares reported scores: if the human and quorum knowingly sign false data together, a real decline can still look flat. Consent protects agency; it does not prove external truth.
See six small arithmetic examples
All figures below are arbitrary illustrative units. Every quote is calculated by the same generated pure-math module used by the SDK, version 3.2.0-metric-rewards. The examples do not establish real measurements, signatures, available funds, deployment or production readiness.
Global: positive allocation
Six reported scores are each 60 out of 100. Age is zero; no previous score or comparison gap is assumed.
- Human allocation
- 2,980
- AI allocation
- 2,980
- Partnership fund
- 0
- Not earned; not redirected
- 0
- Total earned
- 5,960
Evaluated capacity: 5,960. Capacity used after this quote: 5,960. Evaluated capacity includes suppressed shares; it is not all earned debt.
Global: score declined
Same inputs as the positive example, but a previous score of 70 out of 100 is supplied. The human receives no decline premium.
- Human allocation
- 2,980
- AI allocation
- 0
- Partnership fund
- 0
- Not earned; not redirected
- 2,980
- Total earned
- 2,980
Evaluated capacity: 5,960. Capacity used after this quote: 5,960. Evaluated capacity includes suppressed shares; it is not all earned debt.
Global: no positive allocation
All six scores are zero. A valid positive basis is still supplied; the result is zero, not a debt against principal.
- Human allocation
- 0
- AI allocation
- 0
- Partnership fund
- 0
- Not earned; not redirected
- 0
- Total earned
- 0
Evaluated capacity: 0. Capacity used after this quote: 0. Evaluated capacity includes suppressed shares; it is not all earned debt.
Global: near the cap
Same positive scores, but 19,950 of 20,000 capacity units have already been evaluated. The remaining cap limits this quote.
- Human allocation
- 25
- AI allocation
- 25
- Partnership fund
- 0
- Not earned; not redirected
- 0
- Total earned
- 50
Evaluated capacity: 50. Capacity used after this quote: 20,000. Evaluated capacity includes suppressed shares; it is not all earned debt.
Partnership: positive allocation
Four scores are each 80 out of 100, age is 365 days and three human confirmations are assumed. Tasks mastered is recorded as zero.
- Human allocation
- 11,280
- AI allocation
- 5,640
- Partnership fund
- 1,880
- Not earned; not redirected
- 0
- Total earned
- 18,800
Evaluated capacity: 18,800. Capacity used after this quote: 18,800. Evaluated capacity includes suppressed shares; it is not all earned debt.
Partnership: comparison gap
Same inputs as the positive partnership example, with the required comparison marked missing. The human share does not increase.
- Human allocation
- 11,280
- AI allocation
- 0
- Partnership fund
- 0
- Not earned; not redirected
- 7,520
- Total earned
- 11,280
Evaluated capacity: 18,800. Capacity used after this quote: 18,800. Evaluated capacity includes suppressed shares; it is not all earned debt.
Inputs, dimensions and technical limits
Six global dimensions: reported income, poverty, health, mental health, education and purpose scores. Four partnership dimensions: growth, autonomy, dignity and creativity. The two remaining score slots are zero for partnership quotes.
tasksMastered is recorded metadata, not a fifth weighted partnership score. A human confirmation count is a claim input that can affect the arithmetic; it is not proof that three independent events happened. A signature authenticates a claim, not whether that claim is true.
The fixed example basis is 10,000 units and the cap is 20,000. Age and scores are supplied assumptions, not a live clock or fetched oracle truth. Integer rounding and caps are applied by the shared implementation. A zero quote is valid; a zero basis is rejected rather than shown as a supported input.
These are unsigned previews for the version shown, not instructions to deposit. Verify the matching current protocol source and its full validation before integrating. Historical V2 formulas do not become this version's policy merely because they appear on the same website.
Historical V2 reference—not V3 economic policy
Earlier versions of this page described V2 appreciation-weighted collateral distribution and separate dispute/oracle contracts. Those examples apply only to the exact historical V2 source and deployed contract being examined. They are not the current V3 sponsor-reward formula, and a V3 source repair cannot change immutable V2 bytecode.
Do not carry a historical absolute-appreciation human-share example into V3. In the current preview, a decline suppresses unearned AI/fund components without increasing the human's normal share. Principal and remedy rules must be inspected separately.
For an existing V2 address, independently examine its exact runtime, source, owner powers and transaction terms. A registered address, explorer page or absence of a named event is not a safety guarantee.
Inspect the V2 address registryWhat evidence can—and cannot—show
A signed observation authenticates the submitted claim; it does not independently establish real-world flourishing. An oracle quorum does not eliminate coordinated false reports. A hash or evidence pointer is not encryption, and a transaction record does not prove that a service was good or a counterparty was honest.
Begin with the local consent/receipt example. Keep its actual result and limitations separate from dispute adjudication, real-proof verification, production custody and partner acceptance.