Generated proposal
API INTEGRATIONS / REPAIR REVIEW
From broken contract
to a reviewable repair.
See what failed, inspect the proposed change, and check the evidence before a patch leaves your desk.
Run the live invoice repair01—03
Three original failure scenarios.
One deliberate review process.
NVIDIA NEMOTRON × NEBIUS SANDBOX
A repair should bring its evidence.
Explore real, saved model attempts. Choose a run to inspect its proposal and checks.
Original synthetic cases · Replay mode uses no model credits; the separate live workspace runs on Nebius · Candidate-runtime observations are not execution attestation. A changed contract is a new experiment, not proof of self-correction.
Review required
- 1Understand failure
- 2Inspect patch
- 3Review evidence
- 4Export
Baseline contract failed
A small change. An explicit contract.
BEFOREbroken implementation
PROPOSEDreviewed reference
Inspect the evidence, not just the answer.
Documented checks from the local reference fixture suite. These results do not represent a live model or remote sandbox run.
Execution boundary: only reviewed built-in reference functions were run locally. Candidate-generated code is never executed by this interface.
Know exactly what you are reviewing.
A transparent boundary between a useful demonstration and a production claim.
- Data origin
- Original fictional API fixtures
- Repair origin
- Human-reviewed reference implementation
- Execution evidence
- Local built-in fixture report
- Live model calls in this view
- None
- Deployment authority
- None — export for independent review
This desk demonstrates the workflow. Live generated repairs require separately verified provider access, isolated execution, and an evidence record bound to the exact candidate.
SAVED PROVIDER EVIDENCE
A separate record of live attempts.
Read published, sanitized receipts. This button never calls a model or executes a repair.
Not loaded. The reference examples above are independent of live provider results.
Attempt log
Saved results · inspection onlyInspect all attempts to inspect individual attempts.
THE REVIEW STANDARD
Make the change explainable.
Keep the decision yours.
Define what must survive.
Identifiers, response semantics, and request budgets become explicit review requirements.
Test the edge cases.
Empty pages, ambiguous units, and expired credentials expose repairs that only look correct.
Approve a precise artifact.
Export the source and review context together. Production changes remain a separate decision.