v0.13
Company Wiki & Connector Health
- Company Brain
- Connectors
- Chief of Staff
Your crews can now read the company wiki and cite what they read, and your connections tell you when they break instead of failing quietly inside a workflow.
Ask your company wiki
The Chief of Staff now reads the pages your company writes down — handbook, metrics, decision log — and answers from them directly. Every answer names the page it came from, so you can check the source rather than trusting a paraphrase. Ask "what did we decide about vendor spend?" and you get the decision and where it was recorded.
Connectors that raise their hand
A broken connection used to surface as a workflow that quietly returned nothing. Connector health now tracks each connection and alerts you when one needs attention, so a lapsed token is something you fix in a minute rather than something you discover a week later in a briefing that was missing half its input.
Tokens that fail closed
Each connection resolves through a per-user rail. If your token cannot be resolved the call fails rather than falling back to a shared credential, so one person’s access is never quietly borrowed to do another person’s work.
Your Notion OKRs become Goals
If you keep objectives in Notion, they now sync into durable Goals that crews can read and track against. You keep writing them where you already write them, and the rest of the system stops being blind to what you are actually aiming at.
Commitments that close themselves
When a commitment is met, Crew One detects the resolution and closes it rather than waiting to be told. Anything that no longer matters, you can dismiss outright, so the open list stays a real list of what is outstanding.
Everything in this release
- The Chief of Staff reads your company wiki and cites the page each answer came from (BAS-1626).
- Durable connector health, with alerts when a connection needs attention (BAS-1419).
- A per-user connector rail with fail-closed token resolution (BAS-1432).
- Notion OKRs sync into durable Goals (BAS-1412).
- Commitments close the loop, with detected resolution and a founder who can dismiss (BAS-1346).
- Canonical entity resolution, so one person or company resolves to one identity across every surface (BAS-1416).
Fixes
- The connector-health ledger is registered as per-user erasable data (BAS-1424).