Public Statement on the Simulated Standpoint Forum Method

Status: v1.9 public method statement.

Purpose: Make structured adversarial deliberation useful and auditable without creating false authority.

This is a simulated standpoint forum. Named historical and contemporary figures are used as intellectual standpoints for structured adversarial reasoning. They did not participate, endorse the project, or speak the words attributed to a standpoint. The forum is not evidence and does not replace real expert, affected-party, rights-holder, domain, or accessibility review.

What the forum is

The forum is a structured adversarial reasoning method. It uses simulated intellectual standpoints to pressure-test the project from different angles. A named standpoint is a disciplined prompt for a kind of criticism. It is not an imitation of a person, a quotation, historical reconstruction, participation, review, or endorsement.

The forum may help generate objections, rivals, boundary questions, revisions, implementation proposals, and tests. Its outputs remain analysis or proposals until the relevant evidence and real participation exist.

Evidence-room tags

Every material proposition in a forum record should be marked as one of:

• V — verified project fact: directly established by a current source, registry, artifact, test, or repository record;
• H — historical interpretation: a sourced account of an intellectual lineage that remains open to contest;
• I — inference: a reasoned interpretation that goes beyond the direct record;
• N — normative judgment: a claim about what ought to matter or be protected;
• P — proposal: an action for future implementation;
• O — open question: material uncertainty that must not be silently closed.

No vote, convergence, or eloquence can turn H, I, N, P, or O into V. Convergence is recorded as convergence, not truth.

Forum mechanics

Independent opening memoranda

For a major forum, independent tracks first prepare separate memoranda without seeing one another's drafts. The tracks should cover the strongest account of the project, the strongest failure analysis, and a bounded improvement programme. This reduces premature convergence.

Steelman before critique

Before criticizing a position, a chamber must state its strongest recognizable version. The facilitator rejects critiques that attack a weaker substitute.

Adversarial pairings

Each major question receives counter-readings. Typical pairings include systems integration versus reduction or totalization; feedback design versus legitimacy and rights; repair versus transformation of an unjust order; causal operationalization versus lived meaning and care; and publication transparency versus transparency theatre.

Boundary-crossing questions

Each participating chamber answers the same questions:

1. What is the project's strongest contribution if stated modestly?
2. What does its language make easier to see?
3. What does the same language hide or flatten?
4. Which current public statement most risks overreach?
5. What evidence or comparison would change the standpoint's judgment?
6. What should change now without waiting for new empirical research?

Dissent ledger

The record preserves unresolved conceptual disagreement, unresolved empirical questions, unresolved normative conflict, and implementation minority reports. A consensus sentence may not erase dissent. If the project acts despite dissent, the decision record must state why and identify the retained risk.

Affected-party absence check

At every normative or intervention decision, the facilitator asks who is described but absent. Simulated standpoints cannot fill that absence. Any recommendation that requires legitimacy, consent, lived knowledge, domain authority, or rights-holder judgment remains conditional on real participation.

Co-chair rule

Major forums should use two method functions:

1. a systems-method co-chair to protect evidence structure, feedback closure, delay awareness, testability, and maintainability;
2. a public-judgment co-chair to protect plurality, ethics, clarity, public responsibility, and the visibility of absent people.

These are simulated functions unless real participants are explicitly identified with consent and attribution.

Non-numeric disposition criteria

The forum does not synthesize a score. Proposals receive reasons, dependencies, risks, and stop conditions under seven criteria:

• claim-boundary preservation;
• evidence honesty;
• public usefulness;
• ethical and rights protection;
• reversibility;
• testability and auditability;
• maintainability across future editions.

The disposition for each proposal is one of: implement now; build as research infrastructure only; require real review or participation first; defer pending a stated gate; or reject with reasons. An implementation decision does not promote a substantive claim.

Quality and failure conditions

A forum is weak if everyone agrees too quickly, if it produces only philosophical flourish, if objections do not change the project, or if simulation is presented as authority. A forum is procedurally successful only when it leaves a traceable change, a preserved dissent, or a clearly stated reason for no change. Procedural success is not empirical validation.

Prospective-design boundary: T001

T001 is a registered design stub for a future comparison concerning synthetic and conventional voice-deception verification burden. Its status is infrastructure only and its outcome-inspection status is not inspected. The incident set, episode boundary, observation period, operational measures, adequacy criterion, case-selection rule, data sources, analysis plan, decision rule, missing-data rule, domain review, and affected-party review are not yet defined or complete.

T001 is therefore not a preregistration; not a registered, active, or completed test; not a result; and not evidence for C3, Theory F, Repair-Lag Systems Theory, or any other substantive claim. It may become a test only through a new dated and versioned design that closes the stated gaps before case selection or outcome inspection and passes ethical, rights, domain, and affected-party gates. No silent amendment is permitted.

Public-use and stop rules

Forum documents must carry the simulation disclaimer near the beginning. Real contributions must be separated from simulated material and require consent, attribution, and review. Do not use the forum or T001 to claim independent expertise, affected-party legitimacy, external review, public authorization, preregistration, empirical confirmation, live-site verification, or accessibility certification.