Virtual Pages - Source Excerpt 34
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
__( 'Build audit checking that active handoff intake is clear before release packaging.', 'two-identities-anonymous' ),
),
'use' => array(
__( 'Update the manifest when adding or deepening route content.', 'two-identities-anonymous' ),
__( 'Use static mode when no WordPress server is running.', 'two-identities-anonymous' ),
__( 'Run the HTTP route check before release packaging when a local or packaged site URL is available.', 'two-identities-anonymous' ),
),
'review_questions' => array(
__( 'Does the test protect the actual public promise on this route?', 'two-identities-anonymous' ),
__( 'Could an editor-owned page hide required source material?', 'two-identities-anonymous' ),
__( 'Are minimum content thresholds high enough to catch shallow regressions?', 'two-identities-anonymous' ),
),
'publication_boundary' => __( 'Route tests verify presence and shape; they do not prove factual accuracy. Source review and editorial judgment still carry the claim.', 'two-identities-anonymous' ),
),
'report-disposition-ledger' => array(
'summary' => __( 'The public-facing explanation of how incoming reports are sorted, preserved, applied, deferred, duplicated, or blocked.', 'two-identities-anonymous' ),
'full_context' => array(
__( 'The ledger is the memory of review. It records what came in, what was done with it, what public-safe value was promoted, what was blocked, where the source moved, and which checks were run.', 'two-identities-anonymous' ),
__( 'Without a ledger, the archive repeats itself and loses accountability. With a ledger, duplicate follow-up becomes useful owner emphasis rather than noise, and blocked material stays blocked.', 'two-identities-anonymous' ),
),
'evidence' => array(
__( 'Source filename, hash when useful, intake bucket, disposition, reviewer, and archive destination.', 'two-identities-anonymous' ),
__( 'Public work completed or durable no-change, defer, duplicate, or blocker reason.', 'two-identities-anonymous' ),
__( 'Hot-memory effect, long-memory path, and tests or checks run.', 'two-identities-anonymous' ),
__( 'Specific public pages or code paths changed because of the source.', 'two-identities-anonymous' ),
),
'use' => array(
__( 'Use the ledger before reprocessing an archived report.', 'two-identities-anonymous' ),
__( 'Treat duplicate reports as a signal only after hash or content comparison.', 'two-identities-anonymous' ),
__( 'Record blocked public guidance so it does not reappear in later copy.', 'two-identities-anonymous' ),
),
'review_questions' => array(
__( 'Can another reviewer see why this source was handled this way?', 'two-identities-anonymous' ),
__( 'Was actual site work performed, or is there a durable reason no change was made?', 'two-identities-anonymous' ),
__( 'Where can the reviewed source memory be found later?', 'two-identities-anonymous' ),
),
'publication_boundary' => __( 'The ledger can summarize blocked categories without exposing the blocked operational details themselves.', 'two-identities-anonymous' ),
),
'long-memory-goes-to-wiki-fftac-org' => array(
'summary' => __( 'Why bulky reviewed evidence and history live in the wiki memory layer while 2IA keeps public pages readable and accountable.', 'two-identities-anonymous' ),
'full_context' => array(
__( '2IA is the public research surface. Wiki.FFTAC.org is the reviewed long-memory layer. That split lets the public page stay readable while preserving source history, disposition, evidence trails, and future research context.', 'two-identities-anonymous' ),
__( 'The split also protects readers from raw dumps. Public pages should expose the claim, method, confidence, and correction path; long memory can preserve the bulk needed for audit and continuation.', 'two-identities-anonymous' ),
),
'evidence' => array(
__( 'Wiki project index, source archive path, transfer log, checksum or file count when available.', 'two-identities-anonymous' ),
__( '2IA hot-memory note showing which public value was promoted.', 'two-identities-anonymous' ),
__( 'Archive destination for processed handoff files.', 'two-identities-anonymous' ),
__( 'Public page links that summarize the reviewed finding.', 'two-identities-anonymous' ),
),
'use' => array(
__( 'Keep public routes concise enough to read while still substantive enough to stand alone.', 'two-identities-anonymous' ),
__( 'Route bulky provenance and duplicate history to reviewed long memory.', 'two-identities-anonymous' ),
__( 'Do not describe wiki.fftac.org as wiki.fftac.org; this workspace has a clear naming boundary.', 'two-identities-anonymous' ),
),
'review_questions' => array(
__( 'Is this material public-page content or long-memory evidence?', 'two-identities-anonymous' ),
__( 'Has the public page preserved the claim and method without dumping raw context?', 'two-identities-anonymous' ),
__( 'Can a future reviewer find the source trail?', 'two-identities-anonymous' ),
),
'publication_boundary' => __( 'Long memory is not a loophole for publishing unsafe detail. It is reviewed preservation, not public operational guidance.', 'two-identities-anonymous' ),
),
'build-dossiers-around-questions' => array(
'summary' => __( 'The core archive design rule: build every dossier around a public question that can be tested, corrected, and answered with records.', 'two-identities-anonymous' ),
'full_context' => array(
__( 'A serious archive does not begin with a target. It begins with a question: what system exists, who owns it, what data enters, what decisions follow, what rights are affected, what records exist, and what would prove the claim wrong.', 'two-identities-anonymous' ),
__( 'That structure keeps the work lawful and useful. It pushes attention toward accountable institutions, policies, vendors, and records rather than toward private-person exposure or spectacle.', 'two-identities-anonymous' ),
),
'evidence' => array(
__( 'A written public-interest question for the dossier.', 'two-identities-anonymous' ),
__( 'Record categories that could answer the question.', 'two-identities-anonymous' ),
__( 'Affected rights, affected communities, accountable institutions, and known uncertainty.', 'two-identities-anonymous' ),
__( 'Correction condition: what would change the claim.', 'two-identities-anonymous' ),
),
'use' => array(
__( 'Turn anger or concern into a question before collecting material.', 'two-identities-anonymous' ),
__( 'Define what would count as enough evidence and what would count as disproof.', 'two-identities-anonymous' ),
__( 'Keep the dossier focused on systems and decisions.', 'two-identities-anonymous' ),
),
'review_questions' => array(
__( 'What question does this dossier answer?', 'two-identities-anonymous' ),
__( 'Which records would confirm, narrow, dispute, or correct it?', 'two-identities-anonymous' ),
__( 'Who is accountable for explaining the system?', 'two-identities-anonymous' ),
),
'publication_boundary' => __( 'Do not build dossiers around curiosity about private people. Build them around public systems, public power, and correctable claims.', 'two-identities-anonymous' ),
),
'make-power-legible' => array(
'summary' => __( 'The archive goal of translating contracts, policies, technical claims, public narratives, and institutional incentives into language readers can inspect.', 'two-identities-anonymous' ),
'full_context' => array(
__( 'Power often hides in complexity: procurement terms, data-sharing clauses, model claims, retention schedules, platform policies, audit language, and agency acronyms. Making power legible means turning that complexity into public questions and accountable summaries.', 'two-identities-anonymous' ),
__( 'Legibility is not simplification that erases nuance. It is a reading layer that preserves uncertainty, explains what the record can prove, and shows where to look next.', 'two-identities-anonymous' ),
),
'evidence' => array(
__( 'Plain-language summaries of contracts, policy clauses, audits, public statements, and technical claims.', 'two-identities-anonymous' ),
__( 'Glossary or context notes for jargon that changes rights or obligations.', 'two-identities-anonymous' ),
__( 'Comparison between public promises and governing documents.', 'two-identities-anonymous' ),
__( 'Questions for vendors, agencies, platforms, or public bodies.', 'two-identities-anonymous' ),
),
'use' => array(