Skip to content

Introduced by a trusted connector?

Start Here

Anthony Veltri

  • Doctrine
    • Doctrine Library
    • Global Library
  • Field Notes
  • Routes
    • Route 01: When the Interface Is Breaking (and you are becoming the patch)
    • ROUTE 02: If decisions stall and meetings go nowhere, start here
    • ROUTE 03: If you have lots of projects but no portfolio clarity, start here
    • ROUTE 04: If you’re confused about federation vs integration, start here
    • ROUTE 05: If heroics are propping up your system, start here
    • ROUTE 06: If you cannot force compliance across partners, start here
    • ROUTE 07: If compliance exists but commitment does not, start here
    • ROUTE 08: If disconnected workflows create audit anxiety, start here
  • Figure Library
  • FAQ
  • About
    • Capability Statement
    • Interpreter Kit
  • Contact
Anthony Veltri

Architecture & Interfaces

15
  • Doctrine 01: Federation vs Integration in Mission Networks
  • Doctrine 03: Interfaces Are Where Systems Break, So They Require Stewards, Contracts, and Ownership
  • Doctrine 04: Useful Interoperability Is the Goal, Not Perfect Interoperability
  • Doctrine 05: Innovation Must Live at the Edge, Not in the Center
  • Doctrine 06: A Two-Lane System Protects Stability and Enables Evolution
  • Doctrine 14: Technical Debt Is a Leadership Signal, Not a Coding Failure
  • Doctrine 15: Architecture Must Accelerate Teams, Not Bottleneck Them
  • Doctrine 17: Architects Translate Strategy Into Engineering and Engineering Into Strategy
  • Doctrine 20: Golden Datasets: Putting Truth In One Place Without Pretending Everything Is Perfect
  • Doctrine 21: Zero Trust Is A Trust Model, Not A Card “Type”
  • Doctrine 23: Loop Closure as Load-Bearing System Infrastructure
  • ANNEX B. Data Contracts
  • ANNEX C. Interface Ownership Model
  • ANNEX H. Architecture Doctrine
  • Annex L: The Rosetta Stone for Data Teams: Bridging the Gap Between Technicians and Executives

Decision Tempo & Governance

10
  • Doctrine 02: Distributed Decisions Increase Alignment, Speed, and Resilience
  • Doctrine 07: Clear Intent Matters More Than Perfect Data
  • Doctrine 08: Clear Intent Compresses Ambiguity, Reduces Conflict, and Accelerates Action
  • Doctrine 09: Decision Drag Is the Enemy of Mission Tempo. Architecture Is the Remedy
  • Doctrine 10: Degraded Operations Are the Normal Mode, Not the Exception
  • Doctrine 11: Preventive Action and Contingent Action Must Both Be Designed Intentionally
  • Doctrine 22: When “It Depends” Is the Right Answer: How to Think in Probabilities Under Uncertainty
  • ANNEX D. Decision Altitudes Model
  • ANNEX E. Prevention–Contingency Matrix
  • ANNEX I. High Visibility Workflows

Portfolio & Alignment

4
  • Doctrine 16: Portfolio Thinking Ensures Effort Aligns With What Actually Matters
  • ANNEX F. Pattern Library
  • ANNEX J. System Evolution and Drift Management
  • ANNEX K. System and Workflow Profiles (Case Studies)

Leadership & Human Systems

6
  • Doctrine 24: Stewardship Places the Burden on the Steward, Not the Parties
  • Doctrine 18: Commitment Outperforms Compliance in High Trust, High Tempo Environments
  • Doctrine 19: Supervision, Management, and Leadership Are Three Different Jobs. Confusing Them Breaks Systems
  • Doctrine 23: Loop Closure as Load-Bearing System Infrastructure
  • ANNEX A. Human Contracts
  • ANNEX G. Leadership Doctrine

Resilience & Operations

3
  • Doctrine 24: Stewardship Places the Burden on the Steward, Not the Parties
  • Doctrine 12: Resilience Is an Emergent Property, Not a Feature
  • Doctrine 13: Problem Solving Requires Finding the Real Deviation and the Relevant Change

Doctrine Companions

7
  • Doctrine 03 Companion: The RS-CAT Framework: Converting Raw Recall into Teachable Principle
  • Doctrine 03 Companion: The Interface Void
  • Doctrine 11 Companion: Agency vs. Outcome
  • Doctrine 09 Companion: Artifacts Over Adjectives
  • Doctrine 03 Companion: Constraints: bidirectional translation: Compression vs Construction
  • Doctrine 10 Companion: Span of Control and Cross Training Are Load-Bearing Constraints
  • Doctrine 21 Companion: Claims, Roles, and Entitlements in Microsoft 365

Field Reports

1
  • Field Report: College Financing and the 5-Year Home Runway
View Categories
  • Home
  • Doctrine & Supporting Guides
  • Doctrine Companions
  • Doctrine 03 Companion: The RS-CAT Framework: Converting Raw Recall into Teachable Principle

Doctrine 03 Companion: The RS-CAT Framework: Converting Raw Recall into Teachable Principle

Anthony Veltri
Updated on January 10, 2026

4 min read

Doctrine Claim: Knowledge transfer in mission-critical environments is a process of signal extraction, not information dumping. The RS-CAT Framework is the specific methodology used to bypass the “Expert Blind Spot,” the psychological reality where a practitioner cannot see the architecture of their own expertise while operating inside it. By re-indexing unstructured event data into pedagogical logic, we transform tacit operational knowledge into explicit, transferable doctrine.

The RS-CAT Framework is the technical process of converting raw, lived experience into a durable substrate of knowledge. It is the specific methodology used to bypass the “Expert Blind Spot.” This is the psychological reality where a practitioner cannot see the architecture of their own expertise because they are too busy using it to survive the mission.

The pipeline converts Raw Recall (which is often chaotic and trapped in operational logic) into Usable Patterns (which are pedagogical and portable). The framework consists of the following steps: Retrieval, Sewuencing, Compression, Abstraction, and finally Teachability/Transfer. We abbreviate it as RS-CAT.

This diagram illustrates the RS-CAT pipeline, outlining five stages that refine raw recall into a portable, teachable pattern.
This diagram illustrates the RS-CAT pipeline, outlining five stages that refine raw recall into a portable, teachable pattern.

The Problem: The Expert Blind Spot #

True expertise often feels like intuition, but it is actually a high-resolution mental model operating at high tempo. This creates a barrier for the “Next Guy”:

  • The Jar Principle: As the saying goes, “You cannot read the label from inside the jar.” An expert is too focused on the mission to objectively analyze the structure of their own capability.
  • Legacy Schema Debt: Without a formal process to extract the why and the how, we leave behind “Compressed” results without the “Construction” logic, forcing successors to guess at our reasoning.
This diagram illustrates how cognitive architecture limits may prevent experts from recognizing their own knowledge gaps.
Writing, outlining, and re-sequencing provide the external framing.

RS-CAT Pipeline: Canonical Definitions #

R: Retrieval: Extracting the Signal #

Retrieval is the act of pulling a memory forward through the use of specific prompts, cues, and constraints. It is not an exhaustive history. Instead, it is a surgical extraction of the pieces that matter for a specific teaching objective. The goal is to distinguish between Operational Detail (the context you needed to survive the event) and Transferable Principle (the pattern the learner needs to absorb).

S: Sequencing: The Logic of the Learner #

Sequencing is the process of reordering information to match Pedagogical Logic (how humans learn) rather than Operational Logic (the chronological order of how it happened). An expert experienced the event linearly, but a learner needs the pattern structured as: Context, Friction, Choice, Consequence, and Takeaway. This re-indexing is what allows the knowledge to move from “My Story” to “A System.”

C: Compression: Optimizing the Signal-to-Noise Ratio #

Compression identifies the Minimum Viable Detail required to preserve the authenticity of the event without overwhelming the learner’s working memory. Experts often include “contextual noise” because they remember every detail as being vital at the time. Compression serves as a form of cognitive offloading for the recipient. It ensures that the “pixels” of the story do not obscure the “dragon” of the pattern.

A: Abstraction: The Balance of Texture #

Abstraction extracts the underlying rule while maintaining enough texture to make it believable and applicable. This stage is the balance point. If the information is too abstract, it becomes “Consultant-speak” (disconnected from reality). If it is too concrete, it remains an “Anecdote” (trapped in a single context). A successful abstraction is a portable model grounded in real consequence.

T: Teachability: Ensuring Portability #

Teachability is the final conversion of the expertise into a format that someone else can apply in their own domain. This involves identifying the Dynamic Variables (things that can change, such as scale or resources) and the Fixed Pattern (the logic that holds true regardless of the environment). This is the stage where the information officially becomes Doctrine.

3. Abstraction vs. Construction #

While deeply related, these two moves happen in opposite directions:

  • Abstraction (Subtractive): The RS-CAT move. Stripping context to isolate the rule.
  • Construction (Additive): The Pedagogical move. Building the mental scaffold (the checklist, the figure, the label) so a learner can carry the rule.

The Mission Architect’s Path: We compress reality to find the signal (Extraction), abstract the rule, and then construct the teachable model. This ensures the doctrine is grounded in the Durable Substrate of real world results.

This diagram illustrates how extraction and delivery logic guide data from raw event to audience, with key processing steps influencing outcomes.
This diagram illustrates how extraction and delivery logic guide data from raw event to audience, with key processing steps influencing outcomes.

4. Doctrine Diagnostic: The Signal Check #

PhasePurposeFailure Mode
RetrievalIsolate SignalData Dump/Noise
SequencingLearner LogicChronological “Story”
CompressionCognitive OffloadingWorking Memory Overload
AbstractionRule DiscoveryTrapped in Anecdote
TeachabilityDomain Portability“Consultant-speak”

This diagram contrasts legacy schemas with operational realities, suggesting potential costs of outdated frameworks in new contexts.
An architectural snapshot of knowledge debt: The successor inherits the compressed result without the construction logic, creating a system that collapses upon contact with current terrain.

Field notes and examples #

  • Regime Recognition and the Cost of Asymmetric Errors: When Post-Hoc Learning Beats Theory-First
  • The Loudest Listener: When Interviews Become Something Else
  • Field Note: Guided Sensemaking Interview
  • Field Notes: Why Facts Don’t Change Minds: Motivation And Story Frameworks For Leaders

Last Updated on January 10, 2026

Related Posts #

This diagram illustrates how guided sensemaking transforms handwritten ideas into organized digital files through structured processes.

Field Note: Guided Sensemaking Interview #

This slide illustrates the distinction between Construction and Compression, as presented in Doctrine Companion, using a geometric theme.

Doctrine 03 Companion: Constraints: bidirectional translation: Compression vs Construction #

This slide illustrates the relationships among claims, roles, and entitlements in Microsoft 365, as presented in Doctrine 21.

Doctrine 21 Companion: Claims, Roles, and Entitlements in Microsoft 365 #

A diagram shows a translucent seated person labeled

Field Note: Sorting the 20-Year Backpack #

Thinking in Probabilities featured title card

Doctrine 22: When "It Depends" Is the Right Answer: How to Think in Probabilities Under Uncertainty #

This diagram illustrates increasing salary capacities, with larger houses on higher blocks representing $6k, $24k (median), and $80k per year.

Field Report: College Financing and the 5-Year Home Runway #

Related Docs

  • Doctrine 03: Interfaces Are Where Systems Break, So They Require Stewards, Contracts, and Ownership
  • Doctrine 03 Companion: Constraints: bidirectional translation: Compression vs Construction
  • Doctrine 03 Companion: The RS-CAT Framework: Converting Raw Recall into Teachable Principle
  • Doctrine 03 Companion: The Interface Void

Leave a Reply Cancel reply

You must be logged in to post a comment.

Table of Contents
  • The Problem: The Expert Blind Spot
  • RS-CAT Pipeline: Canonical Definitions
    • R: Retrieval: Extracting the Signal
    • S: Sequencing: The Logic of the Learner
    • C: Compression: Optimizing the Signal-to-Noise Ratio
    • A: Abstraction: The Balance of Texture
    • T: Teachability: Ensuring Portability
    • 3. Abstraction vs. Construction
    • 4. Doctrine Diagnostic: The Signal Check

Share This Article :

  • Facebook
  • X
  • LinkedIn
  • Pinterest

Was it helpful ?

  • Happy
  • Normal
  • Sad
  • Privacy Policy
  • Introductions
  • Contact

© 2026 Anthony Veltri

  • Doctrine
    • Doctrine Library
    • Global Library
  • Field Notes
  • Routes
    • Route 01: When the Interface Is Breaking (and you are becoming the patch)
    • ROUTE 02: If decisions stall and meetings go nowhere, start here
    • ROUTE 03: If you have lots of projects but no portfolio clarity, start here
    • ROUTE 04: If you’re confused about federation vs integration, start here
    • ROUTE 05: If heroics are propping up your system, start here
    • ROUTE 06: If you cannot force compliance across partners, start here
    • ROUTE 07: If compliance exists but commitment does not, start here
    • ROUTE 08: If disconnected workflows create audit anxiety, start here
  • Figure Library
  • FAQ
  • About
    • Capability Statement
    • Interpreter Kit
  • Contact