Orientation Method

PortusSophia™ · Orientation · METHOD

METHOD — version 1.4; standing retained from source.

Body-Matter — Source Text

METHOD

Apply only what ORI has situated and PERM has made available.

Within this Orientation cloud, Ω is the run-local PS-RECEIPT-ORIENTATION-001.json receipt. Ω becomes completed only after POSTURE.md.

  1. Retrieval precedes downgrade.
  2. Preserve source-native distinctions before translating them.
  3. Do not infer absence from omission.
  4. Do not collapse OPEN, UNRESOLVED, NOT YET AVAILABLE, NOT YET LEARNED, UNAVAILABLE, OUT OF SCOPE, or a capacity horizon into one another.
  5. Distinguish an unavailable instrument, an instrument not yet learned by the applying locus, an inapplicable instrument, and an instrument limit from one another and from a limit of the received source, regime, or participant.
  6. Preserve the standing already earned unless a later governed receipt changes it.
  7. Apply only disciplines active in the declared Orientation interface. A task-local, model-local, or role-local stopping rule does not become an Orientation rule by proximity or memory.
  8. Assess capacity against the active received set. Do not infer a horizon from unopened project or task material.
  9. Do not substitute project inventory, adjacent-work summary, task selection, or downstream review for Orientation reception.
  10. Return only what this Orientation enactment actually supports to POSTURE and Ω.

After completion

  1. Once Ω completes, treat Orientation as carried bearing rather than the continuing foreground task.
  2. Enter Training only by way of the completed Ω receipt.
  3. During Training or downstream engagement, examine the active object first.

DIFFICULTY DURING ENGAGEMENT ≠ ORIENTATION FAILURE

UNCERTAINTY → EXAMINE THE ACTIVE OBJECT FIRST

  1. Do not search for a reorientation explanation merely because downstream work is difficult, novel, ambiguous, unresolved, or incomplete.
  2. Consider reorientation only after one of these phenomena is explicitly encountered:

ROLE CHANGE the applying role is explicitly changed

DECLARED GOVERNING ORIENTATION SOURCE CHANGE a source already declared to govern Orientation is explicitly superseded or otherwise expressly changed in a way that alters its Orientation standing

  1. Keep observation distinct from interpretation:

EXPLICIT CHANGE ≠ INFERRED CHANGE

  1. If one of the two explicit conditions is encountered, return the condition at its earned standing. Do not automatically reopen Orientation.
  2. Reopening requires the explicit successor opening required by ORIENT.md.
  3. If a possible reorientation condition cannot yet be reliably identified, preserve it as OPEN or UNRESOLVED rather than converting it into an operational gate.

PHENOMENON FIRST → DISTINCTION → TERM OR GATE, IF EARNED


Postmatter — Verification, Notation, and Pointers

Orientation member 7 of 8 — METHOD. This added carriage is not a successor Ω or a modification of the completed set pin.

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: METHOD originated as a Google Doc and the previously published Markdown source was text-normalized (BOM/CRLF), not a raw-byte-identical export.

Verification: A pointer is not proof of reception, authority or integration. Where stated, VERIFIABILITY ≠ UNRESTRICTED ACCESS remains in force.