architecture

Explain Reeve's runtime architecture covering daemon, Hapi, MCP servers, and pulse lifecycle.

Updated Jan 24, 2026

Search Tags:#architecture #debugging #onboarding #mcp #pulse #daemon #hapi

Ready to run

npx skills add https://github.com/reubenjohn/reeve-desk --skill architecture-reubenjohn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/reubenjohn/reeve-desk/tree/main/.claude/skills/architecture
Command: npx skills add https://github.com/reubenjohn/reeve-desk --skill architecture-reubenjohn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reeve's runtime architecture documentation helps engineers understand how the system is constructed and why it behaves as it does, aiding debugging and onboarding.

Core Features & Use Cases

Architecture overview of the daemon, Hapi, MCP servers, and pulse lifecycle.
Troubleshooting guidance for stack-related issues in production and development.
Use Case: onboarding new engineers by walking through the runtime stack from startup to pulse processing.

Quick Start

Ask Reeve to walk you through the full runtime stack from daemon to MCP servers.

Frequently Asked Questions about architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How does the Reeve daemon runtime architecture work?▼

The Reeve runtime architecture operates through a daemon that manages the Hapi executor, MCP servers, and pulse lifecycle to process system events from startup through execution.

What is the pulse lifecycle in Reeve's runtime stack?▼

The pulse lifecycle defines how Reeve processes operational events chronologically, moving from daemon initialization through Hapi execution and MCP server interactions during runtime.

Can I use Reeve's architecture documentation for onboarding new engineers?▼

Reeve's architecture documentation supports onboarding by walking new engineers through the complete runtime stack, explaining the daemon, Hapi executor, MCP server roles, and pulse lifecycle with concrete context references.

How do I debug production issues in Reeve's Hapi and MCP server stack?▼

Debugging Reeve's runtime stack involves tracing the pulse lifecycle across the daemon and Hapi executor to identify where MCP server interactions fail, using architecture documentation to isolate stack-related production issues.

What are the core components of Reeve's runtime architecture?▼

Reeve's runtime architecture consists of the daemon for process management, the Hapi executor for task execution, MCP servers for protocol handling, and the pulse lifecycle for event processing flow.

How do I walk through Reeve's runtime stack from startup to pulse processing?▼

To walk through Reeve's runtime stack, start at the daemon initialization, trace through Hapi executor setup, observe MCP server connections, and follow the pulse lifecycle to understand the complete processing flow.