Skip to content

META.md

Latest commit

 

History

History
113 lines (92 loc) · 6.94 KB

META.md

File metadata and controls

113 lines (92 loc) · 6.94 KB
Raw
schema aether.architecture-document/v1
id renderflow-meta
title Renderflow Meta
kind architecture-document
version 0.1.0
status draft
owners
egohygiene
created 2026-08-19
updated 2026-08-19
governed_by
architecture-meta
depends_on
renderflow-epistemology
renderflow-ai-constitution
related
renderflow-purpose
renderflow-vision
renderflow-principles
renderflow-pillars
supersedes

Renderflow Meta Architecture

Architecture-system overview

Renderflow's architecture is an 18-document graph materialized from the Aether architecture specifications. Each document owns one bounded concern. This index maps ownership and relationships without replacing the documents themselves.

Document inventory

Artifact Path Category Status Governing specification Upstream dependencies
renderflow-purpose PURPOSE.md Identity draft architecture-purpose —
renderflow-vision VISION.md Identity draft architecture-vision renderflow-purpose
renderflow-principles PRINCIPLES.md Identity draft architecture-principles renderflow-purpose, renderflow-vision
renderflow-pillars PILLARS.md Identity draft architecture-pillars renderflow-purpose, renderflow-vision, renderflow-principles
renderflow-manifesto MANIFESTO.md Identity draft architecture-manifesto renderflow-purpose, renderflow-vision, renderflow-principles, renderflow-pillars
renderflow-epistemology EPISTEMOLOGY.md Meta draft architecture-epistemology renderflow-purpose, renderflow-principles
renderflow-ai-constitution AI_CONSTITUTION.md Meta draft architecture-ai-constitution renderflow-purpose, renderflow-vision, renderflow-principles, renderflow-epistemology
renderflow-ontology ONTOLOGY.md Domain draft architecture-ontology renderflow-purpose, renderflow-vision, renderflow-principles, renderflow-epistemology
renderflow-personal-model PERSONAL_MODEL.md Domain draft architecture-personal-model renderflow-purpose, renderflow-vision, renderflow-principles, renderflow-epistemology, renderflow-ontology
renderflow-foundations FOUNDATIONS.md Foundation draft architecture-foundations renderflow-purpose, renderflow-principles, renderflow-epistemology
renderflow-system SYSTEM.md Foundation draft architecture-system renderflow-foundations, renderflow-ontology
renderflow-architecture ARCHITECTURE.md Foundation draft architecture-architecture renderflow-foundations, renderflow-system
renderflow-methodology METHODOLOGY.md Foundation draft architecture-methodology renderflow-principles, renderflow-epistemology, renderflow-ai-constitution, renderflow-foundations, renderflow-architecture
renderflow-design DESIGN.md Experience draft architecture-design renderflow-purpose, renderflow-vision, renderflow-principles, renderflow-personal-model
renderflow-design-system DESIGN_SYSTEM.md Experience draft architecture-design-system renderflow-personal-model, renderflow-design
renderflow-decisions DECISIONS.md Governance draft architecture-decisions renderflow-principles, renderflow-epistemology, renderflow-foundations, renderflow-system, renderflow-architecture
renderflow-roadmap ROADMAP.md Foundation draft architecture-roadmap renderflow-vision, renderflow-pillars, renderflow-architecture, renderflow-decisions
renderflow-meta META.md Meta draft architecture-meta renderflow-epistemology, renderflow-ai-constitution

Relationship graph

flowchart TD
  PURPOSE --> VISION --> PRINCIPLES --> PILLARS --> MANIFESTO
  PURPOSE --> EPISTEMOLOGY --> AI[AI Constitution]
  PRINCIPLES --> EPISTEMOLOGY
  EPISTEMOLOGY --> ONTOLOGY --> PERSONAL[Personal Model]
  PRINCIPLES --> FOUNDATIONS
  EPISTEMOLOGY --> FOUNDATIONS
  FOUNDATIONS --> SYSTEM --> ARCHITECTURE --> METHODOLOGY
  PERSONAL --> DESIGN --> DS[Design System]
  ARCHITECTURE --> DECISIONS --> ROADMAP
  PILLARS --> ROADMAP
  AI --> META
  EPISTEMOLOGY --> META
Loading

Ownership map

  • Identity documents own why the repository exists, its desired future, decision heuristics, strategic capabilities, and public commitments.
  • Meta documents own knowledge integrity, AI authority, and navigation of this document system.
  • Domain documents own canonical concepts and bounded human assumptions.
  • Foundation documents own invariants, logical systems, structure, working method, and strategic evolution.
  • Experience documents own intended experience and reusable semantic design language.
  • Governance owns accepted architectural decisions and historical lineage.

Reading order

  1. PURPOSE, VISION, and PRINCIPLES.
  2. EPISTEMOLOGY and ONTOLOGY.
  3. FOUNDATIONS, SYSTEM, and ARCHITECTURE.
  4. PERSONAL_MODEL, DESIGN, and DESIGN_SYSTEM when evaluating human-facing surfaces.
  5. AI_CONSTITUTION before delegating consequential work.
  6. DECISIONS and ROADMAP for accepted constraints and evolution.

Authoring order

Follow the dependency graph from purpose through identity and evidence, then domain and foundations, experience, governance, roadmap, and finally this META index.

Lifecycle and validation

All documents begin as draft and require human review before becoming active. Validation covers frontmatter, stable identifiers, links, graph acyclicity, ownership boundaries, evidence labels, Markdown structure, and agreement with repository reality.

Change propagation

A material upstream change triggers review of every downstream node. Implementation changes first update the owning specification or decision when they alter durable behavior; META changes whenever inventory or relationships change.

Gaps and omissions

  • No document in this set is intentionally omitted because Renderflow has repository, automation, human, AI, and public or documentation surfaces that justify the complete reference set.
  • Target systems remain provisional where implementation evidence is absent.
  • Repository-local schemas and automated graph validation should be added or connected to Aether in a later conformance pass.

Evidence and uncertainty

  • Observed: The repository README and checked-in implementation establish a specification-driven Rust rendering engine that plans and executes reusable transformation graphs for publication-ready artifacts.
  • Decided for this draft: The repository owns the bounded concern described here and participates through versioned contracts.
  • Proposed: Target systems and later roadmap phases remain proposals until accepted and implemented.
  • Open question: Which parts of this draft should become active in the first independently versioned release?