Martin - Overview

I built Martin to execute work, not to define it. It explicitly performs actions based on established rules and inputs, without making strategic decisions. It serves as the bridge between intent and outcome.

Why this matters: This project represents my bias toward execution systems that remove judgment from repeatable work.

Overview Origin System Plays Innovations Metrics Standards Roadmap

Executive Summary

Purpose: Martin - Overview
Key sections: What Martin Does, What Martin Does Not Do, How This Folder Structure Works Together
Focus: Martin: Personal Operating System Overview

Key Exhibits

Origin: why the system was needed and what changed operationally
Innovations: version progression from prototype to production
Plays: capability layer and workflow taxonomy
Metrics: how effectiveness is measured over time
Standards: constraints that keep outputs reliable

This project is best understood in sequence: Origin, System, Plays, Innovations, Metrics, Standards. Each section builds on the last.

Version History

v3.0Feb 2026Dual-mode architecture (/plan + /act), Snowflake persistence, operator profiles, skills registry
v2.0Jan 2026Google Sheets memory core, portfolio cache, 8 single-account plays validated
v1.8Dec 2025Multi-user architecture, dual logging, smart load experience
v1.5Nov 2025Enterprise Account Framework, contact verification, zero-hallucination guarantees
v1.0Oct 2025Initial system - 5 plays, Google Tasks memory, single-user

What Martin Does

Executes predefined plays
Applies system-level protocols
Enforces standards and validation
Orchestrates multi-step workflows
Produces outputs and captures learning

What Martin Does Not Do

Does not invent strategy
Does not define plays
Does not override system rules
Does not act autonomously

How This Folder Structure Works Together

/system defines execution. /standards defines quality. /plays defines actions. /metrics measures outcomes.

Why Execution Is Separated From Judgment

Separating intent from execution keeps the system reliable and repeatable.

A narrow role prevents scope creep and keeps the tool focused.