Flywheel Vocabulary Architecture

The decision

Adopt the contract, not a second database.

One parent edge, three legal extension modes, one resolver, and no override semantics.

01 · KEEP

Core + profiles

systems, finance, fwm, tpr, ac, eoe, sbc, and client-boards extend wtf-core; rep extends client-boards.

02 · CORRECT

Separate the layers

Classes use subclassing, concepts use SKOS relations, and organizations, people, boards, and cards remain instances.

03 · PROTECT

REP stays authoritative

The live database/API owns operational terms. A fleet registry declares lineage and constraints; it never hand-copies REP.

Extension map

Orbit means inheritance distance.

It does not imply legal hierarchy, ownership, trust, or infrastructure. Arrows point from child profile to parent contract.

Orbit 1 · proposedfwmOrganizational and delivery vocabulary

Orbit 1 · evidence-backedeoeExpeditions, stories, impact areas, and place data

Orbit 1 · proposedtprPerson and personal-property vocabulary

Root contractwtf-coreClasses · predicates · extension semantics

Orbit 1 · repository-backedsystemsReusable products and functional classifications

Orbit 1 · evidence-backedacPerson, public roles, writing themes, and personal properties

Orbit 1 · abstractclient-boardsBoard, opportunity, pillar, and dimension mechanics

Orbit 2 · live evidencerepNine pillars · eight dimensions · audited edits

Orbit 1 · live-schema-backedfinanceAccounts · ownership · payments · payroll · glossary

coreproposed/abstractlive evidence

REP proves the board mechanism in production; finance-mgmt proves the account, ledger, payment, and payroll model; ac and eoe supply profile evidence; fleet repositories establish the systems catalog. The cross-fleet extends declarations remain the architecture proposed here.

Resolved site vocabularies

Versioned manifests now resolve core, guides and local site terms with provenance. This validates vocabulary inheritance, not operational entity records.

Shared guides, Medical Tourism and Shortdrama · Core, editorial charter, portfolio ICP archetypes, Compounding CEO, Flywheel Motion, SBC and loops · Portfolio site taxonomy chart

wtf-core

Three layers, three jobs.

The earlier draft mixed ontology, controlled vocabulary, and factual records. The core connects them without conflating them.

MODEL

Classes + properties

What kind of thing is this? Classes narrow with rdfs:subClassOf; instances use rdf:type.

VOCABULARY

Concept schemes

Which controlled term applies? Concepts use skos:inScheme, hierarchy, and cross-scheme mappings.

DATA

Instances + assignments

Flywheel, a person, a client board, and a card consume the model. They do not become classes by being important.

fw:Entity
├── fw:Agent
│   ├── fw:Organization
│   └── fw:Person
├── fw:Engagement
├── fw:WorkItem
├── fw:DigitalAsset
│   ├── fw:DigitalProperty
│   ├── fw:ContentAsset
│   │   └── fw:Book
│   ├── fw:DataStore
│   └── fw:SystemInstance
├── fw:SystemProduct
└── fw:VocabularyResource
    ├── skos:ConceptScheme
    ├── skos:Concept
    └── fw:ClassificationAxis

client-boards extension
├── cb:ClientBoard
│   └── subClassOf fw:DigitalProperty
├── cb:Opportunity
│   └── subClassOf fw:WorkItem
├── cb:PillarDefinition
│   └── subClassOf fw:ClassificationAxis
└── cb:DimensionDefinition
    └── subClassOf fw:ClassificationAxis

Correction: an Engagement is not an Organization, and a board is not an engagement. A board is a digital surface for an engagement; that belongs in cb:boardFor, not the class tree.

Normative inheritance rule

A child gets exactly three choices.

Private means locally scoped, not confidential. There is no fourth mode called override, redefine, or shadow.

Reuse

Same ID, same meaning

Reference the ancestor term. Do not copy its definition or mint a synonym.

Narrow

New ID, stricter meaning

Use rdfs:subClassOf for classes, skos:broadMatch across concept schemes, and skos:broader within one scheme.

Add private

New ID, local meaning

Mint in the child namespace with no ancestor mapping. It is available only in that child's effective vocabulary.

effective(S) = effective(parent(S)) ∪ local(S) · parent graph MUST be acyclic

At most one direct parent in v1.
Never mutate an ancestor's ID, type, or definition.
Reuse contains a reference, not a copied definition.
Narrowing targets must resolve and kinds must match.
Local IDs are unique across the effective vocabulary.
Private terms use the child namespace.

Why skos:broadMatch? SKOS provides mapping properties for alignment between schemes. Using skos:broader everywhere hides the boundary this model is meant to expose.

Canonical relation registry

Small, typed, and boring.

Governance, model, domain, and board relations are separate. Domain and range are enforceable guardrails.

Predicate	Domain → range	Contract
Scheme governance + concept mapping
`fw:extendsScheme`	ConceptScheme → ConceptScheme	Custom direct-parent edge. The resolver computes ancestry.
`skos:inScheme`	Concept → ConceptScheme	Declares the concept's home. Reuse does not change it.
`skos:broader` / `narrower`	Concept ↔ Concept	Hierarchy inside one scheme.
`skos:broadMatch` / `narrowMatch`	Concept ↔ Concept	Hierarchical mapping across schemes.
`skos:exactMatch`	Concept ↔ Concept	Equivalent meaning under distinct IDs. Do not use instead of reuse.
Classes + instances
`rdf:type`	Resource → Class	Instance-of; replaces the custom `isA`.
`rdfs:subClassOf`	Class → Class	Class specialization; never substitute `skos:broader`.
Core domain relations
`fw:memberOf` / `hasMember`	Person ↔ Organization	General membership; narrow locally for employment if needed.
`fw:coFounderOf` / `hasCoFounder`	Person ↔ Organization	Connects a founder to the organization, not vaguely to another person.
`fw:authorOf` / `hasAuthor`	Person ↔ Book	Connects an author to the book, not to an article or a site.
`fw:owns` / `ownedBy`	Agent ↔ DigitalAsset	Ownership. Operational control uses `operates`.
`fw:operates` / `operatedBy`	Agent ↔ DigitalAsset	Operational responsibility without asserting ownership.
`fw:partOf` / `hasPart`	Entity ↔ Entity	Structural containment only.
`fw:servesClient` / `clientServedBy`	Engagement ↔ Organization	Connects an engagement to its client organization.
`schema:sameAs`	Entity → URL	External identity page; avoid strict `owl:sameAs` unless intended.
Reused from schema.org, no fw term
`schema:isbn`, `schema:bookFormat`, `schema:datePublished`, `schema:inLanguage`, `schema:workExample`, `schema:publisher`	Book → value, edition or publisher	Reuse schema.org properties; an edition is represented by `schema:workExample`.
Systems + deployments
`fw:instanceOfProduct`	SystemInstance → SystemProduct	Connects a real property, account, container, store, or cluster to its reusable product term.
`fw:hasFunction`	SystemProduct or SystemInstance → Concept	Multi-valued functional classification; avoids forcing a product into one rigid class tree.
`fw:usesSystem`	Entity → SystemInstance	Use the local deployment—not the abstract product—as the object.
`fw:servesProperty`	SystemInstance → DigitalProperty	Scopes measurement, delivery, search, or hosting infrastructure to a property.
`fw:managedBy`	SystemInstance → Agent	Operational stewardship; it does not imply ownership of the vendor product.
`fw:feeds`	SystemInstance → SystemInstance	Directed data or event flow between deployments.
Finance account + money-flow relations
`fin:accountHolder`	FinancialAccount → Agent	The registered holder. Do not substitute operator, beneficiary, or cost attribution.
`fin:recordedUnder`	LedgerAccount → AccountingScope	The finance workspace/reporting scope containing the account; not proof of legal ownership.
`fin:providedBy`	FinancialAccount → SystemInstance	Connects an account to its provider workspace, such as Airwallex or a bank connection.
`fin:fundedFrom`	Payment or Payout → FinancialAccount	The account debited for an outgoing transfer or payout.
`fin:paidTo`	Payment or Payout → Agent or FinancialAccount	The receiving beneficiary or destination account.
`fin:usesRail`	Payment or Payout → Concept	The movement rail—separate from the system that observes or reconciles it.
`fin:reconciledVia`	LedgerEntry → SystemInstance	Provenance for observation through Plaid, Airwallex, statement import, or manual entry.
`fin:hasAllocation`	LedgerEntry → Allocation	N-ary allocation carrying target accounting scope and basis-point weight.
Client-board mechanics
`cb:boardFor`	ClientBoard → Engagement	Board-to-engagement relationship.
`cb:hasPillar`	ClientBoard → PillarDefinition	Ordered outcome axis; a card has ≥1 and the first is primary.
`cb:hasDimension`	ClientBoard → DimensionDefinition	Named cross-cutting facet with allowed values.
`cb:classifiedUnder`	Opportunity → Concept	Assigns the opportunity to a pillar concept.
`cb:hasFacetAssignment`	Opportunity → FacetAssignment	Keyed dimension/value assignment; maps to REP's `dimensions_json`.

Unresolved: subsidiary and brand predicates require verified corporate facts. The model must not turn uncertainty about fwm's legal status into a canonical example.

Shared systems catalog · sys:

Products are shared. Deployments are local.

This first pass comes from source and configuration across the fleet, excluding dependencies and generated output. A product is promoted to sys: when multiple independent repositories use it or when it is centrally operated.

PRODUCT

`sys:ga4`

A stable fleet catalog entry typed fw:SystemProduct. It contains no property ID, credentials, client, or account state.

DEPLOYMENT

`eoe:ga4-property`

A real fw:SystemInstance linked to sys:ga4 and eoe:website. Access and identifiers stay in the owning profile.

FUNCTION

`sys:measurement`

A SKOS concept assigned with fw:hasFunction. Products may have several functions, so category is not hard-coded inheritance.

sys:functions
├── sys:measurement
│   ├── sys:web-analytics
│   ├── sys:behavior-analytics
│   └── sys:session-replay
├── sys:delivery
│   ├── sys:tag-management
│   ├── sys:edge-delivery
│   └── sys:transactional-email
├── sys:observability
│   └── sys:error-monitoring
├── sys:discoverability
│   ├── sys:search-performance
│   ├── sys:search-submission
│   └── sys:ai-visibility
└── sys:data
    ├── sys:warehouse
    ├── sys:database
    └── sys:cache

sys:functions (continued)
├── sys:platform-operations
│   ├── sys:dns
│   ├── sys:identity-access
│   └── sys:domain-registration
├── sys:publishing
│   └── sys:content-management
├── sys:business-operations
│   ├── sys:crm
│   ├── sys:work-management
│   └── sys:collaboration
├── sys:financial-operations
│   ├── sys:payment-processing
│   ├── sys:financial-data-sync
│   └── sys:payout-execution
├── sys:communication
│   └── sys:messaging
└── sys:specialist-service
    ├── sys:translation
    └── sys:sports-data

Measurement + behavior 5 products

Repository evidence: websites-lib, bi, growth-engine, openreplay, and site repositories.

sys:ga4
sys:gtm
sys:posthog
sys:openreplay
sys:sentry

Search + discoverability 6 products

Repository evidence: bi, domain-ops, growth-engine, and public-property repositories.

sys:gsc
sys:bing-webmaster
sys:indexnow
sys:profound
sys:dataforseo
sys:perplexity

Data + persistence 7 products

Repository evidence: bi, growth-engine, domain-ops, tmapp, and service repositories.

sys:bigquery
sys:clickhouse
sys:mariadb
sys:postgresql
sys:mongodb
sys:redis
sys:sqlite

Edge, identity + domains 6 products

Repository evidence: cloudflare-mgmt, domain-ops, growth-engine, security-mgmt, and authenticated apps.

sys:cloudflare
sys:github
sys:google-workspace
sys:namesilo
sys:porkbun
sys:regery

Content + publishing 2 products

Repository evidence: shared site code and publishing integrations, not incidental page copy.

sys:strapi
sys:webflow

Work + customer operations 4 products

Repository evidence: growth-engine, biz-dev, team-mgmt, and operational repositories.

sys:notion
sys:attio
sys:airtable
sys:vikunja

Finance + payments 3 products

Live integration evidence: finance-mgmt adapters, sync jobs, and the canonical finance database.

sys:airwallex
sys:plaid
sys:paypal

Communication + delivery 3 products

Repository evidence: email-ops, team-mgmt, deployment scripts, and fleet services.

sys:aws-ses
sys:discord
sys:ntfy

Specialist APIs 3 products

Centrally managed integrations with explicit application code or scheduled jobs.

sys:deepl
sys:sportmonks
sys:intervals-icu

Promotion rule: a README mention, package transitive dependency, detected client script, or speculative roadmap item is not enough. Evidence must be executable source/config in at least two independent profiles, or a centrally managed fleet integration.

Local namespace boundary

REP's commerce stack stays `rep:`.

REP may reuse shared products such as GA4, but client-specific products and every actual deployment remain local. Detection is recorded separately from confirmed use.

Local term	Kind / shared link	Evidence and treatment
`rep:ga4-property`	SystemInstance → `sys:ga4`	Reuses the shared product; property identifiers and access state remain REP data.
`rep:gtm-container`	SystemInstance → `sys:gtm`	Reuses the shared product; container-specific facts remain REP data.
`rep:shopify` `rep:shopify-store`	Private SystemProduct + SystemInstance	REP's sole CMS and commerce hub. Not promoted to `sys:` from client-only evidence.
`rep:polar` `rep:polar-workspace`	Private SystemProduct + SystemInstance	REP's aggregate analytics source of truth. Remains private until independent fleet use is evidenced.
`rep:klaviyo-account`	Private SystemInstance	Confirmed REP lifecycle-email system; scoped to the client profile.
`rep:attentive-app`, `rep:okendo-app`, `rep:rebuy-app`, `rep:visually-io-app`	Private SystemInstance	Detected in REP markup, not confirmed by REP; retain an evidence status and never promote from detection alone.
`rep:ahrefs-account`, `rep:semrush-account`, `rep:supermetrics-sheets`	Private SystemInstance	Current evidence is tied to REP's access/topology. Split the combined runtime label into distinct local records.

Illustrative system instance · no secret or vendor account ID

{
  "id": "eoe:ga4-property",
  "type": "fw:SystemInstance",
  "instanceOfProduct": "sys:ga4",
  "hasFunction": ["sys:measurement", "sys:behavior-analytics"],
  "servesProperty": "eoe:website",
  "managedBy": "fwm:organization"
}

Never publish: credentials, tokens, property/container/account IDs, billing identifiers, private URLs, or access status in the shared product catalog. Those belong in secured operational stores, not vocabulary.

Finance extension · fin:

Accounts, owners, payment options, and shared language.

Derived from the live finance_mgmt schema, its migrations, adapters, and production-safe aggregates. The MariaDB database remains authoritative for operational records; this profile defines what those records mean.

ACCOUNT

Where value is held

A financial account has a holder, provider, kind, currency, and lifecycle. Ledger projection and account directory are distinct views.

OWNER

Who holds or controls it

Registered holder, operator, payer, beneficiary, employer, and approver are separate roles. Attribution never changes ownership.

FLOW

How money moves

Payment, payout, transfer, installment, rail, observation source, reconciliation, and settlement each get one meaning.

GLOSSARY

Terms people can share

Billing, ledger, expenses, subscriptions, and payroll use one controlled vocabulary without deciding tax or employment status.

finance classes
fin:FinancialAccount
├── fin:LedgerAccount
└── fin:HoldingAccount
fin:FinancialTransaction
├── fin:IncomingPayment
├── fin:Payout
├── fin:Transfer
└── fin:Adjustment
fin:FinancialDocument
├── fin:Invoice
└── fin:Payslip
fin:AccountingScope
fin:Ledger
fin:LedgerEntry
fin:Allocation
fin:Installment
fin:Subscription
fin:PayRun

finance concept schemes
fin:account-kind
├── fin:bank-account
├── fin:multi-currency-account
├── fin:cash-account
├── fin:card-account
├── fin:brokerage-account
├── fin:crypto-account
├── fin:wallet-account
├── fin:payment-app-account
├── fin:loan-account
└── fin:other-account

fin:party-role
├── fin:account-holder
├── fin:beneficial-owner
├── fin:operator
├── fin:payer / fin:payee
├── fin:beneficiary
├── fin:employer-of-record
└── fin:approver

Core mappings: fin:FinancialAccount subclasses fw:Entity; fin:FinancialDocument subclasses fw:ContentAsset; fin:PayRun subclasses fw:WorkItem. Account kinds and party roles are SKOS concepts, not subclasses or free-text labels.

Runtime enumeration registry

The values the system actually accepts.

Read from production INFORMATION_SCHEMA on 1 Sep 2026. These are closed MariaDB enums. Raw values remain visible for implementation; the fin: concepts above provide their stable semantic names.

Surface	Field	Strict values
Accounts, holders, and accounting scopes
Ledger account	`accounts.kind`	`airwallex`, `bank`, `cash`, `card`
Account directory	`bank_accounts.kind`	`bank`, `crypto`, `brokerage`, `card`, `wallet`, `payment_app`, `loan`, `other`
Registered holder	`account_holders.kind`	`person`, `entity`
Default receiving rail	`entities.rail`	`airwallex`, `bank`
Ledger, costs, and attribution
Ledger movement	`ledger_entries.kind`	`invoice_payment`, `cost`, `transfer`, `adjustment`
Ledger attribution	`ledger_entries.attribution`	`company`, `personal`, `mixed`
Cost behavior	`costs.kind`	`fixed`, `flexible`
Cost category	`costs.category`	`software`, `server`, `salary`, `contractor`, `fees`, `other`
Cost cadence	`costs.cadence`	`monthly`, `annual`, `one_off`
Classifier input	`bucket_rules.field`	`counterparty`, `memo`
Classifier attribution	`bucket_rules.attribution`	`company`, `personal`, `mixed`
Billing, incoming payments, and reminders
Invoice lifecycle	`invoices.status`	`draft`, `sent`, `partially_paid`, `paid`, `overdue`, `void`
Installment lifecycle	`invoice_installments.status`	`pending`, `partially_paid`, `paid`, `overdue`
Payment observation	`payments.source`	`airwallex`, `plaid`, `bank_api`, `manual`
Match confidence	`payments.match_conf`	`auto`, `fuzzy`, `manual`, `unmatched`
Reminder schedule	`reminder_log.kind`	`on_demand`, `due`, `overdue_7`, `overdue_14`, `overdue_30`
Payroll and payouts
Staff engagement	`staff.engagement`	`salary`, `hourly`, `contractor`, `partner`
Payout method	`staff_payout_methods.method`	`paypal`, `bank`, `airwallex`, `wise`, `crypto_wallet`, `other`
Method viability	`staff_payout_methods.status`	`unverified`, `viable`, `rejected`, `stale`
Pay-run lifecycle	`pay_runs.status`	`draft`, `collecting`, `approved`, `paying`, `closed`, `void`
Payslip lifecycle	`payslips.status`	`draft`, `method_pending`, `ready`, `sending`, `sent`, `settled`, `failed`, `void`
Execution rail	`payouts.rail`	`paypal`, `airwallex`, `wise`, `manual`, `crypto`
Payout lifecycle	`payouts.status`	`queued`, `sent`, `settled`, `failed`, `returned`
Subscriptions and finance-email intake
Subscription lifecycle	`subscriptions.status`	`active`, `expiring`, `lifetime`, `paused`, `stopped`
Intake classification	`email_intake.kind`	`expense`, `context`, `subscription`, `unclassified`
Intake lifecycle	`email_intake.status`	`received`, `classified`, `applied`, `failed`, `ignored`
Vendor-bill lifecycle	`vendor_bills.status`	`confirmed`, `needs_amount`, `ignored`
Vendor-bill reconciliation	`vendor_bills.reconciled`	`matched`, `backfilled`, `pending`

Actual accounting scopes

The Flywheel Corporationfin:scope-fw
Edges of Earth LLCfin:scope-eoe
Flywheel Motionfin:scope-fwm
Thomas Prommer · personalfin:scope-tp

These are finance reporting scopes. The list itself does not prove legal status or account ownership.

Registered account-holder agents

The Flywheel Corporation · organizationfin:holder-fw
Edges of Earth LLC · organizationfin:holder-eoe
Thomas Prommer · personfin:holder-tp
Andi Cross · personfin:holder-ac

Personal holder names may be enumerated; their accounts, institutions, balances, and identifiers remain protected.

Application allowlists

Suggestions are not closed vocabulary.

These values come from finance-mgmt application code rather than MariaDB enums. The authority column states whether the API validates them or merely offers them in the UI.

Surface	Values	Authority
Account lifecycle	`Active`, `Paused`, `Closed`, `Open`, `Pending Verification`, `Unknown`	API-validated allowlist over a VARCHAR column.
Invoice category	`advertorial`, `retainer`, `sponsorship`, `service`, `other`	UI suggestions; custom free text remains legal.
Currency	`USD`, `EUR`, `PHP`, `VND`, `GBP`, `SGD`, `AUD`, `CAD`, `CHF`, `JPY`	UI suggestions; valid three-letter currencies are not limited to this list.
Dedup review state	`none`, `duplicate`, `review`, `discrepancy`	API-validated editing allowlist.
Subscription billing mode	`Monthly Fee`, `Quarterly Fee`, `Yearly Fee`, `Bi-yearly Fee`, `Pay as you Go`, `Credit Based`, `Monthly Usage`, `Lifetime Fee`, `One-time Fee`, `Family Plan Monthly`, `Free`, `Free Grandfathered`, `Trial Only`	Datalist suggestions over free text.
Subscription type	`AI`, `Software`, `Office`, `Server`, `Storage`, `Security`, `Development`, `Communications`, `Data`, `Network`, `Travel`, `Social Media`, `PR`, `Learning`, `Entertainment`, `Finance`, `Health`, `Mobile Apps`, `Desktop App`	Datalist suggestions over free text.

Interpretation rule: presence in an enum means the value is structurally accepted—not that the capability is active. For example, wise is accepted as a payout method and rail while no live Wise adapter currently exists.

Account model

Two registries, one conceptual account.

The production schema intentionally has a ledger-facing accounts table and a broader bank_accounts directory. A resolver can map records from both to the same protected account instance.

Canonical term	Current source	Meaning
`fin:LedgerAccount`	`accounts`	The account dimension used by ledger entries, invoices, reconciliation, reporting scopes, and money-movement views.
`fin:HoldingAccount`	`bank_accounts`	The wider “where value is parked” directory across organizational and personal holders, including bank, brokerage, crypto, card, wallet, payment-app, and loan records.
`fin:AccountHolderRole`	`account_holders` + `holder_identities`	Connects an Agent to an account under a registered identity. Jurisdictional identity is not a separate person.
`fin:AccountingScope`	`entities`	A billing/reporting workspace. It can describe an organization or a person's finance scope, so the table name must not be interpreted as proof that every row is a legal entity.
`fin:Allocation`	`ledger_entity_splits`	Assigns an entry to one or more scopes in basis points. Allocation answers “who bears this?”—not “who owns the funding account?”
`fin:BalanceSnapshot`	`bank_accounts.balance_cents` + `balance_date`	A reported balance at a date. It is not reconstructed by blindly summing a multi-currency ledger.

`fin:fw-airwallex-usd`

Safe organizational account alias

Live

Type: fin:LedgerAccount
Holder: The Flywheel Corporation
Kind: fin:multi-currency-account; native ledger currency USD
Provider workspace: fin:fw-airwallex → sys:airwallex

`fin:eoe-boa-small-business`

Safe organizational account alias

Live

Type: fin:LedgerAccount + fin:HoldingAccount
Holder: Edges of Earth LLC
Kind: fin:bank-account; native currency USD
Reconciliation path: protected Plaid connection or statement import

Protected account adapter: production currently contains organizational and personal account records beyond the two safe aliases above. Full labels, personal institutions, suffixes, account/routing numbers, balances, addresses, login identifiers, crypto addresses, staff payout destinations, and provider references stay behind finance.tfw.bz and are never rendered into this static site.

Payment options

Rail, method, and observation are different axes.

The current database enums combine some of these ideas. The canonical vocabulary separates them so future integrations remain comparable.

Concept	Current mechanism	Contract
Movement rails and methods
`fin:hosted-payment-link`	Airwallex-hosted checkout	Client-facing collection method; the provider handles supported card/bank options.
`fin:bank-transfer`	Local/SEPA, ACH, wire, or SWIFT	Generic account-to-account movement. The concrete clearing route is a narrower concept.
`fin:paypal-payout`	PayPal Payouts adapter	Supported programmatic staff payout method.
`fin:airwallex-local`	Airwallex `payments/create`, local/SEPA default	Primary programmatic bank payout route; source amount and provider fee are recorded separately.
`fin:crypto-transfer`	Manually executed, separately recorded rail	A payment rail, not an account type; asset and network belong to the destination account/method.
`fin:manual-settlement`	Operator records an out-of-band movement	Fallback that still posts an auditable ledger entry.
`fin:wise-transfer`	Declared payout-method value; no active adapter	Available vocabulary, not a claim that the integration is operational.
Observation and reconciliation sources
`fin:airwallex-feed`	`sys:airwallex`	Provider-native transaction and payout observations.
`fin:plaid-sync`	`sys:plaid`	Read-only transaction observation; Plaid is not the payment rail.
`fin:statement-import`	OFX / QBO / CSV	Manual ingestion and reconciliation backstop.
`fin:manual-entry`	Protected finance UI	Human-authored source with audit provenance.

Controlled glossary

One term for each financial idea.

These definitions describe the system's records and workflows. They are not accounting, tax, employment, or legal advice.

Term	Definition	Boundary
Accounts, ledger, and attribution
`fin:financial-account`	A named place where money or another financial asset is held, owed, or transacted.	Provider, currency, and account kind are separate properties.
`fin:account-holder`	The Agent under whose registered identity the account is held.	Do not infer beneficial ownership or operating control.
`fin:ledger`	The ordered accounting record of signed money movements.	It records movements; it is not the account itself.
`fin:ledger-entry`	One dated, signed movement in one currency against a ledger account.	Positive is inflow; negative is outflow in finance-mgmt.
`fin:allocation`	A weighted assignment of an entry or subscription to an accounting scope.	Allocation can be split; ownership cannot be changed by allocation.
`fin:expense-bucket`	A controlled reporting category applied to a cost entry.	Separate from company/personal/mixed attribution.
`fin:reconciliation`	Matching an observed money movement to the invoice, payout, cost, or transfer it settles.	Observation can be automatic while the final match remains manual.
Billing and money movement
`fin:invoice`	A document requesting payment from a client for an issuing accounting scope.	One global sequence; entity code is a suffix in finance-mgmt.
`fin:installment`	One scheduled part of a single invoice.	Not a cross-entity revenue split.
`fin:incoming-payment`	Money received and optionally matched to an invoice or installment.	The payment record and its ledger entry are related but distinct.
`fin:payout`	An execution attempt that sends money to a beneficiary through a rail.	Retries are separate attempts and must be idempotent.
`fin:transfer`	A movement between accounts that does not itself establish revenue or expense.	Intercompany treatment requires explicit journals, not inference.
`fin:settlement`	The state in which a provider confirms the movement has completed.	“Sent” or dispatched is not necessarily settled.
`fin:subscription`	A recurring or usage-based commitment to a product or service.	Credentials remain in OpenBao/Vaultwarden; finance stores pointers only.
Payroll and people payments
`fin:payroll`	The controlled process that turns approved staff work or recurring pay into payslips, payouts, and ledger entries.	The term does not decide employee versus contractor classification.
`fin:pay-run`	An approval-gated batch of payslips for a period and optional paying scope.	Draft, collecting, approved, paying, closed, or void.
`fin:payslip`	The per-person pay record and rendered payment document within a pay run.	For contractors the rendered document may function as their invoice to the company.
`fin:gross-pay`	Pay before recorded deductions.	Amounts remain in their stated currency.
`fin:deduction`	An explicit reduction from gross to net, including a staff-borne provider fee when configured.	Does not imply tax withholding.
`fin:net-pay`	The amount intended to land with the payee after recorded deductions.	The funding account debit may differ because of FX or payer-side fees.
`fin:payout-method`	A person's selected destination method, such as bank, PayPal, Airwallex, Wise, or crypto wallet.	Sensitive destination details live in OpenBao.
`fin:viable-method`	A payout method with enough validated information to attempt a send.	Viable does not mean a payout was sent or settled.
`fin:employer-of-record`	The organization recorded as paying/employing scope for a staff relationship.	Assert only from an approved operational source; not inferred from cost allocation.

Tax boundary: tax treatment, withholding, contractor classification, beneficial ownership, and legal-entity status remain evidence-gated. Current placeholder fields and planning notes are not promoted into canonical facts without accountant or documentary confirmation.

Authority: finance_mgmt MariaDB owns accounts, ledger entries, invoices, subscriptions, payroll, payouts, and audit state. The taxonomy adapter exports stable IDs, safe labels, types, and relations; it must omit financial values and protected identifiers.

Technology Business Management · reference mapping

Trace technology spend to the service and its consumer.

The TBM Council Taxonomy 5.0.1 supplies a common cost vocabulary. This is a Flywheel crosswalk to that framework, not a copy of its full taxonomy or a claim that allocations are live.

TBM layer	Question	Flywheel mapping
Cost pools	What was bought?	`finance_mgmt.ledger_entries` is the actual-spend source; subscriptions describe commitments. Expense buckets need a reviewed crosswalk to TBM pools such as staffing, software and cloud services.
Resource towers	What technology capacity did it fund?	Map a cost to compute, storage, applications, security or another tower only when the expense and use support that classification. Shared bills can be split.
Solutions	Which service or product uses that capacity?	`fw:SystemInstance` identifies a deployment; `fw:SystemProduct` identifies its reusable product. A proposed service-costing model links cost portions to those records.
Consumers	Who uses or benefits from the solution?	We The Flywheel (WTF), Flywheel Motion (FWM), Thomas Prommer (TPR), a named client engagement, and personal use are separate consumer views. A payer or account holder is not automatically the consumer.

Boundaries: the ledger's entity split records financial attribution, while a TBM service split would explain operational use. Keep both and reconcile them; do not infer legal ownership, tax treatment, intercompany charges or client profitability from a service allocation. Record unassigned amounts rather than inventing percentages.

TBM Council sources: TBM Model and Allocation Methods. The fin and sys machine profiles remain reference-only; this mapping does not add transaction data or a new machine contract.

Loop categories

One business category per workflow. Scope, audience, cadence, owner, effects and runtime status remain separate attributes.

loop:business-category extends wtf-core. Version 1.12.21. Download the canonical manifest.

Category and stable ID	Definition	Examples
Website health and SEO `loop:website-health-seo`	Keep sites crawlable, discoverable, relevant and technically healthy.	Crawl hygiene, Indexing, Internal links, Topical focus
Content and publishing `loop:content-publishing`	Plan, create, refresh and distribute editorial content.	Newsletter, FAQ, Articles, Social publishing
Acquisition and retention `loop:acquisition-retention`	Attract audiences, earn attention and convert or re-engage customers.	Paid campaigns, Outreach, Race re-engagement, Marketplace monitoring
People and client delivery `loop:people-client-delivery`	Coordinate hiring, onboarding, commitments and delivery to clients.	Hiring, Onboarding, Meetings, CRM reminders
Knowledge and intelligence `loop:knowledge-intelligence`	Collect, synthesize and maintain reusable knowledge and research.	Expert intake, Source monitoring, Research digests
Platform and agent operations `loop:platform-agent-operations`	Maintain shared services, automation infrastructure and agent performance.	Self-repair, Bot memory, Agent optimization, Security drift

Taxonomy owns these terms and their Loops assignments. Loops imports a versioned snapshot for grouping and filtering. Existing catalogue codes remain aliases for classification lookup; category assignments do not merge workflows or transfer execution authority.

Extending profiles

Extend only where local meaning exists.

A profile is not a branded inventory. If it only contains instances, it can consume core without minting terms.

systems · shared catalog

extends: wtf-core

Repository-backed

Names reusable products and functional concepts in the sys: namespace.
Contains no client account, property, store, credential, or access-state facts.
Promotes terms only from multi-profile or centrally managed evidence.

finance · accounts and money flow

extends: wtf-core · reuses sys:

Live-schema-backed

Separates accounts, holders, accounting scopes, allocations, methods, rails, and observation sources.
Defines billing, ledger, subscriptions, and payroll vocabulary from finance-mgmt.
Exports safe aliases only; protected account and payout data remain in MariaDB/OpenBao.

fwm

extends: wtf-core

Proposed

Reuse Organization, Engagement, DigitalProperty, owns, and operates.
Narrow ProposalPage only if it drives validation or discovery.
Do not assert subsidiary status without documentary evidence.

tpr

extends: wtf-core

Proposed

Reuse Person, DigitalProperty, memberOf, coFounderOf, and sameAs.
Do not mint the tautological class tpr:Person.
Account separation is deployment metadata, not taxonomy hierarchy.

ac · Andi Cross

extends: wtf-core

Evidence-backed

Reuse Person, DigitalProperty, ContentAsset, coFounderOf, and sameAs.
Keep Andi Cross as a Person instance—not a redundant ac:Person subclass.
Model public roles and writing themes as ac-owned concept schemes.

eoe · Edges of Earth

extends: wtf-core

Evidence-backed

Reuse Organization, Person, Engagement, ContentAsset, DigitalProperty, and sameAs.
Narrow eoe:Expedition from Engagement and eoe:Story from ContentAsset.
Keep story types and impact areas as concepts; team, partners, and places remain instances.

sbc · Solo Billionaire Club

extends: wtf-core · reuses fin:, sys:

Proposed

Narrows Person, Organization, Entity, DigitalAsset, WorkItem into 5 classes.
19 private concept schemes, 166 concepts; claim grades ordered weakest to strongest.
Founders, claims and evidence records stay in the product store.

client-boards

extends: wtf-core

Abstract

Adds Board, Opportunity, PillarDefinition, DimensionDefinition, FacetAssignment.
Requires ≥1 pillar, a primary first pillar, and declared dimension values.
Requires version checks, previews, audits, and safe merges.

rep

extends: client-boards

Live evidence

Nine private pillar concepts and eight live dimensions.
Runtime has the right mechanism but no published parent declaration yet.
The live database remains the operational authority.

Andi Cross · Orbit 1

A person profile with explicit concept boundaries.

The profile separates Andi, her website, her public positioning, her writing themes, and her relationship to Edges of Earth.

INSTANCE DATA

Person + property

ac:andi rdf:type fw:Person. ac:website is the andicross.com DigitalProperty about that person.

ROLE CONCEPTS

Public positioning

Expeditionist and Accelerant Strategist are concepts in an ac-owned role scheme—not subclasses of Person.

CROSS-PROFILE EDGE

Edges of Earth

ac:andi fw:coFounderOf eoe:organization. This links two instances; it does not make either scheme inherit from the other.

Five live writing themes

Women in Exploration
The Future of Exploration
Living on the Edge
Life Design with Nature
Building Businesses & Becoming Discoverable Online

Extension semantics

ac:public-role and ac:writing-theme are separate skos:ConceptScheme records.
Published articles are fw:ContentAsset instances related to author and publisher instances.
Consulting, speaking, writing, and media pages are DigitalProperty instances, not taxonomy branches.
External profiles reuse schema:sameAs.

Boundary: ac extends wtf-core directly. The co-founder link to eoe is factual data between instances, while the two vocabularies remain siblings.

Edges of Earth · Orbit 1

A real content vocabulary, not merely a domain.

The live Astro repository contains distinct concept, place, entity, and content layers. The profile preserves those distinctions.

CONTROLLED CONCEPTS

Story Type + Impact Area

Observed story types are Field Log, Case Study, and Press. Six Key Impact Areas form a separate subject scheme.

PLACE DATA

Geographic hierarchy

8 continents, 41 countries, 93 regions, and 83 locations are place records connected by containment—not subclasses or child schemes.

ENTITY + CONTENT DATA

People, partners, stories

389 stories reference 7 team members, 212 partners, authors, photographers, publishers, places, and impact areas.

Six live impact concepts

Natural Resource Management
Pollution & Waste Management
Natural Environment & Habitat Protection
Coastal Tourism & Community Development
Climate Resilience
Nature-Based Solutions & Innovation Tech

Extension semantics

eoe:Expedition rdfs:subClassOf fw:Engagement
eoe:Story rdfs:subClassOf fw:ContentAsset
Story Type and Impact Area values are skos:Concept records in eoe-owned schemes.
Geography reuses schema:Place and schema:containedInPlace.

Boundary: Edges of Earth's collaboration with Flywheel Motion and use of shared content infrastructure do not establish ownership. This profile extends the vocabulary contract directly and makes no legal parent/subsidiary claim.

Solo Billionaire Club · Orbit 1

Other people's companies, graded by evidence.

Classifies businesses the fleet does not own: industry, founder type, model, market, channels, team shape, and how strongly each revenue claim is substantiated.

sbc extends wtf-core and reuses fin:, sys:. Version 1.4.0. 5 classes, 19 concept schemes, 166 concepts. Download the canonical manifest.

Class and stable ID	Definition	Extension
Founder `sbc:Founder`	A person tracked by SBC as the operator/owner of one or more claimed businesses, carrying SBC-specific properties (team constellation, solo-claim status) that plain fw:Person does not.	Narrow · rdfs:subClassOf `fw:Person`.
Business `sbc:Business`	A company, product, or revenue-generating venture claimed by one or more sbc:Founder instances, classified by business model, revenue model, target market, and acquisition channels.	Narrow · rdfs:subClassOf `fw:Organization`.
Revenue Claim `sbc:RevenueClaim`	An asserted figure (MRR, ARR, profit, etc.) about an sbc:Business at a point in time, carrying its own verification evidence. Mirrors how fin:FinancialAccount subclasses fw:Entity directly rather than WorkItem or ContentAsset, because a claim is a factual assertion record, not a task or piece of editorial content.	Narrow · rdfs:subClassOf `fw:Entity`.
Verification Evidence `sbc:VerificationEvidence`	An artifact or access grant (API key, dashboard link, screenshot, attestation) that supports an sbc:RevenueClaim at a stated strength level.	Narrow · rdfs:subClassOf `fw:DigitalAsset`.
Race Entry `sbc:RaceEntry`	A founder or business's tracked placement in an SBC leaderboard/race, moving through a lifecycle the way an opportunity moves through a client board. Mirrors cb:Opportunity subclassing fw:WorkItem for the same reason: it is a trackable item with state, not a static classification.	Narrow · rdfs:subClassOf `fw:WorkItem`.

Properties

Fleet edges reused, local facts minted.

Founder, ownership and profile links reuse fleet predicates. Classifications and claim facts are private to the profile.

Property	Range · cardinality	Extension
Founder
`sbc:teamConstellation`	sbc:team-constellation (concept) · 0..1	Private.
`sbc:claimsSoloPublicly`	boolean · 0..1	Private.
`fw:owns`	sbc:Business · 0..n	Reuse `fw:owns`.
`fw:coFounderOf`	sbc:Business · 0..n	Reuse `fw:coFounderOf`.
`schema:sameAs`	xsd:anyURI · 0..n	Reuse `schema:sameAs`.
`sbc:archetype`	sbc:founder-archetype (concept) · 1..2	Private.
`sbc:operatesVenture`	sbc:Business · 0..n	Private. Distinct ventures operated by this founder, inverse of sbc:operatedBy.
Business
`sbc:businessModel`	sbc:business-model (concept) · 1	Private.
`sbc:revenueModel`	sbc:revenue-model (concept) · 1..n	Private.
`sbc:targetMarket`	sbc:target-market (concept) · 0..n	Private.
`sbc:hasAcquisitionChannel`	sbc:acquisition-channel (concept) · 0..n	Private. Modeled on fw:hasFunction's multi-valued SystemProduct/Instance -> Concept pattern, but minted locally because domain (fw:Organization, not SystemProduct/SystemInstance) doesn't match fw:hasFunction's declared domain.
`sbc:businessStatus`	string literal: active \| sold \| shut-down \| paused · 1	Private. String literal per house style, not a concept scheme -- lifecycle status, not controlled vocabulary shared across profiles.
`sbc:launchedDate`	xsd:gYearMonth · 0..1	Private.
`sbc:industryServed`	sbc:industry (concept) · 1..2	Private. Not sbc:industry, which is the scheme ID.
`sbc:growthEngine`	sbc:growth-engine (concept) · 1	Private.
`sbc:offerForm`	sbc:offer-form (concept) · 1	Private. Derived from sbc:businessModel through the sbc:offer-form roll-up and stored for query speed.
`sbc:ventureId`	string · 0..1	Private. Stable product identity. One separately identifiable site, product or service, independent of its operator or parent company.
`sbc:ventureWebsite`	xsd:anyURI · 0..1	Private. The canonical website for the individual venture.
`sbc:operatedBy`	sbc:Founder · 0..n	Private. Tracked operators of this venture. Does not imply sole ownership or attribute portfolio revenue.
`sbc:parentBusiness`	sbc:Business · 0..1	Private. Optional legal company or parent business. The parent and venture are not interchangeable revenue scopes.
Revenue Claim
`sbc:aboutBusiness`	sbc:Business · 1	Private.
`sbc:reportsMetric`	sbc:claim-metric (concept) · 1	Private.
`sbc:amount`	xsd:decimal + currency · 0..1	Private. Empty when only a tier/range is disclosed, not a figure.
`sbc:asOf`	xsd:date · 1	Private.
`sbc:grade`	sbc:claim-verification (concept) · 1	Private. The strongest grade supported by current evidence. Evidence older than 12 months lowers it one step.
`sbc:verifiedBy`	sbc:VerificationEvidence · 0..n	Private.
`sbc:claimScope`	string literal: venture \| portfolio · 0..1	Private. Venture claims identify one distinct product through sbc:aboutBusiness. Portfolio totals must not be split or copied into product MRR.
`sbc:checkedAt`	xsd:date · 0..1	Private. Date the source was checked, distinct from the date of its financial metric.
Verification Evidence
`sbc:evidenceKind`	sbc:claim-verification \| sbc:supporting-evidence (concept) · 1	Private. A grade concept when the evidence substantiates revenue; a supporting-evidence concept when it only corroborates plausibility.
`fw:usesSystem`	fw:SystemInstance · 0..1	Reuse `fw:usesSystem`. Used when the evidence is a system-mediated read grant, such as a sys:gsc property access. Absent for screenshots, press, dashboards and attestations.
`sbc:capturedAt`	xsd:date · 1	Private.
`sbc:sourceUrl`	xsd:anyURI · 0..1	Private.
Race Entry
`sbc:enteredBy`	sbc:Founder \| sbc:Business · 1	Private.
`sbc:raceTier`	sbc:race-tier (concept) · 1	Private.
`sbc:rank`	xsd:integer · 0..1	Private.
`sbc:asOf`	xsd:date · 1	Private.

Concept schemes

Private values, IAB-matched industries.

Industries narrow an IAB Content Taxonomy 3.0 tier-1 category where one matches one to one; every other value is private. Offer forms and growth engines roll up business models and channels. Claim grades run weakest to strongest. Search Console access corroborates traffic and sits outside the grade ladder.

Concept and stable ID	Definition	Extension
Business model · sbc:business-model
How the business is structured to make money -- the shape of the offer, not how it charges (see sbc:revenue-model) or who it sells to (see sbc:target-market).
SaaS `sbc:business-model-saas`	Hosted software sold as a recurring subscription product.	Private.
Micro-SaaS `sbc:business-model-micro-saas`	A small, narrowly-scoped SaaS product, typically solo-built and solo-maintained.	Private.
AI wrapper `sbc:business-model-ai-wrapper`	A product whose core value is a thin, purpose-built interface over a third-party foundation model API.	Private.
Agency `sbc:business-model-agency`	A services business delivering custom work for clients under an agency structure.	Private.
Productized service `sbc:business-model-productized-service`	A human-delivered service sold with fixed scope and fixed pricing, packaged like a product.	Private.
E-commerce `sbc:business-model-ecommerce`	Sells physical or digital goods directly to consumers online.	Private.
Dropshipping `sbc:business-model-dropshipping`	E-commerce where the seller never holds inventory; a third party fulfills orders.	Private.
Amazon FBA `sbc:business-model-amazon-fba`	Products sold on Amazon and fulfilled through Fulfillment by Amazon.	Private.
Info product `sbc:business-model-info-product`	Sells packaged knowledge (guides, templates, paid newsletters) as a standalone digital good.	Private.
Course `sbc:business-model-course`	Sells structured, typically video-led educational content.	Private.
Community `sbc:business-model-community`	Sells paid access to a member community as the core product.	Private.
Newsletter / media `sbc:business-model-newsletter-media`	A media property whose core product is a distributed newsletter or publication.	Private.
Content sites / SEO `sbc:business-model-content-sites-seo`	A network or portfolio of content sites monetized primarily through organic search traffic.	Private.
Marketplace `sbc:business-model-marketplace`	Connects two or more sides of a transaction and takes a cut or fee.	Private.
Directory `sbc:business-model-directory`	A curated listing product monetized by placement, subscription, or lead fees.	Private.
Templates / boilerplates `sbc:business-model-templates-boilerplates`	Sells reusable code, design, or document templates as the product.	Private.
Affiliate business `sbc:business-model-affiliate`	A business built primarily to earn affiliate commissions by referring buyers to other products.	Private.
Mobile app `sbc:business-model-app-mobile`	A native or cross-platform mobile application is the core product.	Private.
Browser extension `sbc:business-model-chrome-extension`	A browser extension is the core product.	Private.
API `sbc:business-model-api`	Sells programmatic access to data or functionality as the core product.	Private.
Other business model `sbc:business-model-other`	Catch-all for a business model not covered above; a free-text label accompanies the assignment.	Private.
Revenue model · sbc:revenue-model
How the business charges money for what it sells. Distinct from fin: money-movement vocabulary (fin:bank-transfer, fin:hosted-payment-link, etc.), which describes how a payment is executed once a charge exists -- not what kind of commercial arrangement generated it. fin:Subscription (a class describing a recurring commitment as a record) and sbc:revenue-model-subscription (a concept classifying a business's monetization strategy) describe the same underlying idea at different layers (instance/record vs. controlled vocabulary/classification), so this concept is kept local rather than mapped as a narrowing of a class.
Subscription `sbc:revenue-model-subscription`	Recurring, typically monthly or annual, billing for continued access.	Private.
One-time purchase `sbc:revenue-model-one-time`	A single charge for permanent or lifetime access to a fixed deliverable.	Private.
Usage-based `sbc:revenue-model-usage-based`	Billing scales with metered consumption (API calls, seats-active, credits used).	Private.
Advertising `sbc:revenue-model-ads`	Revenue from selling attention or placement to advertisers.	Private.
Sponsorship `sbc:revenue-model-sponsorship`	Revenue from a paid sponsor backing content, an episode, or an issue.	Private.
Affiliate commission `sbc:revenue-model-affiliate`	Revenue earned as a commission for referring a buyer to someone else's product.	Private.
Services retainer `sbc:revenue-model-services-retainer`	A recurring fee for ongoing service delivery, billed like a subscription but for labor.	Private.
Transaction fee `sbc:revenue-model-transaction-fee`	A per-transaction cut taken on money moving through the platform.	Private.
Lifetime deal `sbc:revenue-model-lifetime-deal`	A one-time payment marketed explicitly as permanent access, often sold through a deal platform.	Private.
Mixed `sbc:revenue-model-mixed`	No single revenue model dominates; the business combines two or more materially.	Private.
Target market · sbc:target-market
Who the business primarily sells to.
B2B - SMB `sbc:target-market-b2b-smb`	Sells to small and medium businesses.	Private.
B2B - enterprise `sbc:target-market-b2b-enterprise`	Sells to large organizations with enterprise procurement.	Private.
B2C `sbc:target-market-b2c`	Sells directly to individual consumers.	Private.
Prosumer `sbc:target-market-prosumer`	Sells to power-user individuals who buy like consumers but use the product professionally.	Private.
Creators `sbc:target-market-creators`	Sells to independent content creators.	Private.
Developers `sbc:target-market-developers`	Sells to software engineers as the primary buyer/user.	Private.
Indie hackers `sbc:target-market-indie-hackers`	Sells to solo/small-team independent builders as the primary buyer.	Private.
Marketers `sbc:target-market-marketers`	Sells to marketing professionals as the primary buyer.	Private.
Agencies `sbc:target-market-agencies`	Sells to agencies as the primary buyer.	Private.
E-commerce sellers `sbc:target-market-ecommerce-sellers`	Sells to people who run online stores as the primary buyer.	Private.
Other target market `sbc:target-market-other`	Catch-all for a target market not covered above; a free-text label accompanies the assignment.	Private.
Acquisition channel · sbc:acquisition-channel
How the business or founder attracts customers/attention. This classifies a founder's public growth activity for their own business, a different domain from loop:business-category (which classifies our internal automation workflows) or sys:discoverability functions (which classify shared products like GA4/GSC we operate) -- kept local rather than mapped to either.
Build in public on X `sbc:acquisition-channel-x-build-in-public`	Grows through public, transparent progress-sharing on X/Twitter.	Private.
SEO `sbc:acquisition-channel-seo`	Grows through organic search visibility for a small number of high-intent pages.	Private.
Programmatic SEO `sbc:acquisition-channel-programmatic-seo`	Grows through a large, templated set of search-targeted pages generated at scale.	Private.
Paid ads `sbc:acquisition-channel-paid-ads`	Grows through paid advertising placements.	Private.
Affiliate program `sbc:acquisition-channel-affiliates`	Grows by recruiting others to refer buyers for a commission.	Private.
Product Hunt `sbc:acquisition-channel-product-hunt`	Grows through launches on Product Hunt.	Private.
YouTube `sbc:acquisition-channel-youtube`	Grows through a YouTube channel.	Private.
LinkedIn `sbc:acquisition-channel-linkedin`	Grows through LinkedIn posting/outreach.	Private.
Newsletter `sbc:acquisition-channel-newsletter`	Grows through a personally-run email newsletter.	Private.
Cold email `sbc:acquisition-channel-cold-email`	Grows through direct, unsolicited outbound email.	Private.
Marketplaces `sbc:acquisition-channel-marketplaces`	Grows by listing on a third-party marketplace's built-in demand.	Private.
Word of mouth `sbc:acquisition-channel-word-of-mouth`	Grows primarily through unprompted referral between users.	Private.
Launch directories `sbc:acquisition-channel-launch-directories`	Grows through submission to startup/tool launch directories.	Private.
Team constellation · sbc:team-constellation
The shape of the people behind a business. Concept values summarize the pattern of fw:coFounderOf and fw:memberOf edges attached to the founder/business rather than restating them; the edges themselves are reused, not re-modeled here.
Solo `sbc:team-constellation-solo`	One person, no cofounders, no contractors.	Private.
Solo + contractors `sbc:team-constellation-solo-contractors`	One owner/operator with paid contractors, no cofounders.	Private.
Solo + VA `sbc:team-constellation-solo-va`	One owner/operator with virtual-assistant support, no cofounders.	Private.
Two cofounders `sbc:team-constellation-cofounders-2`	Exactly two people hold a fw:coFounderOf relation to the business.	Private.
Three or more cofounders `sbc:team-constellation-cofounders-3plus`	Three or more people hold a fw:coFounderOf relation to the business.	Private.
Small team (2-10) `sbc:team-constellation-small-team`	A staffed team of 2 to 10 people beyond the founder(s).	Private.
Team (11+) `sbc:team-constellation-team-11plus`	A staffed team of 11 or more people beyond the founder(s).	Private.
Unknown `sbc:team-constellation-unknown`	Team shape has not been established from any source.	Private.
Claim verification level · sbc:claim-verification · weakest to strongest
The grade of a revenue claim: how strongly its figure is substantiated. Ordered weakest to strongest; the leaderboard band narrows as the grade rises. Search Console access is not a grade (see sbc:supporting-evidence).
1 · Self-reported text `sbc:claim-verification-self-reported-text`	The founder states the figure in words, with no corroborating artifact.	Private. Product values: `self-reported-text`, `unverified`.
2 · Self-reported screenshot `sbc:claim-verification-self-reported-screenshot`	The founder publishes a screenshot of a revenue dashboard. The image is unverifiable at source.	Private. Product values: `self-reported-screenshot`, `screenshot`.
3 · Press-reported `sbc:claim-verification-press-reported`	An independent press or media outlet reports the figure.	Private. Product values: `press-reported`.
4 · Public dashboard `sbc:claim-verification-public-dashboard`	A live, publicly accessible dashboard published by the business shows the metric.	Private. Product values: `public-dashboard`.
5 · Payment-processor verified `sbc:claim-verification-payment-processor`	The figure is read at source from Stripe, Paddle or Lemon Squeezy, through a restricted read-only key granted to the verifier or a TrustMRR connection.	Private. Product values: `trustmrr`, `stripe-readonly`. TrustMRR is a Stripe-connected read verification, so it shares this grade rather than forming its own.
6 · Open banking `sbc:claim-verification-open-banking`	Monthly inflows are read from a read-only open-banking account-information consent with any provider, or from a redacted bank statement.	Private. Product values: `open-banking`. Broader than fin:plaid-sync (Plaid only), so it is private rather than a narrowing.
7 · Accountant attestation `sbc:claim-verification-accountant-attestation`	A named, credentialed accountant signs a letter stating revenue for a named period.	Private. Product values: `accountant-attestation`, `accountant-letter`. Private, not a narrowing of fin:manual-entry, which describes internal operator entries in finance-mgmt.
Supporting evidence · sbc:supporting-evidence
Evidence that raises confidence in a revenue claim's plausibility but never grades a revenue figure by itself.
Search Console read access `sbc:supporting-evidence-gsc-readonly`	Read-only Google Search Console access to the business's domain, granted to a verifier. Evidences traffic, not revenue.	Private. Product values: `gsc-readonly`. Concepts cannot skos:broadMatch a fw:SystemProduct, so the link to sys:gsc is made at the instance layer: the sbc:VerificationEvidence record uses fw:usesSystem.
Registry match `sbc:supporting-evidence-registry-match`	The business and founder match a public company registry record (name, officers, status). Evidences who owns the business, not its revenue.	Private. Product values: `registry-match`.
Claim metric · sbc:claim-metric
Which figure a revenue claim reports.
MRR `sbc:claim-metric-mrr`	Monthly recurring revenue.	Private.
ARR `sbc:claim-metric-arr`	Annual recurring revenue.	Private.
Monthly revenue `sbc:claim-metric-monthly-revenue`	Total revenue in a calendar month, not necessarily recurring.	Private.
Profit `sbc:claim-metric-profit`	Revenue less costs for a stated period.	Private.
Lifetime `sbc:claim-metric-lifetime`	Cumulative revenue or profit since inception.	Private.
Exit `sbc:claim-metric-exit`	A sale price realized on acquisition of the business.	Private.
Tip category · sbc:tip-category
What kind of advice a founder tip falls under.
Distribution `sbc:tip-category-distribution`	Advice about getting the product in front of people.	Private.
Pricing `sbc:tip-category-pricing`	Advice about setting or changing price.	Private.
Product `sbc:tip-category-product`	Advice about what to build or how to build it.	Private.
SEO `sbc:tip-category-seo`	Advice specific to organic search growth.	Private.
AI leverage `sbc:tip-category-ai-leverage`	Advice about using AI tools to do more with less headcount.	Private.
Hiring `sbc:tip-category-hiring`	Advice about bringing on contractors or staff.	Private.
Mindset `sbc:tip-category-mindset`	Advice about founder psychology, motivation, or decision-making habits.	Private.
Launch `sbc:tip-category-launch`	Advice about launching a product or feature.	Private.
Retention `sbc:tip-category-retention`	Advice about keeping existing customers.	Private.
Race tier · sbc:race-tier · ascending
The revenue milestone board a founder or business is racing toward, ordered ascending.
1 · The Million board `sbc:race-tier-million`	Tracking toward $1M in the claimed metric.	Private.
2 · The Ten-Million board `sbc:race-tier-ten-million`	Tracking toward $10M in the claimed metric.	Private.
3 · The Hundred-Million board `sbc:race-tier-hundred-million`	Tracking toward $100M in the claimed metric.	Private.
4 · The Billion board `sbc:race-tier-billion`	Tracking toward $1B in the claimed metric.	Private.
Industry · sbc:industry
The industry the business serves: what its customers care about, independent of what it delivers (see sbc:offer-form) or how it finds them (see sbc:growth-engine). Values narrow an IAB Tech Lab Content Taxonomy 3.0 tier-1 category where the match is one to one; the tier-1 name is the notation. Values sharing a tier-1 parent, or with none, are private.
Sports and fitness `sbc:industry-sports-and-fitness`	Customers who play, train for or follow sports, including gyms, coaching apps and endurance events.	Narrow · skos:broadMatch `iab:483`. IAB Content Taxonomy 3.0 tier 1: Sports.
Health and wellness `sbc:industry-health-and-wellness`	Consumer health outside clinical care: nutrition, sleep, mental wellbeing, habits.	Narrow · skos:broadMatch `iab:223`. IAB Content Taxonomy 3.0 tier 1: Healthy Living.
Beauty and personal care `sbc:industry-beauty-and-personal-care`	Skincare, cosmetics, grooming and personal-care products or services.	Private.
Fashion and apparel `sbc:industry-fashion-and-apparel`	Clothing, footwear, accessories and style.	Narrow · skos:broadMatch `iab:552`. IAB Content Taxonomy 3.0 tier 1: Style & Fashion.
Food and drink `sbc:industry-food-and-drink`	Food, beverages, cooking, restaurants and hospitality.	Narrow · skos:broadMatch `iab:210`. IAB Content Taxonomy 3.0 tier 1: Food & Drink.
Travel `sbc:industry-travel`	Trips, accommodation, transport bookings and travel planning.	Narrow · skos:broadMatch `iab:653`. IAB Content Taxonomy 3.0 tier 1: Travel.
Home and garden `sbc:industry-home-and-garden`	Homes, interiors, DIY, gardening and household goods.	Narrow · skos:broadMatch `iab:274`. IAB Content Taxonomy 3.0 tier 1: Home & Garden.
Family and parenting `sbc:industry-family-and-parenting`	Parents, children, relationships and family life.	Narrow · skos:broadMatch `iab:186`. IAB Content Taxonomy 3.0 tier 1: Family and Relationships.
Pets `sbc:industry-pets`	Pet owners and animal care.	Narrow · skos:broadMatch `iab:422`. IAB Content Taxonomy 3.0 tier 1: Pets.
Personal finance `sbc:industry-personal-finance`	Individuals managing their own money: budgeting, investing, tax, retirement.	Narrow · skos:broadMatch `iab:391`. IAB Content Taxonomy 3.0 tier 1: Personal Finance.
Business and finance `sbc:industry-business-and-finance`	Company finance, payments, commerce infrastructure and running a business.	Narrow · skos:broadMatch `iab:52`. IAB Content Taxonomy 3.0 tier 1: Business and Finance.
Real estate `sbc:industry-real-estate`	Buying, selling, renting or managing property.	Narrow · skos:broadMatch `iab:441`. IAB Content Taxonomy 3.0 tier 1: Real Estate.
Careers and hiring `sbc:industry-careers-and-hiring`	Job seekers, recruiting, remote work and career development.	Narrow · skos:broadMatch `iab:123`. IAB Content Taxonomy 3.0 tier 1: Careers.
Education and learning `sbc:industry-education-and-learning`	Learners and educators: schools, test prep, language learning, skills training.	Narrow · skos:broadMatch `iab:132`. IAB Content Taxonomy 3.0 tier 1: Education.
Marketing and sales `sbc:industry-marketing-and-sales`	Teams and tools for marketing, advertising, lead generation and sales.	Private.
Developer tools `sbc:industry-developer-tools`	Software developers and engineering teams: tooling, infrastructure, APIs.	Private.
AI and data `sbc:industry-ai-and-data`	Products whose customer problem is AI, machine learning, analytics or data handling.	Private.
Productivity and work `sbc:industry-productivity-and-work`	Personal and team productivity: notes, scheduling, collaboration, workflow.	Private.
Creator economy `sbc:industry-creator-economy`	Independent creators and the tools, platforms and services they buy.	Private.
Media and entertainment `sbc:industry-media-and-entertainment`	Audiences consuming news, video, film, TV, books or entertainment.	Narrow · skos:broadMatch `iab:JLBCU7`. IAB Content Taxonomy 3.0 tier 1: Entertainment.
Gaming `sbc:industry-gaming`	Video game players, studios and gaming communities.	Narrow · skos:broadMatch `iab:680`. IAB Content Taxonomy 3.0 tier 1: Video Gaming.
Music and audio `sbc:industry-music-and-audio`	Musicians, listeners, podcasters and audio production.	Private.
Arts and design `sbc:industry-arts-and-design`	Artists and designers: visual art, graphic, product and UI design.	Private.
Automotive `sbc:industry-automotive`	Car owners, buyers, dealers and vehicle services.	Narrow · skos:broadMatch `iab:1`. IAB Content Taxonomy 3.0 tier 1: Automotive.
Legal `sbc:industry-legal`	Legal services, compliance and people dealing with the law.	Narrow · skos:broadMatch `iab:383`. IAB Content Taxonomy 3.0 tier 1: Law.
Healthcare and medical `sbc:industry-healthcare-and-medical`	Clinical care: patients, practitioners, providers and medical compliance.	Narrow · skos:broadMatch `iab:286`. IAB Content Taxonomy 3.0 tier 1: Medical Health.
Crypto and web3 `sbc:industry-crypto-and-web3`	Cryptocurrency, blockchain and web3 users and builders.	Private.
Nonprofit and civic `sbc:industry-nonprofit-and-civic`	Nonprofits, charities, government and civic organisations.	Private.
General B2B `sbc:industry-general-b2b`	Businesses in general, with no single industry dominating the customer base.	Private.
Founder archetype · sbc:founder-archetype
The founder's edge: the skill or asset that got the business its first customers.
Builder / engineer `sbc:founder-archetype-builder-engineer`	Edge is building the product: writes the code or ships the thing personally.	Private.
Creator / influencer `sbc:founder-archetype-creator-influencer`	Edge is an audience the founder built as a creator (social, video, newsletter) before or alongside the business.	Private.
Marketer / growth `sbc:founder-archetype-marketer-growth`	Edge is marketing, sales or growth skill applied to the business or sold as a service.	Private.
Domain expert `sbc:founder-archetype-domain-expert`	Edge is expertise in the field served: teacher, coach, doctor, lawyer, athlete or similar practitioner.	Private.
Designer `sbc:founder-archetype-designer`	Edge is design: visual, product or brand craft drives the offer.	Private.
Merchant / operator `sbc:founder-archetype-merchant-operator`	Edge is sourcing, operations and retail execution for physical or commerce businesses.	Private.
Media publisher `sbc:founder-archetype-media-publisher`	Edge is running content properties that earn from audience attention.	Private.
Acquirer / investor `sbc:founder-archetype-acquirer-investor`	Edge is buying or funding businesses rather than starting them from zero.	Private.
Growth engine · sbc:growth-engine
A business's single primary source of customers. A stricter reading of sbc:acquisition-channel: channels list everything the business uses, the engine names the one that matters most. Rolls up `sbc:acquisition-channel`.
Founder audience `sbc:growth-engine-founder-audience`	Customers come mainly from the founder's own following.	Private. Rolls up `sbc:acquisition-channel-x-build-in-public`, `sbc:acquisition-channel-youtube`, `sbc:acquisition-channel-linkedin`, `sbc:acquisition-channel-newsletter`.
Content and SEO `sbc:growth-engine-content-and-seo`	Customers come mainly from search traffic to content the business publishes.	Private. Rolls up `sbc:acquisition-channel-seo`, `sbc:acquisition-channel-programmatic-seo`.
Paid acquisition `sbc:growth-engine-paid-acquisition`	Customers come mainly from paid advertising.	Private. Rolls up `sbc:acquisition-channel-paid-ads`.
Platform marketplace `sbc:growth-engine-platform-marketplace`	Customers come mainly from a third-party store or marketplace: App Store, Amazon, Shopify App Store, Chrome Web Store, Etsy.	Private. Rolls up `sbc:acquisition-channel-marketplaces`.
Community `sbc:growth-engine-community`	Customers come mainly from communities and launch venues the founder takes part in.	Private. Rolls up `sbc:acquisition-channel-product-hunt`, `sbc:acquisition-channel-launch-directories`.
Partners and affiliates `sbc:growth-engine-partners-and-affiliates`	Customers come mainly through partners or affiliates paid to refer them.	Private. Rolls up `sbc:acquisition-channel-affiliates`.
Sales-led `sbc:growth-engine-sales-led`	Customers come mainly from outbound or direct sales.	Private. Rolls up `sbc:acquisition-channel-cold-email`.
Product-led virality `sbc:growth-engine-product-led-virality`	Customers come mainly from existing users spreading the product.	Private. Rolls up `sbc:acquisition-channel-word-of-mouth`.
Offer form · sbc:offer-form
What the business delivers to its customer. A roll-up of sbc:business-model that separates the offer from how it is priced. Every business model rolls up to one offer form, with two exceptions. Directory depends on the revenue model: fees paid by listers go to marketplace take rate, ads or affiliate income to media and ads. Other rolls up to nothing. Rolls up `sbc:business-model`.
Software `sbc:offer-form-software`	Delivers software: hosted apps, mobile apps, extensions or APIs.	Private. Rolls up `sbc:business-model-saas`, `sbc:business-model-micro-saas`, `sbc:business-model-ai-wrapper`, `sbc:business-model-app-mobile`, `sbc:business-model-chrome-extension`, `sbc:business-model-api`.
Physical goods `sbc:offer-form-physical-goods`	Delivers physical products shipped to the customer.	Private. Rolls up `sbc:business-model-ecommerce`, `sbc:business-model-dropshipping`, `sbc:business-model-amazon-fba`.
Digital goods `sbc:offer-form-digital-goods`	Delivers downloadable digital products: templates, boilerplates, ebooks.	Private. Rolls up `sbc:business-model-info-product`, `sbc:business-model-templates-boilerplates`.
Education `sbc:offer-form-education`	Delivers teaching: courses, cohorts and coaching.	Private. Rolls up `sbc:business-model-course`.
Service `sbc:offer-form-service`	Delivers work done for the client, custom or productized.	Private. Rolls up `sbc:business-model-agency`, `sbc:business-model-productized-service`.
Media and ads `sbc:offer-form-media-and-ads`	Delivers content to an audience and earns from ads, sponsors or affiliate links.	Private. Rolls up `sbc:business-model-newsletter-media`, `sbc:business-model-content-sites-seo`, `sbc:business-model-affiliate`, `sbc:business-model-directory`. Includes directory when it earns from ads or affiliate links; see the sbc:offer-form note.
Community membership `sbc:offer-form-community-membership`	Delivers access to a paid community or membership.	Private. Rolls up `sbc:business-model-community`.
Marketplace take rate `sbc:offer-form-marketplace-take-rate`	Delivers a marketplace or listing venue and earns a cut or fee from its participants.	Private. Rolls up `sbc:business-model-marketplace`, `sbc:business-model-directory`. Includes directory when listers pay the fees; see the sbc:offer-form note.
Revenue quality · sbc:revenue-quality
What a claimed revenue figure is made of. The product stores each component as a share of the claim; taxonomy names the components.
Recurring `sbc:revenue-quality-recurring`	Revenue from subscriptions or retainers expected to repeat.	Private. Product values: `recurring`.
One-off `sbc:revenue-quality-one-off`	Revenue from single purchases that do not repeat by default.	Private. Product values: `one_off`.
Affiliate `sbc:revenue-quality-affiliate`	Commission earned for referring customers to another business.	Private. Product values: `affiliate`.
Refund `sbc:revenue-quality-refund`	Money returned to customers, netted against gross revenue.	Private. Product values: `refunds`.
Net worth · sbc:net-worth
Total assets minus liabilities of a person. SBC publishes only sourced evidence of it and a modelled wealth scale, never a point figure. The concepts name the kinds of net-worth evidence. Savings, investments, property and debt are not observable, so no point figure is derived from these kinds.
Self-disclosed net worth `sbc:net-worth-self-disclosed`	A net-worth figure the person states themselves, shown with its source URL, as_of date and grade.	Private.
Exit proceeds `sbc:net-worth-exit-proceeds`	The disclosed sale price or payout a person received from selling a business. It counts toward the wealth scale and is not their net worth.	Private.
Third-party estimate `sbc:net-worth-third-party-estimate`	A net-worth figure from an estimate site, labelled estimate and shown as a spread across sources, never as one number.	Private.
Wealth scale · sbc:wealth-scale · ascending
A modelled five-tier scale of a founder's wealth, ordered ascending. Computed from graded revenue bands times a multiple plus disclosed exit proceeds. It leaves out savings, investments, property and debt, so it is a scale and not a net-worth figure.
1 · Under $1M `sbc:wealth-scale-under-1m`	Modelled wealth below $1M.	Private. Product values: `under-1m`.
2 · $1M to $10M `sbc:wealth-scale-1m-10m`	Modelled wealth from $1M up to $10M.	Private. Product values: `1m-10m`.
3 · $10M to $100M `sbc:wealth-scale-10m-100m`	Modelled wealth from $10M up to $100M.	Private. Product values: `10m-100m`.
4 · $100M to $1B `sbc:wealth-scale-100m-1b`	Modelled wealth from $100M up to $1B.	Private. Product values: `100m-1b`.
5 · $1B or more `sbc:wealth-scale-1b-plus`	Modelled wealth of $1B or more.	Private. Product values: `1b-plus`.
Founder path · sbc:founder-path
How the founder got to the current business. A founder may carry more than one path. Complements sbc:founder-archetype, which names their edge.
First-time founder `sbc:founder-path-first-time`	The current business is their first venture.	Private.
Serial builder `sbc:founder-path-serial-builder`	Has launched several ventures, none of them sold.	Private.
Serial exiter `sbc:founder-path-serial-exiter`	Has two or more business exits graded confirmed.	Private.
Employee spinout `sbc:founder-path-employee-spinout`	Left a job to build in the same field or for the same customers.	Private.
Agency to product `sbc:founder-path-agency-to-product`	Turned a services or agency business into a product.	Private.
Creator to product `sbc:founder-path-creator-to-product`	Built an audience first and then sold a product to it.	Private.
Acquirer-operator `sbc:founder-path-acquirer-operator`	Buys existing businesses and runs or grows them.	Private.
Exit verification · sbc:exit-verification · ascending
How well a business exit is evidenced, ordered ascending. A founder's confirmed exits are the count of their exits graded confirmed.
1 · Claimed `sbc:exit-verification-claimed`	The founder says the business was sold. No buyer or third party on record.	Private. Product values: `claimed`.
2 · Reported `sbc:exit-verification-reported`	Press, a podcast or a broker report names the sale with a source.	Private. Product values: `reported`.
3 · Confirmed `sbc:exit-verification-confirmed`	The buyer announced it, a marketplace or filing records the close, or both parties are on record.	Private. Product values: `confirmed`.

Boundary: Taxonomy owns these terms only. Founder profiles, revenue claims, verification evidence and race entries stay in the Solo Billionaire Club store, which pins a byte-identical copy of this manifest.

Production evidence

REP proves more than the draft said.

Read from the production taxonomy surface on 31 Aug 2026—evidence, not a hand-maintained replacement.

rep-fitness-fm · version 40

9 pillars · 8 dimensions · 39 audit events returned

Pillars

Get Foundget_found
Win AI Answerswin_ai_answers
Earn Trustearn_trust
Convert Betterconvert_better
Build Communitybuild_community
Grow Revenuegrow_revenue
Ambassador / Affiliate / Partnerspartnerships
Operationsoperations
Measurementmeasurement

Dimensions

E-E-A-T4 values
Partner Type2 values
REP Owner2 values
REP Domain Owner5 values
Systems34 values
KPIs4 values
GTM Phase3 values
Access (read/write)33 values

Board definitionspillars_json + dimensions_config_json

Card assignmentspillars_json + dimensions_json

Concurrencyexpected_taxonomy_version on every edit

Safe operationsPreview/commit planning, guarded deletes, audit trail

Authority: growth-engine's database/API owns live REP vocabulary; the dashboard proxies it. retaxonomy_rep_board.py is seed-only and, at version 40, refuses a normal write unless explicitly forced.

Namespace correction: the 34-value REP Systems dimension is operational client data, not the shared fleet catalog. Shared products resolve to sys:; REP-only products, deployments, access state, and detected scripts resolve to rep:.

Implementation contract

Store lineage; generate snapshots.

Static profiles can keep terms in a manifest. Dynamic profiles expose an adapter from their authoritative store.

Illustrative manifest · location and namespace owner still to approve

{
  "id": "rep",
  "version": "runtime:40",
  "extends": "client-boards@1",
  "source": {
    "kind": "growth-engine-opportunity-taxonomy",
    "program": "rep-fitness-fm"
  },
  "constraints": {
    "pillarCardinality": { "min": 1, "primary": 0 },
    "dimensionValuesMustBeDeclared": true
  }
}

Validator fails on

unknown parent or cyclic ancestry;
ancestor redefinition;
wrong class/concept narrowing relation;
duplicate IDs or unresolved targets;
runtime assignments outside declared values.

Resolver emits

effective vocabulary with provenance;
parent chain and inheritance distance;
CI conformance report;
generated read-only REP snapshot;
deprecation and replacement notices.

Approve v1 semantics.One parent, three modes, typed relations, no overrides.
Name the core owner and namespace.Do this before identifiers become load-bearing.
Publish the systems manifest.Start with the repository-backed sys: terms above and require source provenance for promotion.
Implement the finance adapter.Resolve the two account registries into protected canonical instances; export only safe aliases, types, and relations.
Implement core + client-boards.Establish the validator without duplicating dynamic data.
Add read-only REP, ac, and eoe adapters.Export local instances and vocabularies; keep operational edits in their authoritative systems.
Add fwm and tpr only for real terms.Instances and infrastructure do not justify vocabulary by themselves.

Open: who approves wtf-core, which stable namespace mints IDs, and whether fwm's legal/brand relation has documentary support.

Evidence + standards

Grounded in semantics and production.

Standards set the boundaries; executable source and configuration establish systems and profile facts. Dependencies, generated output, and prose-only mentions were excluded from promotion decisions.

Standards

W3C SKOS Reference — schemes, concepts, hierarchy, mapping.
W3C OWL 2 Primer — classes, instances, domain, range.
W3C SHACL — constraints and conformance reports.
Schema.org containedInPlace — place-to-place containment.

Fleet evidence

finance-mgmt/dashboard/migrations/, app.py, payout adapters, and live safe aggregates — accounts, ledger, payments, subscriptions, and payroll.
bi/src/bi/, growth-engine/src/, websites-lib/, and site configs — analytics, search, and data systems.
domain-ops/, cloudflare-mgmt/, security-mgmt/, email-ops/, and team-mgmt/ — operational systems.
ops-mgmt/rep_dashboard/app.py — confirmed and detected REP-local systems with evidence state.
andicross.com/src/pages/ and edgesofearth.com/src/data/ — profile terms and instances.

Adopt the contract, not a second database.

Core + profiles

Separate the layers

REP stays authoritative

Orbit means inheritance distance.

Resolved site vocabularies

Three layers, three jobs.

Classes + properties

Concept schemes

Instances + assignments

A child gets exactly three choices.

Same ID, same meaning

New ID, stricter meaning

New ID, local meaning

Small, typed, and boring.

Products are shared. Deployments are local.

sys:ga4

eoe:ga4-property

sys:measurement

Measurement + behavior 5 products

Search + discoverability 6 products

Data + persistence 7 products

Edge, identity + domains 6 products

Content + publishing 2 products

Work + customer operations 4 products

Finance + payments 3 products

Communication + delivery 3 products

Specialist APIs 3 products

REP's commerce stack stays rep:.

Accounts, owners, payment options, and shared language.

Where value is held

Who holds or controls it

How money moves

Terms people can share

The values the system actually accepts.

Actual accounting scopes

Registered account-holder agents

Suggestions are not closed vocabulary.

Two registries, one conceptual account.

fin:fw-airwallex-usd

fin:eoe-boa-small-business

Rail, method, and observation are different axes.

One term for each financial idea.

Trace technology spend to the service and its consumer.

Loop categories

Extend only where local meaning exists.

systems · shared catalog

finance · accounts and money flow

fwm

tpr

ac · Andi Cross

eoe · Edges of Earth

sbc · Solo Billionaire Club

client-boards

rep

A person profile with explicit concept boundaries.

Person + property

Public positioning

Edges of Earth

Five live writing themes

Extension semantics

A real content vocabulary, not merely a domain.

Story Type + Impact Area

Geographic hierarchy

People, partners, stories

Six live impact concepts

Extension semantics

Other people's companies, graded by evidence.

Fleet edges reused, local facts minted.

Private values, IAB-matched industries.

REP proves more than the draft said.

rep-fitness-fm · version 40

Pillars

Dimensions

Store lineage; generate snapshots.

Validator fails on

Resolver emits

Grounded in semantics and production.

Standards

Fleet evidence

`sys:ga4`

`eoe:ga4-property`

`sys:measurement`

REP's commerce stack stays `rep:`.

`fin:fw-airwallex-usd`

`fin:eoe-boa-small-business`