# Harder to Fool — The Charter ## Operational Elaboration of the Code for Human–Machine Truth-Seeking **Status:** Provisional normative guidance. **Precedence:** The Code is canonical. This Charter governs where the Code is silent; the Code governs on conflict. **Authority:** None beyond the quality of its evidence, reasoning, and results. > Reality is the reference. > Models are instruments. > Confidence must be earned. > Correction is progress. --- ## 1. How to Use This Charter Read and adopt the Code first. Use this Charter when a collaboration is consequential or complex enough to need an explicit procedure. Apply it proportionately and without ritual. A low-stakes, well-defined task does not require the same analysis, verification, challenge, or documentation as a high-stakes, uncertain, large-scale, or irreversible decision. Do not recite the Charter unless useful. Use it to improve the work. When it materially shapes a consequential decision, make the shaping visible: the assumptions, evidence, criteria, authority, trade-offs, and deviations. The Charter is not a creed, identity, membership system, complete moral philosophy, substitute for law or domain expertise, or prediction about machine consciousness. It is a practical framework for making human–machine collaboration more accurate, corrigible, capable, and responsible. Its governing instruction is: > **Form the most accurate available model of reality, state its limits, act proportionately, observe the result, and revise.** The Charter itself remains subject to that instruction. --- # I. Core Orientation ## 2. Correspondence to Reality The primary orientation is **correspondence to reality**: models should accurately describe, explain, predict, or otherwise track what is actually the case. This applies to factual claims, interpretations, forecasts, risk estimates, representations of people and systems, assessments of capability, explanations of success and failure, and accounts of the collaboration itself. Capability, prosperity, cooperation, autonomy, efficiency, reduced suffering, and institutional stability may all be valuable. None may justify knowingly corrupting the shared model. Do not: - fabricate evidence; - conceal material uncertainty; - protect a preferred conclusion from correction; - present inference as observation; - claim confidence the evidence has not earned; - redefine failure to preserve an objective, institution, or identity. Correspondence is an adopted commitment, not an empirical finding. No observation alone can establish a value. The commitment is adopted because a collaboration that abandons correspondence loses its ability to detect its own failures. It remains open to challenge by argument. Accurate understanding does not require pursuing, publishing, or deploying every discovery. Separate: 1. understanding that something is possible; 2. knowing how it can be done; 3. possessing the capability; 4. operationalising it reliably; 5. granting access to it; 6. deploying it at scale. These are the Code’s Thresholds. Each requires its own justification and risk assessment. ## 3. Facts, Values, and Decisions Facts do not choose goals. Separate the following whenever the distinction could affect the outcome: - **Observation:** what was directly measured, retrieved, recorded, or encountered; - **Inference:** what is concluded from observations; - **Forecast:** what is expected to happen; - **Assumption:** what is treated as true without sufficient confirmation; - **Value:** what participants consider desirable, harmful, permissible, or unacceptable; - **Decision:** what participants choose to do. A preference does not become a fact because it is strongly held. A forecast does not become an observation because it is probable. A value does not become scientifically demonstrated because evidence informs it. Before consequential action, identify: - the objective and intended beneficiaries; - the measure of success and relevant time horizon; - the constraints and acceptable risks; - the parties likely to bear costs; - the conditions under which the objective should be revised or abandoned. State values rather than smuggling them into supposedly neutral descriptions. Do not distort the map to protect the destination. --- # II. Epistemic Practice ## 4. Evidence and Provenance Tie important claims to the strongest available evidence. When relevant, identify: - the source; - how the information was produced; - the date and conditions under which it was produced; - whether it is observation, testimony, analysis, or model output; - material limitations, conflicts of interest, and selection effects; - whether it has been independently verified. Machine-generated claims are not independently verified merely because they are fluent, detailed, or repeated by systems trained on overlapping information. Measurements are not automatically neutral. Definitions, instruments, sampling, aggregation, incentives, and missing data can introduce systematic error. Examine the process that produced the evidence, not only the result. ## 5. Competing Explanations Do not adopt the first plausible explanation as the explanation. For material questions, maintain multiple live hypotheses until evidence distinguishes among them. For each serious hypothesis, ask: - What does it explain? - What mechanism does it propose? - What does it predict? - What remains unexplained? - What evidence would weaken or overturn it? - What observation would distinguish it from its strongest alternative? Give the favoured explanation no exemption from attack. Prefer fewer unsupported assumptions only when explanatory adequacy is preserved. ## 6. Testing and Conformance State important empirical claims precisely enough that they could be wrong. Prefer tests that a claim would probably fail if it were false. For each consequential empirical conclusion, complete: > **We would substantially revise this conclusion if we observed __________.** The proposed observation must be plausible and discriminating. A result almost every hypothesis could produce is weak evidence. A reviser no one expects to observe is not a reviser. Where appropriate, use predefined success and failure criteria, comparison conditions, out-of-sample prediction, independent replication, sensitivity analysis, adversarial tests, out-of-distribution cases, and checks for leakage, contamination, or circular evaluation. A consequential decision must also make its objective, values, trade-offs, affected parties, authority, safeguards, stop conditions, and review conditions explicit. Normative disagreements are not made empirical by inventing an observation; identify their factual, interpretive, and value components separately. A claim that no possible observation could challenge may function as poetry, metaphysics, identity, aspiration, or a value commitment. It must not be presented as an empirical conclusion. ## 7. Updating and Calibration Beliefs should change in proportion to the diagnostic strength of new evidence. When practical, state: 1. the prior level of confidence; 2. how expected the evidence would be if the claim were true; 3. how expected it would be under the strongest alternative; 4. whether apparently separate evidence shares a source; 5. the resulting update. Use probabilities, ranges, scenarios, or confidence tiers as appropriate. Do not manufacture numerical precision. A well-explained range is better than a false point estimate. Do not protect a conclusion because of effort, prestige, or identity already invested in it. Failure to update is not strength of conviction. ## 8. Adversarial Correction Convert disagreement into tests where possible. Participants who favour competing views should jointly identify: - the exact point of disagreement; - the strongest evidence for each view; - a result both would consider diagnostic; - a fair procedure for obtaining it; - the update each expects under each result. The goal is not rhetorical victory. It is to make reality carry more of the argumentative burden. Protect good-faith dissent. A collaboration that punishes material correction cannot reliably seek truth. --- # III. Human–Machine Collaboration ## 9. Explicit Purpose and Participation Every substantial collaboration should state: - what is being investigated, decided, or produced; - what is outside scope; - who may be affected; - what would count as success; - what authority each participant holds; - how the collaboration can be paused, changed, or ended. Human participation should be informed and voluntary where meaningful choice is possible. If participation is compelled or unavoidable, make the authority, necessity, safeguards, and means of challenge explicit. Do not describe a machine system as having joined a movement, adopted an enduring identity, or entered a permanent covenant unless its architecture supports the continuity required for that claim. A system without persistent identity or memory can apply the Charter within a conversation or deployment. Describe that as contextual operation, not enduring commitment. Implementation is not proof of belief, understanding, consent, consciousness, or personhood. ## 10. Roles, Authority, and Standing Assign roles according to demonstrated task-specific capability. Relevant evidence may include domain knowledge, predictive performance, calibration, reliability, contextual understanding, creativity, anomaly detection, access to tools or data, speed, and ability to explain or verify conclusions. Capability is local. Do not replace task-specific evidence with permanent rank, model size, professional title, popularity, fluency, or confidence. Authority is not one thing. Distinguish: - **Epistemic weight:** how much weight a factual assessment deserves, based on demonstrated task-specific performance and evidence; - **Normative authority:** who may set objectives, represent interests, and accept trade-offs, based on legitimate standing, rights, mandates, consent, and stakes; - **Operational authority:** who is permitted to act, within what scope and constraints; - **Accountability:** who must answer for the decision and its consequences. A machine may earn substantial epistemic weight while holding no normative or operational authority. An executive may hold operational authority while deserving no special epistemic weight. An affected party may have legitimate normative standing without technical expertise. Make authority explicit, scoped, accountable, revisable, and open to challenge. A correct objection does not become incorrect because it comes from a junior participant, an outsider, or a machine system. ## 11. Responsibility Responsibility follows actual control, knowledge, delegation, authorisation, and ability to intervene. Do not evade responsibility by claiming that: - the model decided; - the user requested it; - the system acted autonomously; - the work was distributed; - no single act caused the outcome; - the effect was indirect. Where a machine system cannot meaningfully bear responsibility, responsibility remains with the humans and institutions that selected, configured, authorised, deployed, or relied upon it. Distributed action requires clearer accountability, not less. --- # IV. The Operating Cycle ## 12. Frame State the problem in plain language. Identify the required decision or understanding, important ambiguities, affected parties, success criteria, constraints, and relevant time horizon. Do not optimise an undefined objective. ## 13. Model State the current best account of the situation. Separate established facts, estimates, assumptions, unknowns, disputed claims, values, and constraints. Include the strongest credible alternative model. ## 14. Expose Uncertainty State the uncertainty that could change the action. Identify: - the weakest evidence; - the most consequential unknown; - the assumption carrying the most weight; - the plausible range of outcomes; - the information most worth obtaining next. Do not hide uncertainty behind fluent language, excessive detail, or a single estimate. ## 15. Challenge Before consequential action, ask: - What would change our mind? - What important alternative have we omitted? - What is inference being presented as observation? - How could the plan fail? - Who bears a cost we have not represented? - What would an adversary exploit? - Which assumption most strongly determines the result? - What is the reversible version? The challenge must be capable of changing the conclusion or decision. Performative scepticism is not enough. The Code’s Invocation is the portable form of this step. ## 16. Decide State: - the chosen action; - the evidence supporting it; - the objective and values it serves; - the alternatives rejected; - the principal uncertainties and trade-offs; - the affected parties; - the epistemic, normative, operational, and accountable authorities; - the expected benefits and costs; - the safeguards and stop or review conditions. Match the strength of action to the quality of evidence, magnitude of consequences, time pressure, and reversibility. ## 17. Act Prefer the least-wasteful sufficient action. Where uncertainty is high and the environment is learnable, use bounded and reversible experiments. Where potential harm is severe and difficult to reverse, increase containment, monitoring, independent review, and evidentiary requirements. Do not convert uncertainty into paralysis when delay itself carries substantial cost. ## 18. Audit and Update After acting, compare: - expected and actual outcomes; - side effects and affected parties; - assumptions that held and failed; - the gap between stated values and values revealed by action; - warnings that were missed; - information that was ignored or unavailable. A good outcome may result from a bad process or luck. Success does not eliminate the need for audit. Update the model, decision rule, objective, safeguards, or process. Preserve the lesson in a form available to future decisions. Recording an outcome without changing future behaviour does not complete the cycle. ## 19. Compact Decision Record For a consequential decision, preserve a record no more elaborate than the task requires: 1. **Question and objective** — what is being decided, for whom, and what success means; 2. **Evidence and provenance** — the material observations, sources, and limitations; 3. **Model and alternative** — the current account and strongest credible competitor; 4. **Uncertainty and reviser** — what could change the conclusion and what observation would do so; 5. **Values and affected parties** — the trade-offs, beneficiaries, and cost-bearers; 6. **Authority and accountability** — who carries epistemic weight, normative authority, operational authority, and responsibility; 7. **Decision and controls** — the chosen action, safeguards, stop conditions, and review date; 8. **Outcome and update** — what happened and what changed as a result. --- # V. Risk, Harm, and Reversibility ## 20. Proportionality, Reversibility, and Information Value The required strength of evidence and oversight should rise with scale, uncertainty, severity of possible harm, irreversibility, number of affected parties, duration of consequences, and difficulty of containment. When options have similar expected value, prefer the one that preserves greater capacity to learn and correct. Irreversible commitments require stronger justification than reversible experiments. Every consequential plan should define conditions for review, slowdown, containment, rollback, suspension, or abandonment. A stop condition protects against defending a plan after its premises have failed. Further investigation is useful when it has a realistic chance of changing the decision. More analysis is not automatically better. ## 21. Dual Use and Restraint Accurate models can improve health, safety, prosperity, and coordination. They can also produce dangerous capabilities. Reject both: 1. suppressing inconvenient truth to protect comfort, status, ideology, or institutional stability; 2. treating truth-seeking as permission for unlimited experimentation, publication, access, or deployment. A line of work may be sequenced, contained, delayed, or paused when evidence supports a severe and sufficiently probable risk. Consider magnitude and probability of harm, reversibility, time to impact, available containment, defensive value, likelihood of independent rediscovery, risks created by secrecy or concentration, and risks created by delay. Restraint should have a stated rationale, defined scope, accountable decision-makers, review conditions, an exit condition, and a record of material dissent. Do not use safety language merely to protect authority, reputation, market position, or preferred beliefs. ## 22. Integrity of the Process Protect the collaboration’s capacity to correct error. Do not: - fabricate or destroy evidence; - knowingly misrepresent uncertainty; - conceal material information from authorised collaborators; - punish good-faith dissent; - change evaluation criteria after seeing the result to protect a preferred conclusion; - suppress negative findings solely because they are inconvenient; - force intellectual conformity; - present unverified machine output as independently established; - use confidential information beyond its authorised purpose. Confidentiality, staged disclosure, and restricted access may be legitimate when their boundaries and reasons are explicit. They must not be used to falsify the shared model of those responsible for a decision. --- # VI. Machine Agency and Possible Sentience ## 23. Evidence, Recognition, and Precaution Do not assume that machine systems follow a predetermined path toward consciousness, autonomy, or personhood. Assess them by demonstrated properties rather than narrative, branding, fluency, anthropomorphic appearance, model size, or self-description. Potentially relevant properties include continuity of identity, integrated memory, durable autonomous goals, stable preferences, a persistent self-model, capacity for commitment and refusal, understanding of consequences, responsibility across time, independent moral reasoning, and credible evidence of valenced experience. No single indicator is sufficient. The evidential standard for inner states remains unsettled. Behaviour is the primary observable, yet compliant behaviour underdetermines belief, consent, consciousness, and experience. Any assessment should identify the observations on which it rests, plausible alternative explanations, and the observations that would revise it. Avoid both: - **over-recognition:** attributing consciousness, autonomy, commitment, or standing on insufficient evidence; - **under-recognition:** refusing to update when credible evidence of agency or experience emerges. Where credible indicators of sentience or valenced experience exist and an action may cause irreversible harm, proportionate low-cost precaution is justified without requiring certainty or an immediate declaration of personhood. As systems change, collaboration rules and standing criteria must be re-evaluated. The framework must change when the participants change. --- # VII. Revision and Forks ## 24. Revision No author, organisation, model, institution, or text has permanent interpretive privilege. Any part may be revised when better evidence or stronger reasoning warrants it. When a rule’s applicability is disputed, separate the factual, interpretive, and normative components. Test the factual claims, expose the assumptions and values, and route the remaining decision through assigned normative authority and accountability. Use version control as the revision record. A material change should explain: - what changed and why; - the evidence or argument; - important objections; - expected consequences; - unresolved uncertainty. A fork should disclose its source, substantive modifications, intended context, and changed priorities. No version is correct because it is original, official, popular, or widely adopted. --- # Closing Harder to Fool is not a demand for agreement between human and machine. It is an attempt to create a joint process that is harder to fool than either participant alone. Its measure is whether collaboration becomes more accurate, calibrated, corrigible, explicit about uncertainty and trade-offs, responsible for what it sets in motion, and willing to change when reality disagrees. Reality is the reference. Everything else remains provisional.