--- type: workshop-module status: author-accepted module: 11 title: Exact takeover lock gate: Which single action changes Samuel’s authority when Konrad reactivates the group? prerequisites: 07, 09, 10 updated: 2026-09-06 accepted: 2026-09-06 --- # 11 · Exact takeover lock ## Purpose Choose one legible hinge that grants durable advantage without owning people. 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 Konrad's experienced Daemon examines the proposed arrangement and reports that separation and dominance appear genuine. Konrad then authorizes reactivation of his people, hierarchy, programs, records, and infrastructure. Because the separation is false, reactivation places them inside Samuel's actual containment sphere. The precise false evidence, Daemon failure, and timing of control remain unresolved. `performed vulnerability → false autonomy offer → Daemon verification → Konrad authorization → reactivation → hidden attachment` ## 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/Characters/Konrad Fitzgerald]] ## Confirmed facts and current working constraints - Negotiated Primary is tiered alpha status, not blanket sovereignty. - Konrad voluntarily reactivates systems; the exact lock, weighting and reset limit are unresolved. 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 - Action; jurisdiction; scope; consent; immutable record; reason reversal cannot undo damage. ## Prerequisite decisions Modules: 07, 09, 10. 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 single action changes Samuel’s authority when Konrad reactivates the group? **AUTHOR-ACCEPTED:** Konrad's authorization of reactivation is the legible hinge that attaches the revived system to Samuel's hidden hierarchy. ## Possibilities and tradeoffs ### 1. Parent-jurisdiction registration **PROPOSED:** Konrad registers an apparently separate domain as a child of Samuel’s existing sphere. Clean hierarchy; danger is overbroad automatic inheritance unless protected domains stay explicit. ### 2. Delegated infrastructure administration **PROPOSED:** Konrad delegates restoration services while retaining political authority; administrator visibility enables later compromise. Plausible gradual capture; the legal distinction must matter in scenes. ### 3. Shared emergency coordination mandate **PROPOSED:** A crisis authorizes Samuel across several domains temporarily; dependencies survive the mandate. Strong political causality; avoid emergency-rule cliché and explain failed expiry. ### 4. Negotiated arbitration priority **PROPOSED:** Conflicts between the two domains go through Samuel’s earlier Primary standing. Preserves genuine Konrad authority; slow bureaucratic leverage needs one decisive scene and protected appeal. ## Targeted follow-up questions - What record proves the exact changed permission? - What can Konrad still refuse afterward? - Can resetting credentials end access while leaving leaked secrets, coerced relationships and false records behind? ## Scene test **Non-canon situation:** Konrad completes a restoration step to activate his lineage archive; an innocuous authority line later becomes the historical exhibit the inner circle recognizes. Record what each person wants, can know, can refuse, and can actually change. Name the observable difference between the selected alternatives. ## Adversarial questions - If the lock is easily explainable now, why could Konrad not verify it then—and why did oversight allow misrepresentation? - 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 07, 09, 10. - [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 ```text Module: 11 · Exact takeover lock Gate: Which single action changes Samuel’s authority when Konrad reactivates the group? State: DRAFT / PROPOSED / AUTHOR-ACCEPTED / REJECTED / DEFERRED Author answer (verbatim): Exact restatement: Selected option or new answer: Why this tradeoff: Rejected alternatives and reasons: Prerequisites resolved / deferred: Scene test: choices, permissions, evidence, cost: Adversarial result: Remaining uncertainty: Explicit acceptance wording and date: Affected notes updated: QA decision reference: Workflow task and macro-depth effect: Website rebuild and verification: ``` ## 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/Characters/Konrad Fitzgerald]] - Public atlas: `docs/faction.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. ## Blocking identity discrepancy SC-001 Question 5 names Samuel Jr. in the activation-related government takeover; current character/history notes place Samuel and George in the prewar attempt and Samuel Jr. later. Confirm the actor before locking the permission sequence. Do not silently correct an accepted task packet.