BusinessOperations
Collaboration Playbook
This table tracks the current and possible tool stack for an AI-native solo
AI-native Builder Tooling Stack
This table tracks the current and possible tool stack for an AI-native solo builder and future small team. It is an operating map, not a procurement plan.
| Category | Tool | Status | Current / possible use | Future use | Notes / risk |
|---|---|---|---|---|---|
| AI Coding | Claude Code | Evaluating | Agentic coding and complex codebase tasks. | Use for architecture-heavy refactors when project tests and docs are mature. | Compare with CodeX and Cursor workflow before relying on it. |
| AI Coding | Claude Design | Later | Design exploration and UI direction. | High-polish visual direction packs. | Keep outputs aligned with Prox OS design tokens. |
| AI Coding | CodeX | Using now | Deep repo changes and prompt-driven implementation. | Parallel branch execution and documentation-aware development. | Keep hard scope and acceptance criteria. |
| AI Coding | Cursor | Using now | IDE-level code editing and project reading. | Daily implementation companion. | Avoid unbounded refactors. |
| AI Coding | Devin | Later | Long-running engineering tasks and PR workflows. | Use after repo tests, docs, and issue templates are mature. | Needs very clear scope and review. |
| Agent Runtime | Dify | Evaluating | RAG, workflow, and agent backend reference. | Could power selected backend workflows. | Do not let it replace Prox OS UI differentiation. |
| Agent Runtime | LobeChat | Evaluating | Multi-model chat UI reference. | Optional personal model hub reference. | UI inspiration, not platform core. |
| Agent Runtime | OpenAI | Using now | LLM provider and agent model layer. | Tool calling, structured outputs, agents, and evals. | Avoid model lock-in by preserving provider boundaries. |
| Agent Runtime | OpenClaw | Evaluating | Self-hosted action-taking agent and Slack/chat integration reference. | Local companion and agent-ops research. | Verify security model and permission scopes. |
| Analytics | PostHog | Using now | API Worker currently has a PostHog client path when configured. | Product analytics with consent and privacy posture. | Watch PII capture, retention, and subprocessor disclosure. |
| Collaboration | Discord | Later | Public community and builders. | External community and early builder support. | Less structured than Slack for internal ops. |
| Collaboration | Slack | Evaluating | Internal AI agent ops and engineering coordination. | Agent identities, logs, approvals, and workflows. | Better for internal ops than public community. |
| Compliance | Drata | Later | Security/compliance automation reference. | Alternative to Vanta when enterprise readiness matters. | Too early for v0.1. |
| Compliance | OneTrust | Later | Enterprise privacy/compliance management. | Large enterprise privacy operations. | Too heavy early. |
| Compliance | Vanta | Later | Security/compliance automation. | SOC 2 readiness when enterprise leads exist. | Too early for v0.1. |
| Data / Database UI | Airtable | Later | Interface/database inspiration and integration target. | Import/export and connector target. | Avoid becoming only an Airtable clone. |
| Data / Database UI | Baserow | Evaluating | Open database and personal data sovereignty reference. | Personal data tables or app data backend option. | Verify API, hosting, and permission fit. |
| Data / Database UI | Notion | Later | Docs/database/workspace inspiration and integration target. | Import/export source and template reference. | Avoid becoming only a Notion clone. |
| Design | Canva | Later | Marketing assets and lightweight design. | Founder marketing and launch assets. | Not a core product dependency. |
| Design | Figma | Evaluating | Design system and UI prototype reference. | Future design handoff and community templates. | Keep tokens and code as source of truth. |
| Development Platform | Cloudflare | Using now | Pages, Workers, R2 direction, analytics, and edge runtime. | Cloudflare-first deployment and app hosting. | Keep provider-switchable boundaries where practical. |
| Development Platform | GitHub | Using now | Repo, issues, release evidence, and developer identity. | App submission, builder workflow, marketplace identity. | Core developer distribution channel. |
| Development Platform | Vercel | Later | Frontend deployment and marketplace reference. | Optional integrations and deployment examples. | Avoid unnecessary platform split. |
| Docs / API | Fumadocs | Using now | Docs site generated from root docs/. | Public docs and AI-readable docs. | Keep docs synced with architecture. |
| Docs / API | Scalar / OpenAPI | Using now | API Worker docs and API explorer direction. | Future API docs and contract validation. | Do not overbuild backend now. |
| Docs / API | Storybook | Using now | UI Workshop and component documentation. | Design system review and visual QA. | Keep design tokens aligned. |
| Observability | Sentry | Later | Error monitoring candidate. | Production reliability once real users exist. | Watch PII capture and retention settings. |
| Payments | Paddle | Later | Merchant of Record option for global SaaS or digital products. | Evaluate when EU/global B2C grows. | Higher fees and policy fit tradeoffs. |
| Payments | Stripe | Evaluating | Direct payments first; future Connect or Managed Payments evaluation. | Early paid access and later marketplace payouts. | Start simple and do not promise global payouts. |
| Project / Ops | Atlassian | Later | Jira/Confluence/Marketplace ecosystem reference. | Future marketplace and team workflow reference. | Not early core. |
Contact Types
| Contact type | Likely timing | How to respond | What not to share |
|---|---|---|---|
| General collaboration | early | sandbox/demo, scope-first conversation | repo access, secrets, user data |
| Commercial customer trial | after usable beta | limited pilot, written scope | unsupported SLA, custom promises |
| Investor/VC intro | after traction or strong demo | public deck, demo, high-level architecture | full private repo, raw secrets, sensitive data |
Response Templates
Ordinary Collaborator
Thanks for the interest. Prox OS is still in founder preview, so the safest next step is a scoped demo or small public contribution. I can share a public overview, current roadmap, and a bounded task area before any deeper access.
Developer Who Wants To Join
Thanks for wanting to build with Prox OS. The clean path is to start from a role spec, allowed paths, and a small contribution scope. We need clean-room IP boundaries: no employer code, employer device, private client material, or work during employer time.
Regional Partner
Thanks for the regional interest. We can discuss market learning, community channels, local product expectations, and pilot ideas. Legal, tax, payment, ICP, data residency, or company setup claims must be reviewed professionally before any commitment.