AI-enabled operations
Personal AI Project OS
A practical operating system that assigns distinct roles to ChatGPT, Google Drive, Asana, n8n, OpenAI API and external research instead of treating AI tools as an unstructured workspace.
WORKING MVP + OPERATING MODELStructural problem
The constraint that defines the system.
AI-assisted project work can fragment across chat, files, tasks, research and automation. Without clear roles, important decisions disappear, actions lose traceability and automation adds complexity rather than reducing it.
Operating model
The system viewed as interacting layers.
Designed intervention
Architecture translated into operating mechanisms.
- 01
Defined ChatGPT for thinking, Drive as the SSOT, Asana for execution, n8n for orchestration and OpenAI API for workflow intelligence.
- 02
Built and stabilized a manual Asana task-processing loop through n8n and OpenAI, returning useful AI comments to Asana.
- 03
Defined daily and weekly operating rituals and explicit rules for when new automation is justified.
- 04
Deferred additional automation until repeated operational pain provides a real trigger.
Value mechanism
Economic value without invented ROI.
The value mechanism is lower cognitive and coordination overhead: durable knowledge, traceable execution, controlled automation and a deliberate boundary between human judgment and workflow intelligence.
Evidence & claim boundary
What the case supports and what it does not claim.
Only the manual Asana-to-OpenAI loop is treated as a working MVP. Later Drive, structured-memory and external-research automation remain future or conditional workflows.