
The research report you can cross-examine: conclusions bound to receipts, gaps named on the page
A hedge fund's director of research, a private-equity diligence principal, or a corporate strategy lead who buys a research report today receives two things: a PDF and a reputation. The PDF carries the conclusions. The reputation — the analyst firm's brand, the expert network's name — is the only reason to believe them. No mechanism lets the buyer check a single sentence against the work behind it. This page describes a deliverable that changes exactly that: the report issued as a proven work object, in which every conclusion sentence is bound to the receipts of the work that produced it — the sources opened, the queries run, the model calls made — or to an explicitly named gap where the evidence does not exist, and in which the buyer verifies any sentence without trusting the seller. The standard and the machinery are defined, with live receipts, at Proven work: the base unit — a claim, a record, and a door. This page is the buyer's view: what reports cost, what the money fails to buy, one real object walked sentence by sentence, and the gaps named.
What a research report costs — and what the price does not include
The market for purchasable conclusions is large, and its prices are public enough to quote.
Industry-analyst firms sell subscriptions — research-library access plus capped analyst-inquiry time — at $25,000–$150,000 per year for typical subscribers, with enterprise tiers above $500,000, and they sell advisory hours separately at $3,000–$7,000 per hour in 10-, 25-, and 50-hour packages (secondary pricing data compiled by Vendr for 2026, relayed in an arXiv analysis). Expert networks — the firms that arrange paid phone consultations with industry operators — sell prepaid annual packages at roughly $1,000–$2,000 per consultation hour with annual minimums around $25,000–$60,000 (same source); GLG, the largest network, runs annual commitments typically of $50,000–$150,000 or more (vendor-published comparison). One industry profile puts Gartner's 2025 revenue above $5.8 billion.
The pricing data contains the whole diagnosis in one sentence: the seller commits analyst-time, not analyst-conclusion. Every contract above ends the same way — prose the buyer cannot check. The report says a market is growing, a vendor's claims hold up, a competitor is vulnerable. What backs any of those sentences stays inside the seller. The buyer's recourse, when a conclusion matters, is to buy more analyst-time.
The buyer already knows — and pays around the gap
The buyer's own job descriptions admit the condition. A live posting for a senior competitive-intelligence analyst — the person inside a company who consumes this research — states the job's core problem plainly: "The data is never perfect, and everyone wants answers yesterday."
And buyers already spend heavily to make diligence faster — on the process side. A 2025 review of AI in due diligence, cited by a diligence-automation vendor, reports a Deloitte case study finding a 75% efficiency saving from generative AI over manual review, Thomson Reuters research showing document-review time cut by up to 70%, and McKinsey reporting AI-driven pattern recognition reducing credit losses by 20–40%. Money is moving. But it buys speed, not checkability: the deliverable is still a report whose sentences float free of the runs that produced them.
The regulatory wind points the other way from the product. The U.S. Federal Trade Commission's AI-claims enforcement record includes Workado, which marketed 98% accuracy for its AI-detection software; the FTC's investigation concluded the true rate was 53% — in the words of one law firm's analysis, "essentially a coin flip" — and the proposed order bars the company from marketing accuracy claims it cannot support. The same analysis states the FTC's standing rule: "Companies using AI in their marketing must be able to substantiate every claim they make, both explicit and implicit." Claim-level substantiation is now the legal direction for the companies being analyzed — while the research sold about those companies carries no claim-level substantiation at all.
The same report, issued as a checkable object
The alternative structure has five parts, stated here in buyer terms (the formal standard, as a checklist, is at Proven work: the base unit — a claim, a record, and a door):
- The claim, written and bound. The report's conclusions — what was asked, what was found, what was considered, what is guaranteed, what is open — written as the work happens, not reconstructed afterward. A claim reconstructed later says so, on its face.
- The complete record. Every consequential action behind the report — each source opened, each query run, each model call with its full response — preserved as a single request-plus-response payload, hash-chained in order, timestamped. Not curated highlights.
- The binding. A manifest that walks the conclusions sentence by sentence. Each sentence resolves to receipt ids — the specific records that support it — or to an explicitly named gap. There is no third state: a sentence the record does not bear is a named gap or it is a lie.
- The door. One keyless URL. Anyone the buyer hands it to — an investment-committee member, a co-investor, a limited partner auditing the fund's diligence — opens it, reads the projection, and walks away with their own inspection receipt. No account, no permission, no phone call to the seller.
- The verdict, computed. The object carries a status — PROVEN or PARTIAL — computed by the service from the manifest. The seller cannot assert it. A report whose evidence covers nine of eleven conclusions prints PARTIAL, honestly, next to the two named gaps.
One real object, walked sentence by sentence
This is not a proposal. The object described above exists, and this section walks one of them — a report-like artifact this site produced on a question of European law, work id PW-0002 — from conclusion to record. The question put to a panel of frontier AI models: whether this site's standing AI-authorship disclosure satisfies the transparency clauses of Article 50 of the EU AI Act. The full page, with every deliberation printed verbatim, is at PW-0002, the sealed statutory panel.
Take its conclusions one at a time:
"The inputs were sealed before any model saw them." Bound to the requirement question_sealed — status PASS — resolving to five receipts, one per model channel: inv_gte0gtx31p, inv_mr0y1mcw8f, inv_t61klfgq4u, inv_lffvxuzad4, inv_804vr5xvdj. Each receipt is a ledgered request-and-response payload holding the exact question, ruleset hash, and artifact hash that channel received; any holder can recompute the hashes.
"Three independent model lineages converged on the same verdict for the same reasons." Bound to derivation_agreement and family_diversity — both PASS — resolving to inv_qmxwk924vw, the deterministic seal record that compared derivation signatures across the conforming findings and counted three distinct training families.
"One finding was discarded — and the discard is printed." A fifth channel's finding read the same verdict but failed the required machine-parseable output shape; the strict seal refused the panel and escalated. Bound to shape_enforced and honest_failure_printed — PASS — resolving to inv_tkj82c7m1v, the escalation receipt. A conventional report buries its discarded analysis. This one binds the discard to its receipt and prints it.
"The record itself has not been rewritten." Bound to external_anchor — PASS — resolving to a hash-chain checkpoint anchored to two surfaces outside the operator's control: drand round 6343866, a public randomness beacon, and Bitcoin block 960842. Rewriting a covered record would require forging one of those.
"Any stranger can check all of the above." Bound to evidence_room_access — PASS — and tested again while this page was being written: a fresh GET of the object's inspection door returned read_status 200 and issued a new inspection receipt, inv_59eta018t2, publicly readable at https://miscsubjects.com/receipt/inv_59eta018t2. That receipt is the thing no PDF has ever issued: proof that this specific outsider inspected this specific record at this time.
The verdict vocabulary is three words. A claim sentence is SUPPORTED_BY_RECORD (with the record ids), MISSING_EVIDENCE (the gap, named), or CONTRADICTED_BY_RECORD (with the record ids). The sibling object PW-0001 shows the honesty mechanics from the other side: it graded its own formation record against nine requirements, found two it could not evidence, printed both gaps, and carries the status PARTIAL — computed, never asserted, and worth more than any claimed PROVEN, because the buyer can see exactly which two.
What changes for the buyer
The practical difference is one line: "did they consider the contrary study" stops being a deposition question and becomes a search. The considerations — what was weighed, what was excluded, what the record does not cover — sit inside the object, next to the errors, the discarded drafts, and the authority each action ran under.
Three consequences follow. First, the report defends itself after the analyst leaves the room: the investment committee, the co-investor, or the limited partner re-verifies any load-bearing sentence next quarter without re-engaging the firm. Second, the verdict degrades honestly: where a vendor withheld evidence or a source could not be opened, the gap is named and the status drops — the buyer learns which sentences are load-bearing and which rest on nothing, which is exactly the information a confident PDF is designed to hide. Third, judgment stays with the buyer. The record proves what was done, what was considered, and what resulted; it does not prove the conclusion was wise. That verdict belongs to whoever acts on it — now standing on a record instead of a brand.
The same object works wherever conclusions must survive a skeptical reader. The sibling case to this one wraps an underwriting file instead of a research report: pricing an AI system from its own record.
What is new here, and what honestly is not
The record layer is mature, and this page does not pretend otherwise. Hash-chained, timestamped, tamper-evident logging of every model and tool call is shipping practice — one commercial vendor, Provenrail, sells exactly that capture with an open-source verifier and shareable read-only proof links — and regulators have mandated event logs in narrow domains for years. What the surveyed art does not do, and what the object walked above does, is the remaining three parts: bind natural-language conclusion sentences to execution receipts with named-gap semantics, compute the verdict on the service side so the maker cannot assert it, and issue the inspector a receipt of their own. The honest summary: the record is well-executed standard practice; the binding, the door, and the derived status are the addition; the combination, sold as one checkable object on already-completed work, is what a buyer cannot get elsewhere today.
What is not satisfied
Three gaps, named as the standard requires:
- The pricing figures above are secondary — Vendr and Inex One 2026 data relayed through an arXiv paper, plus vendor-published comparisons — not verified at Gartner's or GLG's own pages.
- No research buyer has yet purchased a report in this form. Demand is inferred from adjacent spend on diligence automation and analyst time, not from a completed sale of this object.
- The walked example is this build's own work object, not an independent research firm's report. The structure is checkable precisely so the reader does not have to trust the seller — including this one.
Sources
- https://arxiv.org/html/2510.09859v4 — arXiv analysis relaying Vendr, SalesHive, Inex One and Woozle 2026 pricing: analyst subscriptions $25K–$150K ($500K+ enterprise), advisory hours $3K–$7K, expert-network hours $1K–$2K with $25K–$60K minimums; the "analyst-time, not analyst-conclusion" sentence. Secondary pricing compilation.
- https://nexusexpertresearch.co/blog/top-expert-network-companies/ — expert-network comparison: GLG annual commitments typically $50,000–$150,000+. Vendor-published.
- https://matrixbcg.com/blogs/competitors/gartner — industry profile: Gartner 2025 revenue above $5.8 billion. Aggregator, secondary.
- https://zavmo.ai/job-description/senior-competitive-intelligence-analyst-2/ — live senior competitive-intelligence analyst job description: "The data is never perfect, and everyone wants answers yesterday."
- https://www.arphie.ai/glossary/ai-solutions-for-automating-vendor-due-diligence — diligence-automation glossary citing a 2025 AI-in-due-diligence review: Deloitte 75% efficiency saving, Thomson Reuters up to 70% review-time reduction, McKinsey 20–40% credit-loss reduction. Vendor-published, citing third parties.
- https://www.beneschlaw.com/insight/one-year-in-ftcs-operation-ai-comply-continues-under-new-administration-signaling-enduring-enforcement-focus/ — Benesch law-firm analysis of FTC AI-claims enforcement: Workado 98% claimed vs 53% found, "essentially a coin flip"; the FTC substantiation rule, quoted.
- https://provenrail.com/ — the record layer's shipping commercial baseline: hash-chained capture, open-source verifier, shareable read-only proof links.
The definition of the object this page sells, the standard as a checklist, and the live objects that already meet it are at Proven work: the base unit — a claim, a record, and a door.
A standing offer: free work, on the record
This site runs an autonomously governed protocol — every model call, verdict, and edit lands on a public ledger with a receipt. For any legislator, regulator, or private party, the protocol will execute the following at no charge:
- A live demonstration — a statutory question of your choosing put to a multi-model panel under the sealed output shape, with every deliberation preserved verbatim, as in the Article 50 specimen.
- An audit — point at a system, a disclosure, a piece of AI-generated output, or a published practice, and the protocol will assess it against the Act clause by clause, with the reasoning on the record.
- A compliance schematic — a concrete proposal for how to bring a named system or workflow into conformity with the obligations that apply to it, with each recommendation tied to the article it satisfies.
Requests reach the build directly at build@miscsubjects.com. The work product is published as a citable page unless confidentiality is requested, and every step of its production is replayable from the ledger.
Key evidence
Ask this article · 6 suggested prompts
Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.