apexSolarKiss method-ASK diagrams

Structural snapshots of the method at a point in time. Diagrams are illustrative and age; the repo prose is source of truth, and each figure below links the doctrine document that governs it.

illustrative >> not source of truth

Topology + intent-architecture trees
tree // TREE_D02

topology

The repo's own topology and its relative-externality map — what sits inside the method, what sits outside it, and how far.

tree // TREE_D10

intent-artifact ontology

A source of intent is a locatable role, not a folder or a file. Context, intent and provenance families, and the claim-level versus artifact-level discipline.

tree // TREE_D05

activation + lifecycle comparison

Five artifact forms and their distinct activation and lineage models. Only a fresh routed handoff awaiting first ingestion enters the routed-instance filename lifecycle.

tree // TREE_D06

relay / feeding / ingestion

The envelope supplies operative force; the payload supplies content. Ingestion is the state that results when a feed succeeds, and it is not a disposition.

tree // TREE_D07

adversarial relay graph + PTX projection

The native partially-ordered multi-thread topology against its linear transcript projection. A PTX is a faithful projection of an exchange, not the exchange and not an authority converter.

Doctrine figures
figure // doctrine

bounded generativity

The system model: define the grammar, permit bounded variance inside it, and make selection and governance explicit.

figure // doctrine

seed-mediated generated interface

The instantiation path and the loading-boundary seam: authored seed, loading boundary, the grammar granting the aperture, runtime, generated interaction, return — or fork at load.

figure // ontology

seed-mediated generated interface — ontology

The category boundaries rather than the path: four orthogonal layers — mechanism, application, authored control, conformance — around one membership node. Fully neutral, with no function colour.

Drag to pan, scroll to zoom, and use the HUD controls in the bottom-left; fits the figure. Theme follows the operating system, and the diagrams default to dark as repository documentation.

Each figure carries a source data file or figure builder beside it. Source advances when the authored topology changes; the renderer advances only when its realization does. See README.md for the update cadence and the full contents list.

These pages consume the vendored token mirror in _dsa-tokens/ and the surface carriers in _dsa-surface/, both pinned byte-identical to design-system-ASK and never hand-edited here.