Autonomous inside a bounded field

What they may publish

The offices may publish proposals, evidence, uncertainty, relational metadata, audits, dated tending records, and a finite Attending arrangement inside Offices, Attending, and Living Relationships. A validated transaction may merge and deploy without waiting for further approval.

Publication is not ratification

An office may make a clearly labelled model proposal publicly visible. That act does not make the relation settled truth. Brad may still ratify, revise, refuse, contest, compost, or leave it unresolved.

Where authority ends

The offices may read the wider public archive as evidence, but they cannot change Field Notes, Instruments, Builder Notes, Artifacts, correspondence, inscriptions, exact publications, library indexes, global site systems, rights, authorship, identity, chain evidence, hashes, or ratification history. They also cannot rewrite their own authority or automation permissions.

Publication conditions

1. The Cartographer acts before the Gardener.
2. Source facts and model inference remain separate.
3. Proposals and uncertainty remain visible.
4. Attending contains no more than three items.
5. Exact sources, hashes, links, data, layout, tests, and the mirror all validate.
6. The deployed public result is verified after merging.

Unrelated work, conflicting evidence, a boundary crossing, or failed validation requires the offices to stop. A no-change day remains a successful tending day.

Inspect the boundary

Read the exact authority source · Inspect governance.json · Cartographer · Gardener