apexSolarKiss/asset-pipeline-ASK is the mature pressure surface from which most of the method's execution-protocol substrate was operationally refined before being absorbed upstream into apexSolarKiss/control-surface. The project is what the method was first tested against; it is what docs/method.md currently centers as the worked example.

The role is structural, not biographical. The project is the worked example; the method is the durable element. Method-ASK preserves what generalizes beyond the project's domain.

The following method elements emerged through asset-pipeline-ASK work and were articulated against its concrete pressure:

• Aging-rate principle — surfaced through the friction of mixing rules, state, and context in a single doc. State ages fast, rules age slowly, context ages slowly, per-conversation tracking is ephemeral. Each surface earns its own aging rate.
• Source-of-truth split — the corollary discipline: repo carries project state; AGENTS.md carries workflow rules; grounding note carries source-of-intent; operator-side memory carries per-conversation tracking.
• Voice / surface-boundary discipline — surfaced when protected-payload content (positioning vocabulary, strategic rationale, translation tables) showed up in repo-readable surfaces and had to be moved out. The repo can name the structural category; it cannot carry the payload.
• Architecture-uncertain pattern — ontology-first work, architecture-attempt-before-prototype, prototype-as-pressure-surface. The architecture is the project; the prototype is the test rig.
• Vocabulary deconstruction — the architecture-vocabulary-pass discipline: pressure-test terms before they harden into structure. Surface where two words are being used as synonyms when they should not be; surface where a single word is hiding distinctions that matter.
• Two review windows — the per-PR cadence with pre-commit and pre-merge advisor reviews, applied to projects with hardened backbone and active architectural uncertainty.
• Plateau detection — the self-diagnostic signal that surfaces when correct moves chained too quickly become their own drift vector. Stop, preserve what landed, re-enter through a fresh-context pass only when new intent or new pressure is available.

control-surface absorbed the patterns that generalize beyond the asset-pipeline domain:

• Aging-rate principle articulated in AGENTS.md, README.md source-of-truth split, and templates/grounding-note.template.md
• Architecture-uncertain rules overlay at templates/overlays/architecture-uncertain-rules.template.md — opt-in for projects with architectural uncertainty
• Workflow templates (templates/AGENTS.template.md, templates/grounding-note.template.md, templates/architecture.template.md) carrying the patterns each new ASK project inherits
• The two-review-windows cadence encoded in AGENTS.md
• The source-of-truth split between repo, AGENTS.md, grounding note, and operator-side memory

control-surface/examples/asset-pipeline-ASK/notes.md carries the workflow-asset summary for instantiation pattern reuse. That artifact is distinct from this method-altitude explanation.

docs/method.md currently centers asset-pipeline-ASK as the worked example. The articulation includes:

• The architecture-attempt-before-prototype, ontology-first, vocabulary-deconstruction, and pressure-surface principles named explicitly in the pre-architecture moves and execution disciplines sections
• The recursive observation that the project is more than a pipeline — it is a system-building system for governed visual asset production pipelines, parallel to control-surface as a system-building system for AI-native execution workflows
• The asset-pipeline-ASK Worked Example section describing the swing motion (pure ontology → v1 prototype → IA layered-content redirection) as visible method-history

With standalone doctrine docs now split out from docs/method.md — docs/source-of-truth-and-aging-rate.md for aging-rate and docs/voice-surface-boundary.md for voice / surface-boundary discipline — asset-pipeline-ASK pressure remains the historical evidence those docs reference. Architecture-uncertain principles continue to live in docs/method.md and the control-surface architecture-uncertain-rules overlay.

Domain-specific content lives in apexSolarKiss/asset-pipeline-ASK, not here:

• specific asset categories, IA layered-content schema, brand-system / product-class / packet / slot layer details
• the project's protected vocabulary, positioning, and strategic rationale
• domain implementation detail beyond what is needed to make a method principle visible

Method-ASK carries only what generalizes beyond the asset-pipeline domain. When asset-pipeline-ASK refines a principle further, the absorption flows through control-surface for execution-protocol patterns or directly upstream to method-ASK for methodology patterns.