Platform · CCTP

Trajectories that respect your bounds, with audit evidence attached.

CCTP is the contract-constrained post-processor that enforces the per-signal bounds and rate limits declared in your contract, handles bound-recovery smoothing, and ships a full correction ledger plus determinism hash inside the sealed evidence bundle — so every trajectory your auditor opens is provably within your physical and business envelope.

Engine reference Request access

cctp · evidence excerpt

box_bound · per-signal envelope enforced
rate_limit · step-over-step magnitude enforced
recovery · bound-release smoothing applied

✓ per-step violation counts → evidence bundle
✓ deterministic — same seed + contract → byte-identical output
✓ sealed — 9-artefact evidence bundle

Constraint types

Bounds, rates, recoveries — in your contract.

You declare the guardrails your trajectories must respect — per-signal physical envelopes, step-over-step change limits, recovery handling for bound releases — inside a single contract that travels with your run. CCTP reads that contract and enforces it.

Real industrial and clinical processes don't step discontinuously at an envelope edge; they ease back. CCTP recognises that and handles the transition smoothly rather than leaving an unrealistic flat line in your output. Tuning knobs are private to the engine; your contract keeps the envelope declarations only.

contract.json

# Contract guardrail block (shape only)
{
  "constraints": {
    "box_bounds":  [ /* per-signal envelopes  */ ],
    "rate_limits": [ /* step-over-step caps   */ ],
    "recoveries":  [ /* bound-release easing  */ ]
  }
}

Evidence on every run

Violations counted. Corrections recorded.

Every CCTP run ships a per-step violation count, a total final-violation count, a step count, and a determinism hash inside the sealed evidence bundle.

A separate correction ledger captures when, where, and by how much each value was adjusted, so a downstream analyst can reconstruct exactly where the projector acted. No silent smoothing — every touch is accounted for.

cctp_evidence.json

{
  "engine":                    "cctp",
  "steps_taken":               …,
  "final_violations":          0,
  "constraint_violations_per_step": "/* per-step series */",
  "determinism_hash":          "/* sealed in evidence */",
  "seed":                      "/* your seed */"
}

Where CCTP fits

Post-processor you can trust.

CCTP runs after another engine produces trajectories and before the evidence bundle is sealed. The contract declares the envelopes; CCTP enforces them and records every correction.

Industrial SCADA — physical envelopes for process tags, plus step-over-step ceilings for actuated variables.
Healthcare time series — vital-sign physiological ranges and between-measurement change limits.
Financial — non-negative balances, daily-change ceilings, circuit-breaker rules expressed as rate limits.
Energy grid — substation voltage / frequency bands plus ramp-rate ceilings.

bash

rady cctp run \
    --contract ./contract.json \
    --trajectory ./upstream.ndjson \
    --output ./corrected.ndjson

✓ Trajectory loaded, envelopes enforced
✓ Correction ledger written to evidence
✓ Determinism hash sealed in bundle

→ evidence bundle: rady evidence get <job_id>

Bounded trajectories, audit-ready.

CCTP ships alongside DV-FM, Gaussian Copula, and Tabular Diffusion under one Contract-K. Access is enterprise-contracted.

Email sales@radmah.ai How evidence sealing works