Protocol Does Not Transfer
permission → boundary → relationship → correction
Permission in one field does not grant access in another.
This page belongs under Two-Eyed Seeing. The parent page names lineage and holding. This child page names the boundary: protocol is field-specific, relationship-specific, and correction-bearing.
▸ Open MaxCP
▸ ◉ Key Insight
Resonance is not permission. Permission is specific to field, relationship, protocol, and scope.
Resonance opens responsibility, not entitlement.
▸ ⚡ Mantras
- Resonance is not permission.
- Permission is not portable.
- Protocol begins before use.
- Correction is part of relationship.
- Refusal must remain available.
- Removal is not failure when removal preserves the boundary.
▸ ↺ Flowchart
Resonance appears → pause.
Lineage differs → do not transfer permission.
Public teaching is referenced → attribute and bound.
Use extends into a new frame → seek correction.
Permission opens → proceed only within bounds.
Permission narrows or refuses → revise or remove.
▸ ⌘ Micro-Lexicon
- Protocol — the living process by which access, relationship, and responsibility are established.
- Permission — authorization within a specific relationship, field, and scope.
- Resonance — perceived alignment; a signal to approach carefully, not proof of access.
- Correction — guidance that changes the work, not feedback that decorates it.
- Etuaptmumk — a Mi’kmaw teaching; not ARF-originated and not automatically authorized by permission from another Indigenous field.
- nəc̓aʔmat — a Coast Salish teaching shared with permission and integrated into ARF’s Gate.
Protocol Doors
This page has four doors. Use them to keep permission from being treated as portable property.
Name the Field
Permission belongs to a specific relationship and lineage context. Name the field before carrying anything from it.
Do Not Transfer
Permission from one field does not authorize use in another. Similarity is not access.
Seek Correction
The request enters a living field. Response, narrowing, refusal, or removal must be able to change the work.
Accept Refusal
If the gate does not open, the term falls away. Refusal preserves the relationship and the integrity of the work.
Name the field. Do not transfer permission. Seek correction. Accept refusal. That is the process.
Orientation Stream
Protocol, Permission, Lineage, Correction, Relationship, Refusal
This page records an active permission process. ARF has permission to use nəc̓aʔmat within its Gate. That permission does not transfer to Etuaptmumk / Two-Eyed Seeing. A separate relationship requires separate protocol.
Protocol
Access is established through relationship, process, response, and ongoing responsibility.
Permission
Authorization is bounded by the field that gives it. It does not become portable once received.
Correction
Correction must be able to alter wording, scope, placement, or use. Otherwise the process is ornamental.
Refusal
A clean no is not a failed relationship. It is a live boundary doing its work.
Permission-Seeking Is Currently In Process
The permission-seeking process is currently in progress.
The request has not been completed as a settled relationship, certification, or endorsement.
The present work is to approach properly, ask cleanly, offer compensation, remain correctable, and accept refusal if it comes.
This page is being written during the process.
That matters.
Protocol is not something added after the work is finished to make it look respectful.
Protocol is part of the work.
The gate is not decoration.
The gate is live.
The Edge of One Permission
ARF’s Gate carries nəc̓aʔmat because permission was given within that relationship.
That permission matters.
It also has a boundary.
Permission from one Indigenous field does not authorize use of a teaching from another Indigenous field.
Coast Salish permission does not automatically grant Mi’kmaw permission.
To pretend otherwise would collapse difference into convenience.
So the movement pauses.
The next field is approached as itself.
The Bridge Requires Its Own Protocol
Etuaptmumk / Two-Eyed Seeing resonates strongly with ARF’s way of holding structure and relationship together without collapse.
But resonance does not authorize carrying.
The bridge must be built through relationship, not assumption.
Resonance is not permission.
Permission is not portable.
Permission-Seeking as CIP
Permission-seeking is not paperwork performing humility.
It is a live communicative loop.
It is CIP in action.
I enter with intent.
The other side has intent, boundary, responsibility, knowledge, and protocol already present.
My intent does not overwrite theirs.
The request enters the field.
The response changes the field.
Protocol is co-constructed through the encounter.
吞 — Read
Read the field before assuming access.
吐 — Request
Make one clean request.
浮 — Receive
Receive the response without defensiveness.
沉 — Settle
Integrate the answer and update the work.
That process is the teaching.
If Permission Opens
If permission opens, ARF proceeds within the bounds given.
That may mean:
- keeping the public reference with corrected wording,
- adding clearer attribution,
- learning more before saying more,
- placing limits around what ARF may claim,
- or building an ongoing relationship rather than treating permission as a one-time stamp.
Permission is not a trophy. It is responsibility.
If Permission Narrows or Refuses
If permission is not granted, or if correction indicates the named teaching should not be used, ARF will remove public references to Etuaptmumk / Two-Eyed Seeing.
The underlying ARF process will remain describable without carrying the name.
The WHAT is structure. The HOW is the relationships through which structure manifests.
Removal would not be failure.
It would be protocol working.
Refusal preserves the system by naming what cannot proceed.
A clean no is still a gift.
It tells the work where it may not go.
The AI-Assisted Request Question
The request itself may be AI-assisted.
That raises a real protocol question: does AI assistance change the nature of the request, the authorship, the responsibility, or the disclosure required?
This question is part of the field.
AI may help draft, clarify, and organize the request.
It cannot carry the relationship.
It cannot receive permission.
It cannot be corrected in my place.
It cannot pay the cost of misuse.
The responsibility remains human.
If AI helped prepare the request,
that should be disclosed cleanly.
Living Culture, Living Protocol
Inviting an Elder or appropriate steward to speak into this process would not be asking the past to approve the present.
It would be a living conversation.
Tradition is not fossilized.
Protocol is not dead paperwork.
Culture is not a museum label under dim glass.
A living culture can meet modern tools without becoming less itself.
The question is not whether tradition can encounter AI.
The question is whether the encounter is relational, accountable, bounded, and correctable.
Modern does not mean unrooted.
Traditional does not mean frozen.
Protocol Hints
Use these when resonance appears and the urge to carry the teaching arrives before the relationship does.
Check the field. Who gave permission, for what use, in what relationship, and under what limits?
Check response. If correction cannot alter wording, placement, scope, or removal, the process is not real yet.
Check refusal. If the named teaching cannot be removed after refusal, the page is treating permission as decoration.
CTA Rail
This child page records the permission process as part of the work: one field reached its boundary, another field requires its own protocol, and the bridge must be built through relationship.