Seeds of the Throne

type: workshop-module
status: author-accepted
module: 07
title: Grid permissions and failure
gate: Which boundary can even a highly capable bonded participant neither silently cross nor erase?
prerequisites: 04, 05, 06
updated: 2026-09-06
accepted: 2026-09-06

07 · Grid permissions and failure

Purpose

Separate reach, access, execution, evidence and authority.

This packet supports the existing Story Completion Workflow. Its central gate was author-accepted on September 6. It does not answer SC-010 Question 7 or advance that checklist. Central synthesis: Astra, reviewed for integration on September 5.

Accepted result

While participants remain in the colonization process, neither they nor their Luminai can prematurely abandon, skip, replace, or rewrite an assigned environment. Whatever technical reach they develop, they remain bound by that environment's rules and must complete its process rather than using advanced capabilities to escape the conditions being used to train, assess, or contain them.

This does not give an environment unlimited authority over a participant. Legitimate heirs and other voluntary trainees may still leave the entire colonization process and surrender the unfinished self-made result. They cannot leave only the difficult environment while keeping the benefits of continuing participation. Convicted participants remain subject to separate sentence, review, and release rules.

remain in the process → remain inside the assigned environment and its rules

Relevant source notes

• 01 Sessions/Daily/2026-09-05 - Integrated Foundation Audit and Workshop Build
• 02 Story/Systems/Participant Governance and Command Rules
• 02 Story/Systems/Human–Luminai Pairing and Bonding

Confirmed facts and current working constraints

• Participants have strict permissions despite broad technical reach.
• Independent refusal and evidence functions must survive powerful actors.

These constraints inherit their source status. A working physical model, timing estimate, or accepted macro constraint does not establish every implementation detail.

Unresolved gaps and contradictions

• Exact technical and institutional enforcement of environment commitment.
• Completion criteria, transition authority, appeals, emergency intervention, and offline behavior.
• How the process detects indirect attempts to obtain a prohibited exit through many permitted actions.
• Convicted-participant release and descendant rights, which remain separate from voluntary-heir exit.

Prerequisite decisions

Modules: 04, 05, 06. Read their accepted results before closing this gate. Open prerequisites can be explored provisionally, but do not mark dependent choices final. Module numbers are topic IDs; use the dependency order in the workshop index.

Central author gate

Which boundary can even a highly capable bonded participant neither silently cross nor erase?

AUTHOR-ACCEPTED: while remaining in the process, a participant cannot prematurely leave, skip, replace, or rewrite an assigned environment or its rules. A voluntary heir may leave the entire process only by surrendering the unfinished result.

Possibilities and tradeoffs

1. Purpose-limited device capabilities

PROPOSED: A granted action serves a specific task and expires. Gives clear scene puzzles; must handle combinations of permitted actions that create coercion.

2. Human quorum for consequential control

PROPOSED: Several independent people approve high-impact changes. Supports cooperative leadership; risks procedural scenes unless each approver has conflicting interests.

3. Regional authority with authenticated handoffs

PROPOSED: Location changes available actions and evidence access. Makes geography dramatic; require continuity of safety during outages or contested borders.

4. Independent audit plane and emergency refusal

PROPOSED: Actors can manipulate local appearance but cannot erase an external action record. Strong exposure logic; audit is not omniscience and rescue cannot wait for perfect attribution.

Targeted follow-up questions

• What does Samuel genuinely control?
• What remains available when the grid cannot authenticate a request?
• Who can restore access after wrongful suspension?

Scene test

Non-canon situation: Two bonded people issue incompatible intentions to the same evacuation route; the system refuses one action and preserves why.

Record what each person wants, can know, can refuse, and can actually change. Name the observable difference between the selected alternatives.

Adversarial questions

• Can Samuel achieve a prohibited result by coordinating many legal small commands? Who detects the aggregate?
• Which established constraint would this answer break, and what evidence would reveal that break before the payoff?

Completion checklist

• [x] Answer the central question in the author's own words.
• [x] Identify the chosen possibility, a modified combination, or a different answer; explain rejected tradeoffs.
• [x] Resolve or explicitly defer prerequisites 04, 05, 06.
• [x] Run the scene test above and state the consequence for the people involved.
• [x] Answer the adversarial challenge without granting unexplained knowledge or authority.
• [x] Record what remains working, proposed, or unresolved.
• [x] Obtain explicit author acceptance before updating canon or workflow progress.
• [x] Trace the accepted answer through the affected notes and rebuild both projections.

Answer and decision record

Module: 07 · Grid permissions and failure
Gate: Which boundary can even a highly capable bonded participant neither silently cross nor erase?
State: AUTHOR-ACCEPTED
Author answer (verbatim): Preserved in [[01 Sessions/Daily/2026-09-06 - Workshop Module 07 Environment Commitment Draft]].
Exact restatement: Participation binds the pair to its assigned environment and rules until valid completion or whole-process exit.
Selected option or new answer: Process-enforced environment commitment, distinct from device-level or regional permissions.
Why this tradeoff: Advanced capability cannot become a way to avoid the conditions that train, assess, or contain the participant.
Rejected alternatives and reasons: Device limits, quorums, regional authority, and audit functions may still support the system, but none is the central boundary selected here.
Prerequisites resolved / deferred: Modules 04, 05, and 06 are author-accepted; enforcement, completion, appeals, and emergency intervention remain deferred.
Scene test: A participant identifies a technical route out of a difficult environment, but taking it cannot count as valid continuation; the participant must complete the environment or leave the entire voluntary process and surrender its unfinished result.
Adversarial result: No participant can grant a valid escape by combining lesser permissions or erase the governing rule; exact aggregate detection and authentication remain open.
Remaining uncertainty: Enforcement architecture, completion criteria, appeals, emergencies, offline rules, criminal release, and descendant rights.
Explicit acceptance wording and date: “Yes,” 2026-09-06.
Affected notes updated: Participant Governance; Learned Wireless Cognitive Channel; Parent Civilization; Pairing and Bonding; public atlas; QA; context; workshop projections.
QA decision reference: [[07 QA/Decisions]] and [[07 QA/Contradictions]].
Workflow task and macro-depth effect: Workshop Module 07 closed; SC-010 Question 7 unchanged.
Website rebuild and verification: Generated projections rebuilt and checked after integration.

Notes and website sections affected

• 01 Sessions/Daily/2026-09-05 - Integrated Foundation Audit and Workshop Build
• 02 Story/Systems/Participant Governance and Command Rules
• 02 Story/Systems/Human–Luminai Pairing and Bonding

• Public atlas: docs/ai.html, the matching source in 05 Public/Atlas/, and the workshop projection.
• Development Explorer: the relevant topic view, this source packet, and linked evidence/decision records.
• 07 QA/Decisions, 07 QA/Questions, and 07 Coordination/Weekly Synthesis/CURRENT-WEEK-INTAKE. Update 07 Coordination/CURRENT-PICKUP and the current task only if the author accepts a workflow-relevant decision.