Manage provenance-tracked Claude-Desktop-to-Claude-Code research workflows across the three-actor model (Brain, Executor, PI): create journal entries, decisions, missions, evidence clusters, and maintain a research knowledge graph with automatic provenance linking. Includes commands for maintenance, search, and project configuration.
Show RKA pending maintenance: provenance gaps, untagged entries, decisions missing justified_by links, missions missing motivated_by_decision, unassigned clusters, etc.
Search the RKA knowledge base. Pass 2-4 keyword terms (longer queries return empty). Searches journal entries, decisions, literature, missions, claims, and clusters by default.
Switch the active RKA project for this session. Pass the project id (e.g. prj_01ABC...). Without an argument, lists available projects so the user can pick.
Configure Claude Desktop's MCP server entry to use the RKA wrapper. Cross-platform (macOS / Windows / Linux). Atomic with backup; conflict-detects existing entries.
Show RKA project status: active project, phase, current focus, open checkpoints, and recent maintenance items.
Strategic AI for RKA-managed research projects. Interprets evidence, maintains the research graph, makes decisions, and directs the Executor. Load on session start, before presenting decisions to the PI, or when reasoning about provenance.
Implementation AI for RKA-managed research projects. Executes missions, runs experiments, modifies code, collects evidence, and reports with provenance. Load on mission pickup or when producing a Backbrief / report.
PI quick reference for RKA-managed research projects. Resolves checkpoints, sets direction, preserves original intent. Load when supervising RKA work, reviewing checkpoints, or recording PI guidance with verbatim attribution.
Admin access level
Server config contains admin-level keywords
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Persistent research memory for AI-assisted investigations.
RKA gives your research project a brain that doesn't forget between sessions. It stores every finding, decision, hypothesis, and literature reference in a structured knowledge base with full provenance chains. The Brain (Claude) handles all knowledge enrichment — no local LLM required.

(A) Three roles — Researcher (frames and ratifies), Brain (Claude Desktop, synthesizes literature and proposes structured options), Executor (Claude Code, implements bounded missions) — share a typed, provenance-aware knowledge base. Four control properties anchor the architecture: traceability, reversibility, visible disagreement, human-ratified commitment. (B) One operational cycle: the Researcher frames a goal; the Brain restates intent (Confirmation Brief), retrieves context, and proposes structured options; the Researcher ratifies a decision; a mission is dispatched to the Executor; the Executor implements and reports back; the Brain integrates results and opens the next decision cycle.
Month 1 Month 3 Month 6
┌──────────┐ ┌──────────┐ ┌──────────┐
│ "We found │ │ "Based on │ │ "We can │
│ that..." │ │ 3 months │ │ trace │
│ │ ┌─────┐ │ of evi- │ ┌─────┐ │ every │
│ (lost │──▶│ RKA │──▶│ dence..."│──▶│ RKA │──▶│ decision │
│ next │ └─────┘ │ │ └─────┘ │ back to │
│ session) │ │ (all here)│ │ its why" │
└──────────┘ └──────────┘ └──────────┘
Without RKA With RKA With RKA v2
Findings vanish Everything persists Knowledge self-organizes
Built for CS/IoT/CPS security research at UNC Charlotte.
A working draft describing RKA's architecture, design principles, and evaluation is available as a PDF: RKA-paper.pdf — Framing Is Human: Researcher–Brain–Executor Architecture for AI-Assisted Research.
The figure above is Figure 1 of the draft; it provides a one-glance overview of the architecture (panel A) and one operational decision cycle (panel B). The rest of this README is the practical, hands-on companion: setup, CLI, MCP tools, REST API, and the web dashboard. For the conceptual argument and evaluation, read the draft.
Three actors collaborate through a shared knowledge base:
graph LR
PI["🧑🔬 PI<br/><i>Human researcher</i>"]
Brain["🧠 Brain<br/><i>Claude Desktop</i>"]
Executor["⚡ Executor<br/><i>Claude Code</i>"]
RKA["📚 RKA<br/><i>Shared knowledge base</i>"]
PI -->|supervises| Brain
PI -->|supervises| Executor
Brain -->|"strategy, decisions"| RKA
Executor -->|"findings, reports"| RKA
RKA -->|"context, evidence"| Brain
RKA -->|"missions, guidance"| Executor
style RKA fill:#E1F5EE,stroke:#0F6E56,color:#04342C
style Brain fill:#EEEDFE,stroke:#534AB7,color:#26215C
style Executor fill:#E6F1FB,stroke:#185FA5,color:#042C53
style PI fill:#F1EFE8,stroke:#5F5E5A,color:#2C2C2A
Raw observations don't stay raw. The Brain distills journal entries into structured knowledge during maintenance sessions:
graph TD
Entry["📝 Journal entries<br/><i>note · log · directive</i>"]
Claims["🔍 Claims<br/><i>hypothesis · evidence · method<br/>result · observation · assumption</i>"]
Clusters["🗂️ Evidence clusters<br/><i>Grouped claims with<br/>Brain-written synthesis</i>"]
Map["🗺️ Research map<br/><i>Research questions →<br/>clusters → claims</i>"]
Entry -->|"Brain extracts"| Claims
Claims -->|"Brain clusters"| Clusters
Clusters -->|"Brain synthesizes"| Map
style Entry fill:#E6F1FB,stroke:#185FA5,color:#042C53
style Claims fill:#EEEDFE,stroke:#534AB7,color:#26215C
style Clusters fill:#FAEEDA,stroke:#854F0B,color:#412402
style Map fill:#E1F5EE,stroke:#0F6E56,color:#04342C
npx claudepluginhub infinitywings/rka --plugin rkaHarness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.