ACME — a complete CorpoSpec example

Manifest .corpospec/manifest.yaml

Declares company_id, corpospec_version, and the pillars this repo populates.

# yaml-language-server: $schema=https://corpospec.com/schemas/v0.7.1/manifest.schema.json
corpospec_version: "0.1.1"
company_id: "acme-corp"
created: "2025-06-15"
schema_version: "0.1.1"
pillars:
  - entity
  - financials
  - metrics
  - product
  - market
  - people
  - legal
  - governance
  - integrations
  - brand

Entity — legal identity .corpospec/entity/company.yaml

Legal name, registered address, officers, jurisdiction PathRef.

# yaml-language-server: $schema=https://corpospec.com/schemas/v0.7.1/entity.schema.json
id: entity/acme-corp
type: corporation
legal_name: "Acme Corp, Inc."
trade_name: "Acme"
legal_form: "C-Corp"
jurisdiction: "US"
functional_currency: "USD"
registration_number: "7891234"
registration_authority: "Delaware Division of Corporations"
date_of_incorporation: "2025-06-15"
address:
  street: "100 Market Street, Suite 300"
  city: "San Francisco"
  postal_code: "94105"
  state: "CA"
  country: "US"
founders:
  - people/team/alex-chen
  - people/team/sarah-kim
url: "https://acme-corp.example.com"
company_purpose: "To develop and operate a workflow automation platform that enables growing teams to eliminate manual processes through AI-powered tools."
tax_ids:
  - id_type: "EIN"
    value: "84-3219876"
    country: "US"
    description: "Federal Employer Identification Number"
contact:
  email: "hello@acme-corp.example.com"
  phone: "+1-415-555-0142"
number_of_employees:
  value: 12
  as_of: "2026-03-01"
status: active

People — team member .corpospec/people/team/alex-chen.yaml

One file per person. Role PathRef, contact fields, employment facts.

# yaml-language-server: $schema=https://corpospec.com/schemas/v0.7.1/person.schema.json
id: people/team/alex-chen
type: Person
name:
  given: "Alex"
  family: "Chen"
  full: "Alex Chen"
email: "alex@acme-corp.example.com"
role: people/roles/ceo
unit: executive
start_date: "2025-06-15"
end_date: null
status: active
equity: entity/equity/stakeholders/alex-chen
bio: "Co-founder and CEO. Previously VP Product at DataFlow. Stanford CS."

Governance — decision record .corpospec/governance/decisions/0001-entity-jurisdiction.md

Architecture decision as a markdown file with YAML frontmatter.

File not found in the ACME snapshot.

Financial — model .corpospec/financials/model.yaml

Plan, actuals, and forecasts via PathRef into sibling directories.

# yaml-language-server: $schema=https://corpospec.com/schemas/v0.7.1/financial-model.schema.json
id: financials/model
period:
  type: instant
  start: "2026-03-01"
entity: entity/acme-corp
currency: USD

income_statement:
  revenue: 218400
  cost_of_revenue: 54600
  gross_profit: 163800
  operating_expenses:
    research_and_development: 420000
    sales_and_marketing: 180000
    general_and_administrative: 96000
  operating_income: -532200
  net_income: -532200

balance_sheet:
  assets:
    cash_and_equivalents: 1190000
    accounts_receivable: 42000
    total_assets: 1232000
  liabilities:
    accounts_payable: 18000
    total_liabilities: 18000
  equity:
    total_equity: 1214000

cash_flow:
  operating: -44350
  investing: -5000
  financing: 0
  net_change: -49350

custom:
  description: >
    Instant snapshot as of 2026-03-01. Acme Corp is a post-seed SaaS company
    building workflow automation for growing teams. Revenue is MRR $18,200
    annualized to $218,400. Growing 15% month-over-month.
  stage: post-seed
  monthly_recurring_expenses:
    - name: AWS
      amount: 4200
    - name: Google Workspace
      amount: 180
    - name: GitHub Enterprise
      amount: 252
    - name: NovaMind AI API
      amount: 3800
    - name: Datadog
      amount: 450
    - name: Slack
      amount: 156
    - name: Linear
      amount: 120
    - name: Figma
      amount: 90
    - name: Notion
      amount: 144
    - name: Office lease
      amount: 2500
  assumptions:
    - id: asm-fin-001
      description: "Pre-Series A, $2.5M seed closed Oct 2025."
      evidence: "Signed SAFE agreements and bank deposit confirmation."
      invalidation_condition: "Failure to deploy capital within projected timeline."
    - id: asm-fin-002
      description: "MRR growing 15% month-over-month."
      evidence: "Stripe dashboard shows consistent 14-16% MoM growth since Dec 2025."
      invalidation_condition: "MRR growth drops below 10% for two consecutive months."
    - id: asm-fin-003
      description: "14.2 months runway at current burn."
      evidence: "$1,190,000 cash / $49,350 monthly net burn = 24.1 months remaining."
      invalidation_condition: "Unexpected large expense or revenue decline."
    - id: asm-fin-004
      description: "Target Series A at $3M ARR."
      evidence: "Benchmark data from comparable B2B SaaS companies at Series A."
      invalidation_condition: "

# …truncated…

Metrics — definition .corpospec/metrics/definitions/mrr.yaml

Formula, unit, owner. Metrics are defined once, referenced many times.

# yaml-language-server: $schema=https://corpospec.com/schemas/v0.7.1/metric.schema.json
id: metrics/definitions/mrr
name: Monthly Recurring Revenue
abbreviation: MRR
description: Sum of monthly values of all active recurring subscription contracts.
formula: sum(active_subscriptions.monthly_value)
unit: currency
direction: up
frequency: monthly
source:
  system: stripe
  query: stripe.subscriptions.list(status=active).sum(plan.amount)
xbrl_mapping: null
related_metrics:
- metrics/definitions/arr
iso_30414_mapping: null
tags:
- saas
- revenue
- investor-facing