Applied Good
Science, technology, ethics, society, and capital creation guided toward Invest In Vets.
Codee CLIFolder to business assistant
Codee AI Business Agent ยท Applied Good Intelligence
Applied Good Intelligence is Codee's mission rule: use practical AI, proof checks, service contracts, accessibility rules, and payment gates to move from learning to live delivery.
Mission agent core
It is not marketed as human-level AGI. It is a practical business agent: goals, memory, tools, service contracts, proof, accessibility, payment gates, and mission reinvestment.
Science, technology, ethics, society, and capital creation guided toward Invest In Vets.
Every request can become a task with prompt, service, agent, acceptance checks, local files, backend status, and delivery-room link.
Explorer, Builder, Auditor, Launch Operator, and Owner Ops keep each run focused instead of mixing every action together.
Suggest, Auto Edit, Support Auto, and Owner Full make autonomy visible before files, shell commands, network calls, or payments are used.
CODEE.md, AGENTS.md, and service-lane rules tell the next AI or partner what the folder is supposed to become.
`codee memory-vault` gives each Codee user a local-first searchable vault for preferences, service history, proof, support notes, and next steps.
`codee accessibility --write` keeps course text short, high-contrast, voice-friendly, and proof-first.
The connector blueprint separates public tools from backend-gated and owner-gated systems like Stripe, Cloud Run, GCS, and Metricool.
The same folder must still pass service verification before public launch, support handoff, or paid hosted activation.
`codee heartbeat` gives the user a quick status update across identity, platform files, saved proof, task threads, routes, and next commands.
`codee agent-core --write` installs the business-agent loop: observe, understand, plan, act, verify, report, and recommend with guardrails.
`codee registry --write` gives the folder the public command map, service lanes, permission modes, hooks, and proof reports.
`codee checkpoint` snapshots important files before risky edits so a client folder has a repair path without exposing secrets.
`codee test lane` runs the service verifier and eval report together so each lane can prove it is launch-ready.
`codee portal` creates the customer-facing account room for delivery, proof, support, and upgrade paths.
`codee entitlements` shows what each plan unlocks before support, hosting, or Business Suite activation.
`codee starter` creates the first folder, index file, SaaS manifest, service contract, and portal path.
`codee launch --write` creates onboarding, demo scripts, veteran access rules, policy queue, case-study slots, weekly proof, and valuation metrics.
`codee codeeadmin --write` creates the owner operating packet, next-three focus list, entity routing, and AI K9 initiation gates.
`codee remote viewer` prepares phone-to-desktop viewing. `codee remote bridge` prepares safe phone-to-CLI commands.
`codee remote installer`, `host`, `security`, `demo`, `audit`, and `readiness` make the remote lane proof-backed before active control.
`codee company --packet all` writes the mission/company/platform alignment plus data room, governance, IP, impact, case-study, and investor packets.
`codee codeecpa --write` prepares questions, documents, red flags, and review logs for attorneys, CPAs, and board review without replacing them.
Payment lane
The free tool teaches QRCodee first. If the operator wants hosting, scans, a delivery room, or done-for-you help after export, Codee backend creates the Stripe-hosted link and Stripe handles payment securely.
`codee client --ask` collects business, service, target URL, goal, connector needs, and builds the same preview-paywall packet Codee Chat uses.
`codee client --submit` sends the intake to Codee backend, receives a locked preview, and keeps true deploy gated until Stripe verifies payment.
`codee contracts --service codeeqr --write` saves the exact client gets, required inputs, paywall rule, and delivery room slots for that lane.
If Python cannot resolve the API, `codee client --submit` writes `.codee/latest-chat-submit-payload.json` and `.codee/submit-with-shell-curl.sh` so the same intake can still be sent from the shell.
`codee client --connect-wordpress --wordpress-site URL` creates the secure handoff plan for drafting into a client's WordPress site without storing passwords in the CLI.
`codee client --connect-google --drive-folder URL --gmail-query newer_than:30d` creates temporary OAuth handoff links for asset organization and inbox help.
`codee platform --write` adds tasks, agents, memory, permissions, connectors, hooks, and a parity report to the folder.
`codee task create` gives every business request an ID, prompt, acceptance checklist, agent, and backend handoff path. `codee task run --send-result` turns that task into proof the delivery room can show.
`codee agents --write` creates Explorer, Builder, Auditor, Launch Operator, and Owner Ops profiles.
`codee permissions --mode workspace --write` keeps reads, writes, shell use, network, and payments inside a clear policy.
`codee memory --write` creates CODEE.md, AGENTS.md, and service-lane rules for the next AI or human helper.
`codee mcp --write` explains the Codee backend, Playwright, Stripe, and owner-gated cloud connectors.
`codee init --email you@example.com` creates a Codee user ID for tools, tiers, licenses, scans, and delivery rooms.
`codee pricing` lists the simple hosting, partner, and Business Suite options from Codee backend.
`codee upgrade --plan pro --email you@example.com` creates a hosted Stripe Checkout URL.
`codee connect` binds the local folder, user ID, course packet, and generated site to Codee backend.
`codee verify` checks index, target URL, service packet, activation packet, assets, backend connection, payment gate, and timeline.
`codee hooks --write` enables safe event logs for generate, verify, connect, activate, payment-required, deploy, and scan events.
`codee connectors --write` explains what is public, backend-gated, owner-gated, and planned before secrets or payments are involved.
`codee activate` returns the locked hosted activation path. The public link stays gated until payment and uploads are verified.
`codee invoice --plan business-suite --email client@example.com` creates a hosted Stripe invoice page.
`codee license --session-id cs_live...` checks Stripe status and saves local proof in `.codee/license.json`.
`codee support --message "Update my CTA"` saves the request locally and can submit it to Codee support.
`codee doctor` checks local tools, manifests, sensitive files, and the public download, registry, and release URLs.
`codee self-update --write` refreshes the local CLI from the public release URL after saving a checkpoint.
Owner canary gets risky updates first, partner beta gets proven updates next, and public stable stays safer for customers.
`.codee/state.json` records the last command, exit code, service, route, and user thread so the next run starts with context.
Paid-tool value ladder
The public promise is simple: free or sponsored veterans learn first, public customers pay for hosted activation and support, partners pay for repeatable client systems, and Business Suite unlocks the full done-for-you package.
CLI, chat, portal, delivery room, support, proof wall, and payment proof stay tied to the same user and workspace.
Usage should scale by plan: training, pro workspace, partner workflows, and Business Suite support.
The local folder can preview and learn. The backend unlocks hosted deploy, Stripe verification, scans, delivery, and support.
Investor readiness comes from real metrics: conversions, MRR, delivery time, retention, route-scan pass rate, and mission outcomes.
Open-source course command
`codee courses` lists the lanes, but Codee starts beginners on QRCodee so they learn the folder, index file, QR image, scan proof, and support path before adding more products.
Learn QR creation, color, logo placement, scan proof, and how `index.html` becomes the first business page.
Learn the drag-and-drop flyer lane, index export, CTA path, and hosted page proof.
Learn how a guidebook or PDF becomes a hosted app-style product with delivery logic.
`codee course-init --course qrcodee` creates the starter index file, README, course packet, and activation packet inside the folder.
QRCodee, CodeeFlyer, and CodeeApp courses now create a service-specific local site so the user can see the lane before choosing paid hosting.
`codee course-smoke ./qrcodee-course` validates the live course suite and the local course packet.
`codee platform --write` prints the gap report and installs the proof files used by tasks, agents, and scans.
Agent loops
`codee loops` lists the repeatable systems that make the platform useful: intake, course build, route scan, delivery room, support request, Metricool proof, and membership renewal.
AI K9 Kennel should build its own pages and service lanes with Codee before teaching or selling them.
Every loop should leave behind a report, packet, route check, or delivery-room record.
The goal is not one impressive build. The goal is a repeatable path that clients and students can understand.
How people benefit
Most people do not need more random AI output. They need a repeatable way to package an offer, prove links work, and know the next launch step.
Codee writes `CODEE.md`, command files, skills, routes, and reports so the folder becomes a supported business surface.
The `money-map` command turns the idea into audience, offer, CTA, payment path, delivery path, and proof checks.
Codee catches 404s, server errors, and bad links before a client or customer hits the page.
Use Codee with Claude, OpenAI, Gemini, a local editor, or a human builder. Codee keeps the business workflow steady.
ASAP path
Codee should push people toward a simple paid action, not a giant unfinished build.
Who it helps
It is simple enough for a small business owner, but structured enough for AI K9 Partners to use across many client folders.