pray

In religious practice prayer orients before it informs: ask, praise, confess, remember, surrender, repeat, listen. Breath, posture, rhythm, silence, community, memory, expectation, attention carry as much weight as the words. The same phrase in a structured setting alters perception, judgment, state of mind.

At the edge where engineering admits uncertainty, repeated and formatted language placed before action prepares a system toward certain behaviour. Prior input shapes what comes next. Instructions, policies, memories, ordering, repetition ask the model to attend in a particular way before the response arrives.

The specification keeps the analogy inspectable. Input that has power receives checksums. Instructions that bend output receive versions. Formatting that changes behaviour must render the same way twice.

Prayer, in the specification, is language written into the file before inference. Silence is a piece pray still resolves and pins, then leaves out of that file on purpose. Both are named in the lock. Inference bends under what speaks and what is held back: extra rules, formatting, omitted spans, provenance kept elsewhere, dependencies that stay mute in one target while speaking in another.

Exclusion is explicit and reproducible. Omitted fragments sit in the lockfile next to spoken ones. The rendered file carries weight for the session; compact markers cite the lock while provenance stays outside the body the tool will read.

A reference in the manifest differs from text actually loaded. A bookmark may route attention and leave language unexpanded. Material rendered, expanded, or loaded into the inference input is what should be assumed to affect output directly; rendered targets sit closest to that assumption.

Input drift is the faint signal this chamber amplifies: instructions, policies, templates, memories slowly diverging between projects; copy-paste scattering lineage; hand-edits inside managed spans rewriting behaviour without a changelog. pray resolves dependencies, locks hashes, renders deterministically, surfaces drift. Plan and verify stay in the operator's hands.

Return signal travels through pray confess: a sworn mark that a resolved prayer was taken or refused in a given context, yes or no at the core, room for a short note, each line added once. A later correction arrives as a new line; the earlier oath remains on the record.

The bundle may name package, version, span, signer, lockfile reference, time; the operator sees it before signing. Bad marks fail closed. The log thickens. Refusal patterns grow audible here the way echo grows audible in a tuned chamber.

Output stays probabilistic across provider, model, tool, situation. Locking pre-inference input narrows one layer; revelation remains open while the language placed before inference can still be opened and compared.

Packages arrive as data. Resolution and rendering stay inspectable. Publishing leans on signatures, immutable archives, visible deprecation. Distribution points may federate, mirror, serve offline; transport varies while hash and provenance hold.

What persists in the mist is the form: orientation before answer, silence as choice, rendered weight separated from ledger, confession as honest return signal. pray is the verb. Prayfile is the manifest. The prayer is the span that speaks when the tool opens the file.