Conversation records
Each server response gets a conversation ID, message ID, usage metadata, risk flags, and a compressed JSON record.
The next production layer around the public chat is staged behind a launch gate: Stripe checkout entry, token-credit fulfillment, compressed conversation records, safe analytics events, and owner review behind server-side Microsoft Graph verification.
Launch gate
Coming soon after owner review.
The public Port page is intentionally a teaser for now. The live chat, token purchase button, and owner console link stay off this page until the current Canopy chat lanes finish.
- Widget follow-up loop behaves like a useful assistant after cached answers.
- Marketing funnel copy routes buyers through quote intake without overpromising.
- Stripe fulfillment and admin review are verified on the production host before public checkout opens.
What this layer adds
Review the private ledger.
The admin page is noindex and only reads through the server-side admin endpoint. Configure MSAL public values for browser login and server env values for owner verification.
Analytics-safe events
The widget emits open, send, response, paygate, checkout, and error events without prompt text.
Server auth boundary
The admin API verifies a Microsoft Graph bearer token and a configured owner email hash before issuing a signed HttpOnly session.
AI port references
How the port connects to Canopy AI work
Setup path AI integration readiness checklist A consultant-led path from business use case to safe public or internal deployment.Chat Canopy AI chat A constrained chat surface for Canopy-related questions, gated behind provider environment config.Writing AI workflow articles Reference notes on model APIs, agent setup, harnesses, and local-first developer workflows.