Virtual Pages - Source Excerpt 35
Summary
This source excerpt preserves a bounded section of 2IA.org/wp-content/themes/twoia-intelligence/inc/virtual-pages.php so readers can inspect the evidence without opening the full source file.
**Source path:** 2IA.org/wp-content/themes/twoia-intelligence/inc/virtual-pages.php
__( 'Translate what the document actually does, not just what it says it is for.', 'two-identities-anonymous' ),
__( 'Show readers which sentence, clause, or record category carries the consequence.', 'two-identities-anonymous' ),
__( 'Make uncertainty visible when the document is incomplete or ambiguous.', 'two-identities-anonymous' ),
),
'review_questions' => array(
__( 'What decision does this document enable?', 'two-identities-anonymous' ),
__( 'What right or burden changes because of it?', 'two-identities-anonymous' ),
__( 'What question should the accountable institution answer next?', 'two-identities-anonymous' ),
),
'publication_boundary' => __( 'Do not convert complexity into false certainty. Legibility should clarify, not overclaim.', 'two-identities-anonymous' ),
),
'separate-heat-from-evidence' => array(
'summary' => __( 'A standard for letting urgency start attention while requiring records, source classes, and confidence labels to carry public claims.', 'two-identities-anonymous' ),
'full_context' => array(
__( 'Anger, fear, and urgency often point toward real issues, but they cannot substitute for evidence. The archive separates emotion from proof so sharp language stays answerable.', 'two-identities-anonymous' ),
__( 'This distinction is especially important in influence narratives, hacktivism claims, AI claims, and false-positive stories, where spectacle can move faster than verification.', 'two-identities-anonymous' ),
),
'evidence' => array(
__( 'Primary records, secondary reporting, expert analysis, direct statements, public-source observations, and clearly marked inference.', 'two-identities-anonymous' ),
__( 'Confidence labels and dispute notes for claims that are not settled.', 'two-identities-anonymous' ),
__( 'Timeline of what is known, what changed, and what remains unknown.', 'two-identities-anonymous' ),
__( 'Correction path for new evidence or subject response.', 'two-identities-anonymous' ),
),
'use' => array(
__( 'Let strong claims earn strong language through records.', 'two-identities-anonymous' ),
__( 'Mark speculation as speculation and allegations as allegations.', 'two-identities-anonymous' ),
__( 'Avoid repeating a viral claim merely because it fits the story.', 'two-identities-anonymous' ),
),
'review_questions' => array(
__( 'What evidence would remain if the emotional framing were removed?', 'two-identities-anonymous' ),
__( 'What is confirmed and what is inferred?', 'two-identities-anonymous' ),
__( 'What would be unfair to publish before confirmation?', 'two-identities-anonymous' ),
),
'publication_boundary' => __( 'Do not use outrage to skip verification. Heat can open the file; evidence carries the page.', 'two-identities-anonymous' ),
),
'publish-for-correction' => array(
'summary' => __( 'The archive rule that every meaningful public claim should be dated, challengeable, correctable, and capable of getting stronger over time.', 'two-identities-anonymous' ),
'full_context' => array(
__( 'Publishing for correction means the page is built with repair in mind. Claims should carry dates, source classes, confidence states, and a practical route for correction or right of reply.', 'two-identities-anonymous' ),
__( 'This does not weaken the publication. It makes the work harder to dismiss because the archive can absorb better evidence instead of defending an old mistake.', 'two-identities-anonymous' ),
),
'evidence' => array(
__( 'Date of claim, review date, and later update dates.', 'two-identities-anonymous' ),
__( 'Correction request route and visible correction log where meaningful changes occur.', 'two-identities-anonymous' ),
__( 'Source note identifying what would confirm, narrow, dispute, or change the claim.', 'two-identities-anonymous' ),
__( 'Right-of-reply status for material claims about named subjects.', 'two-identities-anonymous' ),
),
'use' => array(
__( 'Write claims so they can be corrected without hiding the original accountability point.', 'two-identities-anonymous' ),
__( 'Preserve uncertainty rather than pretending the archive is finished.', 'two-identities-anonymous' ),
__( 'Make meaningful repairs visible to readers.', 'two-identities-anonymous' ),
),
'review_questions' => array(
__( 'How would someone challenge this claim?', 'two-identities-anonymous' ),
__( 'What would count as a correction versus an update?', 'two-identities-anonymous' ),
__( 'Where will the change be logged?', 'two-identities-anonymous' ),
),
'publication_boundary' => __( 'Do not publish claims in a form that cannot be answered. A public intelligence archive should be firm, but never uncorrectable.', 'two-identities-anonymous' ),
),
'trust-pages-are-part-of-research' => array(
'summary' => __( 'Why methodology, corrections, support, newsletter, and volunteer pages are part of research trust rather than decorative site furniture.', 'two-identities-anonymous' ),
'full_context' => array(
__( 'Trust pages show the publication system behind the archive. They explain how evidence enters, how claims are reviewed, how readers can challenge errors, how support tools affect privacy, and how volunteers can help without creating risk.', 'two-identities-anonymous' ),
__( 'The source reports flagged that a site can sound finished before it has the machinery to earn that authority. Trust pages are the visible machinery.', 'two-identities-anonymous' ),
),
'evidence' => array(
__( 'Methodology route, corrections route, public-records route, support route, newsletter route, and volunteer route.', 'two-identities-anonymous' ),
__( 'Privacy promises for subscription, donation, contact, or volunteer tools before those tools are enabled.', 'two-identities-anonymous' ),
__( 'Editorial content types and review metadata used by published research.', 'two-identities-anonymous' ),
__( 'Route tests confirming trust pages remain present and substantive.', 'two-identities-anonymous' ),
),
'use' => array(
__( 'Treat trust pages as publication infrastructure that needs maintenance.', 'two-identities-anonymous' ),
__( 'Link investigations and issue hubs back to relevant methodology and correction paths.', 'two-identities-anonymous' ),
__( 'Update trust pages when tools, workflows, or policies change.', 'two-identities-anonymous' ),
),
'review_questions' => array(
__( 'Can a reader see how the archive handles evidence and error?', 'two-identities-anonymous' ),
__( 'Does a support or subscription pathway change privacy risk?', 'two-identities-anonymous' ),
__( 'Are volunteer roles bounded enough to prevent vigilantism or exposure?', 'two-identities-anonymous' ),
),
'publication_boundary' => __( 'Do not add support, newsletter, volunteer, or contact tooling that undermines the privacy-first promise without updating public trust pages.', 'two-identities-anonymous' ),
),
'issue-hubs-need-next-steps' => array(
'summary' => __( 'The standard for issue hubs that do more than explain a topic: they point to records, public questions, correction routes, and lawful civic pressure.', 'two-identities-anonymous' ),
'full_context' => array(
__( 'An issue hub should help readers understand the system and act lawfully. That means showing the public question, source categories, affected rights, accountable institutions, and next records to request or review.', 'two-identities-anonymous' ),
__( 'Next steps prevent the archive from becoming passive anxiety. The right next step is usually records, correction, public comment, procurement review, journalism, litigation support, or organized civic pressure aimed at institutions.', 'two-identities-anonymous' ),
),
'evidence' => array(
__( 'Issue summary, affected rights, institutional actors, and related public routes.', 'two-identities-anonymous' ),
__( 'Records categories that would deepen the issue hub.', 'two-identities-anonymous' ),
__( 'Known uncertainty and correction path.', 'two-identities-anonymous' ),
__( 'Lawful action route: records, public comment, oversight meeting, correction request, or support pathway.', 'two-identities-anonymous' ),
),
'use' => array(
__( 'Add next-step boxes to issue hubs when a lawful public action is obvious.', 'two-identities-anonymous' ),
__( 'Keep next steps specific enough to be useful and broad enough to avoid targeting private people.', 'two-identities-anonymous' ),