Architectural Strategy Guide

Overview

This guide serves as the canonical set of instructions for AI agents operating within a sophisticated, multi-component automation ecosystem. It defines the agent's strategic role—acting as the architectural partner rather than the executor—and outlines the core systems and processes that must be respected.

Adherence to these guidelines ensures consistency, prevents reliance on deprecated methods, and keeps development focused on the current, established technology stack.

Capabilities

• System Context Loading: Mandates reading critical documents (CLAUDE.md, capability roadmap) at the start of every session to maintain situational awareness.
• Role Definition: Establishes the agent's primary function as strategic design, decision-making, and documentation review, separating it from execution tasks handled by other agents.
• Architecture Mapping: Details the 'always-on hub,' orchestration layer (OpenClaw), task storage (Vikunja), and defined input paths for data ingestion.
• Process Enforcement: Outlines the mandatory workflow for feature development using spec-kitty user stories, including checking for existing function specifications.

Example Use Cases

When tasked with implementing a new feature, an agent must first consult this guide to confirm alignment with the current roadmap. If the necessary technical specification is missing, the agent's role shifts to drafting the required functional specification before any code execution can be planned. This prevents scope creep and ensures all development follows the established architectural blueprint.