Methodology layer for the ASK family of projects.
This repo carries the cross-project method for designing systems that build systems: doctrine, topology, lineage, source-of-truth structure, and worked-example explanations at method altitude.
It does not carry execution-protocol assets. Those live in apexSolarKiss/control-surface — AGENTS.md rules, templates, prompts, project-instantiation workflow, and worked-example workflow notes.
method-ASK(this repo) — methodology layer, upstreamcontrol-surface— execution-protocol layer- project repos — downstream applications (
asset-pipeline-ASK,urban-observatory,mazeASK)
The methodology layer articulates the cross-project method; the execution-protocol layer encodes calibrated rules that operationalize the method per session; project repos apply the method and execution-protocol lineage to concrete domains.
Linked ASK repos are citations to worked examples, lineage surfaces, or layer relationships unless explicitly stated otherwise. They do not imply code dependency, schema import, aesthetic inheritance, or project-specific doctrine import.
docs/method.md carries the primary method articulation. Standalone doctrine docs and method-altitude worked-example explanations have landed in docs/ and examples/; the article-line index lives at docs/articles.md. Illustrative diagrams have landed in docs/diagrams/ — a topology / relative-externality map, and bespoke figures for system-ASK (worked example), bounded generativity (doctrine), and the seed-mediated generated interface (doctrine + ontology); the diagrams are illustrative, and repo prose remains source of truth. Lineage remains a candidate for later PRs as substrate earns it.
AGENTS.md— repo-local workflow rulesdocs/method.md— primary method articulationdocs/— standalone method doctrine and the article-line indexdocs/intent-artifacts.md— the intent-artifact ontology: carrier classes, activation postures, relay vs feeding, provenance projectiondocs/diagrams/— illustrative diagrams (topology; bounded generativity; seed-mediated generated interface + ontology; intent-artifact ontology; activation + lifecycle comparison; relay / feeding / ingestion; adversarial relay graph + PTX projection); not source of truthexamples/— worked-example explanations at method altitudetools/read/— the site build: it renders the site's home page, and reading pages fordocs/,examples/and the diagram sources from their Markdown and source files, when the site is built; the generated pages are build output and are not committed
- Method // Designing Systems That Build Systems — external articulation of the method category
- From Execution Proof Back to Normative Structure — adversarial iteration as the methodology layer's primary motion
- Adversarial Collaboration — the within-session multi-mind complement, primarily resident in the execution-protocol layer
Copyright 2026 Andrew S Klug // ASK
Licensed under the Apache License 2.0 // see LICENSE