Re:Ask HN: Are you building an AI company brain?
by mfalcon on Friday November 06, 2026 @07:09AM
(#50391422)
Thanks! It helps a lot! If I merge 1, 2 and 3 that would mean creating a service API with the Claude SDK behind to handle requests whenever some employee wants to make a read/write operation.
The write operations will be made only for the documents included in the repo if the agent allows it according to user permissions. Am I right or did I get something wrong?
I'm also thinking about "real time data" like google docs, chats, transcripts, databases, logs...
My current idea would be to keep that out of this repo and have each user to query them (if they have permissions) with their own personal account. This way the system is more simple and maybe cheaper because each employee can use their current Agent plan instead of the service API tokens that are way more expensive and difficult to limit.
What do you think about this?
Some basic tips I hope that help you.
1. When the system is up and running don't run agents in a loop, wake them up when something happens. An email arrives, something changed, a timer triggered. There is no reason for 24x7 agents most of the time.
2. You want a system that does not allow conflicts, as your baseline, for projects where many people are working on the same thing. Think git for documents. How is not important, it's important that it's there
3. A basic coding harness like Claude Code is going to do a million times better than anything you can build yourself. It's already optimized for dealing with tasks in a complex environment and gets updated near daily. Don't roll something yourself or buy a special solution from a vendor
4. It's super easy to provide context for a meeting. It's very hard to get people to read them. Spend time making sure pre-reads are short, concise and relevant.
5. Only have one source of truth for core data. An AI agent will happily find an outdated document and assume that's the truth. Make sure it's strongly enforced that important structured data is in an easy to search single database.
Build it incrementally. Pester your CTO about what task is the most important then start there. Spend your time collecting feedback from the people who use the system and build as little as possible. Very easy to add every feature, harder to make sure you only build the features that make the system better.
When that is said, this could easily become a very fun project to work on! Feel free to reach out if you get blocked.