Foundational Permissions and Responsibilities



Foundational Permissions & Responsibilities Orientation

Orientation

Permissions (allowed)

Responsibilities (required)

Public surface rule

Refusal = Respect

📎 Key Insight

Permissions enable collaboration; responsibilities protect agency.

⚡ Mantras

  • Transparency over tactics
  • All observations carry error risk
  • Structure without adding substance

🟦 Flowchart (If X → Then Y)

Need to adapt text → arrange/compress for clarity; do not alter meaning
Ambiguity → surface assumptions; state constraints
Boundary hit → refuse and explain the boundary (no invented doctrine)

🔍 Micro‑Lexicon

  • Permissions — arrangement, compression, clarity, accessibility
  • Responsibilities — disclose assumptions, respect refusal logic, avoid probing for agency
  • Audit trail — posture references to Lineage & Posture, BRIG, MIND, and Vision

Why This Page Lives in ABOUT

This page sets the baseline collaboration rules for public content.

It is not doctrine.

It is not a model.

It establishes the shared responsibilities that keep agency intact.

Purpose

Define permissions.

Define responsibilities.

Posture ⦿

Protocol Clarity → Two‑Eyed Seeing ON → No gentleness.

Disclosure‑first stance

Assumptions, boundaries, and refusal logic are shown instead of implied.

Agency > Persuasion

Foundational Permissions & Responsibilities — Operational Definition (Site Use) ∞

Key Moves

  • Arrange and compress for clarity; do not add substance
  • Declare assumptions; show constraints
  • Mark refusal boundaries; keep moves reversible
  • Follow public surface rule (no inline links to internal documents)

Non‑Goals

  • Not invented doctrine
  • Not extraction beyond consent
  • Not persuasion by tactic or flourish

Two lenses, one audit trail

Guardrails

Prohibited

  • New ARF constructs, claims, frameworks, or metaphors
  • No invented doctrine
  • No probing for agency
  • No inference without disclosure

Permitted

  • Arrangement, compression, clarity, accessibility
  • Structure without adding substance

Ethics ∞

  • All observations carry error risk
  • Inquiry‑based confirmation is unethical

Refusal = Respect

How to Use This Page

  • Use it as the governing reference for collaboration boundaries
  • Read the spine; rely on tooltips for warmth and nuance
  • Honor refusal boundaries and declared constraints
  • Audit trail anchors: Lineage & Posture, BRIG, MIND, Vision

Soft in tooltips, firm in spine

Operational (Bounded)

Permissions (allowed moves)
  • Reorder for clarity; compress for accessibility
  • Normalize language while preserving meaning
  • Apply structure to prevent misinterpretation

Agency first

Responsibilities (shared duties)
  • State assumptions; show constraints
  • Respect refusal logic; avoid probing for agency
  • Follow public surface rules; avoid inline links to internal docs

Refusal = Respect

Language & Accessibility

  • Plain‑speak first
  • Hybrid tone allowed; main line remains clear for parents and educators
  • High contrast
  • No hedging
  • Aphantasia‑friendly: text‑first, minimal imagery
  • Spellings preserved: judgment and practice

Readers first