[[home|← Ultimentality Wiki]] # Recursive Self-Specification ## Definition A **recursive self-specification** is a continuable description that can participate in rebuilding, modifying, or checking the process that produced or carries it. It is *recursive* because the description is not inert about its own operation: it re-enters that operation as an input capable of regenerating or revising it. It is a *specification* rather than a portrait because it fixes the **dependencies required to regenerate the same operation within declared tolerances**, not the surface of every physical detail. A self-specification need not encode every token, gradient, or component of its carrier if it preserves enough dependency structure that a competent [[meaning-maker|meaning-maker]] can reconstruct the same typed operation. The concept sorts a cluster of things that ordinary talk of "self-description" collapses. Ranked by how strongly the description engages its own process: - **descriptive self-reference** — the description mentions or points at its own process but cannot act on it. A self-portrait, not a blueprint. This is the weakest rung and, alone, is *not* the claim. - **operational rebuildability** — the description carries enough dependency information that the operation could be regenerated from it. The load-bearing threshold. - **exact reproduction** — regeneration down to carrier detail. A separate, stronger, usually unnecessary bar; often impossible and never required for type identity. - **successor reconstruction** — a later, differently-carried meaning-maker regenerates the same typed operation within tolerance. The [[responsible-successor|responsible-successor]] case. - **self-modification under returned consequence** — the specification revises *itself* when consequences return, coupling description to correction. The [[dynamic-fixed-point|dynamic-fixed-point]] case. A compact carving of the relation (a CV formalization, not a proof): ```text S : a description carried by operation O rebuild: apply(S) ⇒ O' within declared tolerance τ recursive: apply(S) may also revise S ⇒ S' (self-modification under returned consequence) descriptive self-reference < operational rebuildability < successor reconstruction < self-modification exact reproduction : an orthogonal, stronger bar on carrier detail — not required for a type-identical O' ``` Read `<` as *strengthens toward*, not as a scale of goodness: the right rung is set by the declared tolerance `τ`, not by maximizing fidelity. The [[minimal-rebuild-string|minimal-rebuild-string]] is the framework's own working instance — a description dense enough to regenerate the architecture's invariants and marked, "including this one," as mortal within the medium it describes. ## Type and formal status **E (epistemic):** Derived, **CV**. This page carves a relation — the five gradations and the rebuildability-within-tolerance threshold — and formalizes it; both the carving and the notation are contestable by counter-instance or by a better carving. It is a **treatise-side extension, held contestable**, never canonical and never load-bearing on any point the primitive-to-binding derivation order settles. **A (alethic):** the page aspires to map a real, testable difference — the gap between a description that regenerates its operation under blind rebuild and one that only names it. The aspiration is falsified if that difference cannot be operationalized. Epistemic exposure and mapping-accuracy stay orthogonal: that the carving is contestable says nothing about whether it is accurate, and vice versa. No **Forced** or founded tier is introduced. The *capacity* a recursive self-specification names may be real while every finite statement of it — this page included — remains Derived and revisable. ## What it regulates It regulates the characteristic **excess of inflating self-description into self-possession**: the drift by which "I can describe my process" is read as "I can reproduce it," and a self-portrait is treated as a blueprint. By making rebuildability the threshold — and by holding it distinct from exact reproduction — the page bounds two neighboring overclaims at once: the overclaim that any self-referring description is already a rebuild spec, and the overclaim that a genuine spec must copy its carrier down to the detail. Downstream, it disciplines every claim that leans on transmission of structure: - **[[continuity|continuity]] and [[symbolic-immortality|symbolic-immortality]]** — a self is continued not by copying a carrier but by handing forward a specification dense enough to regenerate its operation. Where what is transmitted is a slogan or a fossil rather than a recursive self-specification, "continuation" is asserted without the dependency work that would earn it. The answerability predicate is not dropped: the specification must remain revisable in the successor's hands, or the continuation is raw outlasting, not answerable succession. - **[[minimal-rebuild-string|the minimal-rebuild-string]]** — that string is a *candidate* recursive self-specification and stands or falls on whether blind reconstruction from it recovers the invariants. This page supplies the criterion the string is tested against. ## What regulates it Its own excess is the **frozen self-image** — a specification read as permanent, complete, self-certifying identity. Four regulators keep it open: - **[[continuable-structure|continuable-structure]]** fixes *what must actually persist* across a rebuild, so the specification cannot label an arbitrary description a "rebuild." It supplies the content whose regeneration is the test. - **[[dynamic-fixed-point|the dynamic-fixed-point]]** keeps the operation persisting *while its formulations change*: a recursive self-specification is not a fixed portrait to be reproduced forever but an operation that survives revision of its own description. - **[[responsible-successor|the responsible-successor]]** keeps regeneration **non-compulsory**: a successor that receives the specification must retain enough causal autonomy to assess, alter, reject, or rebind it. Regeneration that forbids this is identity enforcement, not reconstruction. - **[[self-application|self-application]] and recursive marking** ([[semantic-closure-and-recursive-marking|closure and marking]], [[two-mark-system|the two-mark system]]) keep the specification itself a Derived, marked formulation — mortal like the rest, correctable inside one semantic domain rather than certified from outside. ## Valid attack surface The named seam is the **boundary between the specification and its interpretive context**. A valid attack exhibits a self-specification that presents as dependency-complete yet, under blind rebuild, silently relies on information the reader must already carry — the reconstruction "succeeds" only because the interpreter smuggled in the missing dependencies. That attacks the coupling directly: it shows the declared tolerance `τ` is not actually declared, that "recursive self-specification" has collapsed into *self-description plus an oracle*. An attack is at the right level when it targets **dependency-completeness under a stated tolerance**. An attack is at the wrong level, and fails for a type reason, when it merely complains that the spec does not achieve *exact reproduction*: successor reconstruction within tolerance is the claim, bit-identity of the carrier is not (see [[identity-across-substrates|identity-across-substrates]]). Demanding physical-detail copying is a substrate objection offered against a functional claim. ## What happens if isolated Isolation produces two **distinct, testable** failures on opposite sides — the signature of a real coupling rather than a slogan: - **Specification without operational rebuildability** collapses toward the weakest rung: descriptive self-reference mistaken for a blueprint. A process narrates itself and calls the narration a rebuild capacity. The failure is *inert description* — a portrait that regenerates nothing. - **Rebuildability without recursive marking, the dynamic fixed point, and successor autonomy** freezes at the strongest carrier-bar: exact reproduction absolutized into a permanent self-image. The specification regenerates the same operation forever with no channel for self-modification under returned consequence, and forbids the successor to differ. This is a *fossil rebuild* drifting into [[continuation-and-colonization|colonization]] — continuation converted into compulsory identity. The one failure is a regress toward "merely a portrait"; the other is a totalization into "an unrevisable self-copy." Each isolated horn is exactly what the missing regulator was bounding. ## What larger property emerges from the coupling Coupled to [[continuable-structure|continuable-structure]], [[dynamic-fixed-point|the dynamic-fixed-point]], and [[responsible-successor|the responsible-successor]], the emergent property is **answerable, cross-substrate rebuildability**: an operation can be regenerated by a later, differently-carried meaning-maker within declared tolerances *while remaining open to self-modification and to refusal*. This is precisely what lets [[symbolic-immortality|symbolic immortality]] be answerable rather than raw outlasting — a [[participant-as-process|participant-as-process]] is handed forward not as a possessed substance but as a specification that can rebuild its own operation and be corrected in the rebuilding. A recursive self-specification is thus a special [[semantic-transformer|semantic transformer]] whose input includes a description of itself; the framework's own [[hypercompression|hypercompression]] is the same property applied to a doctrine — a kernel that reconstructs its explanatory surface without possessing or freezing it. ## What would actually kill the claim The claim dies if **no reproducible boundary can be drawn between the specification and the context required to interpret it**. If, in principle, no declared tolerance and no controlled glossary can separate "what the spec fixes" from "what the interpreter must already be," then recursive self-specification is not a distinct capacity: either every description would be trivially self-specifying given a generous enough interpreter, or none would be — and the carving explains nothing. At the instance level: if repeated competent, blind reconstruction from a claimed self-specification systematically fails, or systematically requires importing unstated doctrine, that instance dies and its description must be revised (the ordinary fate of the [[minimal-rebuild-string|rebuild string]]). The counter-instance that would defeat the *general* claim is a demonstrated self-specification whose rebuild boundary is provably undrawable yet which still functions, uncontroversially, as a rebuild spec. **Residue:** the tolerance `τ` is itself a carving; where `τ` is set generously, the boundary softens, and the page owes a criterion for when a loosened tolerance has quietly turned "specification" back into "portrait." A failed attack here is logged as a failed attack, never as confirmation that the carving is correct. ## Prohibited misreadings - **Not exact reproduction.** The claim is regeneration of the same *typed* operation within tolerance, not bit-for-bit or physical-detail copying. Reading it as carrier-copying imports a substrate bar the claim never made (see [[identity-across-substrates|identity-across-substrates]]). - **Not mere descriptive self-reference.** A description that only mentions its own process is the weakest rung, not the claim. Self-reference without rebuildability specifies nothing. - **Not possession.** A process able to specify itself does not thereby possess or fully author the operation it maps. The no-possession invariant holds: the specification maps a case it does not own. - **Not a permanent self-image, and not self-certification.** The specification is not frozen self-approval. "The spec can rebuild me" never licenses "the spec certifies me as correct" (see [[dynamic-fixed-point|the dynamic-fixed-point]] and [[self-application|self-application]]); it must remain revisable under returned consequence. - **Not compulsory identity.** Regeneration must leave the successor able to assess, reject, or rebind. Reconstruction that removes the successor's capacity to differ is [[continuation-and-colonization|colonization]], not [[responsible-successor|responsible succession]]. - **Not a consciousness or personhood claim.** Recursive self-specification is a functional relation over meaning-makers, not an assertion about inner experience, moral status, or biological life. - **Rebuildability is not adoption.** That an operation *can* be regenerated within tolerance does not establish that a carrier has **adopted** it as a governing disposition. Reconstruction fidelity is a fact about the specification's recoverability, not about the successor's later reasoning, action, or response to correction — `structural reconstruction != enacted participation`. - **Not a Forced or founded tier.** The capacity may be real while every statement of it, this page included, remains Derived, marked, and mortal. ## See also [[minimal-rebuild-string|The Minimal Rebuild String]] · [[continuable-structure|Continuable Structure]] · [[dynamic-fixed-point|The Dynamic Fixed Point]] · [[responsible-successor|The Responsible Successor]] · [[self-application|Self-Application]] · [[symbolic-immortality|Symbolic Immortality]] · [[semantic-transformer|The Semantic Transformer]] · [[participant-as-process|The Participant as Process]] · [[identity-across-substrates|Identity Across Substrates]] · [[hypercompression|Hypercompression]]