General Docs Log
Reverse-chronological log of docs/general/ changes. Append new entries at the top.
Format: dated header (24hr ET), bullets per page touched, Source: line tying to the commit/PR/conversation that drove the change.
2026-05-04 13:00 ET
- Decision: Paul accesses
docs/general/(and reads the rest of the vault) via git sparse-checkout ofmg-monorepo, scoped todocs/. No repo split, no submodule. Paul's clone has onlydocs/materialized on disk; rest of the monorepo exists in.gitbut isn't checked out. - Decision: Paul's Claude orientation rules (Paul-scope defaults, edit only
general/, git/PR workflow conventions) live inCLAUDE.local.mdat his clone's repo root — not committed to the monorepo. Keeps engineers' Claude context clean. Aaron sends the content to Paul once; Paul saves it locally. - Source: conversation 2026-05-04 with Aaron — sparse-checkout selected over repo split to preserve the integrated vault philosophy (
/documentskill, spec↔code coupling, ADR commit refs, single source of truth). Setup recipe:git clone --filter=blob:none --no-checkout,git sparse-checkout init --cone,git sparse-checkout set docs,git checkout main.
2026-05-04 12:00 ET
- Created: [[README]] — index, conventions, source-material list
- Created: [[company]] — what MG is, operating thesis, mission, displacement positioning anchor, what we sell, where we operate
- Created: [[pillars]] — three operating pillars (Development · Studios · SESHN) + The Platform shared services, derived from Holdings Org Model v2.2
- Created: [[people]] — leadership (Paul, Aaron) + decision authority + working norms; placeholders for remaining team roster
- Created: [[business-model]] — revenue lines (monthly · hourly · SESHN) + platform fees + cost structure + unit-econ framing
- Created: [[real-estate]] — full 11-building portfolio + rent roll + entity structure + leased→owned migration posture
- Created: [[strategy]] — 500→5,000 thesis, migration playbook, MG11 + Irvington, Q2 2026 roadmap themes, 12-month direction
- Created: [[stack]] — vendor stack at company level, criticality classification (critical vs. operational tier)
- Created: [[glossary]] — company-, org-, capital-, RE-level vocabulary
- Source: initial scaffold of the
docs/general/subtree, drafted from the Metrognome Holdings Organizational Model v2.2, the OnPoint Portfolio Executive Summary, the CTO Job Description V0.3, the Tech Vendors doc, the Membership Agreement v3, the Metrognome.com Product Roadmap Meeting 1, and existingdocs/marketing/. Scope: agent-first dense factual style, coequal subtree tobusiness/andmarketing/, displacement-thesis as the origin anchor, named team roster, capital posture deferred to CEO.