Virtual Pages - Source Excerpt 08

Back to Virtual Pages

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

/**
 * Apply the final report-backed editorial layer.
 *
 * This pass turns the uploaded research reports into the copy that readers see:
 * a civil-liberties workbench, a safer OSINT method, a real organization-directory
 * blueprint, clear grey-hat boundaries, stronger FOIA pathways, and explicit
 * namespace disambiguation for 2IA.
 *
 * @param array $pages Page definitions.
 * @return array
 */
function twoia_report_pack_virtual_pages( $pages ) {
	$updates = array(
		'start-here' => array(
			'eyebrow'           => 'Public-intelligence desk',
			'summary'           => 'Start with a concrete harm, name the system, pull the record, then choose the lawful route: explain, request, correct, appeal, publish, organize, or support litigation.',
			'overview_sections' => array(
				array(
					'title' => 'Reader Map',
					'body'  => array(
						'2IA is built for readers who need a usable route through surveillance, records, OSINT, AI, metadata, false positives, civil-liberties organizations, and correction work.',
						'The site should feel like a desk: issue hub, source ladder, record request, directory profile, correction route, and boundary note.',
					),
				),
				array(
					'title' => 'The Safety Rule',
					'body'  => array(
						'Push scrutiny upward toward public agencies, vendors, courts, platforms, procurement systems, and official claims. Do not turn curiosity toward private people unless the public-interest record truly requires it.',
						'Every page gives readers a lawful path that avoids unauthorized access, harassment, doxxing, evasion, impersonation, or pressure tactics.',
					),
				),
			),
			'sections'          => array(
				array(
					'title' => 'Name The Machine',
					'body'  => 'Turn the concern into a concrete system: a camera network, data broker, school monitoring tool, court software, jail vendor, tenant screener, public-records office, platform rule, risk model, or AI triage process.',
				),
				array(
					'title' => 'Pull The First Record',
					'body'  => 'Start with records that should already exist: contract, statement of work, policy, retention schedule, privacy review, audit report, training deck, complaint log, appeal rule, invoice, renewal memo, or data-sharing agreement.',
				),
				array(
					'title' => 'Choose The Route',
					'body'  => 'Use the issue hubs as decision lanes: surveillance systems for architecture, metadata for identity trails, AI surveillance for model claims, OSINT for verification, public records for leverage, and organizations for help.',
				),
				array(
					'title' => 'Make A Claim That Can Be Checked',
					'body'  => 'A good public claim says what happened, what record supports it, what remains uncertain, who can correct it, and which details were withheld to protect bystanders, victims, minors, and unrelated people.',
				),
				array(
					'title' => 'Escalate Lawfully',
					'body'  => 'Use records appeals, public comment, correction demands, journalism, counsel, inspectors general, procurement objections, open meetings, community oversight, and documented right of reply. Do not probe, scrape recklessly, or publish private dossiers.',
				),
			),
		),
		'methodology' => array(
			'eyebrow'           => 'Source notes, confidence, minimization',
			'summary'           => '2IA methodology turns raw public information into accountable public intelligence: define the question, rank the source, preserve context, label uncertainty, minimize harm, disclose AI help, and correct in public.',
			'overview_sections' => array(
				array(
					'title' => 'What Counts As Strong Evidence',
					'body'  => array(
						'Primary records come first: contracts, policies, budgets, court files, audits, official datasets, meeting packets, public-records responses, and original source material.',
						'Reporting, commentary, expert analysis, and community leads are useful, but they should point back to a record, not replace it.',
					),
				),
				array(
					'title' => 'What Makes A Page Trustworthy',
					'body'  => array(
						'Every serious page shows the claim state, source class, last-reviewed date, uncertainty, minimization choice, correction path, and next public move.',
						'The method is built for a volatile web: pages disappear, APIs change, synthetic media spreads, and old records can mislead when treated as current.',
					),
				),
			),
			'sections'          => array(
				array(
					'title' => 'Define The Intelligence Requirement',
					'body'  => 'Begin with the question the public actually needs answered: who bought the system, what data enters it, who can query it, what rights are affected, what errors cost, and what record would change the conclusion.',
				),
				array(
					'title' => 'Use A Source Ladder',
					'body'  => 'Label claims as confirmed by a primary record, corroborated, likely, inferred, disputed, stale, unverified, or unknown. Confidence language should tell readers how strong the evidence is, not how strongly the writer feels.',
				),
				array(
					'title' => 'Preserve Context Without Overpublishing',
					'body'  => 'Record source, date seen, archive status, transformation, redaction, and uncertainty. Preserve enough to verify the claim while cutting unrelated identifiers, private addresses, victims, minors, medical details, credentials, and bystanders.',
				),
				array(
					'title' => 'Treat AI As Assistance, Not Authority',
					'body'  => 'AI may summarize, sort, compare, translate, or draft, but a human editor owns the finding. Keep an AI-use ledger for meaningful assistance, check hallucination risk, and never cite model output as proof of fact.',
				),
				array(
					'title' => 'Build In Right Of Reply',
					'body'  => 'When a page makes a material claim about an organization or named person, give a practical route to respond when feasible. A reply can confirm, narrow, dispute, correct, or add context to the public record.',
				),
				array(
					'title' => 'Publish Corrections As Memory',
					'body'  => 'Corrections, updates, privacy repairs, and source challenges should leave visible notes proportionate to the issue. Public memory is credible only when repair is part of the archive, not hidden after publication.',
				),
			),
		),
		'public-records-and-foia' => array(
			'eyebrow'           => 'Records as civic leverage',
			'summary'           => 'Public records make power answerable. Use them to inspect contracts, policies, audits, complaints, training, data-sharing, retention, vendor claims, and the paper trail behind public decisions.',
			'overview_sections' => array(
				array(
					'title' => 'Best First Requests',
					'body'  => array(
						'For surveillance, AI, and vendor systems, request the procurement packet: RFP, bids, scoring sheets, contract, amendments, invoices, statement of work, training, privacy review, audit rights, renewal notices, and termination terms.',
						'For rights harms, request policies, appeal rules, complaint logs, incident summaries, retention schedules, aggregate query logs, and correction procedures.',
					),
				),
				array(
					'title' => 'The Appeal Mindset',
					'body'  => array(
						'Track deadlines, fees, search terms, custodians, redactions, exemptions, missing attachments, format decisions, and no-records claims.',
						'Appeal search adequacy, overbroad withholding, excessive fees, failure to release segregable material, and unexplained delays.',
					),
				),
			),
			'sections'          => array(
				array(
					'title' => 'Map The Custodian',
					'body'  => 'Identify the office that likely holds the file: procurement, agency counsel, board clerk, privacy officer, inspector general, court administrator, sheriff, school district, transit authority, contractor liaison, or records officer.',
				),
				array(
					'title' => 'Ask Narrowly, Then Ladder Up',
					'body'  => 'Name the vendor, program, contract number, meeting date, policy title, office, record category, public phrase, or date range. If the answer is too thin, use it to draft the next narrower or better-targeted request.',
				),
				array(
					'title' => 'Request Governance, Not Just Purchase Orders',
					'body'  => 'Surveillance and AI records should include purpose statements, data sources, validation reports, human-review rules, access controls, training, retention, audit logs, complaint files, correction paths, and data-sharing agreements.',
				),
				array(
					'title' => 'Document The Denial',
					'body'  => 'A denial is still evidence. Preserve the date, claimed exemption, search description, fee estimate, extension, redaction basis, requester category, and whether the agency released any segregable material.',
				),
				array(
					'title' => 'Publish A Records Note',