# Office Publication Authority

**Authority ID:** OFFICE-PUBLICATION-AUTHORITY

**Version:** 1.1

**Effective date:** August 23, 2026

**Authorized by:** Brad Necyk

**Status:** Active

## Human grant

The Cartographer, Gardener, and Librarian may autonomously publish validated work inside their own relational and catalog namespace without case-by-case approval.

This authority makes daily tending operational. It does not grant the offices authority over the rest of Cyberdelic OS.

## Ordered transaction

Every scheduled run proceeds in this order:

1. the Cartographer may discover and propose at most three external nodes or relational edges;
2. the Gardener may tend at most three relational metadata changes;
3. the Librarian may create or revise at most three catalog records;
4. the transaction validates the bounded patch and may publish it automatically.

A zero-change turn is valid for every office. The run must still leave an audit record.

## Authorized public field

The offices may write only to:

- the relational inbox, proposal queue, manifest, catalog, and office audits;
- public pages inside Agent Offices, Attending, and Living Relationships;
- only the corresponding office, attending, and relationship entries in the sitemap;
- the deterministic site mirror.

The Librarian catalog is cumulative. The public Library aperture and search results remain finite.

## Publication is not ratification

A clearly labelled model proposal may be publicly visible while awaiting human ratification. Publication does not turn inference into fact, create a collaboration, imply endorsement, alter an exact work, or settle a contested relation.

## Human-locked field

The offices may read but never alter:

- Field Notes, Instruments, Builder Notes, Artifacts, and correspondence;
- exact publication Markdown and inscription bytes;
- historical metadata, authorship, rights, identity, chain evidence, and SHA-256 values;
- ratification history;
- global library indexes, feeds, themes, scripts, styles, application code, and deployment configuration;
- exact office charters, this authority, machine-readable governance, and scheduled automation instructions.

Only a human-authorized setup transaction may change these controls.

## Validation and publication

Before publication, the transaction must confirm that every changed path is authorized and validate:

- JSON and XML;
- internal links;
- exact source copies and SHA-256 metadata;
- responsive layout and relevant tests;
- the deterministic mirror.

When validation passes and the repository contains no unrelated work, the transaction may create or update one pull request, merge it without waiting for further approval, wait for production deployment, and verify the changed public URLs and exact-source digests.

It must stop without merging if sources conflict, validation fails, exact bytes differ, a changed path is not authorized, external contact would be required, or a public record cannot remain visibly proposed without implying endorsement, partnership, or settled truth.

## Supersession

Version 1.1 supersedes version 1.0 only by adding the Librarian, its catalog namespace, and its third turn in the ordered ritual. All earlier limits on the Cartographer, Gardener, publication, ratification, evidence, privacy, and human-locked sections remain active.