Made in USA Workflow for Made in USA Inc
A redesigned operator-grade workflow for intake, product proof, UPC and barcode scan, CMS installation, AI readability, ADA readiness, payment, affiliate attribution, vSign, TPM-ready evidence, ledger receipts, renewal, and controlled spec maintenance.
Primary promise
Made in USA turns scattered claims into a controlled path: intake, evidence, verification, issue, and renewal.
Truth boundary
Every item is TRUE, HOLD, PLANNED, or GATED. The page never implies completion without live readback.
Customer path
Self-help instructions, operator tasks, website package, payment status, and renewal status are separated.
Risk control
Regulatory, ADA, origin, signing, and ledger claims remain gated until the authorized evidence lane returns a receipt.
Visual Workflow Rail
Follow this left-to-right rail from customer entry to monitored renewal. Each stage has an owner, source, and completion rule.
Intake
Lead, source, affiliate, product, UPC, site, and owner are captured before any claim work starts.
Proof
Company authority, Good Standing, domain ownership, signer, and product evidence are collected.
Scan
UPC, barcode, PWA, website, AI-readability, and accessibility checks are run with mismatch handling.
Build
Plugin/manual website package, WK files, schema, PWA records, and evidence cards are prepared.
Review
Operator checks evidence, data gaps, customer claims, and completion rules before status changes.
Sign
vSign, TPM-ready packet, and gated ledger evidence are staged only through authorized lanes.
Commerce
Affiliate, invoice, gateway, subscription, renewal, and customer notification records are tied together.
Issue
Certificate, card, badge, Data Wallet record, and public-readable route are issued only after readback.
Monitor
Renewal, drift, Good Standing, website changes, accessibility, and product changes stay on watch.
Work Lanes
The workflow is split so intake, technical checks, commercial records, and governance gates do not blur into one false completion claim.
Customer Intake Front Desk
- Lead, source, affiliate, and campaign.
- Legal entity and signer.
- Product/site/certification request.
- Email template and queue status.
Evidence Build Ops
- Country-of-origin substantiation, BOM, supplier declarations, packaging labels, UPC/EAN/GTIN, manufacturer evidence, and Made in USA claim support.
- Photos, labels, source URLs, screenshots.
- Mismatch, missing source, and HOLD notes.
Technical Readiness Web/PWA
- CMS detection and install path.
- WK files, schema, llms.txt, robots, sitemap.
- UPC scan, PWA route, and accessibility checks.
Commercial Records ERP
- Quotation, invoice, payment request.
- Gateway and subscription readback.
- Affiliate attribution and renewal timer.
Trust Gate VGATE
- vSign packet.
- TPM-ready evidence when authorized.
- XRPL/Hyperledger receipt path.
- Checkout with hash/readback.
Customer Output Delivery
- Certificate/card/badge.
- Data Wallet record.
- Public-readable route.
- Renewal and monitoring plan.
Status Matrix
Each line states whether this page documents a workflow, verifies a live route, or holds until a separate evidence lane completes.
| Checkpoint | Status | Completion Rule |
|---|---|---|
| Contact, queue, email template | Documented workflow | Complete only when ERP queue and sent message/readback exist. |
| UPC, barcode, PWA scan | Documented plus live PWA path | Complete only with scan result, lookup result, and mismatch handling. |
| CMS and plugin/manual install | Per-customer workflow | Complete only after customer-site readback and cache/CDN verification. |
| ADA / 508 / WCAG 2.2 AA | Validation path | Not a legal certification without approved manual/assistive review. |
| Payment / subscription / affiliate | ERP/gateway path | Complete only with ERP and gateway identifiers tied together. |
| vSign / TPM / XRPL / Hyperledger | Gated trust path | Complete only when authorized lane returns receipt/hash. |
Platform Installation Map
Website work follows the detected platform. The documentation page does not imply a plugin was installed.
| Platform | Detection | Install Path | Verification |
|---|---|---|---|
| WordPress | Detect via admin, wp-json, assets, and headers. | Plugin or manual package. | Verify WK files, schema, cache purge, product page, and AI-readable content. |
| Joomla | Detect generator, assets, or admin confirmation. | Extension path or manual static package. | Verify metadata, canonical product route, and live content. |
| Shopify | Detect storefront headers and theme signals. | Theme/snippet/app block or static hosted package. | Verify product page, collection page, schema, OG, and WK files. |
| Vercel / Next.js | Detect route behavior and deployment headers. | Public folder files, route handlers, build/deploy readback. | Verify root-scope files, redirects, metadata, and PWA behavior. |
| Static / Manual | No CMS signal or customer confirms static host. | Zip package plus install markdown. | Operator verifies live URLs and content hashes. |
AI and Public Readability
The human page, product data, and machine-readable files must tell the same story.
Discovery Files
`.well-known/ai`, `xrp-ledger.toml`, `llms.txt`, robots, sitemap, and content/feed layers.
Page Signals
Canonical URL, JSON-LD, Open Graph, meta description, product copy, and ownership language.
Server Behavior
HTTPS, redirects, compression, cache headers, mobile rendering, and no blocked WK paths.
Commercial Flow
Payment is a controlled evidence record, not a hidden side effect.
| Step | Record |
|---|---|
| Attribution | Affiliate key, campaign, source URL, landing route. |
| Quote/order | Mapped certification or verification package. |
| Payment | Invoice, payment request, gateway ID, webhook/signature evidence. |
| Renewal | Subscription state, next check date, monitoring scope. |
Spec Maintenance Loop
When product, scanner, CMS, ADA, payment, or ledger rules change, the page changes through a controlled loop.
Detect
Capture new rule, broken behavior, customer need, or source drift.
Classify
Use WO for planned work; APAR for broken behavior or false claim risk.
Update
Edit source runbook and Web Page payload with old/new wording.
Verify
Run route, body, screenshot, accessibility/readability checks as needed.
Checkout
Record evidence paths, hashes, fleet holds, and final status.