Docs
Public map for the operating layer.
This page gives agents, search engines, and partners the same plain-language map: what Apparatus is, what it is not, what is locally proven, and which account actions still need Jalen present.
Treat it as public documentation, not a customer checkout path. Apparatus explains the infrastructure; each flagship earns its own launch proof.
Operating model
What Apparatus is
Apparatus is the parent operating layer for regulated-commerce brands. It keeps source-backed content, launch proof, evidence records, and brand boundaries in one place while each flagship keeps its own public promise.
Brand boundary
What Apparatus is not
Apparatus is not a consumer cannabis shop, not a medical advice site, and not a claim that federal law has already changed. CommerceOS remains the cannabis reference flagship; legacy repository names stay internal.
Launch proof
What the public launch proves
The public surface has the same crawl basics every time: sitemap, robots, canonical URLs, social metadata, structured data, and llms.txt. Custom-domain and Search Console work remains a separate operator-present growth step.
Operator handoff
What still needs Jalen present
Custom-domain selection, DNS changes, Search Console verification, billing, payments, and protected account actions stay operator-present gates. The public product site and production deployment are already live.
Proof status
Launch basics before louder claims.
The public package should stay boring in the right places: crawlable, source-backed, domain-aware, and clear about which steps are still protected.
| Surface | Current proof | Remaining gate |
|---|---|---|
| Crawl map | Homepage, docs, journal index, and five articles are publicly deployed and mapped. | A custom domain remains optional and operator-approved. |
| AI-readable context | llms.txt explains Apparatus, CommerceOS, internal migration boundaries, and Schedule III answer rules. | Keep service and customer claims narrow until commercial proof exists. |
| Structured data | Homepage, docs, journal index, and articles emit page-specific JSON-LD. | Revalidate after any future custom-domain move. |
| Protected accounts | The public deployment does not require shared cannabis customer data or credentials. | Search Console, DNS, billing, and provider admin actions remain operator-present. |