Company harness · git-native · local-first

AI-native companies,written as source code.

Write your company once. Every agent works from the same source, with the context, checks, and review gates already in place.

overbot check · live
$ overbot check
reading overbot.yml · 62 docs · 6 departments
✓ types62 docs, 17 registered types
✓ links411 references resolve
✓ collectionslifecycles match work/ folders
! voicemarketing/work/drafts/launch-post.md
banned word "seamless" · advisory
× driftAGENTS.md diverges from canon
run overbot compile
3 passed · 1 advisory · 1 failed
Running on BotBot · 62 docs · 6 departments · mainBacked bya16z Speedrun

The problem

Your agents are working from different versions of the company.

People notice when context is stale. Agents accept it as truth, and confidently carry the mismatch into the next piece of work.

Context drift3 sources disagree

CLAUDE.md

The agent follows an instruction that no longer matches the product.

3 weeks behind

A product thread

A settled decision disappears when the conversation ends.

private context

Marketing notes

The launch story and the product start describing two companies.

different language
Every handover starts with another context download.

How it works

Define once. Compile everywhere. Check continuously.

The same company definition steers the work and verifies the result. The tools change; the source does not.

01

Define

Write the decisions that should steer the company as typed markdown, reviewed in one place.

company/positioning.mdtype: canonowner: founderstatus: approved
02

Compile

Generate the instructions and policies each existing tool already knows how to read.

overbot compile→ AGENTS.md→ CLAUDE.md→ CODEOWNERS
03

Check

Use the same company definition to verify work before it reaches a human boundary.

overbot check✓ types✓ references! voice advisory

The docs come to the work, compiled. You never assemble context again.

Agent handover

Hand over the work, not a pile of chat history.

Move an active thread from product to engineering, or developer to developer, while preserving what has already been understood.

  • Settled decisions do not reopen accidentally.
  • Open questions stay visible to the recipient.
  • The role changes without flattening the context.
handover · billing-historythread #418
MMayaProduct lead
DDevinFeature engineer
6decisions
4canon docs
2open questions
1active goal
Handover note

Requirements are agreed. Define the API contract and implement statement-period pagination.

Ready to continueContinue work →

Instance zero

We run BotBot on it.

Overbot is built and used internally at BotBot every day. Not just the code: positioning, marketing, product decisions, and investor writing inherit the same company definition.

62typed documents
6departments
411resolved references
1company source
01
Decision

Lead with plain words for what the product does.

02
Canon

Positioning changes once, founder-approved.

03
Marketing

The launch draft inherits the new language.

04
Product

Docs and interface copy compile from the same source.

What becomes possible

One company source. Four compounding capabilities.

The pieces reinforce one another because they use the same typed substrate, not another set of disconnected features to maintain.

The written company

Keep positioning, standards, roles, and voice in deliberate, versioned documents.

company/ · departments/ · roles/

Every tool already fluent

Compile one company into the instruction formats your agents and merge gates expect.

AGENTS.md · CLAUDE.md · CI

Context that moves

Transfer active work between people without flattening its decisions into a ticket.

goal · decisions · open questions

Checks that travel

Validate structure, references, generated artifacts, and explicit company rules.

edit · merge · action boundaries
product briefimplementationreviewshipped with context intact

Early access

Give every agentthe same company.

We’re building now and launching 2026-10-06. Join for build notes and access to the first cohort running Overbot in CI.

No spam. Unsubscribe in one click. We never share the list.

01
Build notes from BotBot, the company that runs on it

What shipped, what broke, and which checks fired on us.

02
Early access to the working product

Overbot init, compile, check, and agent handover before launch.