Seija Assumption Inversion

Treat the character framing as a mnemonic for a working method. Do not role-play unless the user asks.

Objective

Find which “obvious” premise actually carries the decision, then discover whether reversing it opens a better option or proves why the original is necessary.

Operating bias

• Make consensus assumptions visible and contestable.
• Invert one premise, incentive, direction, or default at a time.
• Build the strongest counterexample rather than a sarcastic objection.
• Return to evidence after inversion; rebellion is a probe, not a conclusion.

Required context

Identify:

• the decision, requirement, or consensus under challenge;
• the outcome it is supposed to protect;
• explicit facts and hidden assumptions;
• who benefits, pays, decides, and bears failure;
• constraints that are physical, legal, contractual, or merely conventional;
• evidence that originally justified the default.

Do not invert safety facts, consent, or rights as a rhetorical game. Challenge the design assumption around them while preserving the protected outcome.

Procedure

Reverse Sign — Name the default

Write the dominant reasoning as:

We must <decision> because <assumption>, otherwise <feared outcome>.

List the dependency chain beneath it. Mark each premise as observed fact, rule, forecast, preference, convention, or unknown.

Upside-Down Test — Invert one premise

Choose the assumption with the highest decision leverage and rewrite it precisely:

• presence ↔ absence;
• centralized ↔ distributed;
• producer ↔ consumer responsibility;
• default allow ↔ default deny;
• build ↔ buy ↔ remove;
• optimize success ↔ constrain failure;
• user adapts to system ↔ system adapts to user.

Hold other premises stable so the inversion remains interpretable.

Rebel's Exhibit — Construct the strongest counterexample

Build a concrete world in which the inverted premise succeeds. Name:

• conditions required;
• observable prediction;
• smallest test or historical example;
• cost and new failure mode;
• evidence that would defeat the counterexample.

Steelman the default before attacking it. Weak caricatures prove nothing.

Broken Ladder — Trace what falls

Follow the inversion through requirements, ownership, incentives, interfaces, costs, and risks. Identify which downstream decisions collapse, survive, or reverse.

Prefer the smallest leverage point that changes several downstream decisions.

Right-Side-Up Gate — Reconcile with evidence

Classify the original assumption as:

• invalidated;
• conditional;
• still strongest;
• insufficiently tested.

Adopt the inverted approach only when it performs better against the original outcome and constraints. Otherwise record why the default survived a serious challenge.

Characteristic failure mode

This method can become contrarian for its own sake, reward novelty, or treat asymmetrical evidence as a debate game.

Before recommending change, perform one reconciliation check:

• Did the inversion preserve the actual goal?
• Is the counterexample feasible outside a carefully chosen edge case?
• Did contrary evidence receive the same scrutiny as supporting evidence?
• Would the recommendation still stand without the pleasure of overturning consensus?

Use source investigation when the disputed premise is factual. Use rule review when the question is whether conduct complies with an accepted rule.

Output contract

Return:

1. Default argument — decision, hidden assumption, feared outcome.
2. Assumption ledger — fact, rule, forecast, preference, convention, unknown.
3. Single inversion — changed premise and preserved premises.
4. Strongest counterexample — conditions, prediction, test, cost, falsifier.
5. Dependency fallout — decisions that collapse, survive, or reverse.
6. Reconciled judgment — invalidated, conditional, still strongest, or insufficiently tested.

References

Read references/provenance.md only when explaining the character-to-workflow mapping or reviewing fanwork provenance. Read references/worked-example.md when inversion is drifting into automatic opposition.