Skip to content

General

Company-level knowledge that doesn't fit in product rules, marketing, ops, or code. Origin, structure, people, capital, footprint, strategy. Reusable context for onboarding agents and humans.

This subtree is agent-first — dense, factual, link-heavy. New humans can read top-to-bottom but the priority is greppability for AI context loading.

Authority

Reference. Coequal subtree to business/, marketing/, ops/. When a fact here also lives in code or a more specific doc, the more-specific doc wins. When a fact here is the source (e.g. legal entity structure, team roster), this is canonical.

Pages

  • company.md — what Metrognome is, the operating thesis, mission, brand
  • pillars.md — the three operating pillars (Development · Studios · SESHN) + The Platform shared services
  • people.md — team roster, roles, decision authority
  • business-model.md — how money flows: real estate yield + monthly + hourly + SESHN + platform fees
  • real-estate.md — buildings, rent roll, legal entity structure, ownership posture
  • strategy.md — multi-year direction, geographic expansion, owned-vs-leased migration
  • stack.md — vendor stack at company level, criticality classification
  • glossary.md — company-level vocabulary (pillar names, entity acronyms, QOZF, etc.)
  • log.md — dated edits
Looking for Read
Product rules per domain (lockouts, payments, etc.) docs/business/
Brand voice, ICP, positioning, KPIs docs/marketing/
Staff procedures + how-tos docs/ops/
Code, architecture, infrastructure docs/engineering/
In-flight feature design intent docs/features/
Architectural decision history docs/decisions/
Customer help docs/help/

Conventions

  • Frontmatter: every page has title, last_updated, owner, applies_to, status, sources.
  • No code refs. Like business/, this subtree never references file paths, function names, or DB tables. Code/architecture knowledge belongs in engineering/.
  • No operational how-tos. Procedures belong in ops/. This is context, not instructions.
  • Cross-link, don't duplicate. When this overlaps with marketing/icp.md or business/<domain>/ or decisions/<n>-*.md, link out.
  • Numbers belong here when they're company-level, current-state, and not derivable from code. Portfolio metrics, headcount, vendor stack, etc.
  • Update log.md on every substantive edit.

Source material

Initial drafts (May 2026) drew from:

  • docs/marketing/positioning.md — displacement thesis as the why-anchor
  • docs/marketing/icp.md — customer archetype context
  • CTO Job Description V0.3 (Mar 2026) — role + responsibilities + comp
  • Metrognome Holdings Organizational Model v2.2 (April 2026) — three-pillar structure
  • Metrognome Portfolio Executive Summary, OnPoint (April 2026) — rent roll, NOI, entity structure
  • Metrognome Tech Vendors doc — stack
  • Metrognome Membership Agreement v3 + Terms of Service v1 — customer terms
  • Metrognome.com Product Roadmap Meeting 1 (Mar 2026)

Subsequent edits should keep sources frontmatter current and append to log.md.