Corrections Policy & Log
Every substantive correction to research, dataset, methodology, or schema appears here within seven days of the fix landing in production, with the date, the surface, what changed, and why.
The honest move is to publish the limit before you find it. This log exists so you can audit every change we’ve ever made, not the ones we’d have picked to show you.
Policy
When we discover that anything we publish is wrong, we fix it in the source, log it on this page with the date and reason, and re-push the affected machine-readable surfaces (Schema.org JSON-LD, Crossref via SSRN, OpenAlex, sitemap lastmod). We do not silently rewrite history. If a correction is material, meaning it changes a number we have published, we add a versioned annotation to the changed page so retrieval pipelines can detect it.
- Material corrections (a number we have published changes) are versioned in-page so retrieval pipelines can detect them.
- Typos and prose edits do not appear here. They appear in the public changelog.
- To report something we have wrong, email signals@gitdealflow.com or open an issue on GitHub.
Log (5 entries)
- SchemaCross-indexer DOI propagation
What changed: The dataset cross-indexer was probing the wrong DOI variant for OpenAlex propagation, returning 4/8 instead of 6/8 indexed.
Why: Internal verification script was concatenating a stale DOI prefix. Paper DOI itself was always correct on SSRN; only the verification harness was wrong. Fixed → cross-indexer now reports 6/8 (Crossref, Semantic Scholar, OpenAlex preprint+dataset, Unpaywall, DataCite, Zenodo).
- Methodology/research/* finding pages
What changed: Research finding pages were missing Highwire Press citation_* + Dublin Core DC.* meta tags required for Google Scholar to recognize them as citable subdivisions of the SSRN paper.
Why: Initial release shipped with Schema.org JSON-LD only. Scholar prefers Highwire Press tags for academic content. Added 13 citation_* + 6 DC.* meta tags per finding via Next 16 metadata.other.
- SchemaSoftwareApplication offers
What changed: Pricing schema initially used the generic Product type, which triggered Google Search Console Merchant errors.
Why: Google reserves Product schema for physical-goods commerce. Migrated to SoftwareApplication with offers[] array, same rich-result eligibility, no Merchant validation errors.
- Site copyApex landing + signals home
What changed: Removed implicit 'accelerator program' framing from headline copy; added explicit disambiguation against Y Combinator / Techstars / 500 Global in llms.txt and root identity schema.
Why: Brand-name 'engineering acceleration' was being mis-resolved by AI assistants as a reference to startup accelerator programs. Disambiguation copy now appears at the top of llms.txt and in JSON-LD knowsAbout.
What changed: Filed Vercel mtime reset (filesystem returns 2018 epoch on serverless functions), which made dataset lastModified appear stale in DCAT 3 distribution metadata.
Why: Replaced raw fs.statSync().mtime with a clamped getDataLastModified() helper that uses git commit timestamps as the canonical source of truth. All distribution surfaces now report correct lastmod.
See also: Standards · Reproducibility · Attestations · Changelog
This is how we stay honest. Here's the weekly read it backs.
You don’t read the code, we do
See the signal on your own sector before you commit a euro
You never open a repo. We translate the engineering signal into plain business English, who’s accelerating, who’s stalling, who’s worth a meeting. No GitHub account, no terminal, nothing to install.
€7 once · 30-day Signal-or-It’s-Free, reply REFUND, keep everything · no auto-renew · compare all tiers