Skip to content

Latest commit

 

History

History
49 lines (35 loc) · 3.99 KB

File metadata and controls

49 lines (35 loc) · 3.99 KB

Method // Bridge

This document is a bridge. control-surface readers find here a short explanation of where the methodology layer lives and what it carries. The substance of the method lives upstream in apexSolarKiss/method-ASK.

What lives upstream

The methodology repo carries:

  • the method itself — pre-architecture moves, execution disciplines, synthesis disciplines, cross-phase workflow shape, surface/voice discipline, adversarial iteration and collaboration
  • relative externality and the rule/payload doctrine
  • source-of-truth and aging-rate doctrine + cross-project lineage
  • source-of-intent recovery, validation loop, and external-handoff classification (observation-level)
  • worked-example explanations at method altitude
  • the method topology
  • the absorption discipline that governs when n=1 patterns earn promotion to method-level doctrine

The methodology repo's docs/method.md is the primary articulation. Standalone doctrine docs have split out as substrate accumulated — see Where to read further below.

What stays in this repo

apexSolarKiss/control-surface remains the execution-protocol layer. It owns:

Why the split

The methodology layer and the execution-protocol layer have different aging rates and different audiences. Holding them in one repo would make the meta-repo legible at neither altitude. Keeping the method upstream lets control-surface stay tight as the execution-protocol meta repo while the method evolves at its own cadence.

Where to read further

Self-superseding clause

This bridge stays compact. If it grows, the upstream method repo is absorbing too little or this repo is absorbing too much.