Platform Governance Board¶
Institution — instantiates Shared-Input Variety Platform Design
Sets priorities, standards, funding, exception decisions, and retirement rules for the shared layer.
A Platform Governance Board is a standing, cross-stakeholder body holding the authority to set priorities, standards, and funding for the shared layer, to adjudicate exception and fork requests, and to own the register of correlated risks the shared inputs create. Its defining move is being the human decision authority that stewards the commons — it decides, funds, and rules; it does not build the platform or compute its costs. The board exists because a shared layer without an accountable owner drifts toward either underfunded neglect or a political battleground, and someone has to be the place where those conflicts are settled on the record.
Example¶
A city government runs a shared civic platform — single sign-on identity, payments, notifications, and open-data services — across departments for transportation, parks, permits, and benefits. The departments quarrel over the platform team's priorities; one wants to store resident data outside the shared identity system; and a single shared-component outage once took down permits and benefits simultaneously.
The city charters a Platform Governance Board: the CTO, a delegate from each major department, and a security lead. It sets the platform's funding and standards, rules on the data-storage request by granting a scoped carve-out with conditions and a review date, and maintains a coupling-risk register with blast-radius limits so no single shared component can cascade across services again. Outcome: decisions that had been recurring political skirmishes become chartered rulings with a written rationale and a precedent others can rely on.
How it works¶
- Convene the stakeholders with real decision rights over funding, standards, exceptions, and retirement — not an advisory forum, but a body whose rulings bind.
- Adjudicate exception and fork requests against explicit criteria, so carve-outs are granted for genuine local fit rather than for whoever pushes hardest.
- Own the coupling-risk register, enforcing blast-radius limits, redundancy, and validation on shared inputs that could fail many outputs at once.
- Record decisions so precedent accumulates and later requests are judged consistently.
Tuning parameters¶
- Membership composition — who sits on it (shared-layer team versus output-team delegates). A composition skewed toward the center overrides local needs; skewed toward users starves the commons.
- Decision-rights scope — advisory versus binding, and whether the board controls the budget. Responsibility without funding authority is accountability with no power.
- Exception bar — how readily local-fit carve-outs are granted; loose erodes the shared layer, tight forces bad fits.
- Decision SLA and cadence — how fast the board rules. A slow board becomes the bottleneck it was meant to prevent.
- Standard strictness — how prescriptive the shared standards are, trading interoperability against local freedom.
When it helps, and when it misleads¶
Its strength is that it gives the commons an accountable owner: priorities get set once instead of relitigated per project, free-riding is checked, exceptions are principled, and correlated risk has a body watching it. It is the institution that keeps a shared layer from being either everyone's and therefore no one's, or a monoculture nobody may deviate from.
Its failure mode is the archetype's warning about premature centralization made flesh — the board becomes a slow, politicized bottleneck that turns the shared layer into a battleground, or it under-funds the commons because every department free-rides and none will pay (the tragedy of the commons[n1]). The classic misuse is chartering a board with responsibility but no budget authority, so it can be blamed for the platform yet cannot resource it. The guarding discipline is bounded decision SLAs, explicit and published exception criteria, and real funding authority commensurate with its accountability.
How it implements the components¶
shared_layer_stewardship— the board is the stewardship authority: it sets priorities, funding, standards, and retirement policy for the shared layer.local_fit_exception_path— it is the body that adjudicates and grants scoped exceptions and forks against explicit criteria.coupling_risk_register— it owns the register of correlated risks and enforces the blast-radius and redundancy rules on shared inputs.
It does not draft the time-phased build schedule (common_capability_layer, portfolio_complementarity_map — that is Common Platform Roadmap) nor compute the cost split it funds against (scope_benefit_metric, allocation_and_chargeback_rule — Cross-Output Cost Attribution Model); the board decides and rules, it does not author the calendar or run the sums.
Related¶
- Instantiates: Shared-Input Variety Platform Design — the board is the governing authority over the whole shared layer.
- Consumes: Cross-Output Cost Attribution Model supplies the net-benefit evidence the board funds and prioritizes against.
- Sibling mechanisms: Common Platform Roadmap · Cross-Output Cost Attribution Model · Joint Procurement or Tooling Pool · Modular Capability Library · Product-Line Architecture · Reuse Intake and Fit Assessment · Shared Data or Feature Store · Shared Service Catalog · Stovepipe Retirement Migration Plan
Editorial Notes¶
Form Classification¶
Form family: Organization, Role & Governance
Rationale: Platform Governance Board operates as an enduring role, team, authority, channel, or governance body that allocates responsibility because it sets priorities, standards, funding, exception decisions, and retirement rules for the shared layer.
Independent corroboration: The frozen evidence defines Platform Governance Board as 'Sets priorities, standards, funding, exception decisions, and retirement rules for the shared layer', so its operative form is Organization, Role & Governance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Platform Governance Board is rooted in organizational and management science: Organizational governance creates an accountable steward for priorities, standards, funding, exceptions, and retirement.
Related originating lineages:
- Economics & Finance — Economics and finance materially shaped Platform Governance Board through incentives, contracts, markets, valuation, and strategic choice.
- Law & Governance — Delegated authority, representation, and procedural rules materially shape board legitimacy.
- Political Science — Political science materially shaped Platform Governance Board through power, collective choice, legitimacy, and coalition structure.
Review resolution: Both blind reviewers agree that organizational and management practice is the primary origin. Reconciliation resolves alternate_origin_disagreement, domain_reach_disagreement, encyclopedia_synthesis_disagreement. Formative alternate lineages are retained as economics_finance, political_science, law_governance; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] Tragedy of the commons — Garrett Hardin's term for how a shared resource with no accountable steward is over-used and under-maintained, because each user benefits privately while the cost of upkeep is diffuse. A shared platform without a funded governance body drifts the same way. ↩