Method and Collaboration



nəc̓aʔmat — permission & centre

Method & Collaboration
Orientation

Orientation → Wayfinding → Coherence → Action.

This page shows how the site is made: method, collaboration (including AI), boundaries, and how disclosure & logging work — so readers can see posture and process, not just outcomes.

📎 Key Insight

BRIG runs the build; text‑first minimalism makes work legible; strict governance protects authorship, lineage, and safety.

⚡ Mantras

  • Ship small, ship often.
  • Reveal all work — posture and process, not just polish.
  • Repair is a feature.
  • No default images.

🟦 Flowchart

Need to draft → Brush
Draft is rough → Repair
Ambiguity persists → Invite
Ready to publish → Govern
Contains private/sensitive info → Stop & remove

🔍 Micro‑Lexicon

  • BRIG — Brush, Repair, Invite, Govern (build loop).
  • Text‑First Minimalism — high contrast, short sections, visible BOMB; soft tooltips.
  • Meikyō Shisui — 明鏡止水, clear mirror, calm water (posture).
  • Protocol S — strict containment; no novel generation; compression + consistency only.
  • BOMB — block‑level emphasis; Bomblets — inline tooltips.

Method — Clarity Engine ∞

Structure — BRIG loop: Brush → Repair → Invite → Govern.

Moves from first pass → refinement → clarity → safeguards.

  • Brush: First articulation — put words down fast.
  • Repair: Tighten, remove noise, align with intent.
  • Invite: Ask better questions, triangulate perspectives, widen context.
  • Govern: Boundaries (disclosure, permissions, safety, lineage, scope).

Text‑First Minimalism — Meikyō Shisui ⦿

  • No default images (ethics + accessibility + aphantasia‑friendly).
  • High contrast, short sections, visible BOMB; elaboration in soft tooltips.

Collaboration — Human–AI Roles

  • Human: Author, steward, final decider.
  • AI: Language exoskeleton, structure, compression, QA prompts, rail‑guides.

Modes

  • Protocol S: Strict containment for doctrine/book/dissertation; no novel generation.

Governance — Boundaries

  • Safety: Student‑safe, non‑harm; no sensational content.
  • Consent/Permissions: Honour explicit permissions (e.g., Elders, collaborators).
  • Lineage: Attribute frameworks and influences clearly.
  • Data Care: No publishing private/sensitive info.

Live‑Draft Philosophy

  • Ship small, ship often — clarity grows through iteration.
  • Reveal all work — readers get posture and process, not just polish.
  • Invite correction — repair is an intentional feature, not a flaw.

Page‑Level Disclosure

This page was prepared under Protocol S. Copilot assisted with structure, clarity, and refinement; Tony reviewed and approved all final content.