Invest In Vets Foundation
Veteran-first training, donors, sponsors, land roadmap, board proof, and housing impact reporting.
CodeeAdmin
Owner operating layer
The admin job is simple: reduce the noise, route each request to the right AI K9, run proof before promotion, and show only the next three owner moves unless deep operations are opened.
python3 codee.py codeeadmin . --business "AI K9 / Invest In Vets" --owner "Sean" --focus "land housing mission" --write --force python3 codee.py doctor . python3 codee.py company . --packet all --write --force python3 codee.py codeecpa . --topic "entity, nonprofit, investor, tax, and land acquisition review" --write --force
Entities
CodeeAdmin keeps nonprofit mission work, paid technology operations, and customer delivery proof written separately.
Veteran-first training, donors, sponsors, land roadmap, board proof, and housing impact reporting.
Service delivery, shops, hosting, customer support, technology partners, and operating proof.
CLI, chat intake, delivery rooms, proof loops, courses, customer workspaces, and support commands.
Daily loop
Each item is built to protect owner time: prove routes, check money lanes, route support, and write the next three moves.
CODEEMAIL, delivery rooms, support requests, Stripe/shop/donation summaries, and active blockers.
Route loops and public proof decide if Codee can promote, sell, or send users to a page.
Mission to Landee, services to Codee, content to Cappy, leads to Bizy, review questions to CODEECPA.
Nonprofit funds, paid customer revenue, shops, donations, and investor claims stay in their correct lane.
The owner gets the highest-value moves first, while details stay in the admin packet.
New agents begin only with a job, guardrails, proof route, and owner approval gate.
Each state gets its own land, housing, sponsor, service, and review scorecard before commitments.
AI K9 agent initiation
This keeps the system expandable without letting experiments touch money, public claims, or mission funds too early.