Skip to main content

Buildability

Buildability receipt developer guide

Link proof surfaces to Build Loop execution with explicit, precomputed receipt scaffolds.

This guide covers the public buildability receipt surface introduced in Wave 0 and Wave 1. It keeps the truth boundary explicit, reuses canonical paper segments, and connects paper proof, Signal Canvas, Evidence, and Build Loop without hidden state or live internet rummaging.

Buildability HubProof DivergenceExample Receipt

Admin-approvable posture

read-mostly

The public launch lane is search, receipt, and reproducibility requirements only.

precomputed

Buildability MCP reads deterministic fixtures, receipt payloads, and proof-wave ledgers.

signed-when-available

Unsigned or not_verified verifier states stay visible and continue to block completion.

no live internet rummaging

The launch tools do not scrape registries, browse the web, or look up pilots at runtime.

always_ask approval reality

Mutating workspace tools sit outside this subset; clients should set always_ask and honor pending_approval, approved, rejected, and expired server states.

Contract version: buildability-wave1-v1; read-mostly public launch lane; precomputed deterministic fixtures, buildability receipts, and proof-wave ledgers.

Canonical segment

Use the same canonical paper segment everywhere so receipt, paper, Signal Canvas, and Build Loop routes stay aligned.

Truth boundary

Buildability surfaces only report computed viability and proof receipts. They do not claim live production usage, pilot outcomes, founder sign-off, or external adoption unless explicitly sourced.

Execution handoff

Each receipt links directly to Build Loop with a prefilled paper identifier for deterministic follow-on action.

MCP launch subset

Public launch review uses only search_buildable_papers, get_buildability_receipt, and get_repro_requirements. Wave status stays available through the proof-wave REST route and buildability://wave/{N} resource.

Admin setup

Create a developer key, verify it with GET /api/developers/whoami, and do not claim registry listing, pilot enablement, founder signatures, adoption, or Brier outcomes without external evidence.

curl

curl "https://sciencetostartup.com/buildability/identity-as-attractor-geometric-evidence-for-persistent-agent-architecture-in-llm-activation-space"

Python

import requests

response = requests.get(
    "https://sciencetostartup.com/buildability/identity-as-attractor-geometric-evidence-for-persistent-agent-architecture-in-llm-activation-space",
    timeout=30,
)

TypeScript

const response = await fetch(
  "https://sciencetostartup.com/buildability/identity-as-attractor-geometric-evidence-for-persistent-agent-architecture-in-llm-activation-space"
);

MCP receipt call

{
  "jsonrpc": "2.0",
  "id": 4,
  "method": "tools/call",
  "params": {
    "name": "get_buildability_receipt",
    "arguments": { "receipt_id": "fixture_wave1_no_fake_calibration" }
  }
}