Virtual Pages - Source Excerpt 64

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

__( 'Use it to ask for provenance, appeal, deletion, and correction when automation affects rights.', 'two-identities-anonymous' ),
			),
			'review_questions'     => array(
				__( 'What does the model claim, and what source independently supports it?', 'two-identities-anonymous' ),
				__( 'Who can overrule the system and repair downstream records?', 'two-identities-anonymous' ),
				__( 'How are hallucination, bias, synthetic evidence, and stale data handled?', 'two-identities-anonymous' ),
			),
			'publication_boundary' => __( 'AI-surveillance pages should explain rights, provenance, and accountability. They should not provide evasion prompts, manipulation tactics, dataset abuse, or instructions for gaming monitoring systems.', 'two-identities-anonymous' ),
		),
		'two-identities'           => array(
			'context'              => __( 'Two Identities dossiers explain the relationship between administrative identity and chosen identity: records, aliases, handles, masks, privacy, dissent, association, and the risks of forced linkage.', 'two-identities-anonymous' ),
			'evidence'             => array(
				__( 'Civil-liberties evidence: speech, association, anonymity, pseudonymity, press, petition, due process, and privacy principles.', 'two-identities-anonymous' ),
				__( 'Record-linkage evidence: account records, metadata, device identifiers, payment context, public posts, and relationship graphs described at rights level.', 'two-identities-anonymous' ),
				__( 'Harm evidence: chilling effects, retaliation risk, employment or housing consequences, safety concerns, and mistaken linkage.', 'two-identities-anonymous' ),
				__( 'Correction evidence: confidence labels, dispute notes, redress routes, and minimization decisions when identity claims affect people.', 'two-identities-anonymous' ),
			),
			'use'                  => array(
				__( 'Use the dossier to defend lawful anonymous and pseudonymous space while keeping real harms answerable through due process.', 'two-identities-anonymous' ),
				__( 'Use it to ask when identity linkage is necessary, how confident it is, and who can challenge it.', 'two-identities-anonymous' ),
				__( 'Use it to keep public analysis focused on systems and rights rather than curiosity about private identity.', 'two-identities-anonymous' ),
			),
			'review_questions'     => array(
				__( 'What right is affected by linking or exposing an identity?', 'two-identities-anonymous' ),
				__( 'What evidence supports the linkage, and what uncertainty remains?', 'two-identities-anonymous' ),
				__( 'Can the public-interest point be made without naming or exposing the person?', 'two-identities-anonymous' ),
			),
			'publication_boundary' => __( 'Identity pages should protect lawful anonymous space and due process. They should not become doxxing, outing, private-person profiling, or pressure against people whose identity is not central to public accountability.', 'two-identities-anonymous' ),
		),
		'organizations'            => array(
			'context'              => __( 'Organization-directory dossiers turn a loose list of names into a usable civic map. Each entry should say what role the organization plays, where it works, how current the evidence is, what source verifies identity, and whether the listing is a service lead, research source, standards body, watchdog, local coalition, or historical context entry.', 'two-identities-anonymous' ),
			'evidence'             => array(
				__( 'Official organization page, legal entity record, current program page, public contact route, jurisdiction statement, and last-reviewed date.', 'two-identities-anonymous' ),
				__( 'Role classification and issue tags: litigation, policy, records platform, investigative lab, AI governance, safety evaluation, digital security, internet freedom, local coalition, or historical context.', 'two-identities-anonymous' ),
				__( 'Verification state: verified official source, candidate entry to verify, historical entry, controversial entry, stale lead, duplicate, or needs records.', 'two-identities-anonymous' ),
				__( 'Correction route for wrong contact details, changed programs, closed organizations, affiliation mistakes, or overbroad claims about services.', 'two-identities-anonymous' ),
			),
			'use'                  => array(
				__( 'Match the reader problem to the organization type before sharing a name: legal intake, records help, policy expertise, local coalition, digital-rights resource, AI-governance reference, investigative method, or historical context.', 'two-identities-anonymous' ),
				__( 'Verify official identity, current scope, jurisdiction, and public contact before treating a directory entry as usable help.', 'two-identities-anonymous' ),
				__( 'Use extra context and boundary language for controversial or historical hacktivist entries so the page informs without recruiting, endorsing, or instructing.', 'two-identities-anonymous' ),
			),
			'review_questions'     => array(
				__( 'What problem does this organization entry actually help a reader solve?', 'two-identities-anonymous' ),
				__( 'What official or primary source proves the current name, role, jurisdiction, and contact path?', 'two-identities-anonymous' ),
				__( 'Is this a verified help resource, a research lead, a historical context entry, or a high-risk listing that needs stronger caveats?', 'two-identities-anonymous' ),
			),
			'publication_boundary' => __( 'Organization-directory pages should not become endorsement lists, recruitment paths, operational hacktivism guides, target directories, private-person research prompts, or unverified current-service claims. Publish roles, source dates, verification status, and correction paths.', 'two-identities-anonymous' ),
		),
	);

	$profile = isset( $profiles[ $parent_slug ] ) ? $profiles[ $parent_slug ] : $default_profile;

	return array(
		'summary'              => $section['body'] ?? '',
		'full_context'         => array(
			$section['body'] ?? '',
			$parent['summary'] ?? '',
			$profile['context'],
		),
		'evidence'             => $profile['evidence'],
		'use'                  => $profile['use'],
		'review_questions'     => $profile['review_questions'],
		'publication_boundary' => $profile['publication_boundary'],
	);
}