About
About Hark — shared memory for your AI agents
Hark is built by a founder who kept losing his own ideas — and built the home base he wanted.
How Hark judges itself
A resumed handoff means a different tool picks up the same project within seven days. Hark currently measures a different-tool session after a clean or confirmed handoff, not every brief read. Clean-handoff rate tracks sessions ended with a handoff; time-to-stale tracks the age of dated project state. Recipients answer ‘Was this handoff complete?’ and mark missing blocks. The owner adds gaps as open questions, keeping decisions Proposed. Two handoffs missing the same block trigger a warning before sending. These are how Hark judges itself, not a promise that every handoff succeeds.
Evidence, not an agent's certainty
Every record shows Agreed / Observed / Proposed and a source you can open: where did this come from? Agreed means accepted, not independently verified. Observed is reserved for system evidence such as a merged pull request. An agent's claim is never shown as verified simply because it was accepted.
The founder
Why I built it
I'm Mike Schreiber, and I've spent years building with developers around the world. If you work that way, you know the feeling. The work moves fast, but the understanding doesn't move with it.
We shared projects the old way: status calls, screen recordings, long docs nobody read, and the same context retyped into every new chat. Investors and clients got meetings and slide decks that took hours to prepare and still left them guessing. All that time went into explaining the work instead of doing it.
Then AI agents joined the team, and the problem got sharper. An agent reads your code and your README, then makes its own calls. It can see what you built, but never why. So it quietly undoes decisions you made on purpose, and nobody notices until something breaks.
I built Hark for everyone who's felt that: the founder repeating themselves, the developer inheriting a mystery, the client waiting for an update. The why behind the work shouldn't live in one person's head. Now it doesn't have to.
It's named for the Harkness table — a round table with no head, where every seat is equal and every idea gets heard.
Contact
Email hello@harkstudio.io — it reaches us directly.
Common questions
- Who builds Hark?
- Hark is built by its founder, Mike Schreiber.
- Where does the name Hark come from?
- From the Harkness table — a round table with no head, where every seat is equal and every idea gets heard.
- How can I contact the team?
- Email hello@harkstudio.io. That reaches the founder directly.