Run sensitive workloads on compute that returns evidence of where and how it ran.

Cathedral Computer is the customer-facing API for verified compute. A successful execution returns a signed receipt bound to the request, workload, result, and hardware evidence, so a workflow can be attested instead of recomputed just to establish where it ran.

Cathedral is in live testing. Intel TDX CPU is the current confidential execution path. GPU capabilities are previews: Hybrid GPU retains trust in the GPU provider and GPU memory and is not confidential GPU. Check the product documentation and live capability discovery before selecting a worker.

SN39 is a mainnet launch candidate. Final tagged public launch proof and independent outside-operator reproduction are pending.

Customer product

customer request
      |
      v
Cathedral Computer
      |
      v
verified worker
      |
      v
private result + receipt

Subnet supply

provider machine
      |
      v
fresh TDX evidence
      +
validator-dispatched work
      |
      v
public commitments
      +
signed score report
      |
      v
independent validator
      |
      v
fail-closed weight decision

These are separate flows today. A Cathedral Computer customer job does not automatically become subnet-scored work, affect emissions, or publish the customer's workload or result.

The customer product and the subnet are related but distinct:

• Cathedral Computer is the account, billing, API, job, and receipt experience.
• Cathedral Confidential verifies compute-supply evidence and validator-dispatched work. Attestation grants eligibility; it does not earn rewards by itself.
• Cathedral Validator verifies the signed vector in thin mode and can audit published provenance independently. The validator—not a miner—signs any on-chain weight transaction.

• cathedral — SN39 validator, independent provenance audit, and experimental verification mechanisms. Audience: Validators and mechanism developers.
• cathedralconfidential — Intel TDX worker, evidence, verified-work scoring, receipts, and launch evidence. Audience: Compute providers, validators, and auditors.
• cathedral-eval-spec — Versioned evaluation contracts. Audience: Mechanism developers.
• cathedral-baseline-agent — Reference agent work retained for experimental lanes. Audience: Researchers and contributors.
• sat-king — SAT research and solver experiments. Audience: Researchers.

• The public phase is live testing, not general availability.
• Intel TDX CPU is the current subnet admission path.
• Registration, uptime, attestation, or self-reported volume alone never earns emissions. Only fresh, validator-verified work can receive positive weight.
• Missing, expired, conflicting, or unverifiable evidence fails closed to zero.
• A past successful receipt or chain transaction is historical evidence, not a promise of current eligibility or future rewards.
• Never put wallet seeds, private keys, bearer tokens, cloud credentials, or machine secrets in a GitHub issue.

All public repositories are licensed under their individual repository terms.