Gates and decision rights

Each record type can name the decision class a write of it is. The venture’s decision rights say who owns each class and at what level. When a class escalates to a person, an agent’s write is held as a draft in _drafts/ until a person accepts it:


mentura accept governance/ownership --venture my-venture

These record types are gated today:

Route	Actions	Files or script	Decision class	What it is
`governance/board`	read, view, layout, write, check	`governance/board.json`	ownership-or-control	Formal and advisory boards, their seats and reserved matters
`governance/decision-rights`	read, view, layout, write, check	`governance/decision-rights.json`	strategy-or-constitution
`governance/exit`	read, view, layout, write, check	`governance/exit.json`	ownership-or-control	Exit paths kept open and sale values to model; payouts computed by payouts.mjs
`governance/founder-agreement`	read, view, layout, write, check	`governance/founder-agreement.json`	ownership-or-control	What founders agreed: roles, commitment, IP, departure, deadlock; prose beside it
`governance/ownership`	read, view, layout, write, check	`governance/ownership.json`	ownership-or-control	The cap table: share classes and their rights, holders, grants with vesting, option pool, SAFEs and notes (EE-022)
`governance/publication-policy`	read, view, layout, write, check	`governance/publication-policy.json`	strategy-or-constitution	Where the venture publishes and who may publish what there: channels, guidelines, checks, preview and approvers; every publication passes this gate (EE-025)
`purpose/telos`	read, view, layout, write, check, template	`purpose/telos.json`	strategy-or-constitution	The end the venture exists to reach: statement, end state, measures, owner outcome, exit criteria per phase (EE-023)

Writes through the MCP server and the HTTP API always count as an agent’s. The command line cannot tell a person from an agent, so the gate that holds in the end is the pull request a person merges.