Library
One library every agent reads first.
The Library holds what is true about your business: customers, voice, decisions, metrics, every change you have shipped and the rules your agents follow. Every capability reads it before it starts.
How it works
- 1
Set up the workspace
A short interview covers your company and your systems, and reads your repositories’ instruction files on day one.
- 2
Books take shape
Customers, voice and decisions are written into books you can edit and preview.
- 3
Ledgers fill in
Metric readings and shipped changes land in Metrics and the Changelog as dated records.
- 4
It stays current
The Library Maintainer makes small, cited edits each day when something has actually changed.
Books and ledgers
One home for each fact
Each subject lives in one place. Numbers live only in Metrics, dated changes only in the Changelog, and everything else points to them, so two documents never disagree.
- Books you edit, with save and preview
- Company now, Metrics and Changelog built live from records
- Ledgers built only from records
Provenance
Every fact has a source
Every edit records where it came from, and the Library Maintainer cites its evidence: a commit, a metric reading, a change or a report.
- Stated by you, observed by a tool, or written by an agent run
- Cited edits that point at commits, readings and changes
- Agents look facts up instead of guessing your decisions
Operating rules
Rules written once, followed everywhere
Operating documents hold the rules and skills that shape agent work, like your git workflow or engineering conventions, with history and archive.
- Workspace rules override account rules, which override Boardbox’s
- Skills loaded only when the work calls for them
- Sensitive rule changes need your approval
Where it stops for you
Runs on its own
- Reads your repositories’ instruction files during setup
- Makes small cited edits each day when something changed
- Records metric readings and shipped changes in the ledgers
Waits for you
- Account-wide rule changes
- Changes to your git workflow
- Archiving an operating document
- Any decision only you can state
What it works with
Reads
- Your messages
- Initiative events
- Support results
- Commits
- Metric readings
- Repository instruction files
Produces
- Books
- Metrics ledger
- Changelog
- Operating rules and skills
Where founders use it
Day one
Set up the workspace once and every capability starts from the same picture of your company.
A new rule
Tell any agent how you want something done and it is saved as a rule the rest follow.
What changed this month
Read the Changelog to see every shipped change, each one recorded as it happened.
How it compares with a wiki
In the Tablebird launch
The company is already explained.
The Initiative already knows who Tablebird sells to, how it writes and what it has decided, and so does every capability it calls after this.
Follow the whole launchWhat people ask
- Do I have to write it all up front?
- No. Setup interviews you briefly and reads what it can find. The library grows as the work happens.
- Can I import from Linear?
- Yes, once, into Product. There is no sync and Boardbox never writes back.
- What is the Library Maintainer?
- A built-in daily Automation that makes small cited edits to the library, only when something has changed.
- Is it shared between companies?
- Never. Each workspace is its own company with its own library.
- How do rules and skills work?
- Rules always apply; skills load only when the work calls for them. Your workspace’s copy overrides account-wide and Boardbox defaults.
How it connects to the rest of the company
Every capability reads the same Library and reports into the same Initiatives.
Early access · macOS
Run your next launch from one conversation.
We’re onboarding a few founders and small teams each week, one at a time, starting with the launch you’re planning next.
We email you once, when your seat is ready.