Documentation / THOR Data
10 / 17
THOR orderbook
Customer demand becomes scoped annotation work, funded rewards and accepted delivery.
On this page
The THOR orderbook connects customer contracts with annotation capacity. Each order defines the work, eligibility, acceptance criteria and reward terms, giving qualified firms access to scoped projects and buyers an accountable delivery process.
Browse the orderbook dashboard for listed work.
During the private beta, qualified, whitelisted firms fulfil orders. Annotation opens to permissionless participation after beta, with task qualification and verification continuing to govern access to work. Participation explains that path.
From contract to accepted milestones
The buyer and THOR agree the brief, output format, acceptance criteria and commercial terms. THOR scopes the work into batches and reserves the full budgeted worker reward from treasury-held alpha before main production begins.
Qualified suppliers complete assignments against the fixed specification. Verification checks submissions, and the buyer reviews delivered batches against the agreed acceptance criteria. Rewards are released under the job's staged payment terms: a verification-linked portion followed by an acceptance-linked portion.
From brief to delivery sets out the workflow. Quality and verification explains the checks supporting delivery.
Why annotation firms participate
Capable annotation teams can have competitive delivery costs while lacking direct relationships with AI labs, procurement access or the sales capacity to win international contracts. THOR brings scoped work and access to buyers, allowing firms to focus on production and quality.
Workable liquidity and clear valuation terms are essential to alpha compensation. The job's payment terms must specify how the alpha amount is determined and valued. Realised proceeds depend on price movements, fees and market impact.
Why buyers pay THOR
The buyer commissions an accepted dataset supported by supplier qualification, project management, quality assurance and accountable delivery. THOR earns its spread by turning distributed annotation capacity into a service the buyer can specify, review and rely on.
The brief defines the required output and acceptance standard. Sample-based checks and the agreed correction process support consistent delivery across suppliers and batches.
How the orderbook connects to alpha
Customer demand defines useful work. Treasury-held alpha funds reserved worker rewards, and customer receipts allocated under THOR's confirmed buyback policy fund purchases of SN112 alpha.
Treasury accounting separately tracks the alpha units reserved and paid, their valuation and movements in the available balance. Contract pricing and supplier rewards are agreed per order. Buyback allocations follow the applicable policy and available customer receipts.
Demand-first token economics explains the reserve, emissions accumulation and customer-funded buybacks.
Public reporting and customer confidentiality
Orderbook payment reporting will show alpha units paid and their USD value at payout. Valuation records will identify the pricing basis and timestamp so readers can interpret the dollar figures alongside the token transfers.
Customer contracts and revenue collected are subject to separate disclosure decisions and confidentiality terms. Public job information can explain the work and its progress while restricting source footage and sensitive customer material to authorised participants.
Governance and transparency explains the wider financial reporting commitments. Data rights and access covers customer material.