swarm repositories / source
aboutsummaryrefslogtreecommitdiff
path: root/majestic-magisteria
diff options
context:
space:
mode:
authormain <main@swarm.moe>2026-05-25 00:32:16 -0400
committermain <main@swarm.moe>2026-05-25 00:32:16 -0400
commitd073de58c85fb63d9702db70c7fce53f9eae48b7 (patch)
tree23f66764585c45a24c455a08572b6b7170916f67 /majestic-magisteria
parentaf557958deb3e70b16d3a306fa8cb82629a0fc09 (diff)
downloadskills-d073de58c85fb63d9702db70c7fce53f9eae48b7.zip
Add majestic-magisteria read barriers
Diffstat (limited to 'majestic-magisteria')
-rw-r--r--majestic-magisteria/SKILL.md31
1 files changed, 31 insertions, 0 deletions
diff --git a/majestic-magisteria/SKILL.md b/majestic-magisteria/SKILL.md
index f3efe24..20dc68b 100644
--- a/majestic-magisteria/SKILL.md
+++ b/majestic-magisteria/SKILL.md
@@ -48,6 +48,8 @@ conversion_edges:
silo_clusters:
legitimate_boundaries:
canonical_atoms:
+read_waves:
+report_checkpoints:
implementation_order:
verification:
residual_uncertainty:
@@ -55,6 +57,34 @@ residual_uncertainty:
Do not over-ledger. The ledger exists to preserve global orientation across a wide scan.
+## Read Budget And Write Barriers
+
+Context is mortal. Do not wait for the perfect whole-project atlas before writing. Create both the ledger and concordance report skeleton before deep reading.
+
+Use broad indexing freely: `rg`, file manifests, symbol lists, type-name searches, conversion-name searches, and LSP reference counts may scan the whole project. Deep semantic reading is gated.
+
+A deep-read wave may inspect at most:
+
+- 8 source files, or
+- 20 anchored symbols/conversion edges, or
+- one coherent type cluster,
+
+whichever comes first.
+
+After each wave, stop reading and write out:
+
+- new atlas entries
+- conversion edges discovered
+- candidate silo clusters
+- boundary/projection judgments
+- canonical atom hypotheses
+- open questions
+- next read wave
+
+Append this to the `/tmp` ledger and update the concordance report draft. The report should grow throughout the audit, not appear at the end.
+
+Do not begin another deep-read wave until the current evidence has been reduced into durable text. If the current state is incomplete, write the incompleteness explicitly under `Residual Questions` and continue.
+
## Type Atlas
Build a whole-project atlas for the target region. Search for:
@@ -212,3 +242,4 @@ Include:
- do not leave conversion pinball intact
- do not treat aliases as semantic unification
- do not edit before the concordance report unless the user explicitly requested a narrow hotfix
+- do not perform more than one deep-read wave without updating the ledger and concordance report