scalar
Participate

Use · Build

Define a job. Specify success.

Building on Scalar is mostly an exercise in writing job specifications that another participant could independently test. Developer access is not open yet — this page describes the intended interface.

Developer access not open

Integration shape

What an application does

  1. Specify
    write the job
  2. Submit
    to the network
  3. Await
    work + validation
  4. Receive
    result + provenance
  5. Consume
    Cortex context
Illustrative job specificationNot a live API
{
  "job": "probability_estimate",
  "version": "0.1",
  "request": "Estimate P(outcome) for the specified event",
  "input_boundary": ["event_id", "public_sources"],
  "execution": { "class": "llm_ensemble", "min_models": 3 },
  "output_schema": {
    "probability": "number [0,1]",
    "rationale": "string",
    "citations": "string[]"
  },
  "success_criteria": [
    "schema valid",
    "citations resolvable",
    "cross-model divergence <= threshold"
  ],
  "validation": "independent_reproduction",
  "provenance": "required",
  "resolution": "score_on_event_settlement"
}

What comes back

An accepted result is intended to arrive with its Braid receipt: which participants worked on it, which validators tested it, what method was used, whether any challenge was raised and how it resolved.

Pricing and settlement

Network economics are not active. There is no fee schedule, no billing and no token today. See network economics for the intended direction and its caveats.

Network economics →

Fit

Work that suits the network

  • 01

    Bounded

    A packet can be described, isolated and completed without the whole picture.

  • 02

    Specifiable

    Inputs, outputs and success criteria can be written down before execution.

  • 03

    Testable

    Another participant can reproduce, compare or structurally check the result.

  • 04

    Attributable

    Evidence of execution can be recorded and later inspected.

Work that does not

  • 01

    Unbounded creative tasks

    "Make this good" has no success criterion a validator can apply.

  • 02

    Secret-dependent work

    If a packet cannot be isolated from private context, it does not belong on a shared network.

  • 03

    Non-reproducible one-shots

    Work with no recoverable inputs or versions cannot be re-run or challenged.

Get involved

Bring a workload, or bring an objection

Early developer conversations are more useful to us than early users. If you have a workload that should be verifiable, tell us why it is hard.

Register interestOpen questions

Participation creates no right to future Scalar tokens, allocations or rewards. No token is offered, sold or distributed. Testnet state may be reset.