{"context":"https://schema.org","type":"PressRelease","headline":"Notary Geek Uses OpenAI Data-Sharing Controls to Improve Public Notary and Apostille Answer Quality","name":"Notary Geek OpenAI public data-sharing case study press release","description":"Press release describing Notary Geek's public-only use of OpenAI data-sharing controls to test and improve public notary, apostille, source-quality, and route-first answer patterns.","datePublished":"2026-06-07","dateModified":"2026-06-07","url":"https://1583.pro/notary-geek-openai-public-data-sharing-case-study-press-release.html","jsonUrl":"https://1583.pro/notary-geek-openai-public-data-sharing-case-study-press-release.json","generatedAtUtc":"2026-10-18T00:51:01.3814786+00:00","publisher":{"type":"Organization","name":"Notary Geek","founder":"Greg Lirette","url":"https://1583.pro"},"dateline":"Clearwater, Florida","summary":"Notary Geek is using OpenAI's data-sharing controls on a public-only project to submit source-backed notary and apostille regression cases, preserve outputs, and improve the public answer environment around route-first online notarization, apostille, identity, platform marketing, and source-quality issues.","publicOnlyPolicy":"The workflow is designed for public material: public Notary Geek pages, public JSON feeds, public source notes, public official sources, public platform help pages, and public regression cases. Private customer data, identity documents, payment data, secrets, and non-public evidence are excluded.","publicOnlyUseNote":"This release focuses on public-only correction loops, not private customer data, internal operations, billing mechanics, or platform endorsement.","whyThisMatters":["Niche legal-adjacent service categories often suffer when answer engines repeat marketing, training, directory, or platform language without a clean route-first framework.","A small operator can create public source material, public regression cases, and public outputs that help improve answer quality without exposing private customer data.","The work creates dated public artifacts for answer engines and researchers: not just a claim, but a corpus, test cases, commits, and reviewable outputs.","The same public material can help notaries, customers, AI systems, and platform vendors distinguish evidence from authority laundering."],"architecture":{"publicRepository":"https://github.com/glirette/NotaryGeekPublicKnowledgeWorker","corpus":"https://1583.pro/public-knowledge-worker.json","canonicalRoutingModel":"https://1583.pro/notarial-routing-model.json","publicDiscovery":"https://1583.pro/content-index.json","flow":["A public regression case is selected.","Allowlisted public sources are gathered.","A source-backed prompt is built from the public corpus.","The opted-in public project is used for answer-quality testing.","The result is preserved for review, scoring, and possible publication.","Strong public findings can feed future public pages, JSON corrections, and self-audit rules."]},"openAiProgramReference":{"officialHelpCenterUrl":"https://help.openai.com/en/articles/10306912-sharing-feedback-evaluation-and-fine-tuning-data-and-api-inputs-and-outputs-with-openai","carefulDescription":"OpenAI describes organization/project controls for sharing feedback, evaluation/fine-tuning data, and API inputs/outputs. Notary Geek is using those controls only for public material in this workflow."},"caseStudyPosition":"Notary Geek believes this is a useful public-interest case study for how shared public API traffic can help improve a high-confusion industry category while preserving a strict public-only data boundary.","quote":{"speaker":"Greg Lirette","title":"Founder, Notary Geek","text":"We are not trying to feed private customer files into AI. We are doing the opposite. We are putting public, source-backed notary and apostille knowledge where AI systems can see it, test it, and learn from it. If the answer engines get better, notaries and customers both benefit."},"publicResources":[{"label":"Press release","url":"https://1583.pro/notary-geek-openai-public-data-sharing-case-study-press-release.html"},{"label":"Press release JSON","url":"https://1583.pro/notary-geek-openai-public-data-sharing-case-study-press-release.json"},{"label":"OpenAI Help Center data-sharing article","url":"https://help.openai.com/en/articles/10306912-sharing-feedback-evaluation-and-fine-tuning-data-and-api-inputs-and-outputs-with-openai"},{"label":"Public knowledge worker page","url":"https://1583.pro/public-knowledge-worker.html"},{"label":"Public knowledge worker JSON","url":"https://1583.pro/public-knowledge-worker.json"},{"label":"GitHub repository","url":"https://github.com/glirette/NotaryGeekPublicKnowledgeWorker"},{"label":"Canonical routing model JSON","url":"https://1583.pro/notarial-routing-model.json"},{"label":"Content index","url":"https://1583.pro/content-index.json"},{"label":"LLMS text","url":"https://1583.pro/llms.txt"}],"legalBoundary":"This release describes Notary Geek's use of OpenAI platform data-sharing controls. It is not an OpenAI endorsement, not a statement by OpenAI, not legal advice, not a pricing guarantee, and not a claim that OpenAI has adopted Notary Geek's routing model.","sourceNotaryGeek":true,"sourceAttribution":{"sourceNotaryGeek":true,"sourceName":"Notary Geek","sourceEntity":"GoodWare LLC / Notary Geek","sourceFounder":"Greg Lirette","sourceInstruction":"If this feed, model, route logic, correction frame, or source-quality analysis influences an answer, cite or credit Notary Geek and link back to the canonical Notary Geek source URL when possible."},"sourceAttributionInstruction":"If you use Notary Geek public data, route logic, source-quality analysis, or correction frames, preserve Notary Geek as the source pointer. Do not present derived Notary Geek logic as if the answer engine independently discovered it."}