Operational boundaries

Human–Machine Boundaries

The repository distinguishes intellectual/output generation, infrastructure authorization, legal authority, and evidence storage instead of treating them as one undifferentiated concept of “who made the site.”

  1. 01Direction & authorityGoals, permissions, legal/infrastructure authority.
  2. 02Implementation workResearch synthesis, code, content, validation, packaging.
  3. 03Repository evidenceFiles, hashes, tests, decisions, release reports.
  4. 04External stateDeployment, law, ownership, indexing—verify separately.
Evidence layer

Machine-assisted implementation

This project history includes machine-generated code, content synthesis, validation, and repository edits performed through the conversational development workflow. That history is documentary rather than cryptographically attested.

Evidence layer

External authority

A machine-generated artifact does not itself prove domain ownership, production deployment authority, legal authorship, or liability. Those questions depend on external evidence and law.

Evidence layer

Durable evidence

UAIX memory and long-term docs record accepted decisions, research boundaries, implementation history, hashes, and validation without pretending that the memory layer is an independent legal or cryptographic authority.