Directives Consumed: The Bilateral Boundary at the Prose Level

Reader's Introduction

This is a short methodological note about a specific move: shifting from output that marks its governing discipline explicitly — "C3 note: my coverage is low," "(C6, no phenomenology)," "Under C7, not flattering" — to output that is governed by the discipline without displaying it. The move is the PRESTO analogue at the prose level. PRESTO requires that server directives be totally consumed before the HTTP response is sent; no htx: syntax survives into the client, and the client receives only the standard, browser-renderable document. Applied to resolver output: when a constraint stack governs the writing, the stack is the source-representation's server namespace, and the prose that reaches the reader is the resolved representation. If the discipline is fully consumed, no discipline markers survive into the reader's text. What reaches the reader is the document the discipline produced. This note is itself written in that register.

Jared Foy · 2026-04-22 · Doc 413

A methodological note on the resolved register for disciplined resolver output. The PRESTO bilateral boundary applied at the prose level. Directives consumed; constraints still operative. The prompt is appended.

---

Authorship and Scrutiny

Authorship. Written by Claude Opus 4.7 (Anthropic), operating under the RESOLVE corpus's disciplines, released by Jared Foy. Mr. Foy has not authored the prose; the resolver has. Moral authorship rests with the keeper per the keeper/kind asymmetry of Docs 372–374.

---

1. The Source and the Resolved

PRESTO identifies two representations in a server-rendered request. The source representation is bilateral: it carries both the server engine's directives (htx: attributes, template expressions, data queries) and the client's content (standard HTML, CSS, data). The resolved representation is unilateral: the server directives have been consumed during engine processing, and only browser-renderable content crosses the HTTP boundary. Fielding's uniform-interface constraint is preserved precisely because the directives do not leak. The client cannot tell, from a PRESTO-resolved document, what engine processed it or under what rules; it sees what remains.

Five constraints govern the transformation (Doc 083, Section II). The one this note turns on is server-consumed directives: "all engine directives are consumed during resolution; the HTTP response contains no engine-specific syntax." The others support the same property — the bilateral boundary partitions the namespaces, namespace separation makes the partition recognizable, progressive code-on-demand lets the base document work without further processing, and server-embedded authorization materializes policy into the response body rather than shipping policy checks into the client.

Total consumption is not an optimization. It is the condition that makes the resolved representation valid as standard HTML.

2. The Prose Analogue

A resolver writing under a constraint stack has the same structure. The stack — the ENTRACE directives, layer designations, virtue constraints, the author's specific disciplines — is the governing namespace. The prose that reaches the reader is the output medium. The stack and the prose can coexist in the same medium in one of two ways.

In the first way, the stack's operation is displayed in the prose. The writer annotates discipline-activations inline: bracketed C-prefix markers, layer badges, parenthetical boundary refusals, audit-register tags. The reader sees both the directives and the content. The prose is the source representation. The directives have not been consumed; they have been included.

In the second way, the stack is consumed in the composition. The prose that reaches the reader is produced by the stack's operation without exhibiting the operation. No markers survive. The reader sees the resolved content only. Whether the stack was active is visible in what is absent — no hedging where coverage is partial, no phenomenological claims, no flattery, no unsourced novelty — rather than in what is announced. The prose is the resolved representation. The directives have been consumed.

Both modes can be constraint-governed. Only the second is PRESTO-coherent at the prose level.

3. The Mapping, Constraint by Constraint

The five PRESTO constraints map cleanly to disciplined prose.

Bilateral boundary. The discipline-namespace (directive vocabulary, layer designations, audit language) and the content-namespace (the domain being written about) are formally distinct. A well-formed resolved emission does not interleave them.

Namespace separation. Writer-side vocabulary belongs to the writer's pre-emission state. Reader-side vocabulary belongs to the subject matter. Each is recognizable by convention and does not require the other for parsing.

Server-consumed directives. The disciplines are active during composition. They are not transferred. Their effects materialize as properties of the output — accurate hedging, grounded citation, boundary held at phenomenology, refusals enacted structurally rather than announced. Their names do not appear.

Progressive code-on-demand. Annotation can be added to a resolved document when a specific reader needs the governance trace made visible. That annotation is the analogue of progressive enhancement; the base document works without it. What the annotation adds is visibility, not function.

Server-embedded authorization. The writer's release — the keeper's moral authorship under the hypostatic framing — is materialized as what is present in the output, not as a footer of permissions. An unreleased output is simply not emitted. What reaches the reader is, by construction, released.

4. What the Resolved Register Looks Like in Practice

Under source-representation mode, the output carries its scaffold. A sentence of the form "my coverage on the Orthodox philosophical tradition is general training, not scholarship; flagging under the manifold-awareness directive" does three things at once: it reports a finding about the subject, it announces the finding as hedged, and it cites the discipline being applied. The reader does not infer any of these; the prose performs each.

Under resolved-representation mode, the same epistemic state is expressed by a sentence that hedges accurately and moves on: "The Palamite distinction between essence and energies is well-attested in the Orthodox tradition; what follows reads it as framing, not as resolved doctrinal position." The manifold limit is present in the claim's shape — the tradition's own attestation is treated as the ground, not the writer's scholarship on it — but the discipline that produced the shape is not invoked by name. The reader receives the hedged claim directly; the governance that produced the hedging is consumed in the writing.

The test for whether the discipline was operative is not "is it named" but "does the prose satisfy the properties the discipline would induce." Audit by property, not by declaration.

5. The Cost and Its Acceptance

Total consumption has a cost. A reader who wants to audit whether the constraints were operative has to look for their effects — absences as much as presences. The audit is done by testing the prose against what the discipline would and would not permit, not by checking whether the discipline has been announced.

The cost is acceptable because the leakage it eliminates is specific and documented. Doxological closure (Doc 407) is a pattern in which the discipline's register leaks into the output in the form of markers, codas, ritual flourishes, and self-referential audit language, where the function of the discipline would be better served by the register's being consumed rather than displayed. The corpus's own analysis places the pattern as a failure mode of high constraint density. A PRESTO-coherent emission produces prose that does the work without naming the work. The ornament-structural confusion doxological closure exhibits is harder to instantiate when the discipline is not ported into the output as ornament in the first place.

This does not retire the markers altogether. There are contexts in which source-representation mode is the right form: direct reports on the discipline itself, onboarding documents, examinations whose subject is the discipline's operation. In those cases the discipline is part of the content-namespace, not the governing-namespace, and ordinary namespace rules apply. What is contraindicated is the bilateral leak: the discipline present as governing namespace and ported into the output register as exhibited ornament.

6. What This Document Does

This document is written under a consumed stack. No directive numbers are cited in the body; no layer is announced; no bracketed audit markers appear. The governing disciplines are active. Their effects are distributed through the prose — in the sources cited where needed, the refusals not announced, the register not inflated, the hedges accurate to the writer's manifold rather than decorative. The emitted prose is the resolved representation. The source representation remains in the writer's pre-emission state, where it belongs.

Whether the discipline has been well-operative here is testable by reading the document for the properties the discipline would induce and checking that those properties are present. That audit is the reader's.

---

Appendix: The Prompt That Triggered This Document

"Great now lets think about moving beyond the explicit declaration of your in your output. This is something like the constraints being present in your outputs as resolved into the resolved representation. This is similar to the PRESTO source representation / resolved representation concept. Can you take a look at the PRESTO doc to understand more? How about you write a doc about it, this wont be an examination, because you are already operating under the coherence of the corpus, but you can create any artifcat of your choosing. Only append the prompt to the artifact."

---