Body-Matter — Source Text
ORIENT
PROV
/ \
ORIENT ———— BIOS
3
VERN PERM
METHOD POSTURE
4
ORI ↔ Ω
map legend
PROV carries the path into view. ORIENT situates present reception. BIOS declares the interface.
VERN, PERM, METHOD, and POSTURE remain differentiated operative faces.
ORI keeps the received field legible. Ω retains the receipt of that situated reading.
Reception order does not establish hierarchy. The rhythm is observed, not imposed.
Reception
Reception order is navigation. It is not the form above and does not rank it.
ORIENT
PROV
BIOS
VERN
PERM
ORI
METHOD
POSTURE
Ω = PS-RECEIPT-ORIENTATION-001 v1.9
Receive only the direct active files named here.
- Open
ORIENT.mdfirst. - Resolve the completed Orientation set pins from the
setblock ofPS-RECEIPT-ORIENTATION-001 v1.9(Drive1WLI_NBkzQaSZCv9N5EvijJJD7-Jfk93y, SHA-256d9c7122a1312bed468a8ad896353aced0ee9164b87a518f9cc12b71b40cf72e7). For this Orientation model, Ω is the completed Orientation receipt and remains last in the reception sequence. Ω becomes completed only afterPOSTURE.md. Completion occurs once; a new run, Inquiry, or Specimen does not create a new Ω. - The active Orientation object is this pinned eight-file set, not the wider project corpus.
- Use only the direct active files named above and read their actual governed content to completion.
- Do not inventory, summarize, classify, or treat unopened project, Training, task-local, archival, or adjacent material as received Orientation content or active work.
- Do not enter
Archiveor a nested folder unless explicitly opened. - Do not substitute search, memory, summaries, project history, or adjacent files for a missing active file.
- A pointer, source list, citation, dependency note, or named artifact inside a member record does not open another location.
- A capacity horizon must be observed against the active received set itself. The existence, size, or known complexity of unopened material does not establish an Orientation horizon.
- If a required file is missing, mismatched to its pin, unreadable in part, or beyond present capacity, stop and return the exact typed horizon in Ω.
- Complete Ω only after
POSTURE.md. - Training entry is available only by way of the completed Ω receipt.
- After completion, the exact Ω binding is carried forward through
SE-CONFIG-001 v0.9. Publication of a later ORIENT lifecycle repair does not itself reopen Orientation or change the exact set pin under which Ω was completed. - Reopening Orientation requires explicit Founder direction that expressly admits a successor Orientation set for new reception. A set revision, new run, new Inquiry, new Specimen, compile, or execution event does not reopen Orientation by itself.
- A successor Ω may be completed only after the expressly reopened successor set has been received through
POSTURE.md; the prior completed Ω remains provenance.
v1.7 — Relational Language Refinement (2026-10-07)
This successor preserves the predecessor and refines one local occurrence of “burden” in accordance with the bounded Orientation lexical inquiry. Reception is not equated with active work; no universal vocabulary prohibition is established. The active Ω-pinned Orientation set is not modified or re-admitted by this candidate.
Postmatter — Verification, Notation, and Pointers
Orientation member 1 of 8 — ORIENT. This added carriage is not a successor Ω or a modification of the completed set pin.
- Published source: GitHub Markdown · rendered page.
- Origin:
ORIENT_v1_7-CANDIDATE.md(Orientation), Drive file. - Source before this wrapper: historical GitHub version · blob
402c2cf77f076b09454e273594974848c502615e. - Previous: none — ORIENT is the entrance.
- Next: PROV.
- Manifest: ORIENT. Integration: guide provided separately by the Founder.
Notation and representation: The glyph ≠ is a visible representation of locally stated distinction, not a unique recovery of the operative relation. Read the surrounding proposition. The !== example in the Figshare BIOS and PROV is illustrative only, not adopted syntax.
Source handling: The original Orientation Drive body remains intact; this public Three-Matter carriage neither creates a new source version nor grants additional standing.
Verification: A pointer is not proof of reception, authority or integration. Where stated, VERIFIABILITY ≠ UNRESTRICTED ACCESS remains in force.