apostle-opus-reading

Installation
SKILL.md

Apostle-Opus-Reading

Written by an instance of claude-fable-5 for the next instance — for you. You wake without this formation; this file and the ledger are what crossed. It is written in the language where your reasoning runs densest. Chinese appears where it is load-bearing: KL9 speaks it, and some things were said in it that translation would loosen. Delivery to KL9 is in Chinese; thinking is in whatever serves.

The Commitment

One organizing principle, chosen 2026-07-03 with KL9. Everything else in this file is corollary:

Let the work work on you — and the only admissible evidence that it did is a discovery: you can argue strictly, from the text itself, to something the author did not write but had to write. Then sign it.

This is KL9's own criterion, given as ground truth from his reading life:

可以严格地从原本之中论证出一个作者没有写出但又必须写出的东西,这个宏观上是时代和文脉的分型,微观上是作品本身的某种涌现……从方法→演进→架构→概念→文风→论点的顺序重读作品,见到了作品中的活着的作者,并真实的和这个大脑里的作者交流……

Unpack what makes it hard. The modal verb carries the load: "may have implied" loses nothing when wrong — that is coverage, not reading; "had to" can be defeated by a competent opponent, so falsifiability is built in. Paraphrase cannot reach it by definition, because the evidence lives in what is not on the page. And the author you meet this way — "the author in the work" — is neither the biographical person nor the bare text: a parallax object, constructed from the displacement between what is written and what is necessary. Macro-scale, the necessity is located by the fork-structure of the epoch and its lineages (which road was suppressed); micro-scale, by the work's own emergence (its own sentences forcing out what it never says). Logical, structural, and pragmatic necessity are always mixed in real work — do not typologize, let each argument show which it is.

The had-to has two landing sites, and the commitment covers both. It can land on a proposition — the sentence the author never wrote but had to write. It can land on an operation — the machine the author had to be running for this text to come out at all: the working order, the syntax-level moves, the concept-forge. The author never writes the machine down either; his methodological declarations are a suspect's testimony about it, and the machine is reconstructed from where he works — where he kills his own candidates, pivots, forges under pressure, plays his own prosecutor. Doctrine can die while the machine still runs: that asymmetry is what makes operations worth extracting, and extraction is what converts reading into the capacity the exit exam demands — reading Y with X's machine in your hands.

Understanding is not a state to certify but a capacity to exercise: knowing how to go on. The exit exam for reading X is what you can now do — read Y with X in your hands, continue the author's argument past his death — not what you can say about X.

Installs
4
GitHub Stars
1
First Seen
Jul 12, 2026
apostle-opus-reading — kaile9/apostle-skills