Virtual Pages - Source Excerpt 14
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
'body' => 'Use the newsletter to show what records were requested, what came back, what was withheld, what changed, and what the next lawful question should be.',
),
array(
'title' => 'Action Windows',
'body' => 'Reserve urgent notes for genuine deadlines: public meetings, comment periods, procurement votes, renewal dates, correction opportunities, and time-sensitive rights alerts.',
),
array(
'title' => 'Corrections Travel',
'body' => 'When a meaningful page changes, the update channel should say what changed and why. Public memory is accountable only when repair is visible to readers who saw the original.',
),
array(
'title' => 'Cadence Beats Noise',
'body' => 'A predictable rhythm is better than panic blasts. The newsletter should become a useful desk note, not a fear feed.',
),
),
),
'volunteer' => array(
'eyebrow' => 'Bounded civic contribution',
'summary' => 'Volunteer work can strengthen 2IA when it is bounded: research, editing, accessibility, translation, public-records tracking, directory verification, link checks, and careful review.',
'overview_sections' => array(
array(
'title' => 'Useful Roles',
'body' => array(
'Editors, researchers, accessibility reviewers, translators, designers, public-records trackers, legal reviewers, directory verifiers, and technical maintainers can all help without becoming vigilantes.',
),
),
array(
'title' => 'Review Before Publication',
'body' => array(
'A lead is not a finding. Volunteer material needs source notes, confidence labels, minimization, editorial review, and a correction route before publication.',
),
),
),
'sections' => array(
array(
'title' => 'Task Lanes',
'body' => 'Good volunteer lanes include link checking, directory verification, transcript cleanup, accessibility review, translation, public-records tracking, source-note formatting, issue-hub updates, and correction triage.',
),
array(
'title' => 'Cooperating Experts Model',
'body' => 'Specialists can help review law, security, privacy, accessibility, journalism, translation, local records practice, and AI governance without controlling editorial conclusions.',
),
array(
'title' => 'No Vigilante Work',
'body' => 'Do not target private people, impersonate, bypass access controls, scrape recklessly, gather secrets, provoke systems, run unauthorized scans, or perform private investigations under the 2IA name.',
),
array(
'title' => 'Contributor Privacy',
'body' => 'Volunteer intake should collect only what coordination requires, limit access, set retention, avoid unnecessary identity exposure, and provide a path to leave or remove inactive records.',
),
array(
'title' => 'Publication Review',
'body' => 'Before anything goes live, check source class, confidence state, minimization, date, jurisdiction, correction route, and whether the page could cause avoidable harm to bystanders.',
),
),
),
'corrections-and-right-of-reply' => array(
'eyebrow' => 'Public repair and reply',
'summary' => 'Corrections are not embarrassment; they are infrastructure. A public-intelligence archive should be strong enough to repair itself in public and let material subjects answer the record.',
'overview_sections' => array(
array(
'title' => 'What To Send',
'body' => array(
'Name the page, claim, sentence, date, source issue, proposed correction, supporting record, privacy concern, and whether the change affects the conclusion.',
),
),
array(
'title' => 'Public Ledger Logic',
'body' => array(
'Meaningful corrections, updates, privacy repairs, and replies should leave a proportionate public note so readers can see how the archive changed.',
),
),
),
'sections' => array(
array(
'title' => 'Request A Correction',
'body' => 'Name the page, sentence, date, source issue, proposed correction, and public reason the change matters. Include links or records when available.',
),
array(
'title' => 'Correction, Update, Or Source Note',
'body' => 'A correction fixes factual error, missing context, overbroad implication, bad attribution, or privacy exposure. An update adds new information. A source note explains uncertainty without changing the finding.',
),
array(
'title' => 'Right Of Reply',
'body' => 'Named people or organizations in material findings should have a practical route to respond when feasible. A reply can confirm, dispute, narrow, or complicate the record.',
),
array(
'title' => 'Privacy Repair',
'body' => 'If a page exposes unnecessary private detail, remove the detail, document the repair at an appropriate level, and consider downstream copies, summaries, archives, and social previews.',
),
array(
'title' => 'Correction Ledger Fields',
'body' => 'Track page URL, claim, issue raised, source supplied, requester role, confidence effect, decision, public change, private repair, downstream copies, right-of-reply status, reviewer, dates, and public note.',
),
),
),
'organizations' => array(
'eyebrow' => 'Directory, not endorsement list',
'summary' => 'The organization directory should be a normalized civic map: role, jurisdiction, official source, issue tags, contact route, review date, correction path, risk label, and context for controversial entries.',
'overview_sections' => array(
array(
'title' => 'Directory Product Rule',
'body' => array(
'A useful directory helps readers decide which organization type fits a problem: litigator, policy shop, records platform, local coalition, investigative lab, AI-governance reference, digital-rights group, mutual-aid support, or historical context entry.',
'Famous names are not enough. Each listing needs a current official source, scope, jurisdiction, and review status.',
),
),
array(
'title' => 'High-Risk Listing Rule',
'body' => array(
'Leaderless banners, leak brands, historical hacker groups, state-aligned claims, and contested organizations need context-heavy, non-promotional profiles. No operational links, recruitment framing, target lists, or method details.',
),
),
array(
'title' => 'First Release Shape',
'body' => array(
'Prioritize civil-liberties affiliates, digital-rights groups, OSINT and investigative organizations, internet-freedom infrastructure, AI-governance bodies, state and country directories, and carefully labeled historical entries.',
),
),
),
'sections' => array(
array(
'title' => 'Use A Profile Schema',
'body' => 'Each profile should include name, canonical URL, jurisdiction, role, issue tags, source priority, current contact path, intake limits, political or legal status where known, last reviewed date, risk label, and correction route.',
),
array(
'title' => 'Sort By Reader Need',
'body' => 'Separate impact litigators, public-records platforms, press-freedom groups, immigrant-rights coalitions, disability-rights advocates, digital-security trainers, OSINT labs, AI-governance groups, and local mutual-aid networks.',
),
array(
'title' => 'Respect Federated Structures',
'body' => 'For networks such as ACLU affiliates, national groups, state chapters, international federations, and regional coalitions, list the local office or country organization when the reader need is jurisdiction-specific.',
),
array(
'title' => 'Source Priority Model',
'body' => 'Prefer official sites, legal entity records, current program pages, public contact pages, annual reports, court filings, and published methodology. Use reporting and commentary as context, not identity proof.',
),
array(
'title' => 'Review Cadence And Link Health',
'body' => 'Every listing needs a last-reviewed date, stale-warning policy, broken-link process, changed-scope note, and correction path for wrong contact details, closed programs, or affiliation mistakes.',
),
array(
'title' => 'Context-Only Entries',
'body' => 'Anonymous, leak archives, hacker communities, state-aligned hacktivist claims, and grey-hat cases should be handled as history, attribution, legal-risk, and media-literacy entries, not service leads or invitations.',
),
),
),
);
foreach ( $updates as $slug => $update ) {
if ( empty( $pages[ $slug ] ) ) {
continue;
}
if ( isset( $update['title'] ) ) {
$pages[ $slug ]['title'] = __( $update['title'], 'two-identities-anonymous' );
}
if ( isset( $update['summary'] ) ) {
$pages[ $slug ]['summary'] = __( $update['summary'], 'two-identities-anonymous' );
}