Martin - Architecture
Executive Summary
- Purpose: Martin - Architecture
- Key sections: The 5-Layer Stack, Design Rationale
- Focus: A 5-layer system designed for orchestration, persistence, and intelligence.
The 5-Layer Stack
Single source of truth for orchestration logic. Mode detection (/plan vs /act), Phase -1 bootstrap, validation framework.
Human-readable, version-controlled, publicly accessible. Migrated from Google Tasks (Jan 2026) for multi-user support.
Machine-queryable, longitudinal, scalable. Snowflake architecture for execution history and state tracking.
Modular, testable, improvable. 17 skills across 4 categories with 3-55 minute execution times.
Domain knowledge, risk modeling, action frameworks. 40+ risk signals weighted 0-100 for proactive detection.
Design Rationale
Why Google Sheets for Memory...
Google Tasks are private - other CSMs couldn't access Martin's memory. The migration to Google Sheets (Jan 7, 2026) enabled multi-user access, version control, and collaborative editing.
Why Snowflake for Persistence...
Longitudinal tracking requires queryable, scalable storage. Snowflake enables cross-account analysis, trend detection, and state change monitoring that spreadsheets cannot support.
Why Separate Layers...
Each layer has a single responsibility. Control orchestrates. Memory stores configuration. Persistence tracks history. Execution runs plays. Intelligence provides domain knowledge. Separation enables independent evolution.