> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getnativeflow.com/llms.txt
> Use this file to discover all available pages before exploring further.

# The Authoring Contract

> The shared schema that keeps Studio edits and agent-driven edits consistent with each other.

<Frame>
  <img src="https://mintcdn.com/nativeflow/QMoGJuZEfQT0dul4/images/agent_writes_through_sac.png?fit=max&auto=format&n=QMoGJuZEfQT0dul4&q=85&s=672e2edf960d6f75b0a85fe627e75e95" alt="Agent Writes Through Sac" width="2720" height="1880" data-path="images/agent_writes_through_sac.png" />
</Frame>

Every write an agent makes through NativeFlow's MCP server, whether it's touching styles and props, events and logic, pages and themes, or API and data bindings, resolves to a single call against the Studio Authoring Contract. There is no surface an agent can write to that bypasses it.

Accepted writes route through the Automatic, Notify, or Review governance tier before they reach the project, and every write, accepted or rejected, is recorded in the audit log. This is what keeps an agent-built screen and a hand-built screen structurally identical, and what makes it possible to see exactly what any agent did to a project and why.