> ## Documentation Index
> Fetch the complete documentation index at: https://docs.giwa.tokscale.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Manifesto: Proof of Actual Work

> Why an AI-skill premium exists that almost nobody can verify, and the constraints Tokscale accepts to be the exception.

AI usage becomes proof. Proof becomes opportunity.

## Work needs proof

AI-native development is becoming the norm, and the labor market already prices the skill:

* **56%** AI-skill wage premium in 2025, up from 25% (PwC Global AI Jobs Barometer).
* **1/3** of entry-level jobs now require AI skills, nearly triple fall 2025 (NACE).
* **29%** of developers trust AI output (Stack Overflow 2025).

Employers pay a premium for a skill, screen for it at the door, and neither side can verify it. The employer cannot verify the candidate. The candidate cannot verify the tool. Everyone is screening, nobody is proving.

## The existing signals are broken

The two signals the market uses today both fail the same way.

Usage trackers are self-reported. A local token counter knows what the client tells it, and the client can tell it anything. We should know: our open-source project holds exactly this kind of data, submitted by local clients across 41 integrations, and we label it self-reported because that is what it is.

Résumés cannot be verified. A line that says "AI-native workflow" has no evidence behind it. There is no receipt, no record, no root to check against.

Self-reported usage is forgeable. Verified usage is an asset.

## The declaration

Every request a developer routes through the Tokscale Gateway is paid, signed, and recorded. Usage stops being a claim and becomes a receipt. Receipts accumulate into a work history that no one can forge and no one can take away. That history is the Builder Passport.

The mechanics of the loop are on [The Proof Loop](/overview/proof-loop); the tiers that separate self-reported from attested are on [Verified Usage and the Evidence Ladder](/builder-passport/evidence-ladder).

## The commitments we make

A manifesto without constraints is marketing. These are ours.

**Attestations, not tokens.** The Passport is a set of attestations about an address, never a token owned by one. It cannot be sold, because reputation that can be sold is not a credential. There is no Tokscale token in the MVP, matching GIWA's tokenless, compliance-first design. Revenue is the gateway take rate on real inference, not a token launch.

**Privacy by design.** Prompts, code, and responses never touch the chain. What anchors on GIWA is salted commitments and one merkle root per epoch. A builder can prove their usage without revealing anyone else's, and without revealing their own content.

**Availability, not aspiration.** We publish what is live, label what is local, and name what is Phase 2. Today that means: the gateway runs end to end on the hermetic localnet and has no public origin yet, payments are proven on GIWA Sepolia, no public Usage Root is anchored yet, and Passport issuance, Dojang gating, and Earn are Phase 2. The full accounting is on [Live Evidence](/overview/live-evidence).

## Why we hold the line

Judges have seen many teams claim more than they shipped. Almost none have seen a team ship more than they claim. We intend to be the second kind. The record we are building for developers only has value if our own record is exact, so we keep it exact.

*Proof of Actual Work.*

## Next steps

* For the eight rules these commitments turn into, see [Design Principles](/overview/design-principles).
* For the mechanics behind "usage stops being a claim", see [The Proof Loop](/overview/proof-loop).
* For the current accounting behind "availability, not aspiration", see [Live Evidence](/overview/live-evidence).