Inspiration
An incident can contain many timestamps and still lack the evidence needed to explain a failure. TraceHarbor keeps the evidence, uncertainty and next useful check together.
What it does
The incident evidence desk provides exact source quotations, a timeline, contrary evidence, and a before/after review. A documented deterministic synthetic case evolves from UNKNOWN to a narrowly supported deadline mechanism, then CONFLICTED when a matched-context capture disagrees. Supporting and contrary records remain visible. Dossiers can be exported and verified on reimport. Integrity checks do not authenticate origin or establish production causation. The prototype does not execute checks or remediation.
NVIDIA Nemotron and Nebius
The project integrates the NVIDIA Nemotron alias nvidia/Nemotron-3_5-Lightning through Nebius Token Factory with a constrained structured-output contract and local response validation. A retained historical accepted record remains UNKNOWN because causal configuration and independent provenance are missing. Imported provider metadata is an unauthenticated saved record; model backing weights, origin and semantic entailment were not independently attested. This is not an accuracy benchmark.
Historical execution evidence: native GitHub run 40206978963, original job 121209913696, and the complete saved provider record. The original job reports HTTP 200 and 2,975 tokens. The accepted result remains UNKNOWN. The job supports the historical execution claim; imported metadata alone does not authenticate origin, and this is distinct from the deterministic synthetic demonstration.
The public interface and historical-record review need no account, API key or payment and make no new model call. A separate protected server workflow uses exclusive reservations and fixed request limits. Earlier failed and uncertain effects remain retained, without automatic replay. Standard billing was activated under a bounded existing authorization; that does not prove a successful later inference. No fresh incident-analysis inference was executed for this demonstration video.
Demonstration
The 2:56 video uses an actual screen recording of the synthetic evidence workflow, with labelled detail crops, narration and English captions. Export/import controls are shown as capabilities; the video does not claim a new roundtrip verification. The saved provider record is presented separately as a labelled editorial extract, rather than a new UI capture or live response.
Try it
Open https://traceharbor.onrender.com and choose Start evidence evolution. Review the proposed check, add the captured verification, inspect its source and introduce the conflicting capture. Full, Missing and Conflicting reference cases are also available. For the distinct saved provider record, use examples/recorded/provider_record228.json with Verify imported dossier; this reviews saved data without inference.
Reviewed source and current README: https://github.com/Elinfiny/TraceHarbor/tree/1b2f0eebf014e108d31616bda49a91a97f012a36 Deployed executable-source baseline: https://github.com/Elinfiny/TraceHarbor/tree/e6e8fed27628d1da43973a311fad5ef9cea950a4 The reviewed documentation revision includes the current README and corrected START_HERE.md and EVIDENCE_MATRIX.md; the deployed executable source and existing video are unchanged. Licence: https://github.com/Elinfiny/TraceHarbor/blob/e6e8fed27628d1da43973a311fad5ef9cea950a4/LICENSE
How it is built
Python standard-library services and evidence validation, with an HTML/CSS/JavaScript interface. The guarded runtime keeps credentials on the server, validates structured responses, retains actual status and redacted errors, and prevents automatic retries. The protected capture workflow requires a retained first-fragment acknowledgement before an admitted request can run.
Challenges and learning
Browser capture, session continuity and uncertain provider outcomes required explicit separation between synthetic review, historical records and fresh server effects. A startup check is not an inference test, and a verified quotation is not a verified cause. TraceHarbor preserves these limits as part of the result.
Log in or sign up for Devpost to join the conversation.