{ "version": "2026.05.25-admin-guidebook-v3", "title": "Codee Admin Training Guidebook", "subtitle": "Ten-page operating guide for teaching, selling, hosting, proving, and scaling Codee.", "rule": "The guidebook is a live page, not a flat image. Codee should render readable pages from structured content, then prove every link and route.", "sources": [ { "label": "OpenAI Codex", "url": "https://openai.com/index/codex-now-generally-available/", "takeaway": "Command center, CLI/SDK, admin controls, analytics, and review proof." }, { "label": "Claude Code", "url": "https://code.claude.com/docs/en/how-claude-code-works", "takeaway": "Gather context, take action, verify results, and keep resumable sessions." }, { "label": "Gemini CLI", "url": "https://google-gemini.github.io/gemini-cli/", "takeaway": "Open-source terminal access, tools, MCP, search grounding, checkpoints, and custom context files." }, { "label": "OpenAI Canvas", "url": "https://academy.openai.com/public/clubs/work-users-ynjqu/resources/canvas", "takeaway": "A focused writing and editing workspace can be more useful than copy-paste between chat and documents." }, { "label": "GitHub Copilot cloud agent", "url": "https://docs.github.com/en/copilot/concepts/agents/cloud-agent/about-cloud-agent", "takeaway": "Background agents need tracked plans, logs, branches, test output, and human review." }, { "label": "Stripe usage-based billing", "url": "https://docs.stripe.com/billing/subscriptions/usage-based", "takeaway": "Metered pricing requires configured meters, usage events, customer mapping, invoice checks, and webhook monitoring before it should be sold live." }, { "label": "Stripe meter events", "url": "https://docs.stripe.com/api/billing/meter-event", "takeaway": "Meter events need a configured event name, customer payload, whole-number usage value, and an idempotent identifier before usage can become billable." }, { "label": "OpenAI business data handling", "url": "https://help.openai.com/en/articles/5722486-how-your-data-is-used-to-improve-model-performance", "takeaway": "Business/API data handling, retention, and training controls must be explained separately from consumer chat behavior." }, { "label": "Claude Code data usage", "url": "https://docs.claude.com/en/docs/claude-code/data-usage", "takeaway": "Claude-style tools separate local cache, server retention, commercial terms, and optional model-improvement data settings." }, { "label": "Anthropic cloud partnerships", "url": "https://www.anthropic.com/news/anthropic-amazon-trainium", "takeaway": "Large AI platforms use hyperscale cloud partnerships, but their product value comes from the workflow, model access, trust, billing, and ecosystem around the tool." } ], "pages": [ { "number": 1, "title": "The Codee Operating Model", "tag": "Foundation", "summary": "Codee needs one plain-language model that the owner, clients, students, and partners can understand.", "body": "INVEST IN VETS is the mission umbrella. AI K9 Kennel is the technology and service company. Codee is the platform, CLI, toolkit, delivery-room system, and proof layer. This separation keeps the story clean: the mission explains why, the company builds and operates, and Codee turns ideas into hosted income lanes.", "actions": [ "Explain the mission without promising legal structure that has not been reviewed.", "Explain AI K9 Kennel as the builder and operator of service systems.", "Explain Codee as the repeatable workflow: intake, build, payment, delivery, scan, support." ], "proof": "Admin can describe mission, builder, platform, and license path in under two minutes without mixing them." }, { "number": 2, "title": "What To Learn From AI Platforms", "tag": "Inspiration", "summary": "The best platforms are not only chat boxes. They combine chat, tools, files, agents, proofs, and admin controls.", "body": "OpenAI Codex points toward a command center for agents, SDKs, CLI access, admin controls, and measurable review quality. Claude Code points toward an agentic loop: gather context, act, verify, and resume. Gemini CLI points toward open-source terminal access, built-in tools, MCP extension, custom context, and checkpointing. GitHub Copilot points toward tracked background work that leaves logs, plans, branches, and reviewable output.", "actions": [ "Use chat as the front door, not the whole product.", "Make every Codee run leave a file, route, screenshot, or report.", "Keep humans in approval for money, public claims, and final launch decisions." ], "proof": "Every public Codee lane should have a visible proof artifact and a simple next action." }, { "number": 3, "title": "The Page-Based Guidebook Standard", "tag": "Guidebook", "summary": "A Codee guidebook should be a live page with clean typography, navigation, links, and print/save support.", "body": "A flat image can look good, but it is hard to update, hard to scan, hard to make accessible, and hard to connect to actions. A page-based guidebook lets Codee generate a polished background, strong headings, readable text, clickable links, buttons, sections, and proof routes. The same method can power admin training, client guidebooks, open-source lessons, paid PDFs, and delivery-room resources.", "actions": [ "Write guidebook content as structured data first.", "Render it into a responsive HTML page with strong typography.", "Add print/save, CodeEmail, Codee Chat, and scan links." ], "proof": "The guidebook opens on mobile and desktop, prints cleanly, and has no required text baked inside an image." }, { "number": 4, "title": "The Codee Platform Stack", "tag": "Stack", "summary": "The admin must know which platform does which job before teaching or selling the system.", "body": "GoDaddy controls domains and DNS. Firebase Hosting serves public pages. Google Cloud Run runs backend APIs, QR generation, Stripe webhooks, and fulfillment logic. Google Cloud Storage stores uploads, generated assets, course media, client delivery files, and CodeeBeeper-style workspaces. Stripe handles checkout and payment truth. CodeEmail stores owner notifications and operating threads. Playwright and route scans prove the public experience. OpenAI, Claude, and similar platforms do not make money because storage alone is special; they package compute, storage, model access, workflow, trust controls, billing, and developer experience into one product.", "actions": [ "Never confuse redirect success with payment fulfillment.", "Use the Stripe webhook as the source of truth for paid delivery.", "Use route scans and screenshots before calling a lane launch-ready.", "Keep client files in a controlled storage lane with clear ownership, retention, download, and deletion rules." ], "proof": "Admin can map domain, hosting, backend, storage, payment, email, and proof layers to one service sale." }, { "number": 5, "title": "Open Source Course To Paid Lane", "tag": "Offer Ladder", "summary": "The clean model is teach first, then offer done-for-you help, then charge recurring only for ongoing value.", "body": "The open-source course teaches QRCodee, Codee Flyer, and Codee App lanes. The student learns the method and can export a folder. The paid side removes technical difficulty and gives them a finished lane. Hosting, storage, scans, support, and active edits are the reasons a recurring tier makes sense. Stripe usage-based billing is not the default live model yet. The live model is fixed one-time service sales plus fixed monthly support tiers. Codee now has an internal usage-readiness ledger so the system can measure storage, scan runs, generated assets, support requests, delivery-room hosting, and client workspaces before any metered Stripe invoice is activated.", "actions": [ "Keep course value separate from done-for-you value.", "Keep one-time deliverables separate from monthly support.", "Make every upsell explain what Codee keeps doing after delivery.", "Use /api/codee/billing/usage-readiness to inspect supported usage events before proposing metered billing.", "Do not turn on usage billing until Stripe meters, event idempotency, usage dashboards, and invoice review are tested." ], "proof": "A client can understand exactly what they bought and why any monthly charge exists." }, { "number": 6, "title": "Business-Type Assistants", "tag": "Templates", "summary": "Every business type can get a Codee assistant, but every assistant still follows the same proof system.", "body": "A restaurant needs Codee Table. A barber or beauty pro needs Codee Chair. A contractor needs Codee Crew. A nonprofit needs Codee Mission. A product brand needs Codee Cart. Each assistant changes the intake questions, first offer, deliverables, and proof checks, but the backend method stays the same: intake, build, payment, delivery, scan, support.", "actions": [ "Start each business with one first offer, not ten offers.", "Ask only the intake questions needed to deliver the first lane.", "Reuse the proof system across every business type." ], "proof": "The business-type assistant generates a clear workspace and routes file." }, { "number": 7, "title": "The Codee CLI Workspace", "tag": "CLI", "summary": "The CLI is the local proof engine that makes Codee feel like software, not only a website.", "body": "The CLI creates a .codee folder, writes manifests, generates course folders, builds business-type assistants, scans routes, captures screenshots, and prepares support packets. The user can use OpenAI, Claude, Gemini, or another tool beside it, but Codee keeps the income lane structure and proof files consistent.", "actions": [ "Use codee.py toolkit-init to create the open-source course workspace.", "Use business-assistant-init to create a business-type lane.", "Use admin-certify to prove the operator workspace is ready." ], "proof": ".codee/reports contains the latest route scan, browser scan, support request, or certification report." }, { "number": 8, "title": "Payment, Delivery, And CodeEmail", "tag": "Fulfillment", "summary": "Clients should not wait or wonder after payment. They should land in a delivery room and have returnable proof.", "body": "Stripe checkout handles the payment experience. Stripe webhooks confirm payment state. The client redirect sends the buyer into the delivery room. CodeEmail stores owner notices, launch decisions, client links, scan summaries, and support commands. Email is helpful, but the delivery room is the returnable product home. Current Codee billing uses fixed checkout and subscription prices. Future usage billing can sit behind the same delivery room, but each billable event must be visible to the client before invoice finalization. The internal /api/codee/billing/usage-event endpoint records usage proof first; Stripe meter forwarding remains off until the meter and invoice-preview tests pass.", "actions": [ "Every paid lane needs a delivery-room URL.", "Every delivery room needs the generated asset or next clear step.", "Every important owner update should have a CodeEmail thread.", "For future usage billing, show the client their storage, scans, generated assets, and support usage before charging more." ], "proof": "A completed purchase shows a delivery link, owner notice, and scanable public route." }, { "number": 9, "title": "Admin Scans And Launch Proof", "tag": "Quality", "summary": "A site is not ready because it looks finished. It is ready when the right checks pass.", "body": "Codee should run route scans, 404 loops, Playwright screenshots, checkout route checks, QR checks, delivery-room checks, and mobile readability checks. The scan is the guardrail against broken public links, stale pages, bad redirects, missing assets, and unclear client delivery.", "actions": [ "Run the 404 loop after adding public pages.", "Run course-smoke after changing the open-source course system.", "Run browser-scan on pages that need visual proof." ], "proof": "Latest scan shows zero 404s and a screenshot exists for the public guidebook." }, { "number": 10, "title": "The Mission Scale Path", "tag": "Growth", "summary": "The long-term plan is not only software. It is income systems that fund veteran support and practical training.", "body": "Codee can teach people to turn an index file into an income lane, then offer done-for-you help to businesses that lack a digital presence. The same system can train homeless and disabled veterans first, support local Ohio businesses, and create recurring hosting/support revenue that helps fund land, housing, and AI K9 training goals. The clean legal direction is to keep Codee as an intellectual technology asset that can be licensed into the nonprofit mission ecosystem instead of mixing every asset, client obligation, and mission promise into one bucket. A lawyer and CPA should review the license, revenue share, ownership, tax, and public-benefit language before it is presented as final.", "actions": [ "Keep the course simple enough for beginners.", "Keep paid lanes concrete enough for clients.", "Keep the mission proof honest, transparent, and legally reviewed.", "Document Codee intellectual property, licensing rights, nonprofit use rights, and operating responsibilities before scaling partners." ], "proof": "A beginner can open the course, build a first folder, understand the paid option, and see where the mission fits." } ] }