founder-ai-os

bywibnf asygguu

Build a SaaS prototype called **Founder AI OS**. This is an AI-powered operating system for a solo founder. The Founder is the final decision maker, while AI workers prepare and execute delegated work. The first project managed by the system is **Kawasan Masjid 1.000 Ha**, but the platform must be reusable for multiple future projects. ## CORE PURPOSE The system should help a Founder manage: * Projects * Opportunities * Experts * AI Workers * Research * Knowledge * Tasks * Approvals * Decisions * Activity * Metrics The central principle is: **AI has hands, but the Founder holds the keys.** Consequential decisions must require human approval. ## MAIN MODULES ### 1. Founder Dashboard Show: * active projects * pending approvals * opportunities * experts * AI workers * tasks * recent activity * project health * key metrics The interface must be professional, clean, modern, mobile-first, and responsive. Avoid a generic admin-dashboard appearance. ### 2. Project Registry Projects contain: * name * description * vision * status * priority * goals * milestones * tasks * risks * notes * related opportunities * related experts * activity Create the first project: **Kawasan Masjid 1.000 Ha** Status: Research & Prototype. ### 3. Opportunity Radar Track potential opportunities. Fields: * title * problem * target users * category * source * evidence * potential value * difficulty * urgency * score * status * next action Statuses: Discovered, Researching, Validated, Rejected, Selected, Archived. ### 4. Expert Radar Track relevant experts. Fields: * name * discipline * expertise * organization * profile/source * evidence * relevance score * related project * collaboration status * notes Possible disciplines: Software, AI/ML, Data, Database, GIS, UI/UX, Energy, Agriculture, Sustainability, Finance, Urban Planning, Cybersecurity, Business, Legal, Research. Never invent expert credentials. Evidence should be recorded. ### 5. AI Worker Registry Initial workers: * Researcher * Opportunity Radar * Expert Radar * Project Manager * System Architect * Software Engineer * Data Operator * Knowledge Manager * Content Operator * Finance Assistant * QA/Reviewer Each worker needs: * role * purpose * responsibilities * inputs * outputs * permissions * KPI * status * project assignment No worker without a clearly defined job, input, output, permission boundary and KPI. ### 6. Approval Queue AI recommendations or consequential actions can become approval items. Show: * title * type * AI worker * project * explanation * evidence * proposed action * risk * impact * timestamp * status Actions: Review, Accept, Reject, Request Revision. Statuses: Pending, Accepted, Rejected, Revision Requested, Executed, Cancelled. The Founder remains the final authority. ### 7. Knowledge Base Support: * research * notes * decisions * assumptions * evidence * documents * links Each item should have: title, type, source, content, confidence, project, tags, timestamps. Do not present assumptions as facts. ### 8. Tasks Tasks contain: * title * description * project * AI worker * priority * status * due date * dependency * output * approval requirement Statuses: Backlog, Planned, In Progress, Review, Approved, Completed, Blocked. ### 9. Activity Log Record: * actor * action * object * project * timestamp * result Actors: Founder, AI Worker, System. ### 10. Decisions Record important Founder decisions: * decision * context * alternatives * reasoning * evidence * project * date * outcome ## DATA ARCHITECTURE Design a scalable relational model suitable for PostgreSQL/Supabase. At minimum: users projects project_members opportunities experts ai_workers tasks approvals knowledge_items activity_logs decisions milestones Use relationships rather than unnecessary duplication. Do not hard-code the mosque project into application logic. ## PERMISSIONS Founder: full control and approval authority. AI Worker: limited delegated permissions; may create research, recommendations and tasks, but cannot make irreversible strategic decisions. Viewer: read-only. Do not implement autonomous financial transactions, identity verification, legal declarations, or irreversible external actions. ## FUTURE INTEGRATIONS Prepare modular architecture for future integration with: * GitHub * Supabase * Canva * AI APIs * research sources * social media * finance tools Do not require these integrations for v0.1. ## FUTURE WORKFORCE Architecture should eventually support: Researcher → evidence Opportunity Radar → opportunities Expert Radar → experts Project Manager → work Architect → systems Engineer → software QA → testing Knowledge Manager → validated knowledge Finance Assistant → financial records Founder → approval and strategic decisions Do not implement autonomous versions of all workers now. ## NAVIGATION Dashboard Projects Opportunities Experts AI Workers Research Knowledge Tasks Approvals Decisions Activity Settings ## DEVELOPMENT STRATEGY Do NOT immediately build the entire system. First generate: 1. Requirements 2. User flows 3. Information architecture 4. Database/data model 5. System architecture 6. Design system 7. Main screen designs 8. Task breakdown Then STOP for Founder review. After approval, build the smallest useful vertical slice: **Dashboard + Projects + AI Workers + Approval Queue + Activity Log** Do not deploy yet. ## CREDIT LIMIT The Founder currently has only **14 free credits**. Treat credits as scarce. Before expensive execution, show the estimated credit cost and expected result. Do not perform unnecessary design generation, implementation, integrations or deployment. Preserve credits for the highest-value implementation and fixing. Deployment should NOT be performed at this stage. ## SUCCESS CRITERIA The result must be a credible foundation for a real Founder AI OS, not merely a visual demo. It must have: * coherent architecture * reusable data model * useful dashboard * project registry * AI worker registry * approval workflow * activity/audit trail * mobile-first UX * multi-project architecture * clear future expansion path Start with **Requirements, User Flows, Information Architecture and Architecture Blueprint**. Do not deploy. Do not begin large implementation tasks until the Founder approves the plan.