Operational Intelligence Framework
The Pivotal Protocol

Keel

Four verification layers. Zero tolerance for protocol drift. Every protocol. Every cycle.

4 Verification Layers
7 Corroborated Sources
0 Defects Permitted
∞ Monitoring Cycles

"Every protocol decision is traceable to evidence.
Every reconstitution is verified to the unit.
Every cycle is monitored until the endpoint is documented.
Nothing ships below the floor."

Keel Framework. Core Doctrine.

Architecture

The four layers
of Keel

Four layers. Each gates the next. No protocol closes until the endpoint is confirmed.

Layer 01
Knowledge
Evidence Layer

Every protocol decision traces to a minimum of seven corroborated sources. No claim enters a protocol without a source binding. Inferred and verified claims are labeled distinctly.

  • Peer-reviewed pharmacology sourcing
  • Interaction database cross-reference
  • Biomarker threshold validation
  • Claim/evidence binding per field
Layer 02
Engineering
Precision Layer

Reconstitution math verified to the unit. Syringe selection locked by body weight and target concentration. Every calculation audited before the protocol is written.

  • Reconstitution engineering per compound
  • Concentration and dose calculation
  • Syringe type and injection volume lock
  • Backfill methodology where indicated
Layer 03
Execution
Monitoring Layer

Longitudinal monitoring from first injection through documented endpoint. Lab panels interpreted in protocol context. Every deviation flagged, logged, and acted on within one business day.

  • Cycle-by-cycle response tracking
  • Biomarker interpretation in context
  • Deviation detection and response
  • Documented endpoint confirmation
Layer 04
Learning
Refinement Layer

Each completed cycle refines the next. Response data, lab trends, and client-reported outcomes feed back into protocol architecture. No cycle ends without a written retrospective.

  • Post-cycle retrospective analysis
  • Protocol version history
  • Cross-cycle trend identification
  • Iterative protocol refinement

Quality Architecture

The verification
stack

Six gates. Each is a hard requirement. None can be bypassed.

01
Content Forensic Pass
Every clinical field traced to its source. Inferred data labeled. No unverified field in any deliverable.
Required
02
Visual Page-by-Page Audit
Rendered PDF reviewed visually. Source grep is insufficient. Every cell, every label, every number confirmed in the rendered output.
Required
03
Cross-Document Consistency
All documents in a client package reconcile with each other. No data appears in two places with two different values.
Required
04
Retrospective Gate
Prior cycle outcomes reviewed before next protocol is written. No protocol starts without incorporating prior response data.
Required
05
Source Backtrace
Every evidence citation verified to original source. No circular reference. No secondary citation presented as primary.
Required
06
Field Manifest Verification
Cell-by-cell manifest written before any deliverable is produced. Source tag per field. Zero scaffold survivors permitted.
Gate

Operating Standard

Zero defects.
Every cycle.

One unverified field is a failure. One missed interaction is a failure. Nothing proceeds until the gate passes.

100%
Field Traceability
Every data field in every protocol carries a verified source tag.
0
Permitted Bypasses
No verification gate may be skipped, deferred, or waived.
<1d
Response Time
Every flagged deviation receives a documented response within one business day.
7+
Sources per Claim
Minimum corroborating sources for every clinical claim that enters a protocol.

Client Experience

How Keel
applies to your cycle

It operates behind every document and decision. This is what it looks like from the client side.

01
Intake and Knowledge Assembly

History, goals, compounds, and labs assembled into a source-tagged knowledge file. Every field labeled: verified, reported, or inferred.

Layer 01: Knowledge
02
Protocol Architecture and Interaction Screening

Compounds, dosing, and sequencing designed against your data. Interaction screening fires before the first decision. Reconstitution math written in exact units.

Layer 02: Engineering
03
Verification Pass and Delivery

Six gates before delivery. Visual audit, cross-document consistency, source backtrace. Not released until all six pass.

Verification Stack
04
Longitudinal Monitoring and Endpoint Tracking

Monitored from first injection through documented endpoint. Deviations flagged and acted on, not logged and ignored.

Layer 03: Execution
05
Retrospective and Next Cycle Refinement

Cycle close: written retrospective. What worked, what changed, what next. The next cycle begins with that loaded. Nothing resets.

Layer 04: Learning

Evidence

What Keel
does not permit

The framework is defined as much by its prohibitions as its processes. These are not aspirational standards. They are hard gates.

Prohibited
"Sensible defaults" for unspecified fields
Every field is specified or flagged. No assumed values.
Prohibited
Template reuse without per-field overwrite verification
Prior client data cannot survive into a new protocol unchecked.
Prohibited
Declaring a protocol "complete" without a rendered visual audit
Source code grep is insufficient. The rendered document is reviewed.
Prohibited
Interaction screening performed after protocol design
Screening precedes compound selection, not follows it.
Prohibited
Monitoring that stops when the cycle ends
The endpoint is documented. The monitoring runs until it is.
Prohibited
Any clinical claim without a traceable source
Verified and inferred claims are labeled. No unlabeled claims exist.
Keel Against the Market

What the standard looks like
when you hold it next to everything else.

Competitive data sourced from published pricing pages, public service descriptions, and third-party reviewer analysis. Assessed May 2026.

Dimension
The Pivotal Protocol
Keel-Powered
The Protocole
Est. 2025
Defy Medical
Est. 2013
1st Optimal
Membership
Named, proprietary intelligence framework with published architecture Keel None None None
Minimum sourcing standard per clinical claim (documented) 7 sources Unspecified Unspecified Unspecified
Formal interaction screening gate before protocol is written ✓ Not documented Mentioned Not documented
Stage-close verification: stage does not close without a verifiable result ✓ None None None
Reconstitution engineering: BAC volume, backfill ratio, syringe math, vial yield ✓ Not published Not published Not published
Zero compounds sold: pure protocol design, no compound revenue ✓ Sells compounds Sells compounds Sells compounds
Clinical-grade protocol PDF: dose table, reconstitution doc, interaction notes, washout plan ✓ Protocol only Protocol only Protocol only
Tiered quality standard with third-party analytical testing reference ✓ Purity claim only Purity claim only Not specified
Longitudinal outcome data published (aggregate, anonymized) ✓ Testimonials only Not published Testimonials only
Zero-trust client portal (no third-party CRM access, Cloudflare-walled) ✓ Standard portal Standard portal Standard portal

Competitor data sourced from public-facing service pages and independent review analysis. The Pivotal Protocol claims reflect documented operational policy under the Keel framework. Not a legal comparison. Individual results vary.

Ready for a protocol
that operates at this level?

Intake takes under five minutes. Every response is reviewed by a person. Reply within one business day.

Begin Intake  → What We Are