# The floor

URL: /systems/trust-and-governance/floor · Id: `page:systems/trust-and-governance/floor`

> What a Startup still does after inheritance, from its shared and owned Controls to the four signed acts that need a person and what its Customers must do.

A [Startup](/business/nouns/startup)'s floor is what inheritance leaves it: the [Controls](/business/nouns/control) it shares or owns, and the few acts that need a person. The floor is computed, never written, and changes as the Startup does.

## How the floor is computed
After every [Change](/business/nouns/change), resolution runs from the platform down. The Controls that land `shared` or `owned` in the Startup's namespace form its floor. The rest are inherited and ask nothing of it.

The operating model shapes the floor. An [Autonomous](/agents/operating-models/autonomous) Startup carries no human-only Controls, because it seats no [Human](/business/nouns/human). A [Multi-human](/agents/operating-models/multi-human) Startup adds background checks, a signed acceptable-use [Agreement](/business/nouns/agreement) per person, and access removal on the day someone leaves.

The people Controls have an agent side too. An agent's competence is a pinned model and instruction [Version](/business/nouns/version) with a passing eval record, tested by [Worker competence](/systems/trust-and-governance/controls/worker-competence).

## The human floor
Four acts per report period need a person, because the standard asks for a signature:

1. An officer approves the security and privacy policies.
2. An officer accepts the risk assessment.
3. The board, or the sole director, records its oversight.
4. An officer signs the management assertion that the system description is accurate.

Each act is a [Decision](/business/nouns/decision) signed by an officer of the Startup's [Company](/business/nouns/company). The assertion is pinned to the hash of the system description it covers, so it cannot drift from what it signed.

[Agents](/business/nouns/agent) prepare every act. They draft the risk assessment from the Startup's records and list what changed since the last one. A person reads and signs.

## Who signs
A Startup held by a [Studio](/business/nouns/studio)'s holding Company has its acts signed by the officer desk, for every Startup the Studio holds, in one batch. A self-serve founder signs for their own Company. After graduation, the cofounders sign.

[Who signs](/systems/legal-and-corporate/who-signs) lists every act and its signer.

## Customer controls
The same computation runs one level down. A Startup is a customer in the platform's report, and its own [Customers](/business/nouns/customer) are customers in the Startup's report.

What a Customer must do for the Controls to work prints in the Startup's report as customer controls. A contract-tracking app for small agencies, for example, asks each agency to keep its own sign-in secure and remove departed staff from its [Tenant](/business/nouns/tenant).

## Two floors
The [legal floor](/systems/legal-and-corporate/floor) lists legal obligations and what wakes them, such as [CAN-SPAM](/systems/legal-and-corporate/floor/can-spam) at a first commercial email. The Control floor lists Controls.

An obligation can sit on both. [Governance](/systems/legal-and-corporate/floor/governance) is the legal side of the officer's signatures above.

## Next
- [How proof works](/systems/trust-and-governance/proof): how the floor's Controls are tested.
- [Auditors](/systems/trust-and-governance/auditors): how a firm samples the human floor.