TJ AI Commerce Manifest

TJ GEO Publish Mode

After a project closes, turn on AI-readable publishing in one controlled pass.

This is the missing post-close switch: take a finished TJ site, generate the GEO publish pack, connect support robot context, expose safe machine files, and verify the route before buyer traffic.

Buy or attach project Build publish pack Read manifest
Post-close only No secret in files No DNS write by default No money movement
Knowledge GEO atlas visual surface
llms Short + full AI brief
schema Offer, FAQ, product facts
support Robot + ticket route
Close project Load site facts Generate llms Build schema Update sitemap Seed robot Run checks Publish gate

Reusable console

Fill or auto-load the site facts, then generate the publish contract.

Future TJ sites only change domain, site name, industry, products, prices, return path, support route, and robot script pack. Everything else stays standard.

What this publishes

It creates the public facts AI should read, and the private gates humans must control.

01llms pack

Short and full AI context, buyer route, support path, and safety boundary.

02well-known manifest

Machine-readable product, order, payment, support, GEO, and Traffic OS contract.

03schema and feed

Service, FAQ, product feed entry, price, delivery window, and contact route.

04robot knowledge

Default answers for what the site sells, how to buy, how to contact support, and when to escalate.

05sitemap and robots

Public pages are indexable; admin, payment confirmation, provider, outreach, and evidence pages remain blocked.

06publish report

Pass/fail gates, owner-required-input list, no-secret scan, and post-publish smoke checklist.

Operating rule

Every finished site gets this mode before it is called closed.

The closeout is not complete until GEO publish mode can explain the site to AI, route a buyer to the right product, direct private issues to support, and prove that no secret or money action leaked into public files.

Use guide

How to use it after any TJ project closes.

  1. Confirm the project is locally closed: page works, payment handoff works, support route works, and sensitive pages are blocked.
  2. Open this page, load or enter the new site's domain, product catalog, pricing, support route, robot script pack, and return path.
  3. Generate the publish pack and run npm run geo:publish-mode in the project root for real files.
  4. Review the generated report. Fix missing public facts, broken links, missing manifest entries, or secret-like content.
  5. Only after the report is clean, deploy the site and run read-only smoke against the live URL.