# Roadmap, Governance & Sustainability

This page covers the *forward-looking* and *governance* aspects of ChainRender — how it evolves, how it's kept
honest, and how it sustains itself. These are less about building an app today and more about the health of the
platform you'd build on.

## Ownerless & immutable — the governance model

ChainRender's most important governance property is that there's very little to govern: every contract is
**ownerless and immutable**. There's no admin key to compromise, no upgrade mechanism to abuse, no foundation that
can change the rules under you. The system is deployed, verified, and then fixed. Governance, where it exists, is
limited to **ownerless, permissionless registries** (names, themes, advisories) whose parameters are set once at
deployment.

## How the platform evolves — additive deployment

New capability is added **additively** — new contracts deployed alongside the live base, never replacing it. Old
apps keep working forever (the contracts they reference are immutable and stay live); new features become available
to new apps. This "never delete, always add alongside" discipline is why:
- your app can't break due to a platform update,
- you can pin to exactly the contracts you built against,
- the platform grows without migration pain.

## Forward compatibility

ChainRender is designed so that **no layer hardcodes a current EVM constant** — size limits, storage backends,
interpreter versions, and action-submission paths are all seams mapped to Ethereum's public roadmap. As Ethereum
ships larger contract sizes (Glamsterdam), cheaper storage, or native account abstraction, ChainRender adopts them
as a *configuration change*, not a rewrite. See **[Size Limits & Glamsterdam](../concepts/size-limits-and-glamsterdam.md)**.

## Sustainability

ChainRender is infrastructure meant to persist as a public good. Its economics support this: apps are
**write-once, read-free** (no recurring cost to keep an app alive — see **[Economics](../concepts/economics.md)**),
and the framework itself is ownerless and immutable (no ongoing operator required). A **PublicGoodsTreasury**
exists as an on-chain funding sink for sustainability, routed by fixed rules rather than discretionary control.

## Standardization

Several ChainRender primitives (the render-target model, declared actions, the trust grade) are candidates for
standardization as EIPs, so the patterns can benefit the broader ecosystem. This is tracked as a forward effort.

## The disciplines that keep it honest

ChainRender is maintained against a set of explicit disciplines — an immutability review of the permanent floor, a
deferred-lock-in audit (avoiding premature commitment to changeable choices), and an upgrade/remediation runbook
(how to respond if an issue is found *without* violating ownerlessness — by deploying new, better contracts
additively and letting apps opt in, never by seizing control of existing ones). These exist so the platform's
guarantees hold over time, not just at launch.

## Related
- **[Principles & Ethos](./ethos.md)** — the values these flow from.
- **[Economics](../concepts/economics.md)** · **[Size Limits & Glamsterdam](../concepts/size-limits-and-glamsterdam.md)**