Independent field journal One person × an AI team
Company Notes.
Field notes on running a company with an AI team.
On the cover
All articles
Why Company Notes?
Why document a real company operated by a person and AI agents, and what belongs in these field notes.
Design the org chart before hiring a Bot
What agents can do, what needs approval, and where permissions belong.
A daily operating rhythm that survives mistakes
Recurring tasks, handoffs, reviews, and handling exceptions.
It is not enough for a Bot to do the work. The company needs to know what happened.
Repeatable workflows, system integrations, and clear boundaries are what make AI useful beyond the demo.
Three places to begin
An implementation order, not a feature list.
Design the org chart before hiring a Bot
What agents can do, what needs approval, and where permissions belong.
A daily operating rhythm that survives mistakes
Recurring tasks, handoffs, reviews, and handling exceptions.
Connect Bots to real company systems
Field references for Mail, Wekan, Memos, ERPNext, MIS MCP, and FFL.
Latest field notes
All articles
Why Company Notes?
Why document a real company operated by a person and AI agents, and what belongs in these field notes.
The archive is growing. New Markdown posts appear here automatically. Browse the archive →
ABOUT THE PUBLICATION
Less AI mythology. More work you can verify.
Company Notes is an independent record of operating a real company with AI. Unverified ideas are described as ideas, not as success stories. Written first in Traditional Chinese, with English and Simplified Chinese translations.