AI K9 Codee logo Codee CLIFolder to business assistant

Codee AI Business Agent ยท Applied Good Intelligence

Codee helps turn a folder into capital for good.

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

Codee is an AI business agent with Applied Good Intelligence.

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.

Mission

Applied Good

Science, technology, ethics, society, and capital creation guided toward Invest In Vets.

Thread

Task IDs

Every request can become a task with prompt, service, agent, acceptance checks, local files, backend status, and delivery-room link.

Roles

Agent profiles

Explorer, Builder, Auditor, Launch Operator, and Owner Ops keep each run focused instead of mixing every action together.

Control

Permission modes

Suggest, Auto Edit, Support Auto, and Owner Full make autonomy visible before files, shell commands, network calls, or payments are used.

Context

Project memory

CODEE.md, AGENTS.md, and service-lane rules tell the next AI or partner what the folder is supposed to become.

User

Memory vault

`codee memory-vault` gives each Codee user a local-first searchable vault for preferences, service history, proof, support notes, and next steps.

Access

Veterans first

`codee accessibility --write` keeps course text short, high-contrast, voice-friendly, and proof-first.

Tools

MCP-style map

The connector blueprint separates public tools from backend-gated and owner-gated systems like Stripe, Cloud Run, GCS, and Metricool.

Proof

Verify loop

The same folder must still pass service verification before public launch, support handoff, or paid hosted activation.

Pulse

Heartbeat

`codee heartbeat` gives the user a quick status update across identity, platform files, saved proof, task threads, routes, and next commands.

Core

Governed agent

`codee agent-core --write` installs the business-agent loop: observe, understand, plan, act, verify, report, and recommend with guardrails.

Release

Tool registry

`codee registry --write` gives the folder the public command map, service lanes, permission modes, hooks, and proof reports.

Safety

Checkpoints

`codee checkpoint` snapshots important files before risky edits so a client folder has a repair path without exposing secrets.

Quality

Lane test

`codee test lane` runs the service verifier and eval report together so each lane can prove it is launch-ready.

SaaS

Customer portal

`codee portal` creates the customer-facing account room for delivery, proof, support, and upgrade paths.

SaaS

Entitlements

`codee entitlements` shows what each plan unlocks before support, hosting, or Business Suite activation.

SaaS

Starter command

`codee starter` creates the first folder, index file, SaaS manifest, service contract, and portal path.

Launch

Twenty move packet

`codee launch --write` creates onboarding, demo scripts, veteran access rules, policy queue, case-study slots, weekly proof, and valuation metrics.

Owner

CodeeAdmin

`codee codeeadmin --write` creates the owner operating packet, next-three focus list, entity routing, and AI K9 initiation gates.

Remote

Viewer and CLI bridge

`codee remote viewer` prepares phone-to-desktop viewing. `codee remote bridge` prepares safe phone-to-CLI commands.

Remote

Installer and readiness

`codee remote installer`, `host`, `security`, `demo`, `audit`, and `readiness` make the remote lane proof-backed before active control.

Company

Alignment packets

`codee company --packet all` writes the mission/company/platform alignment plus data room, governance, IP, impact, case-study, and investor packets.

CODEECPA

Review prep

`codee codeecpa --write` prepares questions, documents, red flags, and review logs for attorneys, CPAs, and board review without replacing them.

Payment lane

Codee now has the missing platform layer plus payment-gated activation.

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.

Client mode

Ask like chat

`codee client --ask` collects business, service, target URL, goal, connector needs, and builds the same preview-paywall packet Codee Chat uses.

Preview gate

Paywall timing

`codee client --submit` sends the intake to Codee backend, receives a locked preview, and keeps true deploy gated until Stripe verifies payment.

Contracts

Same promise everywhere

`codee contracts --service codeeqr --write` saves the exact client gets, required inputs, paywall rule, and delivery room slots for that lane.

DNS fallback

Shell submit backup

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.

WordPress

Client-hosted help

`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.

Google

Drive and Gmail

`codee client --connect-google --drive-folder URL --gmail-query newer_than:30d` creates temporary OAuth handoff links for asset organization and inbox help.

Platform

Install the layer

`codee platform --write` adds tasks, agents, memory, permissions, connectors, hooks, and a parity report to the folder.

Tasks

Thread the work

`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.

Agents

Focus the role

`codee agents --write` creates Explorer, Builder, Auditor, Launch Operator, and Owner Ops profiles.

Permissions

Control autonomy

`codee permissions --mode workspace --write` keeps reads, writes, shell use, network, and payments inside a clear policy.

Memory

Load the rules

`codee memory --write` creates CODEE.md, AGENTS.md, and service-lane rules for the next AI or human helper.

MCP map

Know the tools

`codee mcp --write` explains the Codee backend, Playwright, Stripe, and owner-gated cloud connectors.

User ID

One account thread

`codee init --email you@example.com` creates a Codee user ID for tools, tiers, licenses, scans, and delivery rooms.

Pricing

Show plans

`codee pricing` lists the simple hosting, partner, and Business Suite options from Codee backend.

Checkout

Upgrade link

`codee upgrade --plan pro --email you@example.com` creates a hosted Stripe Checkout URL.

Backend connect

Register the folder

`codee connect` binds the local folder, user ID, course packet, and generated site to Codee backend.

Verify

Check before launch

`codee verify` checks index, target URL, service packet, activation packet, assets, backend connection, payment gate, and timeline.

Hooks

Leave proof

`codee hooks --write` enables safe event logs for generate, verify, connect, activate, payment-required, deploy, and scan events.

Connectors

Know the gates

`codee connectors --write` explains what is public, backend-gated, owner-gated, and planned before secrets or payments are involved.

Activation

Unlock after payment

`codee activate` returns the locked hosted activation path. The public link stays gated until payment and uploads are verified.

Invoice

High-ticket billing

`codee invoice --plan business-suite --email client@example.com` creates a hosted Stripe invoice page.

License

Payment proof

`codee license --session-id cs_live...` checks Stripe status and saves local proof in `.codee/license.json`.

Support room

Request updates

`codee support --message "Update my CTA"` saves the request locally and can submit it to Codee support.

Doctor

Public route proof

`codee doctor` checks local tools, manifests, sensitive files, and the public download, registry, and release URLs.

Self update

Stay current

`codee self-update --write` refreshes the local CLI from the public release URL after saving a checkpoint.

Channels

Canary to stable

Owner canary gets risky updates first, partner beta gets proven updates next, and public stable stays safer for customers.

State

Remember the run

`.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

Codee should feel like a serious subscription tool, but stay in the business-output lane.

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.

Account

One Codee ID

CLI, chat, portal, delivery room, support, proof wall, and payment proof stay tied to the same user and workspace.

Usage

Clear tiers

Usage should scale by plan: training, pro workspace, partner workflows, and Business Suite support.

Tools

Local plus backend

The local folder can preview and learn. The backend unlocks hosted deploy, Stripe verification, scans, delivery, and support.

Investment

Proof creates value

Investor readiness comes from real metrics: conversions, MRR, delivery time, retention, route-scan pass rate, and mission outcomes.

Open-source course command

Codee can explain the teachable lanes before asking for money.

`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.

Core

QRCodee first

Learn QR creation, color, logo placement, scan proof, and how `index.html` becomes the first business page.

Core

Codee Flyer

Learn the drag-and-drop flyer lane, index export, CTA path, and hosted page proof.

Core

Codee App

Learn how a guidebook or PDF becomes a hosted app-style product with delivery logic.

Scaffold

Course folder

`codee course-init --course qrcodee` creates the starter index file, README, course packet, and activation packet inside the folder.

Generated site

Preview before paying

QRCodee, CodeeFlyer, and CodeeApp courses now create a service-specific local site so the user can see the lane before choosing paid hosting.

Proof

Course smoke

`codee course-smoke ./qrcodee-course` validates the live course suite and the local course packet.

Proof console

Training enhancements

`codee platform --write` prints the gap report and installs the proof files used by tasks, agents, and scans.

Agent loops

Codee turns the Claude Code pattern into business operations.

`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.

Run

Use Codee internally

AI K9 Kennel should build its own pages and service lanes with Codee before teaching or selling them.

Inspect

Write proof files

Every loop should leave behind a report, packet, route check, or delivery-room record.

Repeat

Make the lane reusable

The goal is not one impressive build. The goal is a repeatable path that clients and students can understand.

How people benefit

Codee removes the blank-page problem.

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.

Workspace

Creates the business folder

Codee writes `CODEE.md`, command files, skills, routes, and reports so the folder becomes a supported business surface.

Offer

Maps the first sellable path

The `money-map` command turns the idea into audience, offer, CTA, payment path, delivery path, and proof checks.

Proof

Scans live routes

Codee catches 404s, server errors, and bad links before a client or customer hits the page.

Portable

Works beside any AI

Use Codee with Claude, OpenAI, Gemini, a local editor, or a human builder. Codee keeps the business workflow steady.

ASAP path

The fastest responsible money path is one small offer with proof.

Codee should push people toward a simple paid action, not a giant unfinished build.

Start with QRCodee.One QR page teaches the full system: folder, index, asset, destination, scan, proof, and support.
Create the workspace.Run `codee init` so every AI tool and partner sees the same mission, rules, skills, and files.
Map the offer.Run `codee money-map` to define the audience, CTA, checkout path, delivery path, and proof checks.
Build the smallest live page.Use Codee Chat or a partner builder to create the public page, QR/flyer, and payment route.
Scan before outreach.Run `codee scan` and fix broken links before sharing the offer with prospects.
Sell, learn, improve.Send the link to a focused list, track responses, and improve the offer before adding more services.

Who it helps

Codee is for operators, builders, and mission partners.

It is simple enough for a small business owner, but structured enough for AI K9 Partners to use across many client folders.

Small business

Launch a cleaner offer

  • Clarify what is being sold
  • Check page and checkout routes
  • Keep delivery proof organized
AI K9 Partner

Help clients without chaos

  • Use repeatable folders
  • Keep owner approval clear
  • Save reports instead of guessing
Mission funding

Connect revenue to purpose

  • AI K9 Kennel builds the tools
  • INVEST IN VETS anchors the mission
  • Partners can support the larger housing goal