Generated Derivatives

The Æther Flow Project is a two-part research program about foundational physics and the governed, human-accountable AI research system used to organize and test that work. Its physics track asks whether ordinary general relativity can be interpreted, and eventually derived, from a deeper Æther or Æther-Flow foundation; general relativity remains the exact benchmark for observable gravity, while the first-principles substrate derivation is still open.

Its AI track uses tracked tasks, Director decisions, bounded AgentJobs, roles, validation, memory preflight, completions, handoffs, and human gates so that theoretical work remains inspectable without becoming accepted physics by workflow alone. A generated derivative is a reader-facing copy, explanation, or visual presentation made from tracked material: it can make the project easier to read, compare, inspect, or navigate without becoming the owner of the claims it presents.

GitHub-facing Markdown supports repository and AI-assisted reading; tracked HTML supports visual no-network reading; PDFs and document copies support inspection and download; generated wiki pages and object browsers support discovery; and diagrams and public assets support comprehension. Each remains downstream from its registered source, registry row, or governed control record.

The publication chain makes that relationship auditable: a canonical source or registry supplies the claim basis, a source specification binds the intended output to inspected material and limits, a publication brief defines the reader job, visual strategy, acceptance criteria, and forbidden patterns, and the generated output then receives deterministic checks plus desktop, mobile, or before-and-after review evidence. Markdown, HTML, PDF, and website versions may use different layouts, but parity requires the same source basis, authority boundary, and core claims rather than identical section order.

Provenance records, derivative registries, status labels, source paths, and hashes help readers trace an output back to what produced it; a hash identifies particular file contents, not scientific correctness, and publication approval records a bounded reader-surface decision rather than physics authority. When a derivative and its owner disagree, read the derivative label, find the source basis, inspect the named source, source specification, registry row, handoff, or control record, and state what the derivative helps readers do and what it cannot prove. The source wins, and the derivative needs repair.

As a contextual Documents route outside the five-item primary dropdown, Generated Derivatives presents these limits through contextual copy, tables, and provenance rather than a separate Source authority component section. No generated Markdown, HTML page, PDF, document copy, wiki note, diagram, public asset, registry row, hash, validator PASS, screenshot, review receipt, AI output, or website page independently proves a physics claim, completes the open first-principles derivation, promotes the proposed ontology or a benchmark, expands workflow authority, overrides a human gate, or replaces direct source inspection.