Source identity stays outside model authority
The model may synthesize evidence but cannot invent the evidence graph it is allowed to cite.
A domain-neutral Python service that snapshots heterogeneous sources, extracts and profiles them deterministically, runs hierarchical source-grounded analysis, validates every cited source/chunk relationship, and renders bounded Telegram reports.
Source is not publicly released; claims are bounded to the documented release evidence.
If the source cannot be read, the system should refuse to invent an answer.
Question · Can this conclusion be traced to evidence the system actually read?
APPLIES TO
Analysts · Operations teams · AI Engineering teams · Multi-format evidence workflows
PROOF
Multi-format source-grounded analysis · 64 targeted tests · 500-report renderer fuzz · 48/48 wheel RECORD verification
CAPABILITIES
10 declared in the project record
Synthesis never gets to invent the evidence graph.
FAIL-CLOSED SOURCE
If the source cannot be read, it cannot become evidence.
OCR/Vision for scanned PDFs/images is not supported.
500 reports · 3,816 pages · max 3,638 UTF-16 units
The constraints that matter.
The model may synthesize evidence but cannot invent the evidence graph it is allowed to cite.
Structure, missingness, distributions, and provenance should not depend on generation quality.
A source that cannot be extracted should never become plausible-looking analysis.
What would make the preferred answer fail?
EVALUATION METHOD
Analysis quality starts with source fidelity: unreadable, uncited, or ownership-invalid evidence must fail before synthesis is accepted.
Format matrices, malformed-input suites, source/chunk mutation tests, deterministic profiling fixtures, renderer fuzzing, and provider-failure replay.
What the evidence actually supports.
64 passed
Dependency-available release checks; not represented as the full pytest/coverage suite.
25 fixtures · 24 accepted · 1 expected scanned-PDF rejection
OCR/Vision for scanned PDFs/images is not supported.
24 sources · 34 chunks · 5 simulated LLM calls · 2 Telegram pages
Simulated provider path; not live semantic-quality proof.
24 sources · 34 chunks · 5 simulated LLM calls · 26 Telegram pages
Offline evidence only.
500 reports · 3,816 pages · max 3,638 UTF-16 units
Renderer boundary, not end-to-end delivery proof.
48 RECORD entries verified
Package structure verified; production deployment not implied.