Tools · Notion vs Tools ← Tools menu Updated 10-09-2026

Notion ↔ Tools — source-of-truth split

Short reference · canonical sits here · same structure as tools.eliteoutsiders.com (rule 15)

Where every kind of content/system knowledge lives for byCaliber, and how Claude reads it.

A. tools.bycaliber.work (this site) — strict minimum. Live state, counters, boards, process pages. AL-facing first. English only.
B. Notion — full source of truth. Doctrine, prompts, grammars, CRM databases, plans. Everything Claude consumes at execution time lives here: Claude Code HQ — universal patterns · byCaliber — Claude Code HQ — specifics · byCaliber hub (Notion top-level).
C. Audience tags inside Notion — every page, every toggle, every block must carry one of three tags so Claude knows what to read and what to skip:
D. Navigation — AL navigates Notion via ⌘P + keyword. So page titles must be searchable: descriptive, English, no emoji-only titles, no acronyms unless explicit.
E. Hard rule — no Notion edit without explicit AL go. Especially no deletion. Claude always warns first. Triple-confirm before any merge or archive.

Per-topic source of truth

Topic Canonical location Audience Status
Brand identityNotion HQ (to create)not tagged yetnot settled
Sales scriptsNotion + Cal.comnot tagged yetnot settled
CRM dataD1 bycaliber (to come)not tagged yetnot settled
Analytics & eventsD1 bycaliber events tablenot tagged yetlive
Plans & calendarsNotion + Cal.comnot tagged yetnot settled
Process docsThis intranetnot tagged yetlive
Visual assetsDrive (TBD)not tagged yetnot settled
Email templatesBrevo (magic link) + Resend (worker mail) dashboardsnot tagged yetlive
Source codeGit repos (bycaliber-site, bycaliber-tools)not tagged yetlive
Weekly business steeringtools · /weekly-business-steering (D1 weekly_steering + steering_notes)bothCanonical here since 2026-09-10 (migration 0005 to apply)
Actions boardtools · /lf-cross-platform-content (D1 board_state)bothStructure shipped 2026-09-10, no task wired yet
Acquisition architecture (live state)tools · /architecture · doctrine: Notion · byCaliber HQ specificsbothSkeleton here, doctrine in Notion
Cal.com questionnaire wordingtools · /cal-questionnairesbothCanonical here (Cal.com can lose it)
Crons / robotstools · /cronsbothCanonical here

Naming conventions

F. English only for any page/title/toggle/block tagged [for Claude] or [for AL & Claude]. Pages tagged [for AL] can stay in any language — AL's choice.
G. Page titles — descriptive, searchable in ⌘P. No emoji-only titles. Acronyms only with full form on the page.
H. Block-level tags — every meaningful block in a process page carries its audience tag. Saves Claude a full re-read and saves AL the burden of segregation by colour.

Where things must mirror

  1. Any routine/event/cron that touches the byCaliber pipeline → tracked on /crons. Mirror summary in Notion if the process page exists.
  2. Every Notion canonical page → listed in byCaliber — Claude Code HQ — specifics. When a page changes status, update both.
  3. This page (notion-vs-tools) is the short reference. The long form lives in Notion.

n8n VPS — REST + MCP wiring

I. Instance — No byCaliber workflow on the shared n8n instance (Hostinger VPS, 72.62.187.71:5678). The instance, the token (N8N_VPS_API_TOKEN in ~/.config/eo/secrets.env) and the MCP wiring (mcpServers.n8n-eo) are the EO ones, available if a byCaliber workflow is ever created.
J. Trigger a workflow (REST) — Same call as EO: POST /api/v1/workflows/<workflowId>/execute with the X-N8N-API-KEY header. Nothing to trigger for byCaliber today.
K. Instance-MCP — Same MCP server as EO. No byCaliber workflow exposed.
L. Workflows for byCaliber — None (read from the n8n API on 27/08/2026, see /crons: no N8N card).

Page rebuilt on the EO structure on 2026-09-10 · iterate as the pipeline crystallizes.