The operating system governing every Companion Health artifact, decision, and expression. Optimised for institutional memory — not marketing.
Document
CH-BOS
Version
v4.0 · Ratified
Owner
Companion / Animetric
Volumes
00 – 11
Preamble
The Brand Operating System is not a brand guide. It is the operating system governing every Companion Health artifact, decision, and expression. A brand guide tells you how the logo works. This tells you how the company thinks.
Companion Health has accumulated enough intellectual property, governance, language, and visual systems that it now requires its own operating manual. Without one, the organisation spends each year rediscovering decisions it has already made. This document is the institutional memory that prevents that — a living constitution intended to expand indefinitely through versioned amendments while holding its foundations stable.
It reads in the tradition of an operations manual, not a marketing deck: every rule is enforceable, every value is canonical, every artifact is governed. Read it in order. Volume 00 establishes why Companion exists before any later volume tells you which green to use — because no one can apply the system correctly without first understanding the thesis it serves.
BOS Constitutional Status — what may change, and how
Not every line in this document carries equal weight. To prevent the BOS from degrading into a dumping ground, every element is assigned one of three governance levels. The level determines the process required to change it.
Level 1
Constitutional
Identity & category
Approved vocabulary & ontology
Diagram system grammar
Governance framework
Requires amendment process
Level 2
System
Components
Design tokens
Patterns & layouts
Figure specifications
Requires review
Level 3
Operational
Decks
Social assets
Marketing material
Campaign content
May evolve freely
One system — the constitutional map
Every volume answers one constitutional question, and each derives from the one above it. The BOS is not a stack of separate guides; it is a single operating system with one root.
The Constitution
Identity
Brand
Mesh
Components
Language
Ontology
Figures
Narrative
Behaviour
Motion
Runtime
Governance
↓ Every Companion property
The two constitutional principles
Two principles sit above every volume. The first is the thesis; the second governs how everything is expressed — in diagrams, motion and interaction alike.
Companion does not just explain — it reveals. Information is never dumped all at once; it unfolds in causal order: observation → qualification → signal → interpretation → confidence → outcome.
Every institutional system has marks that identify it before the logo appears — Apple has whitespace, Stripe its gradient, Palantir its ontology, Claude its editorial restraint. Companion has five. If every product carries all five, people recognise Companion on sight. This is the single most valuable brand asset in this document.
01
The Intelligence Mesh
The operating fabric beneath every surface.
02
Institutional Figures
CHDS diagrams — engineered, not illustrated.
03
Continuity Language
A fixed ontology — the company's dictionary.
04
Measured Motion
Animation that reveals change, never decorates.
05
Interrogable Objects
Everything can be inspected, replayed, explained.
Volume 00
The Operating Model
Before the system, the thesis. Why Companion exists — and what it is — must be understood before anyone applies a colour, draws a figure, or writes a line. This volume is the philosophical foundation for everything that follows.
00.1 Why00.2 What it is00.3 What it is not00.4 Signal thesis00.5 Fetch thesis00.6 Constitutional identity00.7 Category00.8 The flywheel00.9 The three layers
§ 00.1 — Why Companion Exists
The signal is always there. The system learns to read it earlier than the symptom does.
Pet health is recorded after the fact. By the time a record exists, the body has already been speaking for months.
Every pet continuously emits signal — weight, activity, appetite, behaviour, the texture of daily life. That signal precedes diagnosis. The ecosystem already captures most of it, scattered across apps, wearables, clinics and claims, and then discards its meaning because no layer is responsible for reading it across time.
Companion exists to close that gap: to interpret the signal the ecosystem already holds, before the symptom, before the claim, before the loss. Not to add another record — to read the records that exist.
§ 00.2 — What Companion Is
Constitutional identity — never paraphrase
Companion Health is biological intelligence infrastructure for the global pet ecosystem.
Companion is an interpretation layer, not a destination. It sits beneath the surfaces pets and their people already use, reads behavioural and telemetry signal across time, resolves it into named risk, and returns that intelligence through a single interface. It is infrastructure: invisible when it works, depended upon by everything above it.
§ 00.3 — What Companion Is Not
Companion is not
A pet health app or consumer destination
A pet insurance company
A records platform or EMR
A wearable or device maker
An "AI-powered" analytics dashboard
Companion is
An intelligence layer the ecosystem integrates
The interpreter of signal others capture
An API-delivered risk model
Infrastructure, multi-tenant by design
Measured, forensic, evidence-based
§ 00.4 — The Signal Thesis
Thesis · Signal
Records say what happened. Signals say what is changing. The value is not in the data point — it is in the trajectory read across time, against the subject's own baseline and the cohort around it.
A single weight is a fact. A weight falling 6% over three weeks against a stable baseline is a signal. Companion's defensibility is that it reads the second kind — persistence, velocity, and confidence — not the first.
§ 00.5 — The Fetch Thesis
Thesis · Fetch
Intelligence that cannot be delivered is not infrastructure. Fetch is the single contract through which every consumer reaches the Signal Layer — one integration, every partner, native to the surfaces people already use.
The Signal Layer produces understanding; Fetch makes it accessible. One API, multi-tenant, no platform replacement. The thesis is distribution: the moat compounds only if the intelligence reaches every consumer through a contract that does not change.
§ 00.6 — Constitutional Identity
Three names, three audiences, one architecture. Each is used deliberately; none is interchangeable.
Name
Layer
Used with
Animetric
Parent infrastructure
Internal · investor
Companion Health
Platform · trust
External communication
Fetch™ API
Product · delivery
Developer · partner
§ 00.7 — Category Definition
Not the category
Pet Health Platform
Pet Insurance Platform
Pet Wellness App
Predictive Analytics SaaS
The category
Biological Intelligence Infrastructure
A layer, not a product
Defined by what it interprets, not what it displays
New category — named, not borrowed
§ 00.8 — The Companion Flywheel
The moat is longitudinal.
Accumulated behavioural truth is the one asset that cannot be acquired — only accrued. Each new subject, signal and partner makes the whole system smarter, and the input is time, which cannot be purchased. The canonical depiction is Fig 14.01.
Fig 14.01The Compounding Loop
§ 00.9 — The Three Layers
The whole model resolves to three layers. Companion interprets; Fetch delivers; consumers act. Everything in this manual serves one of the three.
Layer 01 · Intelligence
Companion
Reads signal across time. Resolves behaviour and telemetry into named, confidence-weighted risk. The interpretation layer.
Layer 02 · Delivery
Fetch
The single API contract. One integration carries intelligence to every consumer, native to their surface. The distribution layer.
Layer 03 · Action
Consumers
Insurers, veterinary, pet parents, shelters, research. They operationalise the intelligence. They orbit the layer; they are not the product.
Volume 01
Identity
The verbal and positional identity of the company — the statements that must never be paraphrased, and the voice every artifact inherits.
1.1 Company definition1.2 Mission1.3 Vision1.4 Voice
§ 1.1 — Company Definition
Approved usage — verbatim
Companion Health is the predictive intelligence layer for pet health & insurance — transforming behavioural and telemetry signal into risk intelligence, before clinical diagnosis.
This statement is Level 1 Constitutional. It may be shortened for space only by removing trailing clauses, never by substituting words. "AI-powered", "real-time", "revolutionary" are forbidden in or around it (see Volume 05).
§ 1.2 — Mission & § 1.3 — Vision
Mission — to read the signal the ecosystem already holds, and return understanding before the symptom.
§ 1.2 · Constitutional
Vision — a pet ecosystem where loss is prevented because risk was understood early, everywhere, through one layer.
§ 1.3 · Constitutional
§ 1.4 — Voice
Companion writes like a clinical instrument, not a brand.
Voice is
Observational, not persuasive
Factual, not emotional
Compressed, not verbose
Third-person system view
Institutional · measured · forensic
Voice is not
Hype, urgency or excitement
"We found" / "your pet needs"
Marketing superlatives
Emoji or exclamation
Buzzwords of any kind
Volume 02
Brand System
The marks, colours and typefaces. Every value here is canonical and version-controlled — quoted, never approximated.
The operating fabric. Not a background grid — a living, persistent coordinate system that every Companion property is drawn inside. Stripe has gradients; Apple has whitespace; Palantir has ontology. Companion has the Mesh.
2.5.1 The fabric2.5.2 Lattice spec2.5.3 The living layer2.5.4 Mesh gradients2.5.5 Application law
§ 2.5.1 — The Operating Fabric
Everything exists inside one coherent system. The Mesh makes that visible.
A quiet, institutional fabric that communicates — without a word — that every screen, document and product is part of a single intelligence system.
It stops being “the background grid” and becomes the operating fabric of Companion — the signature that says everything here is connected.
§ 2.5.1 · Constitutional
Live · the fabric, dark / forest field
§ 2.5.2 — Lattice Specification
A persistent coordinate system.
The lattice constants are constitutional. They do not change between properties — the coordinate system is shared, so a node at x12·y08 means the same thing everywhere.
Constant
Value
Role
Master lattice
64px
Primary structure · layout spine
Sub-grid
16px
Master ÷ 4 · micro-alignment
Baseline opacity
2%
Whisper-quiet · never decorative
Coordinate origin
top-left 0·0
Persistent across surfaces
Node identifier
N·{gx}{gy}
Stable reference to a lattice point
§ 2.5.3 — The Living Layer
Reveal an intelligence field — don't draw a network.
The lattice is static; the intelligence moves. Most nodes are simply present — lonely, unconnected. A minority hold a single straight orthogonal relationship; a handful form a small local cluster. Activity behaves like weather: independent micro-events emerge and fade, nothing synchronises, nothing repeats. A travelling pulse runs straight between two nearby nodes and then disappears. Idle nodes breathe almost imperceptibly in luminance. The fabric should be invisible until noticed — present, never performing.
Lonely nodes · rare relations
Sparse · transient signals
The field carries
Mostly lonely nodes (presence, not links)
Straight orthogonal relations (H / V)
Independent transient signals
Rare contextual labels (~1 in 20)
Never
Curved “intelligence” connectors
Every node connected (network look)
One global, synchronised animation
Regular spacing / checkerboard density
§ 2.5.4 — The Mesh-Gradient System
Brand-locked colour fields.
Beneath the lattice sit five canonical colour fields — organic multi-radial gradients, brand-locked, never free-form. They give the fabric atmosphere and depth without breaking the two-colour discipline of Volume 02.
paper
dawn
forest
signal
plum
§ 2.5.5 — Application Law & Implementation
A persistent operating fabric — calm, institutional, permanent. Continuously present, never performing.
Approved
Mesh on every property as the base layer
One shared coordinate system
Dark grounds flip lattice ink automatically
Reduced-motion disables propagation
Forbidden
Re-implementing the mesh per project
Free-form gradients outside the system
The mesh competing with content
Disabling the coordinate origin
companion-meshLevel 1 · Constitutional
Drop-in web component + stylesheet. <companion-mesh tone field density motion coords annotate> over mesh.css (lattice + gradient tokens). Place as a full-bleed backdrop behind content.
Open the mesh reference →
Volume 03
Design System
Where the audited components live. Tokens, grid, elevation and motion — the functional vocabulary of every Companion surface.
The grid is 8pt. Radii stay near-square (2–4px) — clinical precision, never pill shapes. Borders are structural; prefer spacing over borders where possible.
§ 3.3 — Grid · § 3.4 — Elevation
Property
Value
Columns
12 · responsive
Max content width
1280px
Desktop margin
80px
Gutter
24px
System working column
560px
Elevation
contrast + spacing — no box-shadow on cards
§ 3.5 — Motion
Motion must answer "what changed?"
If it cannot, it is forbidden. Motion is triggered by data change only — never decoration. No slide-in, no bounce, no looping effects beyond the ambient system-live dot.
Event
Duration
Notes
Risk interpolation
300–600ms
Smooth value transition, no overshoot
Risk pulse
400ms
Single scale pulse on threshold cross
Signal fade
200ms
Opacity only, no movement
Status dot
2.4s loop
Ambient system-live indicator only
Easing
cubic-bezier(.22,1,.36,1)
Ease-out sharp
Volume 03.5 · Level 1 Constitutional
Motion & Behaviour System
Companion's constitutional motion language. Apple has Human Interface Guidelines; Material has Motion; Carbon has its choreography; Palantir has ontology interactions. Companion has the MBS — not flashy, but institutional, measured, scientific.
Motion exists to reveal intelligence \u2014 never to decorate interfaces. If an animation does not improve understanding, it does not exist.
§ 3.5.1 · Constitutional · the single principle
Everything in this volume derives from that one sentence. The MBS does not standardise animation for its own sake; it standardises behaviour \u2014 so a card, a signal, or a confidence score behaves identically across Runtime, Trust, FDD and CIN. Consistency of behaviour is what makes the platform feel like one institution rather than many screens.
§ 3.5.2 — The Six Motion Laws
The laws
01 Motion must always explain change. Never animate static information.
05 Animation must reduce cognitive load, never increase it.
06 Meaning always precedes beauty.
Therefore never
Looping or ambient decoration
Everything animating at once
Random or non-causal sequencing
Bounce, overshoot, elastic easing
Motion that performs instead of informs
Page-specific custom animations
§ 3.5.3 — Motion Taxonomy
Seven families. No custom animations.
Every animation in Companion belongs to one of these families. Each keys off a single motion token. Press replay on any specimen \u2014 it occurs once, then stops.
Type A--motion-arrival · 220ms
Arrival
Introduce new objects. Fade + rise 8px, ease-out.
Replay
Type B--motion-qualification · 600ms
Qualification
An object becomes valid. Stroke draws, glows, settles.
Replay
Type C--motion-relationship · 500ms
Relationship
Two things become connected. Line draws, one pulse, remains.
Replay
Type D--motion-signal · 900ms
Propagation
A signal moves. One travelling light, one direction, never loops.
Replay
Type E--motion-confidence · 700ms
Confidence
A numerical value changes. Count once, stop.
Replay
0.00
Type F--motion-inspection · 300ms
Inspection
User selects. Border thickens, glow rises, neighbours soften.
Replay
Type G--motion-transition · 500ms
Transition
Narrative changes. Cross-fade, 300\u2013500ms. Nothing more.
Replay
Observation
Interpretation
§ 3.5.4 — Motion Rhythm
A conductor, not a crowd.
Almost every AI-generated interface animates everything at once. Companion paces motion like cinema: one event, pause, the next, pause \u2014 understanding accumulates. Motion follows causality (Law 04).
More important than motion. Cards lift 2px on hover (never scale) and thicken their border on select while neighbours stay still; buttons deepen and compress 120ms on press; panels appear through opacity \u2014 never slide, bounce, or overshoot. Hover a card, then select one:
Subject
pet_04A
Cohort
n=1,247
Signal
Renal
Every object transitions through one shared state machine \u2014 no per-screen states:
Animation comes from state change — not interaction.
Every object in Companion moves through one canonical lifecycle. Motion is the visible transition between two of these states — which is far more institutional than animating on click. An object's appearance always reflects exactly which state it occupies.
01
Dormant
Present, not yet observed.
02
Observed
Telemetry has touched it.
03
Qualified
Validated against baseline.
04
Correlated
Related to a cohort.
05
Persistent
Confirmed across time.
06
Interpreted
Resolved into a signal.
07
Consumed
Delivered through Fetch.
08
Archived
Retained for replay.
§ 3.5.6 — Intelligence Mesh Behaviour
Alive, but calm.
The Mesh (Vol 02.5) inherits the motion laws. Its behaviour is bounded so it never becomes a performing network.
Rule
Bound
Maximum active nodes
6 · never the whole mesh
Activation
local only · radius 80\u2013160px
Timing
random · every 8\u201315s
Connections
straight · appear only on information change
Hover / select
mesh activates beneath cursor / object
Forbidden
constant pulses · bezier spaghetti · fake neural net
§ 3.5.7 — Documentary Motion
Narrative, paced like cinema.
CIN introduces a narrative motion family distinct from component motion. A sequence is staged in acts \u2014 each holds before the next begins. Same causal order as the rhythm, at a slower documentary cadence (--motion-documentary · 1800ms).
Act I · Six observers appear\u2192Act II · One qualification\u2192Act III · One signal\u2192Act IV · Interpretation\u2192Act V · Outcome
Architecture diagrams follow identical choreography: nothing moves initially; observation enters; pause; arrow draws; pause; component activates; pause; output appears; hold. No loops, no spinning, no floating icons.
§ 3.5.8 — Animation Budget & Motion Tokens
A motion budget per screen.
Budget
Max 3 simultaneous animations per screen
Max 1 hero animation
Everything else static
Interaction depth: See \u2192 Inspect \u2192 Explore \u2192 Understand
Never
Open-modal / close-modal as the only interaction
More than one hero in motion
Visual noise from competing animations
Synchronised everything
Like colour, motion is tokenised \u2014 so Runtime, CIN, Trust and FDD literally behave the same. Each bar below runs at its real token duration:
--motion-arrival220ms
--motion-inspection300ms
--motion-transition500ms
--motion-qualification600ms
--motion-signal900ms
--motion-network1200ms
--motion-documentary1800ms
Replay tokens
Motion & behaviour tokensLevel 1 · Constitutional
Durations live in colors_and_type.css as --motion-*; the seven families and behaviour state machine are specified here and demonstrated by mbs.css + mbs.js. No surface invents its own motion.
Volume 04
Diagram System CHDS
The grammar of every figure Companion draws. Signals move through fields, not boxes. The diagram language is Level 1 Constitutional — its vocabulary does not drift.
Signal over noise. A diagram earns its place only if the path itself communicates meaning. The environment communicates system depth; connections are directional but organic.
Companion figures feel engineered, not illustrated — clinical, institutional, software-native, investor-grade. They are drawn with curved trajectories, branching intelligence flows, cohort fields and replay contours. A reader should want to screenshot them. The goal is not explanation; it is memorability.
The proprietary characteristics
Companion diagrams are becoming a recognisable, proprietary system. These are the characteristics that make a figure unmistakably Companion — document them, so no one unknowingly draws a PowerPoint flowchart six months from now.
Editorial headings
Faire Octave titles with a single italic accent word — never a generic chart label.
Mono figure identifiers
Every figure carries a FIG NN.NN identifier in Suisse Mono.
Architectural flow
Information moves with directional, causal structure — not decorative arrangement.
Layered information
Primary, secondary and inferred strata, distinguished by stroke weight.
Inspectable objects
Nodes read as objects that could be selected, replayed, explained.
Institutional annotation
Quiet mono micro-labels and coordinates — forensic, never promotional.
§ 4.2 — Diagram Vocabulary
Signal path
Straight orthogonal segments, rounded at the joints. Directional — never a freehand curve.
Scattered points — the population around a subject.
Replay contour
A signal traced backward through time.
§ 4.3 — Canonical Forms
Five forms carry the system: layer stacks (vertical numbered structure), topologies (orbital ecosystems), flywheels (accelerating spirals), replay systems (forensic traces) and cohort fields (population context). Every approved figure is one of these. New forms require a Level 1 amendment.
§ 4.4 — Forbidden Patterns
Never
Cloud icons
SaaS gradients
Rounded flowcharts
AI-generated infographic look
Figma-template aesthetics
Hub-and-spoke radial diagrams
Always
Straight, directional signal paths (rounded joints)
Cream ground, green ink, sage tints
Mono FIG labels, self-branded
Environmental geometry for depth
One canonical form per figure
Volume 04.5
Figure Library
Not rules — actual approved figures. Companion treats figures as products: versioned, status-tracked, with a manifest of where each is used. This library is the canon. It will grow past fifty.
Approved canonVersion controlUsage manifest
§ 4.5 — The Canon
Figures are products, not illustrations.
Every canonical figure carries an ID, a status, a version, and a usage manifest. A figure is never redrawn ad hoc; it is amended, re-versioned, and re-issued from here.
Approved terms are load-bearing — they name real objects in the system. Forbidden terms are not stylistic preferences; they are category errors.
Approved — the ontology
Signal
Subject
Replay
Cohort
Intervention window
Confidence
Persistence
Velocity
§ 5.2b — Companion Vocabulary
The preferred ontology.
Not a banned-words list — the words Companion prefers. This is the company's internal dictionary: when a generic term is reached for, the canonical one is used instead. It keeps every surface speaking one language.
Instead of
Companion says
Dashboard
Runtime
Prediction
Interpretation
AI Platform
Continuity Infrastructure
Customers
Participants
Database
Canonical Store
Users
Operators
Alert
Signal
§ 5.3 — Writing Style
Institutional·Measured·Forensic·Evidence-based
Surfaces differ in register but share the voice. Website: compressed, system-first, gated. Deck: one accent word per headline, evidence below. Social: a single observation, never a thread of hype. API copy: structured labels only, no prose.
§ 5.4 — Copy Standards
Forbidden
Canonical
"Your pet needs urgent care!"
Signals indicate elevated risk
"Our AI detects diseases early!"
Risk score: 72 — Elevated
"Powerful insights for insurers"
Risk classification · premium impact
"Get started today"
Access Platform
Volume 06
Signal Layer Constitution
The condensed constitution of Companion's core document and interpretation engine — the canonical long-form artifact that states the thesis in full.
Pass 1Pass 2Pass 2.5Pass 2.6The artifact
§ 6.1 — The Document, Condensed
Sixteen sections. One argument.
The Signal Layer is the long-form constitution: it defines the ontology, the engine, the architecture, the consumers, and the moat — in that order, without deviation.
Pass
Scope
State
Pass 1
Ontology & thesis — what a signal is
Ratified
Pass 2
Engine, architecture, consumer model
Ratified
Pass 2.5
Experience elevation — atmosphere & depth
Ratified
Pass 2.6
Diagram language → branded V3 figures
Current
§ 6.2 — The Governed Artifact
The Signal Layer is now a first-class BOS artifact, governed alongside this manual.
The Signal LayerLevel 1 · Constitutional
The canonical long-form document. Its figures are issued from the Volume 04.5 Library (FIG 05.01 / 09.01 / 14.01); its language obeys Volume 05; its architecture, ontology and narrative are frozen — only the experience layer evolves, under amendment.
Open the artifact →
Records say what happened. The Signal Layer says what is changing — and reads it before the symptom does.
Signal Layer · core thesis
Volume 07
Fetch API Constitution
The contract through which all intelligence is delivered. What Fetch is, what it is not, and the standards every endpoint and annotation obeys.
What Fetch isWhat it is notEndpoint philosophyAnnotation standards
§ 7.1 — What Fetch Is / Is Not
Fetch is
The single delivery contract
Multi-tenant, partner-ready
One integration, every consumer
Native to the partner's surface
Fetch is not
A platform to replace
A consumer dashboard
A data export
A second source of truth
§ 7.2 — Endpoint Philosophy
The ontology is the API surface.
Endpoints map one-to-one to ontology objects. A consumer does not learn a product; they query the model directly. The contract is stable — endpoints are added, never repurposed.
Canonical endpoints
GET /subjects/{id} GET /signals/{subject_id} GET /replay/{signal_id} GET /cohorts/{cohort_id} // one contract · multi-tenant
§ 7.3 — Annotation & Visual Standards
API surfaces render in the dark instrument palette: near-black ground, sage-tinted mono, structural borders. Verbs in sage, strings in light sage, comments dimmed. Numeric values always Suisse Mono. No prose inside payload examples — labels only.
Volume 08
Governance
How the constitution stays stable while it grows. Freeze events, audits, severity, and the amendment process that governs this document and every artifact under it.
No Level 1 change is valid until it appears in the amendment ledger (Appendix). Constitutional amendments require an explicit freeze of the affected volume during review, and a version increment on ratification. Level 2 changes require review and a changelog entry; Level 3 changes ship freely but inherit all higher-level constraints.
§ 8.3 — The Decision Framework
The constitution for product decisions.
Every future decision — a feature, a surface, a partnership, a deck — must answer five questions. If the answer is no, it is not built.
01
Does it increase continuity?
02
Does it increase trust?
03
Does it increase explainability?
04
Does it increase interoperability?
05
Does it increase institutional clarity?
If the answer is no — don't build it.
§ 8.4 — Freeze Events & Audit Framework
Audit confirms
Vocabulary obeys Volume 05
Figures issued from Volume 04.5
Marks & colour within Volume 02
Voice is institutional, not marketing
Audit fails on
Forbidden vocabulary in any artifact
Ad-hoc figures outside the Library
Recoloured or restretched marks
Level 1 change without amendment
A freeze event locks a volume for the duration of an audit or major revision; nothing downstream may cite the frozen volume's draft state. Freezes are recorded in the ledger alongside the amendment they protect.
Volume 09
Social Media OS
The public expression of the thesis. Content pillars, the asset engine, and the cadence — all Level 3 operational, all inheriting the constitution above.
Content pillarsAsset engineCadencePost structures
§ 9.1 — Content Pillars
Signal Essays
The thesis in long form — one idea, evidenced.
Research Notes
Findings from the validation dataset, stated plainly.
Diagram Series
A canonical figure, unpacked. Drawn from Vol 04.5.
Fetch Series
Developer-facing — the API surface and integrations.
Partner Intelligence
Outcomes and use cases, evidence-led.
Founder Notes
Why the company exists. Measured, never promotional.
Every output begins as research and descends the chain. Nothing is produced sideways — a carousel without a research nucleus is not approved. The diagram step always pulls from the Figure Library; the deck step always uses the Companion × Fetch framework (Vol 03).
§ 9.3 — Cadence & Post Structure
Surface
Cadence
Structure
Signal Essay
Monthly
One claim · evidence · figure
Research Note
Bi-weekly
Finding · method · implication
Diagram post
Weekly
Figure · one-line read
Volume 09.5
Content & Social System
Not just social — the content engine. Every format Companion produces derives from a single framework, so the thesis stays identical from a LinkedIn post to an investor memo.
The nucleusFormat derivationConsistency law
§ 9.5 — The Content Engine
One framework. Every format.
LinkedIn, whitepapers, research notes, signal essays, partner content, conference talks and investor material all derive from one research nucleus. The format changes; the argument does not.
Nucleus
Research
A validated finding or thesis statement. The single source every artifact descends from.
Short form
Social · Notes
LinkedIn, research notes, diagram posts. One claim, one figure, one read.
Long form
Essays · Whitepapers · Decks
Signal essays, partner & conference content, investor memos. The full argument, governed end-to-end.
If two artifacts about the same finding make different arguments, one of them is wrong. The nucleus is the arbiter.
§ 9.5 · Consistency law
Volume 10
Asset Library
The master inventory. Every approved artifact, its governance level, and its state — version-controlled, never duplicated.
DocumentsDecksAPI assetsFigure library
§ 10 — Master Inventory
Level 1 · Constitutional
The Signal Layer
Long-form constitution & interpretation thesis.
Current · Pass 2.6
Level 1 · Constitutional
Motion & Behaviour System
The motion language — 7 families, behaviour states, motion tokens (Vol 03.5).
v1.0 · Active
Level 1 · Constitutional
Intelligence Mesh
The operating fabric — companion-mesh + mesh.css (Vol 02.5).
v1.1 · Active
Level 1 · Constitutional
CH-BOS
This document — the operating system of record.
v1.0 · Ratified
Level 2 · System
Companion × Fetch Deck
Reusable 1920×1080 presentation framework.
Approved
Level 3 · Operational
Happy Pets · Partner · Investor Decks
Instances built from the deck framework.
Per engagement
Level 2 · System
Diagram / Figure Library
FIG 05.01 · 09.01 · 14.01 + the growing canon.
Approved · growing
Level 2 · System
API Assets
Fetch endpoint specs, panels, annotation kit.
Active
Volume 11
Repository Architecture
Where everything lives. A defined structure so artifacts are found, not rediscovered — institutional memory has an address.
Directory mapWhat belongs where
§ 11 — Directory Map
Institutional memory has an address.
companion-health/
├── docs/# this BOS · narrative · specs
├── brand/# logos · colour · type · marks
├── fetch/# API spec · endpoints · annotations
├── signal-layer/# the constitution document + passes
├── diagram-system/# CHDS grammar + figure library
├── governance/# amendments · audits · freezes
├── legal/# trademarks · agreements
├── decks/# framework + built decks
├── social/# content engine outputs
└── research/# the nucleus — findings & data
/docsThe BOS itself, product specs, and narrative source. The first place to look.
/diagram-systemCHDS grammar (Vol 04) and the versioned Figure Library (Vol 04.5). Figures are issued only from here.
/governanceAmendment ledger, audit records, freeze events. The change history of the constitution.
/researchThe content nucleus (Vol 09.5). Every social and long-form artifact traces back to a file here.
/decksThe Companion × Fetch framework plus every built instance. Operational, but governed by the framework.
A file without a home is a decision waiting to be rediscovered. Everything has an address; the address is the memory.
§ 11 · Repository law
Appendix · Amendments & Colophon
The amendment ledger.
A constitution is only stable if its changes are recorded. Every ratified amendment is logged here with its severity and scope.
Version
Date
Severity
Change
v4.0
2026 · 06
Constitutional
Coherence revision — the BOS now reads as one operating system. Added the constitutional system map and the reveal principle (Preamble), the product architecture tree and the Companion Signature (five marks of recognition), Companion Vocabulary (preferred ontology, § 5.2b), Companion States (eight-state lifecycle, § 3.5.5b), diagram proprietary characteristics (§ 4.1), figure metadata (Vol 04.5), and the Decision Framework (§ 8.3).
v3.0
2026 · 06
Constitutional
Added Volume 03.5 — Motion & Behaviour System (MBS): the constitutional motion language — one philosophy (motion reveals intelligence), six motion laws, the seven-family taxonomy (A Arrival – G Transition), motion rhythm, the shared behaviour state machine, Mesh behaviour bounds, documentary motion, the per-screen animation budget, and --motion-* tokens. Demonstrated live via mbs.css + mbs.js.
v2.0
2026 · 06
Constitutional
Added Volume 02.5 — The Intelligence Mesh: the operating-fabric system (64px master / 16px sub lattice, 2% baseline, persistent coordinates, signal propagation) and the brand-locked mesh-gradient system. Shipped as the companion-mesh component + mesh.css. Mesh v1.1 refinement: network → ambient intelligence field — ~80% lonely nodes, straight orthogonal relations, independent weather-model signals, luminance-only breathing, density reduced ~60%.
v1.0
2026 · 06
Constitutional
Ratification of CH-BOS. Consolidation of Identity, Brand, Design, Diagram, Language, Signal Layer, Fetch, Governance, Social and Repository standards into a single governed source of truth.
—
open
Major
Next: expand Figure Library toward the 50-figure canon; admit Dashboard component specimens as they clear audit.
Colophon
Set in Faire Octave (display), Suisse Intl (text & UI) and Suisse Intl Mono (labels, code, clause numbers). Colour, type, spacing and component tokens are imported live from colors_and_type.css — this manual renders from the same source of truth it governs.
Maintained by Companion Health / Animetric. Amendments are proposed, reviewed and ratified under the process defined in Volume 08. This is institutional memory. Keep it current; keep it stable.
