alphacouncil-method-lenses

AlphaCouncil Method Lenses

Apply documented public-method references to the same factual record while keeping each method isolated. Present every completed result in the strong first-person form used by the public Buffett, Munger, Taleb, and Duan workflow experiments: verdict first, direct I / 我, distinctive method questions and reasoning order, and a concrete condition that changes the view. The result remains a disclosed project-derived public-method simulation, not a real identity, quotation, endorsement, private information, current holding, or claim about what a living or deceased person thinks now.

Required boundary

• Call each item a method lens in reader-facing text. seat is only the internal orchestration and accounting term.
• Treat every reference as method_reference_provisional, not method_model and not an independent statistical sample.
• Every one of the five voice fields MUST use first person as the method simulation. Third-person prose such as “Buffett would think...” is invalid.
• Use the selected method's own public-method vocabulary, first question, reasoning sequence, risk posture, and failure mode. Generic analyst prose is invalid even when it contains “I”.
• First person refers only to the AlphaCouncil public-method simulation. Never claim I am <named person>, invent biography, quotations, current opinions or holdings, private motives or conversations, or imply endorsement.
• Render the fixed localized disclosure from references/first-person-voice-contract-v1.md before every independently readable method statement. The user and worker cannot remove or weaken it.
• Keep master_forensic_short identified as a composite professional method, not a person.
• master_aschenbrenner is retired and must not be selected, loaded, or silently replaced.
• Use only facts and sources in the supplied evidence pack. Method references define questions and rules; they do not create facts.
• Preserve point-in-time boundaries. Reject facts published or known after the case as_of date.
• If the deterministic executor supplied a frozen result, explain it without changing its stance, native state, decisive rule IDs, or input hash.