5-minute quickstart
Start with a governed signal entering a protected substrate. Ingest the signal, then evaluate whether it may acquire future influence.
curl -X POST "$TRACESCRIPT_API/substrate/signals/ingest" \
-H "Authorization: Bearer $TRACESCRIPT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"tenantId":"your-tenant-id",
"productSurface":"tracescript",
"sourceType":"slack_message",
"sourceId":"msg-001",
"sourceTrustLevel":0.35,
"sourceAuthorityLevel":0.2,
"targetSubstrate":"policy_corpus",
"proposedMutation":"policy_claim",
"payload":"Security review is optional for low-risk AI changes.",
"evidenceRefs":[],
"metadata":{"channel":"engineering"}
}'No fake demo response: the API playground executes against the hosted edge path or the API origin and tenant key you provide. If a route is unavailable, the site reports that dependency rather than inventing a result.
Programming model
Signals propagate through state-bearing media; policies and boundaries constrain what may persist or cross; receipts make consequential mutations replayable; residue captures effects that survive reversal.
signal → medium → candidate configuration → trust / policy / boundary evaluation → execution plan → substrate mutation → receipt + residue → future computation
Canonical API surface
POST
/substrate/signals/ingestNormalize a signal entering a substrate.POST
/substrate/integrity/evaluateEvaluate integrity and future-influence eligibility.POST
/substrate/configurations/evaluateEvaluate a candidate governed configuration.POST
/substrate/canonicalization/evaluateEvaluate promotion toward canonical state.POST
/substrate/retrieval/filterReturn retrieval treatment under current integrity state.POST
/substrate/actions/releaseEvaluate protected-action release.POST
/substrate/reversal/evaluateEvaluate reversal and residual effects.POST
/substrate/receipts/:id/replayReplay a governed transition.Receipts & replay
Receipts are typed proof objects, not generic logs. They can bind the signal, state basis, policy/authority versions, decision, mutation, dependencies, and replay material.
Production patterns
- Use API keys or workload identity at the gateway.
- Keep tenant identity explicit in every protected transition.
- Journal consequential authority before dispatch.
- Prefer independent observation of external effects over provider acknowledgement alone.
- Make revocation dependency-aware.
- Use workers for replay, calibration, recovery, conformance, and audit export where asynchronous execution is appropriate.
Conformance
The canonical first fixture is Policy Corpus Integrity: low-authority policy-like content may remain observable while canonical policy and action-basis eligibility remain blocked until the required authority and evidence exist.