The problem: machine-read facts drift from human-read pages

A small business's information is scattered and inconsistent, and nobody knows which copy AI search will cite. This engine's premise is simple: build the human page and the machine data from one business-approved snapshot, and handle corrections as a re-publication of that same snapshot.

Publication gate: prove site control first

Publication happens only after site control is proven by a DNS TXT record or an HTTPS file (2026-09-11). Since October 23, 2026 business-place registrations are checked against the real public registers. The approval record explains who provided and accepted the information; it is not a certification of truth — the code carries the literal string 'does not certify facts'.

Publication gate: prove site control firstBusiness providesinformationSite-control proofDNS TXT recordor HTTPS file(2026-09-11)Public-registercheckbusiness registrations(since 2026-10-23)Approval recordwho provided,who acceptedPublicationThe approval record is not a certification of truth — the code carries the literal string 'does not certify facts'A correction is handled as a re-publication of the same snapshot.
Publication follows proof of site control and a public-register check; the approval record is not a certification of truth.

The bundle: one snapshot, five kinds of output

publication_bundle produces, from one snapshot, the profile HTML (with embedded JSON-LD; approved questions and answers are also marked up as FAQPage), facts.json, per-question answer pages, a related-services directory (CollectionPage) and discovery files. List pages carry published facts, the sitemap carries lastmod timestamps and IndexNow is notified (2026-10-09).

The bundle: one snapshot, five kinds of outputOne approved snapshotcontent the business approvedthe single source for humanpages and machine dataProfile HTML with embedded JSON-LDapproved Q&A also marked up as FAQPagefacts.jsonthe machine-readable facts filePer-question answer pagesRelated-services directoryCollectionPageDiscovery fileslist pages with published facts · sitemap lastmod · IndexNow notified (2026-10-09)publication_bundle builds all of these from one snapshot — the outputs have no room to drift apart.
The five kinds of output publication_bundle builds from one approved snapshot.

The observation loop: numbers as they are

A local observer was built on September 12, 2026 and has run unattended on six channels since September 24. Baseline on September 25: 12 of 15 questions answered, zero mentions of our services. Re-measurement on October 22: 13 answered, still zero. Not picking only the good numbers is the premise of the product, which is what makes the November 2 GEO deployment — readable AI answers with sources and original evidence, the exposure engine, answer pages, a crawl queue — a measurable change.

The observation loop: numbers as they areQuestions answered out of 15 (six channels · unattended since 2026-09-24)2026-09-25baseline12 of 15 answeredmentions of our services: 02026-10-22re-measurement13 of 15 answeredmentions of our services: 02026-11-02GEO deployment — readable AI answers with sources and original evidence,exposure engine, answer pages, crawl queueNot picking only the good numbers is the premise of the product — it is what makes the deployment a measurable change.
Answered counts at baseline and re-measurement, and zero mentions: the numbers as they were.

The service opened on this engine: FactMind

AI-search registration homepage public on September 10, 2026; Google sign-in, the registration backend and the first live self-service registration (FactMind 0) on September 11; a moderation-model benchmark on September 12 followed by the decision never to suspend on a model's verdict alone; every customer-app flow complete on September 24; terms, privacy, refund and business-notice pages on October 6; the GEO engine and Kakao, Naver and Apple sign-in on November 2; mail through the company server on November 3. Two months, 280 commits, six release tags.

An actual republish record, 2026-11-07 (selected fields)approval“승인 완료 · 정보를 고쳤다면 다시 승인” (approved; re-approve after any edit)site_controlverifiedpublishHTTP 201verifyHTTP 200live JSON-LDWebApplication · FAQPage · publisher: FactMindSource: public evidence factmind-publication.json — HTTP status and observed JSON-LD types only;not byte parity of the whole snapshot nor external-AI citation performance.
Selected fields from the actual 2026-11-07 republish record (public evidence factmind-publication.json).