Skip to content

knowledge-load

Deprecated

This command is deprecated. All rp1 commands are now self-contained and load KB context automatically via their agents. You no longer need to run /knowledge-load before using other commands.

For agent developers: Use direct Read tool calls to load KB files progressively. See the Knowledge-Aware Agents concept page.

Loads and prepares knowledge base context for downstream agents.

Synopsis

/knowledge-load

/rp1-base/knowledge-load

Description

The knowledge-load command ingests the knowledge base from .rp1/context/ and prepares it for use by other agents. It builds an internal knowledge graph, extracts entities and relationships, and optimizes the context for memory constraints.

This command is typically called internally by other KB-aware agents, but can be invoked directly to verify the KB is loadable.

Parameters

Parameter Default Description
mode progressive Loading mode: progressive (index.md only) or full (all files)
RP1_ROOT .rp1/ Root directory for KB artifacts
PROJECT_PATH . Project path (for monorepo subprojects)
FOCUS_MODE balanced Context allocation strategy
MEMORY_BUDGET Auto Memory limit for loaded context

Loading Modes

Mode Files Loaded Use Case
progressive index.md only Default; agents load more on-demand
full All KB files Legacy; holistic analysis

Focus Modes

Mode Allocation Use Case
project 80% project / 20% system Feature development
system 50% project / 50% system Architecture analysis
balanced 60% project / 40% system General use

Loading Strategy

The command adapts its loading strategy based on repository type:

Single Project: - Loads: index.md, concept_map.md, architecture.md, modules.md, patterns.md

Monorepo Root: - Loads: index.md, architecture.md, dependencies.md, patterns.md - Optional: Project summaries

Monorepo Subproject: - Loads: dependencies.md, patterns.md, projects/{name}/*.md - Context: System architecture and shared components

Examples

Basic Usage

/knowledge-load

/rp1-base/knowledge-load

Expected output (single project): 

READY

Expected output (monorepo): 

READY [monorepo: 2 projects - rp1-base, rp1-dev]

Error Response

If the KB doesn't exist or is corrupted:

ERROR: Required documentation files not found. Run /knowledge-build first.

Output

The command returns a status with deprecation warning:

Progressive Mode (Default): 

⚠️ DEPRECATION WARNING: This command is deprecated. Commands now load KB automatically.

READY [progressive]

Loaded: index.md (~80 lines)
Available: architecture.md, modules.md, patterns.md, concept_map.md
Use Read tool to load additional files as needed.

Full Mode: 

⚠️ DEPRECATION WARNING: This command is deprecated. Commands now load KB automatically.

READY [full: 5 files, ~1180 lines]

Response Meaning
READY [progressive] Progressive mode, index.md loaded
READY [full: N files] Full mode, all KB files loaded
READY [progressive, system: N projects] Monorepo root, progressive
READY [progressive, project: name] Monorepo subproject, progressive
ERROR: message Loading failed with reason

Memory Budget Management

If the KB exceeds memory budget, compression is applied in this order:

  1. Remove tertiary project details (keep interfaces only)
  2. Compress unused shared code
  3. Summarize verbose descriptions
  4. Remove historical information
  5. Compress target project details (last resort)

Instead of using this deprecated command, agents should load KB files directly:

## 1. Load Knowledge Base

Read `{RP1_ROOT}/context/index.md` to understand project structure.

Based on your task, selectively load additional files:
- Code review → Read `{RP1_ROOT}/context/patterns.md`
- Bug investigation → Read `{RP1_ROOT}/context/architecture.md` + `modules.md`
- Feature work → Read `{RP1_ROOT}/context/modules.md` + `patterns.md`

See the Knowledge-Aware Agents concept page for more on progressive loading patterns.

See Also