APS Visual Explanatory Grammar
This document establishes the canonical visual architecture of APS_WEB. It defines the purpose, hierarchy, semantics, continuity structure, pedagogical integration, naming conventions, and governance principles that organise APS diagrams across the framework.
APS Visual Explanatory Grammar
Canonical Visual Architecture and Diagram Integration Standards for APS_WEB
APS diagrams are not decorative illustrations. They are explanatory instruments designed to stabilise, organise, and communicate the explanatory structure of viability-oriented organised persistence within the APS framework.
This document establishes the governing principles, semantic conventions, pedagogical hierarchy, continuity architecture, and integration standards that define the APS visual system across APS_WEB.
The aim is to ensure that APS visuals remain:
- explanatory rather than decorative,
- pedagogically intelligible,
- visually coherent,
- structurally integrated,
- recursively interpretable,
- and organisationally consistent across the framework.
APS diagrams should therefore be understood as:
- analytic projections of organised persistence,
- architectural representations of explanatory structure,
- recursive continuity grammars,
- and navigational instruments for biological explanation.
The APS visual system is not ancillary to the framework. It constitutes part of the framework’s explanatory infrastructure.
1. The Purpose of APS Diagrams
APS diagrams exist to:
- clarify viability-oriented organisation,
- stabilise explanatory orientation,
- visualise organisational continuity,
- reduce conceptual ambiguity,
- organise recursive explanatory relations,
- support progressive conceptual integration,
- and assist navigation across multiple explanatory scales and domains.
APS diagrams do not replace prose explanation. They stabilise and support it.
The governing principle is:
APS diagrams should reveal organisational structure while preserving interpretive clarity.
APS diagrams should therefore prioritise:
- intelligibility,
- hierarchy,
- explanatory pacing,
- organisational coherence,
- and recursive continuity.
2. The APS Visual Hierarchy
No single diagram should attempt to perform every explanatory function simultaneously.
APS visuals operate across multiple levels of explanatory architecture.
The visual system therefore functions as a staged pedagogical hierarchy rather than a single total explanatory diagram.
2.1 Foundational Ontology Visuals
Purpose
- Define the core ontology of APS
- Present the fundamental explanatory structure of living systems
- Stabilise the reader’s initial conceptual orientation
Characteristics
- Minimal conceptual overload
- Strong visual hierarchy
- Clear organisational geometry
- Elegant explanatory simplicity
- Stable conceptual architecture
- Implied rather than explicit continuity
Typical Uses
- Homepage explanatory core
- Orientation pages
- Introductory APS articles
Canonical Examples
- aps-foundational-framework.png
- architecture-visual.png
Governing Principle
Foundational ontology visuals should answer:
“What kind of organisational reality does APS describe?”
rather than:
“How does every explanatory process within APS operate simultaneously?”
2.2 Continuity Architecture Visuals
Purpose
- Visualise recursive organisational continuity
- Explain viability maintenance across time
- Clarify dynamic persistence and regulatory integration
Characteristics
- Recursive organisational flow
- Dynamic continuity relations
- Integrated persistence cycles
- Temporal maintenance logic
- Moderate conceptual density
- Strong continuity semantics
Typical Uses
- Intermediate explanatory pages
- Structural integration articles
- Continuity-focused conceptual synthesis
Canonical Examples
- architecture-continuity-visual.png
- evolution-continuity-visual.png
- cognition-continuity-visual.png
- diagnosis-continuity-visual.png
- ecology-continuity-visual.png
- philosophy-continuity-visual.png
Governing Principle
Continuity visuals should clarify:
“How organised persistence is continuously enacted and maintained.”
rather than merely:
“Which conceptual domains exist.”
2.3 Framework Navigation Visuals
Purpose
- Orient readers within the conceptual topology of APS
- Clarify major explanatory domains
- Support cross-site conceptual navigation
Characteristics
- Moderate explanatory density
- Strong domain grouping
- Reduced recursive complexity
- Clear pedagogical hierarchy
- Navigation-oriented structure
Typical Uses
- Orientation pages
- Navigation sections
- Framework overview articles
Canonical Examples
- aps-framework-map.png
Governing Principle
Framework navigation visuals should answer:
“Where within the APS framework does this explanatory domain belong?”
2.4 Domain Structural Visuals
Purpose
- Clarify the explanatory architecture of specific domains
- Present conceptual organisation without full recursive continuity
Characteristics
- Stable explanatory relations
- Moderate conceptual integration
- Reduced temporal recursion
- Strong local conceptual coherence
Typical Uses
- Domain introduction articles
- Intermediate explanatory pages
- Cluster overviews
Canonical Examples
- evolution-visual.png
- cognition-visual.png
- philosophy-visual.png
2.5 Canonical Synthesis Visuals
Purpose
- Integrate multiple explanatory layers simultaneously
- Present advanced recursive conceptual architecture
- Support deep framework synthesis
Characteristics
- High conceptual density
- Multi-layer explanatory integration
- Recursive cross-domain relations
- Extensive continuity architecture
Restriction
Canonical synthesis visuals should not normally appear on:
- homepage entry pathways,
- introductory orientation pages,
- or early conceptual onboarding sections.
3. Progressive Pedagogical Disclosure
APS visual complexity should increase progressively across the site.
Readers should gradually learn:
- visual semantics,
- continuity logic,
- recursive explanatory structure,
- and conceptual integration.
The visual system should therefore function as:
- pedagogical scaffolding,
rather than:
- immediate total exposition.
Early Orientation
Simple ontology visuals.
Intermediate Explanation
Continuity architecture visuals.
Advanced Integration
Canonical synthesis visuals.
4. Visual Semantics
APS diagrams employ stable visual semantics so that readers progressively learn how to interpret diagrammatic structure across the framework.
4.1 Colour Semantics
Colours indicate explanatory domains rather than decorative variation.
| Colour Domain | Meaning |
|---|---|
| Blue | Constitutional organisation |
| Green | Evolutionary continuity |
| Amber | Cognition and evaluation |
| Red | Diagnostic perturbation and failure |
| Teal | Ecological coupling |
| Grey | Explanatory integration and meta-level structure |
| Purple | Philosophical integration and conceptual grounding |
Governing Principle
Colour should:
- orient,
- stabilise,
- and group explanatory domains,
not:
- create spectacle,
- visual competition,
- or decorative excess.
Muted palettes are preferred over saturated palettes.
4.2 Arrow Semantics
Arrows must maintain stable explanatory meaning across APS visuals.
Solid arrows
Primary organisational continuity or explanatory dependence.
Dashed arrows
Conditional, indirect, or contextual relations.
Bidirectional arrows
Reciprocal organisational dependence.
Loop arrows
Recursive regulation, persistence dynamics, or continuity maintenance.
Governing Principle
Arrows should not ambiguously mix:
- causation,
- temporal succession,
- conceptual association,
- and explanatory dependence.
Where necessary, captions should explicitly clarify arrow semantics.
4.3 Shape Semantics
Shape variation should communicate explanatory role.
Rounded rectangles
Stable conceptual domains.
Circles
Processes, continuity relations, or recursive dynamics.
Diamonds
Transitions, bifurcations, or diagnostic distinctions.
Shaded regions
Integrated explanatory fields or conceptual clusters.
Governing Principle
Shape variation should indicate explanatory function rather than decorative diversity.
5. Continuity Grammar
Continuity diagrams now constitute a formal explanatory class within APS visual architecture.
These visuals represent:
- recursive organisational persistence,
- dynamic viability maintenance,
- continuity across scales,
- adaptive reorganisation,
- and ongoing explanatory integration.
Continuity visuals should therefore:
- emphasise recursive structure,
- reduce mechanistic linearity,
- employ fluid organisational flow,
- and visually imply persistence through continuous reorganisation.
The governing continuity principle is:
Living systems persist through continuously organised activity rather than static structural stability.
6. Diagram Construction Standards
6.1 Canonical File Structure
SVG remains the canonical APS master format.
SVG is preferred because it supports:
- scalability,
- editability,
- semantic layering,
- responsive rendering,
- typography control,
- and future revision.
PNG exports may serve as:
- stable publication assets,
- homepage-ready visuals,
- or integration renders derived from canonical SVG masters.
6.2 Typography
APS diagrams should employ clean sans-serif typography with strong hierarchical organisation.
Hierarchy Rules
- Titles larger than domain labels
- Domain labels larger than node labels
- Captions visually subordinate to diagrams
Typography should prioritise:
- readability,
- scanning efficiency,
- conceptual hierarchy,
- and visual calmness.
6.3 Spacing
APS diagrams should favour:
- generous whitespace,
- uncluttered geometry,
- domain separation,
- and balanced conceptual pacing.
A smaller number of highly legible concepts is preferable to dense conceptual saturation.
Compression should be avoided whenever possible.
6.4 Diagram Titles
Every major APS visual should include:
- a concise title,
- or surrounding contextual framing clearly identifying the figure’s explanatory role.
6.5 Canonical Naming Conventions
Canonical file naming should communicate explanatory role and hierarchical status.
Examples
- aps-foundational-framework.png
- aps-framework-map.png
- architecture-continuity-visual.png
- cognition-continuity-visual.png
Naming Principles
Names should:
- indicate explanatory function,
- stabilise hierarchy,
- support navigational clarity,
- and reinforce pedagogical sequencing.
6.6 APS Figure Identification
Major diagrams may employ APS figure identifiers such as:
- APS-F1
- APS-F2
- APS-C1
- APS-E1
This system may later support:
- publication integration,
- cross-referencing,
- reusable figure architecture,
- and visual citation systems.
7. Caption and Interpretation Standards
Captions are interpretive components of APS diagrams, not merely labels.
APS captions should normally contain three functions.
7.1 Structural Identification
What the figure shows.
Example
“A continuity architecture diagram illustrating recursive viability maintenance within APS.”
7.2 Interpretive Clarification
What relations or symbols represent.
Example
“Loop arrows indicate recursive continuity and organisational persistence.”
7.3 Conceptual Framing
Why the structure matters.
Example
“The figure illustrates how biological persistence emerges through continuously organised activity rather than static equilibrium.”
Governing Principle
Captions should reduce interpretive ambiguity before readers encounter conceptual complexity.
8. Homepage Integration Policy
Homepage diagrams should:
- remain visually restrained,
- support orientation,
- minimise conceptual overload,
- and function primarily as conceptual anchors.
The homepage should communicate:
- APS identity,
- explanatory orientation,
- and conceptual accessibility,
not:
- total architectural complexity.
8.1 Homepage Visual Hierarchy
Recommended homepage progression:
Entry Layer
Minimal conceptual orientation.
Foundational Layer
Foundational ontology visuals.
Structural Layer
Continuity architecture visuals.
Navigation Layer
Framework map visuals.
Domain Expansion
Specialised continuity grammars.
This produces:
- progressive conceptual disclosure,
- reduced cognitive overload,
- and improved explanatory pacing.
9. Diagram Governance and Migration
APS visuals now constitute a formal explanatory infrastructure.
Diagram governance is therefore necessary to preserve:
- coherence,
- hierarchy,
- readability,
- and pedagogical stability.
9.1 Diagram Migration Principle
When a diagram becomes too conceptually dense for its pedagogical location, it should migrate to:
- a dedicated architecture page,
rather than forcing additional complexity into the original context.
9.2 Redundancy Control
Older visuals that duplicate newer canonical diagrams may:
- be archived,
- repositioned,
- simplified,
- or retired.
The visual system should evolve toward:
- clarity,
- stability,
- and reduced redundancy.
9.3 Canonical Status
Certain APS visuals may acquire canonical status as stable explanatory infrastructure.
Canonical visuals should:
- maintain naming consistency,
- remain visually harmonised,
- support cross-site integration,
- and function as reusable explanatory anchors.
10. Governing Visual Philosophy
APS visual architecture should remain:
- explanatory rather than decorative,
- organisational rather than classificatory,
- recursively coherent,
- pedagogically staged,
- visually integrated,
- and conceptually intelligible.
The central aim of APS visual architecture is not graphical sophistication for its own sake, but explanatory intelligibility.
The governing principle of the APS visual system is therefore:
APS visuals should reveal the organised continuity of living systems while preserving interpretive clarity.