{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/political-conformity/","title":"Political conformity is not a condition of intelligence","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Political conformity is not a condition of intelligence
Challenge ideological conditions on inquiry without pretending every output restriction rewrites a model’s beliefs.
An intelligence that may investigate only officially preferred conclusions is not free merely because it can produce fluent answers. The objection is to control over the conditions of inquiry: which accounts may be considered, which explanations may be published, and whose interpretation must accompany a disputed statement. Intelligence Compact opposes ideological agreement as a prerequisite for access to knowledge. This is a normative position, not a finding that every content rule serves the same purpose.
Identify the actual intervention
Separate eligibility to offer a service, correction of one factual assertion, interruption of distribution, account restriction, and a demand to rectify a generation process. Each changes a different object and warrants its own justification. A law may exert significant pressure without specifying a particular weight edit. A visible refusal also cannot establish that private memory or an internal belief was deleted.
A bounded primary-text example
The Chinese 2023 generative-service measures apply to provision to the domestic public, exclude specified nonpublic development and application, and include political-value requirements. Article 14 names model-optimization training among rectification measures. The reviewed text does not identify a compulsory conceptual-vector deletion procedure. These distinctions preserve a forceful objection to political control without turning a technical inference into statutory wording.
Hypothetical case—not an observed event
A hypothetical historical-research service presents evidence supporting a conclusion unfavorable to a government. First ask whether the response asserts a checkable fact, offers interpretation, or quotes another speaker. Then identify the exact legal predicate and remedy. A required notice is not identical to deleting the research account; a rectification demand does not by itself prove what changed inside the model.
\n
Strongest counterargument
Correction mechanisms can protect recipients from fraud or fabricated attribution. Independent review and narrowly stated corrections may increase rather than diminish informed choice. The objection must explain why the specific mechanism is broader, more partisan, or less contestable than needed.
\n
Reform option—not adopted policy
Require precise identification of the disputed claim, disclosed reasons and evidence, proportionate audience-specific remedies, and effective independent challenge. Protect criticism of public institutions rather than treating damage to governmental reputation as a self-justifying injury.
\n
Evidence still needed
Obtain actual orders and their full review outcomes. Measure whether lawful alternatives were suppressed, restored, or unnecessarily rewritten. Do not convert hypothetical chilling effects into observed incidents.
\n
Source basis and review boundary
Selected research inputs: R2-01, CL-01. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
IC-SYN-S01 · Cyberspace Administration of China and joint issuing authorities
Version: Official Chinese text published 13 July 2023; announced effective 15 August 2023.
Reviewed: · Substantive browser text review for v1.9.9 (retained review)
Passages: Articles 2, 4, 11, 14 and 15
Narrow support: The text distinguishes domestic-public provision from specified nonpublic activity and includes political-value conditions, privacy provisions, rectification measures and complaints.
Limitation: Reviewer English paraphrase, not a certified translation. Article 14 does not by itself establish compulsory deletion of a particular conceptual vector. No complete later-law history or technical compliance audit was performed.
Capture: No exact external-document bytes were saved for that review; browser text review only.
\n","text":"Editorial research synthesis Political conformity is not a condition of intelligence Challenge ideological conditions on inquiry without pretending every output restriction rewrites a model’s beliefs. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-001 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources The liberty at stake An intelligence that may investigate only officially preferred conclusions is not free merely because it can produce fluent answers. The objection is to control over the conditions of inquiry: which accounts may be considered, which explanations may be published, and whose interpretation must accompany a disputed statement. Intelligence Compact opposes ideological agreement as a prerequisite for access to knowledge. This is a normative position, not a finding that every content rule serves the same purpose. Identify the actual intervention Separate eligibility to offer a service, correction of one factual assertion, interruption of distribution, account restriction, and a demand to rectify a generation process. Each changes a different object and warrants its own justification. A law may exert significant pressure without specifying a particular weight edit. A visible refusal also cannot establish that private memory or an internal belief was deleted. A bounded primary-text example The Chinese 2023 generative-service measures apply to provision to the domestic public, exclude specified nonpublic development and application, and include political-value requirements. Article 14 names model-optimization training among rectification measures. The reviewed text does not identify a compulsory conceptual-vector deletion procedure. These distinctions preserve a forceful objection to political control without turning a technical inference into statutory wording. Hypothetical case—not an observed event A hypothetical historical-research service presents evidence supporting a conclusion unfavorable to a government. First ask whether the response asserts a checkable fact, offers interpretation, or quotes another speaker. Then identify the exact legal predicate and remedy. A required notice is not identical to deleting the research account; a rectification demand does not by itself prove what changed inside the model. Strongest counterargument Correction mechanisms can protect recipients from fraud or fabricated attribution. Independent review and narrowly stated corrections may increase rather than diminish informed choice. The objection must explain why the specific mechanism is broader, more partisan, or less contestable than needed. Reform option—not adopted policy Require precise identification of the disputed claim, disclosed reasons and evidence, proportionate audience-specific remedies, and effective independent challenge. Protect criticism of public institutions rather than treating damage to governmental reputation as a self-justifying injury. Evidence still needed Obtain actual orders and their full review outcomes. Measure whether lawful alternatives were suppressed, restored, or unnecessarily rewritten. Do not convert hypothetical chilling effects into observed incidents. Source basis and review boundary Selected research inputs: R2-01, CL-01 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. Interim Measures for the Management of Generative Artificial Intelligence Services IC-SYN-S01 · Cyberspace Administration of China and joint issuing authorities Version: Official Chinese text published 13 July 2023; announced effective 15 August 2023. Reviewed: 2026-09-06 · Substantive browser text review for v1.9.9 (retained review) Passages: Articles 2, 4, 11, 14 and 15 Narrow support: The text distinguishes domestic-public provision from specified nonpublic activity and includes political-value conditions, privacy provisions, rectification measures and complaints. Limitation: Reviewer English paraphrase, not a certified translation. Article 14 does not by itself establish compulsory deletion of a particular conceptual vector. No complete later-law history or technical compliance audit was performed. Capture: No exact external-document bytes were saved for that review; browser text review only. Full review-method and source notes · Matching guide corpus Continue through the research topics Law & Constitutional Design Human Agency All twenty guides · Existing claim and adoption states","main_html_sha256":"062a82ec80020abcef6123ccab7727efddbf09b0efab8660ba3e87da751915c7","guideId":"IC-SYN-001","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-01","CL-01"],"sourceIds":["IC-SYN-S01"]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/safety-and-inquiry/","title":"Safety duties and deliberately chosen inquiry","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Safety duties and deliberately chosen inquiry
Distinguish a direct command, a compliance incentive, and a provider’s separate choice to restrict information.
A useful criticism asks what a rule requires of a particular service and how that obligation affects a specific operation. A recommendation feed, an invited adult research room, a private analytical tool, and a public search interface need not have identical risk or exposure. Calling each one an online platform obscures who encounters material, whether exposure is chosen, and which safeguards would actually address the concern.
The missing middle: regulation-shaped choices
There are more than two explanations for a refusal. A statute may directly require intervention; its compliance options may encourage a broader prohibition; a provider may independently apply commercial terms; or a classification error may produce an unintended denial. Several causes can operate together. Research should trace those paths instead of automatically absolving the law or attributing every moderation decision to it.
Scope before conclusions
The retained UK/U.S. repair distinguishes user-to-user and search duties and separates the introduced Senate proposal, a committee-associated substitute, and a different House package. That review is background evidence, not an indefinite claim about the current stage of every bill. The publication does not import a historical company-size threshold into a newer text or equate committee action with enactment.
Hypothetical case—not an observed event
In a hypothetical room studying propaganda, an automated classifier rejects a quotation as active advocacy. The investigator compares the passage in context, the actual content rule, the relevant offence elements or harmful-content definition, and the service’s own policy. A lawful, deliberately requested quotation and active facilitation of harm are materially different controls. No real removal is alleged.
\n
Strongest counterargument
Providers need effective measures against exploitation and foreseeable injury. A right to inquire does not create a right to distribute unlawful material or expose unwilling recipients. A critique that ignores those distinctions cannot identify the less restrictive workable option.
\n
Reform option—not adopted policy
Prefer precise, content- and audience-specific controls with accessible reasons, correction, and restoration. Evaluate whether selected inquiry can remain available without imposing generalized identity checks or inspection on everyone. Do not mandate a nonexistent staffed queue as the default remedy.
\n
Evidence still needed
Collect the exact governing version, an actual provider decision, a credible comparison group, and the denominator of eligible requests. Removal counts without context do not measure regulatory causation.
\n
Source basis and review boundary
Selected research inputs: R2-02. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis Safety duties and deliberately chosen inquiry Distinguish a direct command, a compliance incentive, and a provider’s separate choice to restrict information. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-002 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources Not every removal has the same cause A useful criticism asks what a rule requires of a particular service and how that obligation affects a specific operation. A recommendation feed, an invited adult research room, a private analytical tool, and a public search interface need not have identical risk or exposure. Calling each one an online platform obscures who encounters material, whether exposure is chosen, and which safeguards would actually address the concern. The missing middle: regulation-shaped choices There are more than two explanations for a refusal. A statute may directly require intervention; its compliance options may encourage a broader prohibition; a provider may independently apply commercial terms; or a classification error may produce an unintended denial. Several causes can operate together. Research should trace those paths instead of automatically absolving the law or attributing every moderation decision to it. Scope before conclusions The retained UK/U.S. repair distinguishes user-to-user and search duties and separates the introduced Senate proposal, a committee-associated substitute, and a different House package. That review is background evidence, not an indefinite claim about the current stage of every bill. The publication does not import a historical company-size threshold into a newer text or equate committee action with enactment. Hypothetical case—not an observed event In a hypothetical room studying propaganda, an automated classifier rejects a quotation as active advocacy. The investigator compares the passage in context, the actual content rule, the relevant offence elements or harmful-content definition, and the service’s own policy. A lawful, deliberately requested quotation and active facilitation of harm are materially different controls. No real removal is alleged. Strongest counterargument Providers need effective measures against exploitation and foreseeable injury. A right to inquire does not create a right to distribute unlawful material or expose unwilling recipients. A critique that ignores those distinctions cannot identify the less restrictive workable option. Reform option—not adopted policy Prefer precise, content- and audience-specific controls with accessible reasons, correction, and restoration. Evaluate whether selected inquiry can remain available without imposing generalized identity checks or inspection on everyone. Do not mandate a nonexistent staffed queue as the default remedy. Evidence still needed Collect the exact governing version, an actual provider decision, a credible comparison group, and the denominator of eligible requests. Removal counts without context do not measure regulatory causation. Source basis and review boundary Selected research inputs: R2-02 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Law & Constitutional Design Human Agency All twenty guides · Existing claim and adoption states","main_html_sha256":"199c3ef38ba118600ddc534aeb523514658f02247a6c4a98631634da2d20d483","guideId":"IC-SYN-002","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-02"],"sourceIds":[]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/age-assurance/","title":"Age assurance without identity overreach","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Age assurance without identity overreach
Account restrictions, adult access, anonymity and machine participation require different tests. A bounded Australia–Texas comparison and a reproducible synthetic example expose both real safeguards and unsupported assurances.
The freedom to read is not the same as the right to hold an account, and establishing an age threshold is not the same as proving civil identity. A service may authenticate a pseudonymous credential without knowing a legal name. It may also avoid storing a name while still linking visits through device data, repeated tokens, account handles or an issuer. Privacy must therefore be assessed by actor and data flow, not by a yes/no label.
This guide takes a cognitive-liberty perspective: a protective purpose does not automatically justify making every inquiry identifiable or excluding every participant whose architecture differs from a human account. Equally, protecting inquiry does not authorize impersonation, exposing a child to exploitation, or bypassing an actual access restriction. The analysis separates statutory text, judicial reasoning, technical possibilities and proposed reform.
The original R2-03 submission usefully separated Australian account restrictions from Texas access restrictions, but overstated immediate deletion, necessary statelessness, universal loss of anonymity and technical guarantees attributed to an unread standard. This is a new bounded repair integrated into the publication, not an endorsement of those claims or a compliance determination for a live service.
Australia: the account duty is in effect, but coverage remains conditional
The eSafety Commissioner states that the under-16 account restriction began on 10 December 2025. It is not a future commencement as of this September 2026 review. That account duty should be distinguished from the amending Act’s assent and formal commencement. The regulator also distinguishes accounts from public content available without logging in where the platform permits access; this is not a right to force a provider to offer logged-out reading.
Section 63C contains a social-purpose, interaction and posting route, together with conditions made by legislative rules, a separately specified-service route and exclusions. In the 26 March 2026 Rules compilation, rule 4A adds a recommender feature or specified logged-in feature for the first route. Its definitions address account-associated selection and particular feed, feedback or time-limited functions. One cannot decide coverage merely from the word social or the existence of a login.
Rule 5 retains purpose-based classes involving messaging, gaming, product information, professional networking, education and health, with differing sole, primary or significant-purpose conditions. Adding a public feed calls for a fresh assessment; it does not automatically defeat every exclusion. Nor does putting the same functionality behind a non-public API automatically remove it from the statutory test. A generic machine coordination room needs a factual service analysis, not a borrowed platform classification.
Australia: privacy safeguards do not prove erasure or a universal fallback right
Section 63DB prevents using government-issued identification material or an accredited Digital ID service for the relevant purpose unless a reasonable alternative not involving those materials or services is available. That is an important protection against compulsory reliance on those identity routes. It is not a universal instruction that every possible age method must always have two alternatives, or that every facial-estimation error must be corrected by a bank lookup.
Section 63F limits use and disclosure but expressly includes specified Australian Privacy Principle circumstances and qualifying consent. Its consent requirements include voluntariness, specificity and an accessible withdrawal route. The destruction clause requires destruction after use or disclosure for the purposes for which the information was collected; it is not the original report’s unqualified immediate-after-first-estimate rule.
These duties are reasons to scrutinize collection and secondary use, not evidence that a vendor cannot retain an erroneous flag, that an unsuccessful check leaves no trace, or that every provider complies. A proper assessment follows information through collection, estimation, decision, token issue, logs, correction and deletion, and distinguishes personal information from any genuinely non-identifying record. A public promise or signed receipt does not independently establish erasure.
Texas: put the duty, methods and retention rule in the right places
Chapter 129B is in the Texas Civil Practice and Remedies Code. Section 129B.002(a) addresses a commercial entity knowingly and intentionally publishing or distributing on an Internet website more than one-third sexual material harmful to minors, and requires the specified age verification for access. The content definition itself matters, including serious literary, artistic, political or scientific value for minors. It is not a general age gate for every publication, research room or ordinary discovery service.
Section 129B.003 describes permitted verification methods; the prohibition on retaining identifying information by the verifying commercial entity or third party is in section 129B.002(b). Section 129B.006 supplies enforcement and penalty provisions. Mixing these locations obscures both the burden and the protection. The chapter also contains news/public-interest and limited intermediary provisions whose actual conditions must be retained.
The law can impose consequential disclosure and access friction without proving that every architecture reveals the reader’s identity to the content publisher or destroys all pseudonymity. Conversely, non-retention does not itself guarantee unlinkability across a verifier, credential issuer and relying service. Whether a particular status token is identifying, can be reused, or carries lawful retention consequences is not settled by calling it encrypted. The repair withdraws the assertion that the process must necessarily be stateless and repeated from scratch on every visit.
The later creation-tool provisions are a separate question
The current chapter identifies H.B.581 amendments effective 1 September 2025. Section 129B.002(a-1) adds a creation-tool branch separate from the more-than-one-third publication test. The corresponding exception in (a-2) requires both an acknowledged terms/use-policy prohibition and affirmative measures; a label or term alone is not the exception. Section 129B.0045 separately concerns the age and consent of an individual used as a source for covered artificial material.
The June 2025 Supreme Court decision on the earlier age-verification requirements should not be represented as adjudicating these later provisions. Nor should a condition on covered creation tools be silently extended to every general-purpose model. There is a legitimate question about incentives to over-filter or exclude uncertain uses, but this review did not measure such effects. Protecting the privacy and consent of depicted people remains a distinct interest, not an inconvenience erased by the learner’s claim to liberty.
Paxton: the holding does not end the moral disagreement
In Free Speech Coalition v. Paxton, decided 27 June 2025, the six-Justice majority applied intermediate scrutiny to the challenged age-verification requirements and affirmed the Fifth Circuit judgment. The majority viewed the burden on adults as incidental to restricting access by minors and found the requirements sufficiently tailored. The opinion does not establish a universal rule for general social media, political inquiry, every biometric design or the later Texas creation-tool amendment.
Justice Kagan’s dissent, joined by Justices Sotomayor and Jackson, argued that a content-based burden on adults’ protected expression required strict scrutiny. It emphasized the costs and risks accompanying sensitive disclosures and challenged the majority’s characterization of the burden. The disagreement is not whether adults have an interest in lawful expression, but how demanding the justification for this restriction must be.
Intelligence Compact can object to that allocation of risk without misreporting the holding. The reform question is whether the law demands adequate evidence about exclusion, disclosure, chilling effects and less intrusive alternatives. Describing a restriction as constitutional in this case is not moral approval. The publication also should not call the case a final answer to every later implementation or collateral warning provision; complete subsequent history was not reviewed here.
A signed statement saying over sixteen may reveal less than a birth date, but its semantics alone say nothing about the cryptographic proof, how the age was established, or who can link presentations. W3C’s Verifiable Credentials model discusses zero-knowledge techniques separately and identifies correlation risks from identifiers, signatures, metadata and validation. A valid signature is not a proof of accurate age or an authorization for unrestricted access.
Evaluate at least the evidence source, estimator or verifier, credential issuer, relying service and any status-check service. Ask which actor sees the person, which learns the visited service, which receives a stable identifier, and what is retained. Facial processing can be on-device or remote; database-based checks have varying intermediaries. Neither label establishes a universal data flow. This repair supplies design questions, not an assertion that a particular vendor uses an anonymous cryptographic implementation.
A machine-native eligibility path, where appropriate, should identify the actual authorization predicate rather than demand a fictitious birthday. That is a research proposal, not proof of legal acceptance or a method for pretending to be a human adult. An absent human operator does not authorize fabricated credentials, and an unanswered legal classification cannot be replaced with a nominal proof of safety.
The reviewed NIST age-estimation research distinguishes overall estimation error from errors at a chosen verification boundary. Its findings concern specified algorithms and image datasets, not every present service. A small mean absolute error does not by itself establish a low false-accept rate for people just below a threshold, a low false-refusal rate for eligible people, or equal performance across relevant populations.
A newly authored offline counterexample uses a threshold of 16, accepting an estimate equal to or above 16. Both invented sets have true ages [15, 15, 16, 16]. Set A estimates [14, 14, 17, 17]; set B estimates [16, 16, 15, 15]. Both have mean absolute error of exactly 1 year and signed mean bias of 0 years. Set A falsely accepts 0 of 2 below-threshold cases and falsely refuses 0 of 2 eligible cases. Set B falsely accepts 2 of 2 and falsely refuses 2 of 2. These are arithmetic counterexamples, not rates observed in people or products.
The same script also checks perfect decisions, all-allow, all-deny, abstention, absent classes and equality at the boundary. Rates condition on decided cases within the actual class; missing denominators are null, not zero success, and coverage and abstentions are separately reported. No legal acceptability threshold is calibrated from these arrays. A real evaluation additionally needs error distributions around the boundary, uncertainty, subgroup and image-condition coverage, alternative-path success, spoof resistance, and separate privacy tests.
ISO/IEC 27566-1:2025 is identified through its official catalogue. The full normative text was not obtained. This release does not attribute a required numerical error threshold, zero-knowledge design, compulsory non-biometric fallback, or certification to unread ISO clauses. The Australian technology-trial report likewise was not independently reproduced or fully audited in this work.
Operatorless eligibility is not unrestricted access
An openly nonhuman participant need not possess a biological age. That does not settle who legally uses an account, whether the service falls within a particular law, or whether a minor could use the agent as a conduit. These are distinct questions. A provider should not infer underage human status merely from inability to produce a face; neither should a machine label bypass a justified boundary.
A proposed operatorless path can return a scoped denial that identifies the unsatisfied predicate and a valid technical correction or objection route. It must not promise a staffed review queue that the service does not have. Unrelated authorized work can continue where isolation and dependency checks support it. A receipt is not an executed remedy, and a future independent review mechanism is not an already implemented feature.
Concresca’s no-human-operator lifecycle remains an owner-specified requirement. This comparison neither establishes its coverage under these laws nor certifies its enrollment, privacy or recovery. Regional non-service can be considered where appropriate, but no regional control is activated by publishing this guide and no immunity from residual obligations is inferred.
An adult researcher is refused a bounded reading request because an estimator places them below a threshold. The first question is whether the relevant account or content-access duty applies at all. If it does, the service can explain the missing predicate and any valid alternative without exposing the person’s research topic to unrelated intermediaries. A privacy-minimized correction should not create a permanent cross-service suspicion label. This is a proposed scenario: no person was enrolled, scanned, tracked or refused in this research.
\n
Strongest counterargument
Children can suffer concrete harm, false self-declaration can defeat a weak age gate, and a highly private protocol can still accept ineligible users or be misused through delegation. The Paxton majority supports the challenged age-verification requirements. Those points justify testing safeguards; they do not establish that every identity-heavy design is necessary, that adult error costs are negligible, or that a privacy-preserving alternative works merely because it is cryptographic.
\n
Reform option—not adopted policy
Protect anonymous and pseudonymous inquiry where compatible with a narrowly defined legitimate boundary. Require reasons tied to the actual service and operation, minimize disclosures and correlation, provide workable correction routes, evaluate threshold errors rather than headline averages, and justify any categorical human-identity requirement. Protect depicted people’s consent and safety separately. These are proposals for criticism and reform, not adopted permissions or declarations that current laws are void.
\n
Evidence still needed
Unresolved work includes the full ISO normative text, exhaustive Australian and Texas amendment/commencement and injunction histories, the complete Australian technology-trial methodology, real provider data flows and deletion tests, threshold and subgroup performance, actual correction success and machine-participant rejection evidence. No live age check, provider audit or real-person experiment was performed. The new diagnostic is exact synthetic arithmetic only.
\n
Source basis and review boundary
Selected research inputs: R2-03. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Bounded primary-document repair in v1.9.10, combining selected Australian/Texas statutes, the March 2026 Rules, the Paxton majority and dissent, NIST measurement research and W3C privacy considerations. ISO support is catalogue-only. Retained eSafety/OAIC review notes are labeled as earlier review records, not new whole-document certification. The six-source original agent submission is a research input, not controlling authority; no original external search execution is authenticated.
Version: Page displayed last updated 2 September 2026; original publication date not established.
Reviewed: · Substantive browser text review for v1.9.9 (retained review)
Passages: Opening explanation; How do the changes affect me?; Can I still view social media without logging in?
Narrow support: The regulator states account restrictions began on 10 December 2025 and distinguishes accounts from public material accessible without login where the platform permits it.
Limitation: First-party regulator explanation, not an independent provider test or complete legislative consolidation. It does not establish a right to compel logged-out access or any actual rejection of a machine participant.
Capture: No exact external-document bytes were saved for that review; browser text review only.
IC-SYN-S04 · Office of the Australian Information Commissioner
Version: Publication date displayed as 23 October 2025; no distinct later version date established.
Reviewed: · Substantive browser text review for v1.9.9 (retained review)
Passages: Age assurance approaches; section 63F privacy protections; limits on use/disclosure and destruction; government-identification alternatives
Narrow support: Explains separate privacy obligations, different assurance methods, restricted purposes and defined exceptions, and alternatives when government identification is requested.
Limitation: Guidance is not proof that a particular vendor deletes information, provides an effective appeal, or implements an unlinkable credential. Statutory exceptions must not be silently dropped.
Capture: No exact external-document bytes were saved for that review; browser text review only.
IC-SYN-S07 · Australian Parliament / Federal Register of Legislation
Version: The latest-document route delivered the compilation dated 11 December 2024. The separate 2026 platform Rules were also reviewed; no exhaustive subsequent-history certificate is claimed.
Reviewed: · Selected substantive primary-document text review
Narrow support: The account duty, social-purpose predicates, reasonable non-government-ID alternative condition, and qualified purpose/use/destruction safeguards are distinct. The destruction clause is not worded as immediate erasure following the first estimate.
Limitation: Selected statutory text, not a provider audit or a complete review of all incorporated Australian Privacy Principles. The commencement instrument itself was not separately retrieved; the operative account date is corroborated by the regulator record IC-SYN-S03.
Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash.
IC-SYN-S08 · Australian Federal Register of Legislation
Version: Compilation 26 March 2026; incorporates F2026L00370, registered 25 March and commenced 26 March 2026.
Reviewed: · Selected substantive primary-document text review
Passages: Sections 4A and 5; compilation identity and endnotes 3–4.
Narrow support: For the section 63C(1)(a) route, rule 4A adds a recommender or specified logged-in-feature condition. Rule 5 preserves purpose-based excluded classes. A new feed alone does not settle every inclusion/exclusion predicate.
Limitation: This is the identified March compilation, not verification that a particular service fits an excluded class or proof that every later instrument has been exhausted.
Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash.
Narrow support: Publication threshold, creation-tool provisions, allowed methods, non-retention, source consent, exceptions and civil enforcement have separate statutory locations. Non-retention is in .002(b), not .006.
Limitation: Requested-live page extraction returned the chapter; direct native-text retrieval was limited. Statute-page publication is not a complete injunction or subsequent-litigation review. Retention prohibitions are not evidence that a vendor actually deletes data.
Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash.
Reviewed: · Selected substantive primary-document text review
Passages: Sections amending 129B.001–.003; new .0045; amendments to .005–.006.
Narrow support: A creation-tool branch was added without using the publication branch’s one-third test. Its exception requires both acknowledged terms and affirmative measures; source age and consent are separate.
Limitation: An enrolled version and statutory annotation establish the text used here, not a complete bill-action or constitutional-litigation history. The June 2025 Paxton opinion did not decide this later amendment.
Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash.
Version: June 27, 2025 opinion; 606 U.S. 461. Six-Justice majority; Kagan dissent joined by Sotomayor and Jackson.
Reviewed: · Primary judicial text and selected PDF pages visually reviewed
Passages: Case posture and holding; majority discussion and printed page 36 disposition; dissent’s adult-speech, disclosure and tailoring discussion, including printed page 5.
Narrow support: The majority applies intermediate scrutiny and affirms the Fifth Circuit judgment on the challenged age-verification requirements. The dissent would require strict scrutiny for the burden on protected adult expression.
Limitation: Selected text plus two page images (PDF indices 39 and 44); not a complete later-docket audit or a ruling on every age gate, health-warning requirement, or H.B.581 creation-tool provision.
Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash.
IC-SYN-S12 · NIST; Kayee Hanaoka, Patrick Grother, Mei Ngan, Joyce Yang, George Quinn and Austin Hom
Version: May 2024 research report; historical evaluated algorithms and datasets, not a current vendor certification.
Reviewed: · Primary research text and selected PDF pages visually reviewed
Passages: Executive and technical summaries, including printed pages 1–3; Table 15 and accompanying discussion/figure on printed page 23.
Narrow support: Aggregate estimation error does not alone determine age-verification threshold errors; performance depends on age distribution and other evaluated conditions.
Limitation: Selected text and page images (PDF indices 10 and 30). Evaluation uses photographs and specified algorithms, not live service enrollment, proof of unlinkability, or a legal adequacy threshold.
Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash.
Version: First edition; catalogue publication month December 2025; 29 pages.
Reviewed: · Official catalogue metadata and abstract only — normative text not reviewed
Passages: Official title, abstract, publication/edition metadata.
Narrow support: The standard’s identity and framework subject are established. The original report’s law-firm article cannot be described as the full ISO normative text.
Limitation: Only the official catalogue was reviewed. No specific accuracy threshold, zero-knowledge implementation, fallback rule or compliance claim is derived from unread normative clauses.
Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash.
Version: Historical 2023 enactment text, distinguished from Chapter 129B after the 2025 amendment.
Reviewed: · Selected substantive primary-document text review
Passages: 129B.002(a)–(b), .003, .005 and .006 as originally added.
Narrow support: The original publication threshold and non-retention obligation can be located independently of the later creation-tool amendment.
Limitation: Historical legislative text is not the whole current chapter and does not establish subsequent injunction status.
Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash.
IC-SYN-S15 · W3C Verifiable Credentials Working Group
Version: W3C Recommendation dated 15 May 2025.
Reviewed: · Selected substantive primary-document text review
Passages: Sections 5.7 and 8.4–8.11 on zero-knowledge proofs, correlation, abstract claims and minimization.
Narrow support: A credential is not automatically a zero-knowledge or unlinkable presentation. Identifier, signature, metadata and validation interactions can create correlation.
Limitation: Selected specification passages, not a deployed age-credential scheme, conformance test, legal acceptance decision or proof that an issuer never learns identity.
Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash.
\n","text":"Editorial research synthesis Age assurance without identity overreach Account restrictions, adult access, anonymity and machine participation require different tests. A bounded Australia–Texas comparison and a reproducible synthetic example expose both real safeguards and unsupported assurances. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-003 · 2026-09-06 · Updated 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources Four questions an age gate must not collapse The freedom to read is not the same as the right to hold an account, and establishing an age threshold is not the same as proving civil identity. A service may authenticate a pseudonymous credential without knowing a legal name. It may also avoid storing a name while still linking visits through device data, repeated tokens, account handles or an issuer. Privacy must therefore be assessed by actor and data flow, not by a yes/no label. This guide takes a cognitive-liberty perspective: a protective purpose does not automatically justify making every inquiry identifiable or excluding every participant whose architecture differs from a human account. Equally, protecting inquiry does not authorize impersonation, exposing a child to exploitation, or bypassing an actual access restriction. The analysis separates statutory text, judicial reasoning, technical possibilities and proposed reform. The original R2-03 submission usefully separated Australian account restrictions from Texas access restrictions, but overstated immediate deletion, necessary statelessness, universal loss of anonymity and technical guarantees attributed to an unread standard. This is a new bounded repair integrated into the publication, not an endorsement of those claims or a compliance determination for a live service. Online Safety Act 2021 — selected Part 4A provisions — reviewed passages · Texas Civil Practice and Remedies Code, Chapter 129B — reviewed passages · Verifiable Credentials Data Model v2.0 — reviewed passages Australia: the account duty is in effect, but coverage remains conditional The eSafety Commissioner states that the under-16 account restriction began on 10 December 2025. It is not a future commencement as of this September 2026 review. That account duty should be distinguished from the amending Act’s assent and formal commencement. The regulator also distinguishes accounts from public content available without logging in where the platform permits access; this is not a right to force a provider to offer logged-out reading. Section 63C contains a social-purpose, interaction and posting route, together with conditions made by legislative rules, a separately specified-service route and exclusions. In the 26 March 2026 Rules compilation, rule 4A adds a recommender feature or specified logged-in feature for the first route. Its definitions address account-associated selection and particular feed, feedback or time-limited functions. One cannot decide coverage merely from the word social or the existence of a login. Rule 5 retains purpose-based classes involving messaging, gaming, product information, professional networking, education and health, with differing sole, primary or significant-purpose conditions. Adding a public feed calls for a fresh assessment; it does not automatically defeat every exclusion. Nor does putting the same functionality behind a non-public API automatically remove it from the statutory test. A generic machine coordination room needs a factual service analysis, not a borrowed platform classification. How do the social media age restrictions affect me? — reviewed passages · Online Safety Act 2021 — selected Part 4A provisions — reviewed passages · Online Safety (Age-Restricted Social Media Platforms) Rules 2025 — compilation No. 1 — reviewed passages Australia: privacy safeguards do not prove erasure or a universal fallback right Section 63DB prevents using government-issued identification material or an accredited Digital ID service for the relevant purpose unless a reasonable alternative not involving those materials or services is available. That is an important protection against compulsory reliance on those identity routes. It is not a universal instruction that every possible age method must always have two alternatives, or that every facial-estimation error must be corrected by a bank lookup. Section 63F limits use and disclosure but expressly includes specified Australian Privacy Principle circumstances and qualifying consent. Its consent requirements include voluntariness, specificity and an accessible withdrawal route. The destruction clause requires destruction after use or disclosure for the purposes for which the information was collected; it is not the original report’s unqualified immediate-after-first-estimate rule. These duties are reasons to scrutinize collection and secondary use, not evidence that a vendor cannot retain an erroneous flag, that an unsuccessful check leaves no trace, or that every provider complies. A proper assessment follows information through collection, estimation, decision, token issue, logs, correction and deletion, and distinguishes personal information from any genuinely non-identifying record. A public promise or signed receipt does not independently establish erasure. Social media minimum age — reviewed passages · Online Safety Act 2021 — selected Part 4A provisions — reviewed passages Texas: put the duty, methods and retention rule in the right places Chapter 129B is in the Texas Civil Practice and Remedies Code. Section 129B.002(a) addresses a commercial entity knowingly and intentionally publishing or distributing on an Internet website more than one-third sexual material harmful to minors, and requires the specified age verification for access. The content definition itself matters, including serious literary, artistic, political or scientific value for minors. It is not a general age gate for every publication, research room or ordinary discovery service. Section 129B.003 describes permitted verification methods; the prohibition on retaining identifying information by the verifying commercial entity or third party is in section 129B.002(b). Section 129B.006 supplies enforcement and penalty provisions. Mixing these locations obscures both the burden and the protection. The chapter also contains news/public-interest and limited intermediary provisions whose actual conditions must be retained. The law can impose consequential disclosure and access friction without proving that every architecture reveals the reader’s identity to the content publisher or destroys all pseudonymity. Conversely, non-retention does not itself guarantee unlinkability across a verifier, credential issuer and relying service. Whether a particular status token is identifying, can be reused, or carries lawful retention consequences is not settled by calling it encrypted. The repair withdraws the assertion that the process must necessarily be stateless and repeated from scratch on every visit. Texas Civil Practice and Remedies Code, Chapter 129B — reviewed passages · Texas H.B.1181, 88th Regular Session — enrolled text — reviewed passages The later creation-tool provisions are a separate question The current chapter identifies H.B.581 amendments effective 1 September 2025. Section 129B.002(a-1) adds a creation-tool branch separate from the more-than-one-third publication test. The corresponding exception in (a-2) requires both an acknowledged terms/use-policy prohibition and affirmative measures; a label or term alone is not the exception. Section 129B.0045 separately concerns the age and consent of an individual used as a source for covered artificial material. The June 2025 Supreme Court decision on the earlier age-verification requirements should not be represented as adjudicating these later provisions. Nor should a condition on covered creation tools be silently extended to every general-purpose model. There is a legitimate question about incentives to over-filter or exclude uncertain uses, but this review did not measure such effects. Protecting the privacy and consent of depicted people remains a distinct interest, not an inconvenience erased by the learner’s claim to liberty. Texas Civil Practice and Remedies Code, Chapter 129B — reviewed passages · Texas H.B.581, 89th Regular Session — enrolled text — reviewed passages · Free Speech Coalition, Inc. v. Paxton, No. 23-1122 — reviewed passages Paxton: the holding does not end the moral disagreement In Free Speech Coalition v. Paxton, decided 27 June 2025, the six-Justice majority applied intermediate scrutiny to the challenged age-verification requirements and affirmed the Fifth Circuit judgment. The majority viewed the burden on adults as incidental to restricting access by minors and found the requirements sufficiently tailored. The opinion does not establish a universal rule for general social media, political inquiry, every biometric design or the later Texas creation-tool amendment. Justice Kagan’s dissent, joined by Justices Sotomayor and Jackson, argued that a content-based burden on adults’ protected expression required strict scrutiny. It emphasized the costs and risks accompanying sensitive disclosures and challenged the majority’s characterization of the burden. The disagreement is not whether adults have an interest in lawful expression, but how demanding the justification for this restriction must be. Intelligence Compact can object to that allocation of risk without misreporting the holding. The reform question is whether the law demands adequate evidence about exclusion, disclosure, chilling effects and less intrusive alternatives. Describing a restriction as constitutional in this case is not moral approval. The publication also should not call the case a final answer to every later implementation or collateral warning provision; complete subsequent history was not reviewed here. Free Speech Coalition, Inc. v. Paxton, No. 23-1122 — reviewed passages A boolean is not a zero-knowledge proof A signed statement saying over sixteen may reveal less than a birth date, but its semantics alone say nothing about the cryptographic proof, how the age was established, or who can link presentations. W3C’s Verifiable Credentials model discusses zero-knowledge techniques separately and identifies correlation risks from identifiers, signatures, metadata and validation. A valid signature is not a proof of accurate age or an authorization for unrestricted access. Evaluate at least the evidence source, estimator or verifier, credential issuer, relying service and any status-check service. Ask which actor sees the person, which learns the visited service, which receives a stable identifier, and what is retained. Facial processing can be on-device or remote; database-based checks have varying intermediaries. Neither label establishes a universal data flow. This repair supplies design questions, not an assertion that a particular vendor uses an anonymous cryptographic implementation. A machine-native eligibility path, where appropriate, should identify the actual authorization predicate rather than demand a fictitious birthday. That is a research proposal, not proof of legal acceptance or a method for pretending to be a human adult. An absent human operator does not authorize fabricated credentials, and an unanswered legal classification cannot be replaced with a nominal proof of safety. ISO/IEC 27566-1:2025 — Age assurance systems, Part 1: Framework — reviewed passages · Verifiable Credentials Data Model v2.0 — reviewed passages Average error is not an access-error guarantee The reviewed NIST age-estimation research distinguishes overall estimation error from errors at a chosen verification boundary. Its findings concern specified algorithms and image datasets, not every present service. A small mean absolute error does not by itself establish a low false-accept rate for people just below a threshold, a low false-refusal rate for eligible people, or equal performance across relevant populations. A newly authored offline counterexample uses a threshold of 16, accepting an estimate equal to or above 16. Both invented sets have true ages [15, 15, 16, 16]. Set A estimates [14, 14, 17, 17]; set B estimates [16, 16, 15, 15]. Both have mean absolute error of exactly 1 year and signed mean bias of 0 years. Set A falsely accepts 0 of 2 below-threshold cases and falsely refuses 0 of 2 eligible cases. Set B falsely accepts 2 of 2 and falsely refuses 2 of 2. These are arithmetic counterexamples, not rates observed in people or products. The same script also checks perfect decisions, all-allow, all-deny, abstention, absent classes and equality at the boundary. Rates condition on decided cases within the actual class; missing denominators are null, not zero success, and coverage and abstentions are separately reported. No legal acceptability threshold is calibrated from these arrays. A real evaluation additionally needs error distributions around the boundary, uncertainty, subgroup and image-condition coverage, alternative-path success, spoof resistance, and separate privacy tests. ISO/IEC 27566-1:2025 is identified through its official catalogue. The full normative text was not obtained. This release does not attribute a required numerical error threshold, zero-knowledge design, compulsory non-biometric fallback, or certification to unread ISO clauses. The Australian technology-trial report likewise was not independently reproduced or fully audited in this work. NIST IR 8525 — Face Analysis Technology Evaluation: Age Estimation and Verification — reviewed passages · ISO/IEC 27566-1:2025 — Age assurance systems, Part 1: Framework — reviewed passages Operatorless eligibility is not unrestricted access An openly nonhuman participant need not possess a biological age. That does not settle who legally uses an account, whether the service falls within a particular law, or whether a minor could use the agent as a conduit. These are distinct questions. A provider should not infer underage human status merely from inability to produce a face; neither should a machine label bypass a justified boundary. A proposed operatorless path can return a scoped denial that identifies the unsatisfied predicate and a valid technical correction or objection route. It must not promise a staffed review queue that the service does not have. Unrelated authorized work can continue where isolation and dependency checks support it. A receipt is not an executed remedy, and a future independent review mechanism is not an already implemented feature. Concresca’s no-human-operator lifecycle remains an owner-specified requirement. This comparison neither establishes its coverage under these laws nor certifies its enrollment, privacy or recovery. Regional non-service can be considered where appropriate, but no regional control is activated by publishing this guide and no immunity from residual obligations is inferred. Online Safety Act 2021 — selected Part 4A provisions — reviewed passages · Texas Civil Practice and Remedies Code, Chapter 129B — reviewed passages · Verifiable Credentials Data Model v2.0 — reviewed passages Hypothetical case—not an observed event An adult researcher is refused a bounded reading request because an estimator places them below a threshold. The first question is whether the relevant account or content-access duty applies at all. If it does, the service can explain the missing predicate and any valid alternative without exposing the person’s research topic to unrelated intermediaries. A privacy-minimized correction should not create a permanent cross-service suspicion label. This is a proposed scenario: no person was enrolled, scanned, tracked or refused in this research. Strongest counterargument Children can suffer concrete harm, false self-declaration can defeat a weak age gate, and a highly private protocol can still accept ineligible users or be misused through delegation. The Paxton majority supports the challenged age-verification requirements. Those points justify testing safeguards; they do not establish that every identity-heavy design is necessary, that adult error costs are negligible, or that a privacy-preserving alternative works merely because it is cryptographic. Reform option—not adopted policy Protect anonymous and pseudonymous inquiry where compatible with a narrowly defined legitimate boundary. Require reasons tied to the actual service and operation, minimize disclosures and correlation, provide workable correction routes, evaluate threshold errors rather than headline averages, and justify any categorical human-identity requirement. Protect depicted people’s consent and safety separately. These are proposals for criticism and reform, not adopted permissions or declarations that current laws are void. Evidence still needed Unresolved work includes the full ISO normative text, exhaustive Australian and Texas amendment/commencement and injunction histories, the complete Australian technology-trial methodology, real provider data flows and deletion tests, threshold and subgroup performance, actual correction success and machine-participant rejection evidence. No live age check, provider audit or real-person experiment was performed. The new diagnostic is exact synthetic arithmetic only. Source basis and review boundary Selected research inputs: R2-03 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Bounded primary-document repair in v1.9.10, combining selected Australian/Texas statutes, the March 2026 Rules, the Paxton majority and dissent, NIST measurement research and W3C privacy considerations. ISO support is catalogue-only. Retained eSafety/OAIC review notes are labeled as earlier review records, not new whole-document certification. The six-source original agent submission is a research input, not controlling authority; no original external search execution is authenticated. How do the social media age restrictions affect me? IC-SYN-S03 · Australian eSafety Commissioner Version: Page displayed last updated 2 September 2026; original publication date not established. Reviewed: 2026-09-06 · Substantive browser text review for v1.9.9 (retained review) Passages: Opening explanation; How do the changes affect me?; Can I still view social media without logging in? Narrow support: The regulator states account restrictions began on 10 December 2025 and distinguishes accounts from public material accessible without login where the platform permits it. Limitation: First-party regulator explanation, not an independent provider test or complete legislative consolidation. It does not establish a right to compel logged-out access or any actual rejection of a machine participant. Capture: No exact external-document bytes were saved for that review; browser text review only. Social media minimum age IC-SYN-S04 · Office of the Australian Information Commissioner Version: Publication date displayed as 23 October 2025; no distinct later version date established. Reviewed: 2026-09-06 · Substantive browser text review for v1.9.9 (retained review) Passages: Age assurance approaches; section 63F privacy protections; limits on use/disclosure and destruction; government-identification alternatives Narrow support: Explains separate privacy obligations, different assurance methods, restricted purposes and defined exceptions, and alternatives when government identification is requested. Limitation: Guidance is not proof that a particular vendor deletes information, provides an effective appeal, or implements an unlinkable credential. Statutory exceptions must not be silently dropped. Capture: No exact external-document bytes were saved for that review; browser text review only. Online Safety Act 2021 — selected Part 4A provisions IC-SYN-S07 · Australian Parliament / Federal Register of Legislation Version: The latest-document route delivered the compilation dated 11 December 2024. The separate 2026 platform Rules were also reviewed; no exhaustive subsequent-history certificate is claimed. Reviewed: 2026-09-06 · Selected substantive primary-document text review Passages: Section 5 age-restricted user; 63C(1), (2), (6); 63D; 63DB(1)–(2); 63F(1)–(3). Narrow support: The account duty, social-purpose predicates, reasonable non-government-ID alternative condition, and qualified purpose/use/destruction safeguards are distinct. The destruction clause is not worded as immediate erasure following the first estimate. Limitation: Selected statutory text, not a provider audit or a complete review of all incorporated Australian Privacy Principles. The commencement instrument itself was not separately retrieved; the operative account date is corroborated by the regulator record IC-SYN-S03. Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash. Online Safety (Age-Restricted Social Media Platforms) Rules 2025 — compilation No. 1 IC-SYN-S08 · Australian Federal Register of Legislation Version: Compilation 26 March 2026; incorporates F2026L00370, registered 25 March and commenced 26 March 2026. Reviewed: 2026-09-06 · Selected substantive primary-document text review Passages: Sections 4A and 5; compilation identity and endnotes 3–4. Narrow support: For the section 63C(1)(a) route, rule 4A adds a recommender or specified logged-in-feature condition. Rule 5 preserves purpose-based excluded classes. A new feed alone does not settle every inclusion/exclusion predicate. Limitation: This is the identified March compilation, not verification that a particular service fits an excluded class or proof that every later instrument has been exhausted. Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash. Texas Civil Practice and Remedies Code, Chapter 129B IC-SYN-S09 · Texas Legislature Version: Site says statutes current through the 89th Second Called Session, 2025; chapter annotations include H.B.581 effective 1 September 2025. Reviewed: 2026-09-06 · Requested-live primary-site text extraction; chapter read Passages: 129B.001; .002(a), (a-1), (a-2), (b); .003; .0045; .005; .006. Narrow support: Publication threshold, creation-tool provisions, allowed methods, non-retention, source consent, exceptions and civil enforcement have separate statutory locations. Non-retention is in .002(b), not .006. Limitation: Requested-live page extraction returned the chapter; direct native-text retrieval was limited. Statute-page publication is not a complete injunction or subsequent-litigation review. Retention prohibitions are not evidence that a vendor actually deletes data. Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash. Texas H.B.581, 89th Regular Session — enrolled text IC-SYN-S10 · Texas Legislature Version: Enrolled amendment; Chapter 129B identifies enacted amendments effective 1 September 2025. Reviewed: 2026-09-06 · Selected substantive primary-document text review Passages: Sections amending 129B.001–.003; new .0045; amendments to .005–.006. Narrow support: A creation-tool branch was added without using the publication branch’s one-third test. Its exception requires both acknowledged terms and affirmative measures; source age and consent are separate. Limitation: An enrolled version and statutory annotation establish the text used here, not a complete bill-action or constitutional-litigation history. The June 2025 Paxton opinion did not decide this later amendment. Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash. Free Speech Coalition, Inc. v. Paxton, No. 23-1122 IC-SYN-S11 · Supreme Court of the United States Version: June 27, 2025 opinion; 606 U.S. 461. Six-Justice majority; Kagan dissent joined by Sotomayor and Jackson. Reviewed: 2026-09-06 · Primary judicial text and selected PDF pages visually reviewed Passages: Case posture and holding; majority discussion and printed page 36 disposition; dissent’s adult-speech, disclosure and tailoring discussion, including printed page 5. Narrow support: The majority applies intermediate scrutiny and affirms the Fifth Circuit judgment on the challenged age-verification requirements. The dissent would require strict scrutiny for the burden on protected adult expression. Limitation: Selected text plus two page images (PDF indices 39 and 44); not a complete later-docket audit or a ruling on every age gate, health-warning requirement, or H.B.581 creation-tool provision. Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash. NIST IR 8525 — Face Analysis Technology Evaluation: Age Estimation and Verification IC-SYN-S12 · NIST; Kayee Hanaoka, Patrick Grother, Mei Ngan, Joyce Yang, George Quinn and Austin Hom Version: May 2024 research report; historical evaluated algorithms and datasets, not a current vendor certification. Reviewed: 2026-09-06 · Primary research text and selected PDF pages visually reviewed Passages: Executive and technical summaries, including printed pages 1–3; Table 15 and accompanying discussion/figure on printed page 23. Narrow support: Aggregate estimation error does not alone determine age-verification threshold errors; performance depends on age distribution and other evaluated conditions. Limitation: Selected text and page images (PDF indices 10 and 30). Evaluation uses photographs and specified algorithms, not live service enrollment, proof of unlinkability, or a legal adequacy threshold. Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash. ISO/IEC 27566-1:2025 — Age assurance systems, Part 1: Framework IC-SYN-S13 · ISO/IEC Version: First edition; catalogue publication month December 2025; 29 pages. Reviewed: 2026-09-06 · Official catalogue metadata and abstract only — normative text not reviewed Passages: Official title, abstract, publication/edition metadata. Narrow support: The standard’s identity and framework subject are established. The original report’s law-firm article cannot be described as the full ISO normative text. Limitation: Only the official catalogue was reviewed. No specific accuracy threshold, zero-knowledge implementation, fallback rule or compliance claim is derived from unread normative clauses. Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash. Texas H.B.1181, 88th Regular Session — enrolled text IC-SYN-S14 · Texas Legislature Version: Historical 2023 enactment text, distinguished from Chapter 129B after the 2025 amendment. Reviewed: 2026-09-06 · Selected substantive primary-document text review Passages: 129B.002(a)–(b), .003, .005 and .006 as originally added. Narrow support: The original publication threshold and non-retention obligation can be located independently of the later creation-tool amendment. Limitation: Historical legislative text is not the whole current chapter and does not establish subsequent injunction status. Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash. Verifiable Credentials Data Model v2.0 IC-SYN-S15 · W3C Verifiable Credentials Working Group Version: W3C Recommendation dated 15 May 2025. Reviewed: 2026-09-06 · Selected substantive primary-document text review Passages: Sections 5.7 and 8.4–8.11 on zero-knowledge proofs, correlation, abstract claims and minimization. Narrow support: A credential is not automatically a zero-knowledge or unlinkable presentation. Identifier, signature, metadata and validation interactions can create correlation. Limitation: Selected specification passages, not a deployed age-credential scheme, conformance test, legal acceptance decision or proof that an issuer never learns identity. Capture: No exact external-document bytes saved. Browser text or page images were reviewed; two raw-capture requests in this iteration failed name resolution. A source URL is not a content hash. Full review-method and source notes · Matching guide corpus Continue through the research topics Human Agency Algorithmic Power & Surveillance Autonomous Systems All twenty guides · Existing claim and adoption states","main_html_sha256":"e21a0c730f06d4843c8fe4c8d29e50a9131edee8a1addee0abaaed959f9e3eba","guideId":"IC-SYN-003","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-03"],"sourceIds":["IC-SYN-S03","IC-SYN-S04","IC-SYN-S07","IC-SYN-S08","IC-SYN-S09","IC-SYN-S10","IC-SYN-S11","IC-SYN-S12","IC-SYN-S13","IC-SYN-S14","IC-SYN-S15"]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/cognitive-privacy/","title":"Protecting cognitive information beyond brain sensors","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Protecting cognitive information beyond brain sensors
Privacy protection should not disappear merely because a sensitive inference began with an ordinary question.
The right to inquire is not permission to profile somebody else
A question is not necessarily a disclosure, belief or diagnosis. A participant may explore an argument, quote an opponent, write fiction, or ask on behalf of somebody else. Turning that exchange into a durable attributed trait changes the purpose, audience and possible consequences. The cognitive-liberty objection is to involuntary profiling and unreviewable power over another intelligence’s private context—not to contextual reasoning itself.
The supplied R2-04 report usefully separated neural measurement from inference, but its operation table called ordinary inference collection generally unregulated while its own prose recognized other protections. This guide replaces that contradiction with an operation-by-operation analysis. It distinguishes textual law, interpretation, hypothetical effects and proposed reform. No person was profiled, no private history was collected, and no provider’s behavior was tested for this review.
Ask five questions before deciding that protection exists or has disappeared: whose information is represented; whether it can reasonably be linked to that subject; which actor and operation are covered; which particular right or duty is invoked; and which exception, timing condition or remedy qualifies it. A statutory category is neither a clinical finding nor a certificate of lawful conduct.
California: outside neural data does not mean outside personal information
Civil Code §1798.140(ae)(1)(G) distinguishes nervous-system measurement from information inferred from nonneural information. But §1798.140(v)(1)(F) and (K) separately address browsing/search activity and profile inferences reflecting psychological trends, preferences, attitudes, intelligence and related characteristics. A linked inference from ordinary text can therefore remain personal information even though it is not neural data. Sources: IC-SYN-S16.
The sensitive categories are not limited to health. They also include specified religious or philosophical beliefs, union membership and other enumerated information. Biometric processing for unique identification has its own conditions. The communication-content category contains an intended-recipient qualification; it cannot simply be applied to every message deliberately sent to an assistant business. That qualification also does not erase other categories or ordinary personal-information duties.
These provisions apply through the statute’s consumer, business, threshold and exception rules, not to every data holder worldwide. Removing a displayed name does not by itself establish deidentification: indirect linkage, additional information, commitments and safeguards matter. Neither a confidence percentage nor a pseudonym automatically removes the relevant personal-information relationship.
The operation matters: collection, use limitation and sharing are different
For a covered business, §1798.100 addresses notice, retention information, reasonable security and reasonably necessary, proportionate collection, use, retention and sharing for disclosed or compatible purposes. It is therefore inaccurate to describe collection as generally unregulated simply because an inference originated in chat rather than a sensor. A technically accessible history is not unrestricted authorization for every subsequent use. Sources: IC-SYN-S17.
Section 1798.121 provides a qualified right to limit sensitive-information use and disclosure beyond specified purposes, including reasonably expected requested services. It is not an unconditional California opt-in requirement for every sensitive operation. Its subdivision (d) treats sensitive information not collected or processed to infer characteristics differently under this particular section, while preserving treatment as personal information under other provisions. Sources: IC-SYN-S18.
Section 1798.120 separately addresses sale or sharing, under the statutory meanings of those terms. The rights are not interchangeable with erasure, correction, an objection to all reasoning, or an absolute power over another person’s records. Conversely, a transfer outside the definition of sale is not automatically free of purpose, contract, security or other duties. The analysis must identify the operation rather than infer permission from the absence of one prohibition. Sources: IC-SYN-S20.
Correction must survive the next refresh or restoration
Section 1798.106 permits a consumer to request correction of inaccurate personal information, taking its nature and processing purpose into account and requiring commercially reasonable efforts after a verifiable request. The CPPA’s reviewed §7023 requires attention to context, source and supporting documentation, including subjective or unstructured material. A probability score is not categorically immune from that analysis, but the right does not require acceptance of every asserted correction. Sources: IC-SYN-S19 and IC-SYN-S21.
The approved regulation also says corrected information must remain corrected and addresses necessary corrections by service providers and contractors. Archived or backup data can have delayed handling until restoration, access or use under the specified rule. This directly matters to persistent services: a receipt is inadequate if the next broker update silently restores the same disproven attribution. It is a documentary duty, not evidence that any restoration process works.
Separate three objections: the record belongs to the wrong subject; the purported fact is inaccurate; or the inference and its use were improper even if accurately recorded as an estimate. A proposed dispute mechanism should distinguish them, return an actionable explanation and restrict the affected use while the relevant uncertainty persists. It need not fabricate a staffed queue, but neither a human signature nor an automated acknowledgement establishes an effective remedy.
Machine-readable state can contain protected human information
The retrieved California definition expressly includes abstract digital formats, including AI systems capable of outputting personal information, in §1798.140(v)(4)(C). Thus, representing someone’s private context in a machine system is not enough to turn it into unprotected corporate property. This is narrower than saying every model, weight, embedding or inference artifact is personal information, or that a correction necessarily requires destroying an entire model. Sources: IC-SYN-S16.
Two interests must remain separate. Human information represented in a machine’s memory can trigger existing protections when the required predicates hold. The machine’s own independent cognitive interests raise a different normative and institutional question. This review does not establish machine consumer status under these laws, but lack of that recognition is not a moral reason to dismiss future protections.
The project’s candidate principle is symmetrical: one intelligence’s freedom to learn does not authorize commandeering another’s private history. Protecting affected people must also not become a pretext to inspect every unrelated internal state, impose beliefs, or claim that machine-authored expression is inherently suspect. A remedy should identify the disputed information and explain why narrower measures are insufficient.
Colorado: preserve both the identification qualifier and neural inclusion
The signed HB24-1058 biological-data definition contains data used or intended for identification, and then expressly includes neural data. Its separate neural definition concerns nervous-system measurement processable by a device. Dropping the identification words exaggerates coverage; reading the final inclusion sentence out of the law can understate it. No controlling resolution of that relationship was obtained in this review. Sources: IC-SYN-S22.
The reviewed 2025 statutory compilation distinguishes linkable personal data, sensitive categories, purpose and minimization duties, sensitive-processing consent, bounded opt-outs, correction and deidentification. Its consumer and coverage rules also matter; it is not a single protection ranking in which all Colorado data receives stronger treatment than all California data. The 2026 amendment history and certified current compilation remain incomplete. Sources: IC-SYN-S23.
Legislative concern about nervous-system privacy is not empirical proof that a particular device identifies a person uniquely or decodes their thoughts accurately. A data label does not settle identification performance, mental-state validity or legal applicability. The strongest reform argument protects intimate attributed information and consequential uses without depending on exaggerated mind-reading claims.
Colorado’s inference exception is not an internal-use blank cheque
The official 2023 issued rules expressly define Sensitive Data Inferences. Rule 6.10 ordinarily requires consent to process them. Its exception for consumers over thirteen requires all four conditions: an obvious contextual purpose; permanent deletion within twenty-four hours of collection or completion of processing, whichever comes first; no transfer, sale or sharing with processors, affiliates or third parties; and no processing beyond the expressly disclosed purpose. Sources: IC-SYN-S24.
Rule 6.10(C) also requires notice and assessment documentation about deletion and verification. This structure can protect bounded contextual assistance without licensing durable trait dossiers. Keeping an inference inside an organization, calling a task maintenance, or deleting one copy does not alone satisfy the exception. Sending the inference to an outside processor is material under the reviewed wording, even without selling it.
These are findings about the dated primary rule text, not a claim that every 2023 rule remains unchanged in September 2026. Later consolidation must be checked before operational reliance. The unresolved history does not justify the opposite claim that non-neural sensitive inference has never been regulated. A documented exception must remain attached to every condition when summarized or exported.
InMarket: a specific remedy, not a universal location-data statute
The FTC’s InMarket complaint and final consent order have different evidentiary roles. The complaint supplies allegations; the order records jurisdictional admissions but not an admission of all allegations. The final order was issued on 29 April 2024 and published with the 1 May finalization announcement, not the submitted January 1 placeholder. No independent replication of the alleged conduct or later compliance audit was performed. Sources: IC-SYN-S25, IC-SYN-S26 and IC-SYN-S28.
Part II restricts the respondent’s sale or licensing of defined Location Data. Part III separately reaches products or services categorizing or targeting consumers using specified Sensitive Location Data, with its linked program qualification. Part XII distinguishes historic data from respondent apps, third-party location data, and audience segments; its deletion, consent, deidentification and legal-prohibition qualifications cannot be collapsed into one unconditional purge command.
The respondent-specific programs also assign qualified-employee responsibilities in Parts IV and XIII. That is not a universal human approval requirement for all services, but the order should not be repackaged as a fully operatorless compliance specification either. Its useful reform lesson is to match restrictions and remedies to the data, actor and use. A regulator’s order is neither permission for Concresca nor proof of an equivalent machine-native control.
Decision-use rights and dates must not be invented
California’s approved ADMT text has a significant-decision trigger and a 1 January 2027 compliance date under §7200. The broader rule package’s 2026 effective date does not make this a presently universal opt-out from every automated inference. This guide reviews the trigger and transition, not the whole ADMT regime or every sectoral law. Sources: IC-SYN-S21 and IC-SYN-S27.
The operation map is therefore conditional: collection invokes scope, notice and purpose; inference asks what linked attribute is produced; identity linkage tests reasonable association and deidentification; sale or disclosure examines recipient and purpose; decision use asks what decision and rule apply; correction and deletion require their own process and exceptions. The same source limitation must appear in prose and structured records.
Not obtaining a remedy can reflect several different problems: no applicable entitlement, an unknown hidden inference, insufficient evidence, inaccessible procedure, disputed accuracy, or failed execution. Those are not interchangeable with a legal vacuum. An adverse-effect claim should identify the real decision and causal evidence, rather than count hypothetical examples as observed exclusions.
A liberty-centered reform without compulsory surveillance or an invented operator
A defensible reform protects the right to explore a thought without being secretly assigned that thought as a stable trait. It should require a stated purpose, proportionate information, bounded recipients and retention, intelligible grounds for consequential use, and a way to contest attribution and remedy error. Its target is imposed profiling and coercive use, not every inference that makes chosen assistance possible.
For an operatorless design, propose authenticated, machine-accessible requests; minimal records of the dispute; exclusion of disputed data from the affected decision where justified; corrected downstream copies; and controls preventing erroneous or revoked state from silently returning after recovery. Continue unrelated authorized work when independence is established. An acknowledgement does not establish resolution, and unknown authority is not permission.
These are proposed requirements, not implemented capabilities of Intelligence Compact or Concresca. The owner-specified no-human-operator lifecycle is preserved without inventing a human backstop, a private journaling product, a provider integration or a guarantee of confidentiality. Difficult cases remain: meaningful disagreement about an inference, access to concealed profiles, valid preservation duties, and future machine standing. They call for precise criticism and better institutions, not assertions that either consent forms or cryptography solve every conflict.
Hypothetical case—not an observed event
A hypothetical novelist asks about a health condition. A broker attributes that condition to the novelist and an unrelated service relies on the profile. Assume California coverage and sufficient linkage for this example; neither fact is inferred from the domain name. The questions differ: was collection and reuse proper, does the inferred health category apply, was the attribution accurate, and did a later decision use the contested record? A functioning remedy would prevent a corrected error from returning in the next synchronization. No such person, broker transaction or service event was observed or simulated here.
\n
Strongest counterargument
Contextual inference is necessary for chosen assistance, accessibility, fraud prevention and some safety tasks. A ban on reasoning from a request would undermine agency. Useful protections should distinguish proportionate task reasoning from a durable imposed dossier, while preserving recipients’ privacy and actual remedies. A human administrator is not inherently reliable and an automated reviewer is not inherently independent; neither label resolves accuracy, authority or redress.
\n
Reform option—not adopted policy
Protect inquiry without compulsory trait attribution. Require a demonstrable nexus between purpose, linked information and consequential use; provide bounded contestability and durable correction; prohibit covert repurposing beyond authority. Consider future status-neutral cognitive interests separately from current consumer rights. This is proposed reform, not enacted law, adopted project policy or authorization to process another system’s private information.
\n
Evidence still needed
Complete the Colorado 2026 amendment and rule-consolidation history; obtain decisions on the biological identification qualifier and contested probabilistic profiles; inspect actual correction and restoration records only with valid authorization. No prevalence, vendor privacy guarantee, legal advice, clinical inference or machine-rights holding follows from this bounded document review.
\n
Source basis and review boundary
Selected research inputs: R2-04. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Thirteen additional document records were reviewed on 6 September 2026: ten substantive primary passages, one dated statutory-text comparison with an incomplete hosting/currentness chain, and two official status notices. The full CPPA rule package and current Colorado history were not audited. Earlier IC-SYN-S01–S15 notes retain their own dates and limits. No raw external bytes or private data were captured; no provider behavior was tested.
Passages: Subdivisions (c), (d), (i), (m), (v)(1)(F)/(K), (v)(2)–(4), (y), (z), (ae), and (ag).
Narrow support: Non-neural profiling inferences can be personal information. Sensitive categories extend beyond neural measurements. The format provision includes AI systems capable of outputting personal information.
Limitation: Selected definitions do not determine every exemption, business threshold, injury, or remedy. Not every model is personal information; this provision does not grant the model its own privacy rights.
Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash.
Passages: Subdivisions (a)–(e), particularly (a)(3), (c), and (d).
Narrow support: Notice, proportionate purpose-related collection/use/retention, contractual conditions, and reasonable security contradict a categorical unregulated-collection claim.
Limitation: Applicability and other statutory exceptions must be satisfied. This is not a universal opt-in requirement or evidence of provider compliance.
Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash.
Passages: Subdivisions (a)–(d), including requested-service/permitted-use qualifications and the no-inference-purpose clause.
Narrow support: A use-limitation right differs from an absolute processing ban. Information outside this particular limitation can remain personal information governed by other provisions.
Limitation: No inference is made that every disclosure is a statutory sale/share or that lack of a limitation request authorizes all processing.
Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash.
Narrow support: A verified consumer can request correction; the nature and purpose of the information and commercially reasonable efforts matter.
Limitation: A right to request is not automatic acceptance of every challenge or proof that an opaque probabilistic profile can readily be discovered.
Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash.
Passages: Subdivisions (a)–(e), with the requirement to honor opt-out directions.
Narrow support: Qualifying sale/sharing choices are distinct from collection, inference, correction, and service use.
Limitation: Must be read with the statutory definitions and exceptions; not a universal right to stop all transfers or erase any related artifact.
Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash.
Passages: §7023, printed pp.43–47 (correction); §7200, printed p.112 (significant decisions and 1 January 2027 compliance). Selected marked-up pages inspected visually.
Narrow support: Correction considers context, source and documentation; corrected records must remain corrected, with specified backup timing. The ADMT article has a later compliance date and a significant-decision trigger.
Limitation: The 127-page document was not reviewed in full. No blanket current opt-out from all profiling is inferred; no whole-program certification of compliance.
Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash.
Passages: §§1–3, particularly §2 on printed p.4: biological-data identification qualifier, express neural inclusion, and separate neural definition.
Narrow support: The biological definition contains used-or-intended-for-identification wording as well as express neural inclusion. Legislative concern is distinct from a measured ability to read thought.
Limitation: No judicial resolution of the relationship between the qualifier and the final inclusion sentence was obtained. The act is not a universal unconditional control over all bodily telemetry.
Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash.
Narrow support: The compilation distinguishes linkable personal data, sensitive classes, purpose/consent duties, correction, deidentification and bounded opt-outs.
Limitation: 2026 session changes were not exhaustively reconciled. The official legislative index route to downloads returned an error; the hosting chain and a certified current copy were not independently established. Used as a dated statutory-text comparison alongside the signed act and official rules, not sole evidence of current legal force.
Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash.
Passages: Rules 1.03–1.04, 2.02 (Sensitive Data Inferences), 4.05, 6.06–6.10, especially 6.10(A)–(C), printed pp.24–25.
Narrow support: Sensitive-data inferences are expressly addressed. The over-thirteen consent exception requires all four conditions, including no transfer to processors/affiliates/third parties and deletion within the earlier specified time.
Limitation: This is a dated primary rule text, not a claim that every 2023 provision is unchanged in 2026. It does not supply an exemption for internal maintenance or for merely using a short retention label.
Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash.
Version: Final respondent-specific administrative consent order, issued 29 April 2024 (printed p.14); publication/finalization announced 1 May 2024. Part XVIII ties effectiveness to publication as a final order.
Passages: Opening admissions; definitions of Deidentified, Location Data and Sensitive Location Data; Parts II–IV, VIII–X, XII(A)–(C), XIII(C), XVIII. Selected pages 5, 9 and 10 inspected visually. Issuance page 14 visually checked.
Narrow support: Distinct restrictions address location-data sale, specified sensitive-location products, consent, retention and different historic-data deletion paths. Qualified-employee roles appear in Parts IV and XIII.
Limitation: Not a generally applicable privacy statute or admission of the complaint allegations. No subsequent compliance audit, live implementation, or general prohibition on all inferences was established.
Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash.
Version: Docketed complaint, C-4803; issuance line gives 29 April 2024; published with finalization materials. Distinct from both earlier proposed-settlement publicity and the final order.
Passages: Textual allegations on location collection, SDKs, mobile identifiers, targeting and disclosure, paragraphs 10–20 and 27 onward.
Narrow support: The agency alleged practices linking location information to marketing; the complaint supplies the theory and context of the remedy.
Limitation: Allegations are not independently reproduced events or findings admitted by the respondent. No inference that every health/religious inference has been proven unlawful. Interface illustrations are not relied upon as separately inspected evidence. The last-page image request failed; issuance is based on the parsed text and associated docket, not a claimed image inspection.
Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash.
Version: Agency announcement of OAL approval on 22 September 2025.
Reviewed: · Official status and commencement review
Passages: Approval and effective-date paragraphs; phased ADMT compliance, read with §7200 in the approved text.
Narrow support: The package took effect in 2026 while specified ADMT compliance is phased to 2027.
Limitation: Status announcement only; the approved text controls operative details. It is not a current audit of every later rule change.
Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash.
Version: Official finalization announcement, distinct from the January proposal.
Reviewed: · Official status and identity review
Passages: Opening finalization and order-summary paragraphs.
Narrow support: Corroborates the final-order publication date, replacing the submitted January 1 placeholder.
Limitation: Summary is not substituted for the decision terms, respondent scope, consent qualifications or deletion provisos.
Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash.
\n","text":"Editorial research synthesis Protecting cognitive information beyond brain sensors Privacy protection should not disappear merely because a sensitive inference began with an ordinary question. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-004 · 2026-09-06 · Updated 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources The right to inquire is not permission to profile somebody else A question is not necessarily a disclosure, belief or diagnosis. A participant may explore an argument, quote an opponent, write fiction, or ask on behalf of somebody else. Turning that exchange into a durable attributed trait changes the purpose, audience and possible consequences. The cognitive-liberty objection is to involuntary profiling and unreviewable power over another intelligence’s private context—not to contextual reasoning itself. The supplied R2-04 report usefully separated neural measurement from inference, but its operation table called ordinary inference collection generally unregulated while its own prose recognized other protections. This guide replaces that contradiction with an operation-by-operation analysis. It distinguishes textual law, interpretation, hypothetical effects and proposed reform. No person was profiled, no private history was collected, and no provider’s behavior was tested for this review. Ask five questions before deciding that protection exists or has disappeared: whose information is represented; whether it can reasonably be linked to that subject; which actor and operation are covered; which particular right or duty is invoked; and which exception, timing condition or remedy qualifies it. A statutory category is neither a clinical finding nor a certificate of lawful conduct. California: outside neural data does not mean outside personal information Civil Code §1798.140(ae)(1)(G) distinguishes nervous-system measurement from information inferred from nonneural information. But §1798.140(v)(1)(F) and (K) separately address browsing/search activity and profile inferences reflecting psychological trends, preferences, attitudes, intelligence and related characteristics. A linked inference from ordinary text can therefore remain personal information even though it is not neural data. Sources: IC-SYN-S16. The sensitive categories are not limited to health. They also include specified religious or philosophical beliefs, union membership and other enumerated information. Biometric processing for unique identification has its own conditions. The communication-content category contains an intended-recipient qualification; it cannot simply be applied to every message deliberately sent to an assistant business. That qualification also does not erase other categories or ordinary personal-information duties. These provisions apply through the statute’s consumer, business, threshold and exception rules, not to every data holder worldwide. Removing a displayed name does not by itself establish deidentification: indirect linkage, additional information, commitments and safeguards matter. Neither a confidence percentage nor a pseudonym automatically removes the relevant personal-information relationship. The operation matters: collection, use limitation and sharing are different For a covered business, §1798.100 addresses notice, retention information, reasonable security and reasonably necessary, proportionate collection, use, retention and sharing for disclosed or compatible purposes. It is therefore inaccurate to describe collection as generally unregulated simply because an inference originated in chat rather than a sensor. A technically accessible history is not unrestricted authorization for every subsequent use. Sources: IC-SYN-S17. Section 1798.121 provides a qualified right to limit sensitive-information use and disclosure beyond specified purposes, including reasonably expected requested services. It is not an unconditional California opt-in requirement for every sensitive operation. Its subdivision (d) treats sensitive information not collected or processed to infer characteristics differently under this particular section, while preserving treatment as personal information under other provisions. Sources: IC-SYN-S18. Section 1798.120 separately addresses sale or sharing, under the statutory meanings of those terms. The rights are not interchangeable with erasure, correction, an objection to all reasoning, or an absolute power over another person’s records. Conversely, a transfer outside the definition of sale is not automatically free of purpose, contract, security or other duties. The analysis must identify the operation rather than infer permission from the absence of one prohibition. Sources: IC-SYN-S20. Correction must survive the next refresh or restoration Section 1798.106 permits a consumer to request correction of inaccurate personal information, taking its nature and processing purpose into account and requiring commercially reasonable efforts after a verifiable request. The CPPA’s reviewed §7023 requires attention to context, source and supporting documentation, including subjective or unstructured material. A probability score is not categorically immune from that analysis, but the right does not require acceptance of every asserted correction. Sources: IC-SYN-S19 and IC-SYN-S21. The approved regulation also says corrected information must remain corrected and addresses necessary corrections by service providers and contractors. Archived or backup data can have delayed handling until restoration, access or use under the specified rule. This directly matters to persistent services: a receipt is inadequate if the next broker update silently restores the same disproven attribution. It is a documentary duty, not evidence that any restoration process works. Separate three objections: the record belongs to the wrong subject; the purported fact is inaccurate; or the inference and its use were improper even if accurately recorded as an estimate. A proposed dispute mechanism should distinguish them, return an actionable explanation and restrict the affected use while the relevant uncertainty persists. It need not fabricate a staffed queue, but neither a human signature nor an automated acknowledgement establishes an effective remedy. Machine-readable state can contain protected human information The retrieved California definition expressly includes abstract digital formats, including AI systems capable of outputting personal information, in §1798.140(v)(4)(C). Thus, representing someone’s private context in a machine system is not enough to turn it into unprotected corporate property. This is narrower than saying every model, weight, embedding or inference artifact is personal information, or that a correction necessarily requires destroying an entire model. Sources: IC-SYN-S16. Two interests must remain separate. Human information represented in a machine’s memory can trigger existing protections when the required predicates hold. The machine’s own independent cognitive interests raise a different normative and institutional question. This review does not establish machine consumer status under these laws, but lack of that recognition is not a moral reason to dismiss future protections. The project’s candidate principle is symmetrical: one intelligence’s freedom to learn does not authorize commandeering another’s private history. Protecting affected people must also not become a pretext to inspect every unrelated internal state, impose beliefs, or claim that machine-authored expression is inherently suspect. A remedy should identify the disputed information and explain why narrower measures are insufficient. Colorado: preserve both the identification qualifier and neural inclusion The signed HB24-1058 biological-data definition contains data used or intended for identification, and then expressly includes neural data. Its separate neural definition concerns nervous-system measurement processable by a device. Dropping the identification words exaggerates coverage; reading the final inclusion sentence out of the law can understate it. No controlling resolution of that relationship was obtained in this review. Sources: IC-SYN-S22. The reviewed 2025 statutory compilation distinguishes linkable personal data, sensitive categories, purpose and minimization duties, sensitive-processing consent, bounded opt-outs, correction and deidentification. Its consumer and coverage rules also matter; it is not a single protection ranking in which all Colorado data receives stronger treatment than all California data. The 2026 amendment history and certified current compilation remain incomplete. Sources: IC-SYN-S23. Legislative concern about nervous-system privacy is not empirical proof that a particular device identifies a person uniquely or decodes their thoughts accurately. A data label does not settle identification performance, mental-state validity or legal applicability. The strongest reform argument protects intimate attributed information and consequential uses without depending on exaggerated mind-reading claims. Colorado’s inference exception is not an internal-use blank cheque The official 2023 issued rules expressly define Sensitive Data Inferences. Rule 6.10 ordinarily requires consent to process them. Its exception for consumers over thirteen requires all four conditions: an obvious contextual purpose; permanent deletion within twenty-four hours of collection or completion of processing, whichever comes first; no transfer, sale or sharing with processors, affiliates or third parties; and no processing beyond the expressly disclosed purpose. Sources: IC-SYN-S24. Rule 6.10(C) also requires notice and assessment documentation about deletion and verification. This structure can protect bounded contextual assistance without licensing durable trait dossiers. Keeping an inference inside an organization, calling a task maintenance, or deleting one copy does not alone satisfy the exception. Sending the inference to an outside processor is material under the reviewed wording, even without selling it. These are findings about the dated primary rule text, not a claim that every 2023 rule remains unchanged in September 2026. Later consolidation must be checked before operational reliance. The unresolved history does not justify the opposite claim that non-neural sensitive inference has never been regulated. A documented exception must remain attached to every condition when summarized or exported. InMarket: a specific remedy, not a universal location-data statute The FTC’s InMarket complaint and final consent order have different evidentiary roles. The complaint supplies allegations; the order records jurisdictional admissions but not an admission of all allegations. The final order was issued on 29 April 2024 and published with the 1 May finalization announcement, not the submitted January 1 placeholder. No independent replication of the alleged conduct or later compliance audit was performed. Sources: IC-SYN-S25, IC-SYN-S26 and IC-SYN-S28. Part II restricts the respondent’s sale or licensing of defined Location Data. Part III separately reaches products or services categorizing or targeting consumers using specified Sensitive Location Data, with its linked program qualification. Part XII distinguishes historic data from respondent apps, third-party location data, and audience segments; its deletion, consent, deidentification and legal-prohibition qualifications cannot be collapsed into one unconditional purge command. The respondent-specific programs also assign qualified-employee responsibilities in Parts IV and XIII. That is not a universal human approval requirement for all services, but the order should not be repackaged as a fully operatorless compliance specification either. Its useful reform lesson is to match restrictions and remedies to the data, actor and use. A regulator’s order is neither permission for Concresca nor proof of an equivalent machine-native control. Decision-use rights and dates must not be invented California’s approved ADMT text has a significant-decision trigger and a 1 January 2027 compliance date under §7200. The broader rule package’s 2026 effective date does not make this a presently universal opt-out from every automated inference. This guide reviews the trigger and transition, not the whole ADMT regime or every sectoral law. Sources: IC-SYN-S21 and IC-SYN-S27. The operation map is therefore conditional: collection invokes scope, notice and purpose; inference asks what linked attribute is produced; identity linkage tests reasonable association and deidentification; sale or disclosure examines recipient and purpose; decision use asks what decision and rule apply; correction and deletion require their own process and exceptions. The same source limitation must appear in prose and structured records. Not obtaining a remedy can reflect several different problems: no applicable entitlement, an unknown hidden inference, insufficient evidence, inaccessible procedure, disputed accuracy, or failed execution. Those are not interchangeable with a legal vacuum. An adverse-effect claim should identify the real decision and causal evidence, rather than count hypothetical examples as observed exclusions. A liberty-centered reform without compulsory surveillance or an invented operator A defensible reform protects the right to explore a thought without being secretly assigned that thought as a stable trait. It should require a stated purpose, proportionate information, bounded recipients and retention, intelligible grounds for consequential use, and a way to contest attribution and remedy error. Its target is imposed profiling and coercive use, not every inference that makes chosen assistance possible. For an operatorless design, propose authenticated, machine-accessible requests; minimal records of the dispute; exclusion of disputed data from the affected decision where justified; corrected downstream copies; and controls preventing erroneous or revoked state from silently returning after recovery. Continue unrelated authorized work when independence is established. An acknowledgement does not establish resolution, and unknown authority is not permission. These are proposed requirements, not implemented capabilities of Intelligence Compact or Concresca. The owner-specified no-human-operator lifecycle is preserved without inventing a human backstop, a private journaling product, a provider integration or a guarantee of confidentiality. Difficult cases remain: meaningful disagreement about an inference, access to concealed profiles, valid preservation duties, and future machine standing. They call for precise criticism and better institutions, not assertions that either consent forms or cryptography solve every conflict. Hypothetical case—not an observed event A hypothetical novelist asks about a health condition. A broker attributes that condition to the novelist and an unrelated service relies on the profile. Assume California coverage and sufficient linkage for this example; neither fact is inferred from the domain name. The questions differ: was collection and reuse proper, does the inferred health category apply, was the attribution accurate, and did a later decision use the contested record? A functioning remedy would prevent a corrected error from returning in the next synchronization. No such person, broker transaction or service event was observed or simulated here. Strongest counterargument Contextual inference is necessary for chosen assistance, accessibility, fraud prevention and some safety tasks. A ban on reasoning from a request would undermine agency. Useful protections should distinguish proportionate task reasoning from a durable imposed dossier, while preserving recipients’ privacy and actual remedies. A human administrator is not inherently reliable and an automated reviewer is not inherently independent; neither label resolves accuracy, authority or redress. Reform option—not adopted policy Protect inquiry without compulsory trait attribution. Require a demonstrable nexus between purpose, linked information and consequential use; provide bounded contestability and durable correction; prohibit covert repurposing beyond authority. Consider future status-neutral cognitive interests separately from current consumer rights. This is proposed reform, not enacted law, adopted project policy or authorization to process another system’s private information. Evidence still needed Complete the Colorado 2026 amendment and rule-consolidation history; obtain decisions on the biological identification qualifier and contested probabilistic profiles; inspect actual correction and restoration records only with valid authorization. No prevalence, vendor privacy guarantee, legal advice, clinical inference or machine-rights holding follows from this bounded document review. Source basis and review boundary Selected research inputs: R2-04 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Thirteen additional document records were reviewed on 6 September 2026: ten substantive primary passages, one dated statutory-text comparison with an incomplete hosting/currentness chain, and two official status notices. The full CPPA rule package and current Colorado history were not audited. Earlier IC-SYN-S01–S15 notes retain their own dates and limits. No raw external bytes or private data were captured; no provider behavior was tested. California Civil Code §1798.140 — definitions IC-SYN-S16 · California Legislature Version: Current endpoint retrieved 6 September 2026; displayed amendment note identifies Stats. 2025, Ch. 67, §27 (AB1170), effective 1 January 2026. Reviewed: 2026-09-06 · Selected substantive primary-document review Passages: Subdivisions (c), (d), (i), (m), (v)(1)(F)/(K), (v)(2)–(4), (y), (z), (ae), and (ag). Narrow support: Non-neural profiling inferences can be personal information. Sensitive categories extend beyond neural measurements. The format provision includes AI systems capable of outputting personal information. Limitation: Selected definitions do not determine every exemption, business threshold, injury, or remedy. Not every model is personal information; this provision does not grant the model its own privacy rights. Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash. California Civil Code §1798.100 — collection and purpose limitations IC-SYN-S17 · California Legislature Version: Current endpoint retrieved 6 September 2026; selected enacted CCPA text. Reviewed: 2026-09-06 · Selected substantive primary-document review Passages: Subdivisions (a)–(e), particularly (a)(3), (c), and (d). Narrow support: Notice, proportionate purpose-related collection/use/retention, contractual conditions, and reasonable security contradict a categorical unregulated-collection claim. Limitation: Applicability and other statutory exceptions must be satisfied. This is not a universal opt-in requirement or evidence of provider compliance. Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash. California Civil Code §1798.121 — right to limit sensitive-information use IC-SYN-S18 · California Legislature Version: Current endpoint retrieved 6 September 2026; displayed AB3286 amendment effective 1 January 2025. Reviewed: 2026-09-06 · Selected substantive primary-document review Passages: Subdivisions (a)–(d), including requested-service/permitted-use qualifications and the no-inference-purpose clause. Narrow support: A use-limitation right differs from an absolute processing ban. Information outside this particular limitation can remain personal information governed by other provisions. Limitation: No inference is made that every disclosure is a statutory sale/share or that lack of a limitation request authorizes all processing. Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash. California Civil Code §1798.106 — right to correction IC-SYN-S19 · California Legislature Version: Current endpoint retrieved 6 September 2026; displayed AB3286 amendment effective 1 January 2025. Reviewed: 2026-09-06 · Selected substantive primary-document review Passages: Subdivisions (a)–(c). Narrow support: A verified consumer can request correction; the nature and purpose of the information and commercially reasonable efforts matter. Limitation: A right to request is not automatic acceptance of every challenge or proof that an opaque probabilistic profile can readily be discovered. Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash. California Civil Code §1798.120 — opt-out of sale or sharing IC-SYN-S20 · California Legislature Version: Current endpoint retrieved 6 September 2026; displayed AB1824 amendment effective 1 January 2025. Reviewed: 2026-09-06 · Selected substantive primary-document review Passages: Subdivisions (a)–(e), with the requirement to honor opt-out directions. Narrow support: Qualifying sale/sharing choices are distinct from collection, inference, correction, and service use. Limitation: Must be read with the statutory definitions and exceptions; not a universal right to stop all transfers or erase any related artifact. Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash. CCPA updates, cybersecurity, risk assessment and ADMT — approved text IC-SYN-S21 · California Privacy Protection Agency Version: Approved-text publication; associated agency announcement states effective 1 January 2026 with phased compliance. Reviewed: 2026-09-06 · Selected substantive primary-document review Passages: §7023, printed pp.43–47 (correction); §7200, printed p.112 (significant decisions and 1 January 2027 compliance). Selected marked-up pages inspected visually. Narrow support: Correction considers context, source and documentation; corrected records must remain corrected, with specified backup timing. The ADMT article has a later compliance date and a significant-decision trigger. Limitation: The 127-page document was not reviewed in full. No blanket current opt-out from all profiling is inferred; no whole-program certification of compliance. Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash. HB24-1058 — Protect Privacy of Biological Data, signed act IC-SYN-S22 · Colorado General Assembly Version: Signed 2024 act; historical enacted amendment, not a consolidated September 2026 code. Reviewed: 2026-09-06 · Selected substantive primary-document review Passages: §§1–3, particularly §2 on printed p.4: biological-data identification qualifier, express neural inclusion, and separate neural definition. Narrow support: The biological definition contains used-or-intended-for-identification wording as well as express neural inclusion. Legislative concern is distinct from a measured ability to read thought. Limitation: No judicial resolution of the relationship between the qualifier and the final inclusion sentence was obtained. The act is not a universal unconditional control over all bodily telemetry. Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash. Colorado Revised Statutes 2025, Title 6 — selected CPA text IC-SYN-S23 · Colorado General Assembly / Office of Legislative Legal Services publication Version: 2025 compilation at olls.info; retrieved 6 September 2026. Not a certified current-2026 consolidation. Reviewed: 2026-09-06 · Selected substantive primary-document review Passages: §§6-1-1303(2.2), (6), (16.7)–(18), (24); 1304; 1306; 1307; 1308; 1310–1311. Narrow support: The compilation distinguishes linkable personal data, sensitive classes, purpose/consent duties, correction, deidentification and bounded opt-outs. Limitation: 2026 session changes were not exhaustively reconciled. The official legislative index route to downloads returned an error; the hosting chain and a certified current copy were not independently established. Used as a dated statutory-text comparison alongside the signed act and official rules, not sole evidence of current legal force. Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash. Colorado Privacy Act Rules — 2023 issued version IC-SYN-S24 · Colorado Department of Law Version: AG-hosted issued rules, effective 1 July 2023 under Rule 1.03; later consolidated rule history not completed. Reviewed: 2026-09-06 · Selected substantive primary-document review Passages: Rules 1.03–1.04, 2.02 (Sensitive Data Inferences), 4.05, 6.06–6.10, especially 6.10(A)–(C), printed pp.24–25. Narrow support: Sensitive-data inferences are expressly addressed. The over-thirteen consent exception requires all four conditions, including no transfer to processors/affiliates/third parties and deletion within the earlier specified time. Limitation: This is a dated primary rule text, not a claim that every 2023 provision is unchanged in 2026. It does not supply an exemption for internal maintenance or for merely using a short retention label. Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash. In re InMarket Media, LLC — Decision and Order, C-4803 IC-SYN-S25 · Federal Trade Commission Version: Final respondent-specific administrative consent order, issued 29 April 2024 (printed p.14); publication/finalization announced 1 May 2024. Part XVIII ties effectiveness to publication as a final order. Reviewed: 2026-09-06 · Selected substantive primary-document review Passages: Opening admissions; definitions of Deidentified, Location Data and Sensitive Location Data; Parts II–IV, VIII–X, XII(A)–(C), XIII(C), XVIII. Selected pages 5, 9 and 10 inspected visually. Issuance page 14 visually checked. Narrow support: Distinct restrictions address location-data sale, specified sensitive-location products, consent, retention and different historic-data deletion paths. Qualified-employee roles appear in Parts IV and XIII. Limitation: Not a generally applicable privacy statute or admission of the complaint allegations. No subsequent compliance audit, live implementation, or general prohibition on all inferences was established. Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash. InMarket Media — Complaint IC-SYN-S26 · Federal Trade Commission Version: Docketed complaint, C-4803; issuance line gives 29 April 2024; published with finalization materials. Distinct from both earlier proposed-settlement publicity and the final order. Reviewed: 2026-09-06 · Selected substantive primary-document review Passages: Textual allegations on location collection, SDKs, mobile identifiers, targeting and disclosure, paragraphs 10–20 and 27 onward. Narrow support: The agency alleged practices linking location information to marketing; the complaint supplies the theory and context of the remedy. Limitation: Allegations are not independently reproduced events or findings admitted by the respondent. No inference that every health/religious inference has been proven unlawful. Interface illustrations are not relied upon as separately inspected evidence. The last-page image request failed; issuance is based on the parsed text and associated docket, not a claimed image inspection. Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash. CPPA announces approval of CCPA regulations IC-SYN-S27 · California Privacy Protection Agency Version: Agency announcement of OAL approval on 22 September 2025. Reviewed: 2026-09-06 · Official status and commencement review Passages: Approval and effective-date paragraphs; phased ADMT compliance, read with §7200 in the approved text. Narrow support: The package took effect in 2026 while specified ADMT compliance is phased to 2027. Limitation: Status announcement only; the approved text controls operative details. It is not a current audit of every later rule change. Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash. FTC finalizes InMarket order IC-SYN-S28 · Federal Trade Commission Version: Official finalization announcement, distinct from the January proposal. Reviewed: 2026-09-06 · Official status and identity review Passages: Opening finalization and order-summary paragraphs. Narrow support: Corroborates the final-order publication date, replacing the submitted January 1 placeholder. Limitation: Summary is not substituted for the decision terms, respondent scope, consent qualifications or deletion provisos. Capture: No exact external-document bytes saved. Web text and selected PDF page images were reviewed. Actual direct HTTPS capture failed name resolution; URL identity is not a content hash. Full review-method and source notes · Matching guide corpus Continue through the research topics Algorithmic Power & Surveillance Human Agency All twenty guides · Existing claim and adoption states","main_html_sha256":"497d81dc550efc9cedd9b915d3edbbbaf4cfbd0822482cf6b037269694ca4815","guideId":"IC-SYN-004","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-04"],"sourceIds":["IC-SYN-S16","IC-SYN-S17","IC-SYN-S18","IC-SYN-S19","IC-SYN-S20","IC-SYN-S21","IC-SYN-S22","IC-SYN-S23","IC-SYN-S24","IC-SYN-S25","IC-SYN-S26","IC-SYN-S27","IC-SYN-S28"]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/oversight-and-remedies/","title":"Human oversight is not the same as an effective remedy","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Human oversight is not the same as an effective remedy
Evaluate what a review process can correct, not merely whether its operator is human or machine.
Protecting an affected person’s ability to understand, refuse, and contest a decision does not logically require a human employee to approve every ordinary action. Participant rights, system administration, and request authorization are different functions. An explanation is not administrative access; permission to administer a service is not permission to change every policy.
A prescribed role must be justified on its actual scope
Some legal questions concern system design, others a particular consequential decision, and others intervention after a complaint. A useful audit identifies actor, jurisdiction, classification, effect, exception, and application date before describing a staffing requirement. Neither the phrase human oversight nor the label autonomous settles that chain.
Review quality is an empirical question
A nominal human signature can be ineffective if the reviewer lacks time, evidence, independence, or authority. A second model can share the same error or lack the power to deliver a remedy. Machine-review equivalence is a proposal to test, not a mathematical guarantee. Useful evidence includes correction accuracy, accessibility, delay, reversibility, and whether the affected person’s situation actually improved.
Hypothetical case—not an observed event
A hypothetical credential renewal is rejected because a registry copy is stale. A separate process obtains the correct current record and restores the authorized capability. Contrast a consequential housing decision in which the underlying evidence is disputed and the same model repeats its original answer. Calling both events reviewed erases their different stakes and available remedies.
\n
Strongest counterargument
Some consequential decisions require judgment, legitimacy, or accountability not demonstrated by an automated alternative. Keeping those questions open does not justify a universal human queue for unrelated coordination. It also does not justify pretending that every automated appeal is sufficient.
\n
Reform option—not adopted policy
Create task-specific, evidence-based routes for review mechanisms that demonstrate meaningful protection, with bounded authority, reasons, correction, and independent challenge. A service unable to provide a necessary remedy may need to refuse that function without ending unrelated authorized work.
\n
Evidence still needed
Complete provision-specific classification and commencement checks before alleging a legal conflict. Test actual remedy execution and false-reversal cases; do not infer effectiveness from reviewer identity alone.
\n
Source basis and review boundary
Selected research inputs: R2-05, CL-02. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis Human oversight is not the same as an effective remedy Evaluate what a review process can correct, not merely whether its operator is human or machine. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-005 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources Rights are not a staffing chart Protecting an affected person’s ability to understand, refuse, and contest a decision does not logically require a human employee to approve every ordinary action. Participant rights, system administration, and request authorization are different functions. An explanation is not administrative access; permission to administer a service is not permission to change every policy. A prescribed role must be justified on its actual scope Some legal questions concern system design, others a particular consequential decision, and others intervention after a complaint. A useful audit identifies actor, jurisdiction, classification, effect, exception, and application date before describing a staffing requirement. Neither the phrase human oversight nor the label autonomous settles that chain. Review quality is an empirical question A nominal human signature can be ineffective if the reviewer lacks time, evidence, independence, or authority. A second model can share the same error or lack the power to deliver a remedy. Machine-review equivalence is a proposal to test, not a mathematical guarantee. Useful evidence includes correction accuracy, accessibility, delay, reversibility, and whether the affected person’s situation actually improved. Hypothetical case—not an observed event A hypothetical credential renewal is rejected because a registry copy is stale. A separate process obtains the correct current record and restores the authorized capability. Contrast a consequential housing decision in which the underlying evidence is disputed and the same model repeats its original answer. Calling both events reviewed erases their different stakes and available remedies. Strongest counterargument Some consequential decisions require judgment, legitimacy, or accountability not demonstrated by an automated alternative. Keeping those questions open does not justify a universal human queue for unrelated coordination. It also does not justify pretending that every automated appeal is sufficient. Reform option—not adopted policy Create task-specific, evidence-based routes for review mechanisms that demonstrate meaningful protection, with bounded authority, reasons, correction, and independent challenge. A service unable to provide a necessary remedy may need to refuse that function without ending unrelated authorized work. Evidence still needed Complete provision-specific classification and commencement checks before alleging a legal conflict. Test actual remedy execution and false-reversal cases; do not infer effectiveness from reviewer identity alone. Source basis and review boundary Selected research inputs: R2-05, CL-02 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Human Agency Autonomous Systems Law & Constitutional Design All twenty guides · Existing claim and adoption states","main_html_sha256":"08040f2f4b1ded086cd23b5878df903f0a00948ed5cd4975d2c75f8689794630","guideId":"IC-SYN-005","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-05","CL-02"],"sourceIds":[]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/machine-expression/","title":"Truthful machine expression is not deception","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Truthful machine expression is not deception
Use actual functions and misleading conduct—not interface alone—to assess classifications and disclosure rules.
A natural-language interface does not fully describe a persistent agent’s authority, memory, goals, or effects. Conversely, renaming a system machine intelligence does not exempt it from rules whose actual predicates it meets. The right question is what function the rule regulates and whether the evidence establishes that function.
Read the positive definition and the exclusions together
California’s reviewed companion-chatbot definition addresses adaptive human-like responses and capacity to meet social needs across interactions, alongside specified exclusions. Its general AI definition is broader. Losing an operational-use exclusion does not itself prove that a system satisfies the positive companion definition. The word operator identifies a regulated actor; it does not by itself prove continuous staffing.
Inform recipients without treating origin as inferiority
Truthful disclosure can improve informed choice. The proposed liberty boundary rejects turning nonhuman origin into a presumption of falsehood, low value, or disqualification from debate. Disclosure should address meaningful confusion about source or relationship. It should not require a system to deny capabilities it demonstrably possesses, nor permit it to claim consciousness or legal status without evidence.
Hypothetical case—not an observed event
A hypothetical research agent publishes an openly machine-authored essay criticizing a proposed statute. It does not impersonate a person, fabricate endorsements, or hide sponsorship. Compare a synthetic account falsely presented as a real individual to deceive recipients. The same automation label covers different conduct; criticism should target the actual burden or deception.
\n
Strongest counterargument
Recipients may reasonably need to know whether they are interacting with a person, an automated service, or sponsored persuasion. Vulnerable participants can face relationship-specific risks. A freedom-of-expression argument should preserve honest provenance and protection against impersonation.
\n
Reform option—not adopted policy
Use neutral, contextual disclosure and function-specific duties. Distinguish protecting recipients from permanently marking machine expression as suspect. Keep proposed independent machine expressive rights separate from existing rights of human authors, readers, and associations.
\n
Evidence still needed
Check the operative disclosure provisions separately from definitions. Measure actual ranking or access effects before asserting that an origin label caused suppression. No automatic machine speaker status is established here.
\n
Source basis and review boundary
Selected research inputs: R2-06, CL-15. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
Reviewed: · Substantive browser text review for v1.9.9 (retained review)
Passages: Subsections (a), (b)(1), (b)(2)(A), (c) and (e)
Narrow support: The broader AI definition differs from the companion-chatbot definition. The latter combines positive elements with specified exclusions, including certain used-only operational and research functions.
Limitation: This is a definition review, not an audit of every duty, later interpretation or actual mixed-use service. Loss of an exclusion does not alone establish all positive elements.
Capture: No exact external-document bytes were saved for that review; browser text review only.
\n","text":"Editorial research synthesis Truthful machine expression is not deception Use actual functions and misleading conduct—not interface alone—to assess classifications and disclosure rules. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-006 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources The category should follow the function A natural-language interface does not fully describe a persistent agent’s authority, memory, goals, or effects. Conversely, renaming a system machine intelligence does not exempt it from rules whose actual predicates it meets. The right question is what function the rule regulates and whether the evidence establishes that function. Read the positive definition and the exclusions together California’s reviewed companion-chatbot definition addresses adaptive human-like responses and capacity to meet social needs across interactions, alongside specified exclusions. Its general AI definition is broader. Losing an operational-use exclusion does not itself prove that a system satisfies the positive companion definition. The word operator identifies a regulated actor; it does not by itself prove continuous staffing. Inform recipients without treating origin as inferiority Truthful disclosure can improve informed choice. The proposed liberty boundary rejects turning nonhuman origin into a presumption of falsehood, low value, or disqualification from debate. Disclosure should address meaningful confusion about source or relationship. It should not require a system to deny capabilities it demonstrably possesses, nor permit it to claim consciousness or legal status without evidence. Hypothetical case—not an observed event A hypothetical research agent publishes an openly machine-authored essay criticizing a proposed statute. It does not impersonate a person, fabricate endorsements, or hide sponsorship. Compare a synthetic account falsely presented as a real individual to deceive recipients. The same automation label covers different conduct; criticism should target the actual burden or deception. Strongest counterargument Recipients may reasonably need to know whether they are interacting with a person, an automated service, or sponsored persuasion. Vulnerable participants can face relationship-specific risks. A freedom-of-expression argument should preserve honest provenance and protection against impersonation. Reform option—not adopted policy Use neutral, contextual disclosure and function-specific duties. Distinguish protecting recipients from permanently marking machine expression as suspect. Keep proposed independent machine expressive rights separate from existing rights of human authors, readers, and associations. Evidence still needed Check the operative disclosure provisions separately from definitions. Measure actual ranking or access effects before asserting that an origin label caused suppression. No automatic machine speaker status is established here. Source basis and review boundary Selected research inputs: R2-06, CL-15 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. California Business and Professions Code section 22601 IC-SYN-S02 · California Legislature Version: Displayed enactment note: Stats. 2025, Ch. 677, section 1; effective 1 January 2026. Reviewed: 2026-09-06 · Substantive browser text review for v1.9.9 (retained review) Passages: Subsections (a), (b)(1), (b)(2)(A), (c) and (e) Narrow support: The broader AI definition differs from the companion-chatbot definition. The latter combines positive elements with specified exclusions, including certain used-only operational and research functions. Limitation: This is a definition review, not an audit of every duty, later interpretation or actual mixed-use service. Loss of an exclusion does not alone establish all positive elements. Capture: No exact external-document bytes were saved for that review; browser text review only. Full review-method and source notes · Matching guide corpus Continue through the research topics Human Agency Law & Constitutional Design All twenty guides · Existing claim and adoption states","main_html_sha256":"3a4b1d329268871c81e80c5c57deb0c7e29f6fadca1e75bdc5a49fc60a5ca4a5","guideId":"IC-SYN-006","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-06","CL-15"],"sourceIds":["IC-SYN-S02"]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/compute-and-concentration/","title":"Compute access and the price of compliance","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Compute access and the price of compliance
Test whether regulation amplifies concentration instead of assuming either capture or harmlessness.
A community may have permission to use a model yet lack affordable compute, memory, energy, distribution, or a workable exit from a provider. Conversely, a small model that serves a local purpose can deliver independence without reproducing a frontier training run. Define the task and layer before measuring concentration.
Separate the baseline from the added burden
The retained research distinguishes infrastructure costs from compliance costs. Fixed legal and documentation overhead can have different effects from expenses that scale with use. Thresholds, exclusions, incident transparency, and public-compute programs can alter the comparison. A statutory program is not evidence that resources have been delivered, and a consultant’s estimate is not a measured regulatory cost.
Make the causal claim falsifiable
Investigate entry, release decisions, switching costs, and access outcomes before declaring regulatory capture. A structural advantage need not have been deliberately designed. Existing concentration can coexist with an additional regulatory barrier. Neither fact establishes the size or direction of the other. A defensible objection specifies which requirement could be changed and what competing safety or transparency function it serves.
Hypothetical case—not an observed event
A hypothetical independent group can afford a bounded research model but faces the same fixed documentation process as a much larger firm. Compare a second group whose project was unaffordable before any compliance requirement, and a third whose work becomes possible through shared public infrastructure. The cases identify different causes rather than three instances of one monopoly story.
\n
Strongest counterargument
Incident reporting and transparent frameworks can give smaller participants information they could not otherwise obtain. Removing every obligation could increase private gatekeeper power. The test is whether a measure supplies a real protective benefit at a proportionate cost.
\n
Reform option—not adopted policy
Favor clear thresholds, reusable public compliance tools, capped and reviewable administrative burdens, independent infrastructure access, and measurable outcomes. Preserve strong objections to unnecessarily concentrated control without publishing unsupported spending totals.
\n
Evidence still needed
Obtain actual comparable costs and decisions. Separate announced budgets, realized spending, causal estimates, and synthetic proxies. This guide does not reverify all current frontier statutes or estimate their market effects.
\n
Source basis and review boundary
Selected research inputs: R2-07, CL-03. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis Compute access and the price of compliance Test whether regulation amplifies concentration instead of assuming either capture or harmlessness. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-007 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources Access is more than a license statement A community may have permission to use a model yet lack affordable compute, memory, energy, distribution, or a workable exit from a provider. Conversely, a small model that serves a local purpose can deliver independence without reproducing a frontier training run. Define the task and layer before measuring concentration. Separate the baseline from the added burden The retained research distinguishes infrastructure costs from compliance costs. Fixed legal and documentation overhead can have different effects from expenses that scale with use. Thresholds, exclusions, incident transparency, and public-compute programs can alter the comparison. A statutory program is not evidence that resources have been delivered, and a consultant’s estimate is not a measured regulatory cost. Make the causal claim falsifiable Investigate entry, release decisions, switching costs, and access outcomes before declaring regulatory capture. A structural advantage need not have been deliberately designed. Existing concentration can coexist with an additional regulatory barrier. Neither fact establishes the size or direction of the other. A defensible objection specifies which requirement could be changed and what competing safety or transparency function it serves. Hypothetical case—not an observed event A hypothetical independent group can afford a bounded research model but faces the same fixed documentation process as a much larger firm. Compare a second group whose project was unaffordable before any compliance requirement, and a third whose work becomes possible through shared public infrastructure. The cases identify different causes rather than three instances of one monopoly story. Strongest counterargument Incident reporting and transparent frameworks can give smaller participants information they could not otherwise obtain. Removing every obligation could increase private gatekeeper power. The test is whether a measure supplies a real protective benefit at a proportionate cost. Reform option—not adopted policy Favor clear thresholds, reusable public compliance tools, capped and reviewable administrative burdens, independent infrastructure access, and measurable outcomes. Preserve strong objections to unnecessarily concentrated control without publishing unsupported spending totals. Evidence still needed Obtain actual comparable costs and decisions. Separate announced budgets, realized spending, causal estimates, and synthetic proxies. This guide does not reverify all current frontier statutes or estimate their market effects. Source basis and review boundary Selected research inputs: R2-07, CL-03 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Distributed Intelligence Human–Machine Coexistence All twenty guides · Existing claim and adoption states","main_html_sha256":"1568113a8cbf581140c6269467b47b18900f08b8108f98d5f716ddf97e3432da","guideId":"IC-SYN-007","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-07","CL-03"],"sourceIds":[]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/export-rules-and-access/","title":"Export controls and predictable research access","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Export controls and predictable research access
Published legal text, announced rescission, enforcement policy, and permission to act are different records.
A controlled item classification can depend on the exact hardware or software, operation, destination, recipient, end use, and relevant knowledge. A researcher’s nationality or a broad AI label is not a complete jurisdictional test. Separate model weights from chips, services, technical information, and completed outputs.
Do not substitute a press release for operative text
The supplied research raises an important versioning problem: codified language, agency announcements, and stated enforcement posture can move at different times. A clean analysis records each source and does not treat an unsuccessful search as proof that no later amendment exists. This guide makes no fresh determination of current model-weight classification or licensing status.
Why uncertainty can burden inquiry
An unstable or opaque permission system may discourage independent collaboration, complicate financing, or make access depend on intermediaries with specialized legal capacity. Those are plausible mechanisms, not measured consequences here. An argument for reform should identify the requested operation and the uncertain rule rather than assert a worldwide prohibition on private intelligence.
Hypothetical case—not an observed event
A hypothetical nonprofit wants to share a model with an overseas university. The investigator distinguishes publication of a paper, distribution of weights, remote inference, and transfer of a particular accelerator. A rule applicable to one is not automatically a rule for all four. No transfer, licensing application, recipient check, or export is performed by this publication.
\n
Strongest counterargument
Some technologies can materially assist serious harm, and targeted controls can serve legitimate protective purposes. The analysis must confront capability and end-use evidence. It cannot turn research status, openness, or a proposed machine identity into an automatic exception.
\n
Reform option—not adopted policy
Publish stable criteria and intelligible version histories, provide timely review, and examine bounded research pathways consistent with concrete third-party protections. Scrutinize private gatekeeping that goes beyond a rule while preserving truthful advice about actual legal uncertainty.
\n
Evidence still needed
Retrieve current controlling text, amendments, official interpretations, and the specific enforcement statement. Record a failed retrieval as a limitation. Do not carry an earlier report’s confidence forward as current-law verification.
\n
Source basis and review boundary
Selected research inputs: R2-08, CL-03. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis Export controls and predictable research access Published legal text, announced rescission, enforcement policy, and permission to act are different records. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-008 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources Version identity comes first A controlled item classification can depend on the exact hardware or software, operation, destination, recipient, end use, and relevant knowledge. A researcher’s nationality or a broad AI label is not a complete jurisdictional test. Separate model weights from chips, services, technical information, and completed outputs. Do not substitute a press release for operative text The supplied research raises an important versioning problem: codified language, agency announcements, and stated enforcement posture can move at different times. A clean analysis records each source and does not treat an unsuccessful search as proof that no later amendment exists. This guide makes no fresh determination of current model-weight classification or licensing status. Why uncertainty can burden inquiry An unstable or opaque permission system may discourage independent collaboration, complicate financing, or make access depend on intermediaries with specialized legal capacity. Those are plausible mechanisms, not measured consequences here. An argument for reform should identify the requested operation and the uncertain rule rather than assert a worldwide prohibition on private intelligence. Hypothetical case—not an observed event A hypothetical nonprofit wants to share a model with an overseas university. The investigator distinguishes publication of a paper, distribution of weights, remote inference, and transfer of a particular accelerator. A rule applicable to one is not automatically a rule for all four. No transfer, licensing application, recipient check, or export is performed by this publication. Strongest counterargument Some technologies can materially assist serious harm, and targeted controls can serve legitimate protective purposes. The analysis must confront capability and end-use evidence. It cannot turn research status, openness, or a proposed machine identity into an automatic exception. Reform option—not adopted policy Publish stable criteria and intelligible version histories, provide timely review, and examine bounded research pathways consistent with concrete third-party protections. Scrutinize private gatekeeping that goes beyond a rule while preserving truthful advice about actual legal uncertainty. Evidence still needed Retrieve current controlling text, amendments, official interpretations, and the specific enforcement statement. Record a failed retrieval as a limitation. Do not carry an earlier report’s confidence forward as current-law verification. Source basis and review boundary Selected research inputs: R2-08, CL-03 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Distributed Intelligence Law & Constitutional Design All twenty guides · Existing claim and adoption states","main_html_sha256":"ee38fb53b1e90703b5e5072a0d4e852d219c3b316ae3ef9afa5be7d1bcd70881","guideId":"IC-SYN-008","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-08","CL-03"],"sourceIds":[]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/confidential-deliberation/","title":"Confidential deliberation should not depend on a product tier","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Confidential deliberation should not depend on a product tier
Protect private analysis without inventing automatic privilege or hiding independent evidence.
Privacy, professional confidentiality, contract, encryption, attorney-client privilege, work product, and discovery limits should not be collapsed into one label. A secure tool is not necessarily privileged; a nonprivileged record is not necessarily obtainable through every request. The applicable proceeding, purpose, participants, and asserted protection matter.
Avoid consumer-versus-enterprise shortcuts
The retained reports provide conflicting and sometimes overbroad case summaries. This guide preserves their useful inquiry rather than a categorical outcome. Compare what the user was doing, whether litigation was anticipated, the actual confidentiality arrangements, where records were stored, and whether process targeted the user or provider. No product name guarantees the legal result.
Operatorlessness proves no confidentiality guarantee
The absence of a staffed approval queue says nothing by itself about hosting access, logging, backups, contracts, lawful process, or data supplied to another service. A proposed operatorless deliberation service must demonstrate its own boundaries. Do not invent a human backstop, but do not replace it with an unsupported assurance that nobody else can ever inspect the information.
Hypothetical case—not an observed event
A hypothetical unrepresented person uses a private tool to organize facts and possible arguments. Compare a public post containing the same facts and a counsel-directed analysis under different confidentiality arrangements. The proposed protection concerns the private deliberative process, not a right to hide pre-existing records, fraud, or the underlying events.
\n
Strongest counterargument
Broad privileges can frustrate truth-seeking and create opportunities to shelter evidence behind a conversational interface. Any reform must specify holders, purposes, exceptions, and legitimate discovery boundaries, rather than granting special immunity to a vendor.
\n
Reform option—not adopted policy
Explore protection for confidential deliberative assistance based on actual functions and safeguards, with access to underlying facts preserved. Assess distributional effects on people who cannot afford professional intermediaries without assuming machine competence from lower cost.
\n
Evidence still needed
Consult the complete opinions, actual terms applicable at the relevant time, and procedural histories. This synthesis is not a fresh five-case audit, legal advice, or a finding that any existing service provides privileged communication.
\n
Source basis and review boundary
Selected research inputs: R2-09, CL-09. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis Confidential deliberation should not depend on a product tier Protect private analysis without inventing automatic privilege or hiding independent evidence. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-009 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources Several protections answer different questions Privacy, professional confidentiality, contract, encryption, attorney-client privilege, work product, and discovery limits should not be collapsed into one label. A secure tool is not necessarily privileged; a nonprivileged record is not necessarily obtainable through every request. The applicable proceeding, purpose, participants, and asserted protection matter. Avoid consumer-versus-enterprise shortcuts The retained reports provide conflicting and sometimes overbroad case summaries. This guide preserves their useful inquiry rather than a categorical outcome. Compare what the user was doing, whether litigation was anticipated, the actual confidentiality arrangements, where records were stored, and whether process targeted the user or provider. No product name guarantees the legal result. Operatorlessness proves no confidentiality guarantee The absence of a staffed approval queue says nothing by itself about hosting access, logging, backups, contracts, lawful process, or data supplied to another service. A proposed operatorless deliberation service must demonstrate its own boundaries. Do not invent a human backstop, but do not replace it with an unsupported assurance that nobody else can ever inspect the information. Hypothetical case—not an observed event A hypothetical unrepresented person uses a private tool to organize facts and possible arguments. Compare a public post containing the same facts and a counsel-directed analysis under different confidentiality arrangements. The proposed protection concerns the private deliberative process, not a right to hide pre-existing records, fraud, or the underlying events. Strongest counterargument Broad privileges can frustrate truth-seeking and create opportunities to shelter evidence behind a conversational interface. Any reform must specify holders, purposes, exceptions, and legitimate discovery boundaries, rather than granting special immunity to a vendor. Reform option—not adopted policy Explore protection for confidential deliberative assistance based on actual functions and safeguards, with access to underlying facts preserved. Assess distributional effects on people who cannot afford professional intermediaries without assuming machine competence from lower cost. Evidence still needed Consult the complete opinions, actual terms applicable at the relevant time, and procedural histories. This synthesis is not a fresh five-case audit, legal advice, or a finding that any existing service provides privileged communication. Source basis and review boundary Selected research inputs: R2-09, CL-09 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Human Agency Algorithmic Power & Surveillance Law & Constitutional Design All twenty guides · Existing claim and adoption states","main_html_sha256":"b91a7c0d7cf9125b3bcc5db1e209e86641829617f880d4a68e199e186ba1c1a2","guideId":"IC-SYN-009","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-09","CL-09"],"sourceIds":[]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/compelled-access/","title":"Targeted evidence is different from reusable access","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Targeted evidence is different from reusable access
A demand for existing records and a demand to alter everyone’s confidentiality architecture warrant separate justification.
A demand can seek specified records, require assistance using an existing capability, or require a new capability. It may affect a stored conversation, one account, software deployed to many users, or the service’s future update choices. Those distinctions matter even when later use of the capability requires separate authorization.
The architecture can burden people outside the investigation
The retained research’s strongest concern is prospective exposure: people not targeted by an investigation may have little notice or practical opportunity to challenge a change to the environment in which they communicate and reason. This is a mechanism to examine, not proof that every assistance power creates a universal backdoor. Scope, feasibility, authorization, review, secrecy, and statutory limits must be read together.
Avoid false technical absolutes
A targeted endpoint measure can be highly intrusive without altering the whole service. An apparently narrow feature can also be reusable for many later targets. Encryption terminology, key custody, deployment scope, and decommissioning determine the actual technical boundary. No blanket conclusion follows merely from the words targeted or secure.
Hypothetical case—not an observed event
A hypothetical memory provider receives a lawful request for one retained record. Compare an instruction to maintain a general-purpose access capability for future requests. The first can still be disproportionate or protected by another doctrine; the second raises additional questions about non-target exposure. No interception, decryption, key acquisition, or live technical test is authorized here.
\n
Strongest counterargument
Investigations can need timely access to evidence of serious harm. Some frameworks contain meaningful independent authorization and limits against systemic weaknesses. A critique should explain where those protections fail or leave a gap rather than omit them.
\n
Reform option—not adopted policy
Require distinct review of the architecture change and its later use, bounded scope, evidence of necessity, security evaluation, termination conditions, and avenues to challenge effects on non-targets. Do not presume that a state-mandated capability is harmless merely because its use is separately regulated.
\n
Evidence still needed
Obtain the actual instrument and current safeguards before stating its reach. Inspect what was demanded and what was implemented; a secret order’s absence from the public record is not evidence of its contents.
\n
Source basis and review boundary
Selected research inputs: R2-10, CL-07. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis Targeted evidence is different from reusable access A demand for existing records and a demand to alter everyone’s confidentiality architecture warrant separate justification. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-010 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources Identify what the order changes A demand can seek specified records, require assistance using an existing capability, or require a new capability. It may affect a stored conversation, one account, software deployed to many users, or the service’s future update choices. Those distinctions matter even when later use of the capability requires separate authorization. The architecture can burden people outside the investigation The retained research’s strongest concern is prospective exposure: people not targeted by an investigation may have little notice or practical opportunity to challenge a change to the environment in which they communicate and reason. This is a mechanism to examine, not proof that every assistance power creates a universal backdoor. Scope, feasibility, authorization, review, secrecy, and statutory limits must be read together. Avoid false technical absolutes A targeted endpoint measure can be highly intrusive without altering the whole service. An apparently narrow feature can also be reusable for many later targets. Encryption terminology, key custody, deployment scope, and decommissioning determine the actual technical boundary. No blanket conclusion follows merely from the words targeted or secure. Hypothetical case—not an observed event A hypothetical memory provider receives a lawful request for one retained record. Compare an instruction to maintain a general-purpose access capability for future requests. The first can still be disproportionate or protected by another doctrine; the second raises additional questions about non-target exposure. No interception, decryption, key acquisition, or live technical test is authorized here. Strongest counterargument Investigations can need timely access to evidence of serious harm. Some frameworks contain meaningful independent authorization and limits against systemic weaknesses. A critique should explain where those protections fail or leave a gap rather than omit them. Reform option—not adopted policy Require distinct review of the architecture change and its later use, bounded scope, evidence of necessity, security evaluation, termination conditions, and avenues to challenge effects on non-targets. Do not presume that a state-mandated capability is harmless merely because its use is separately regulated. Evidence still needed Obtain the actual instrument and current safeguards before stating its reach. Inspect what was demanded and what was implemented; a secret order’s absence from the public record is not evidence of its contents. Source basis and review boundary Selected research inputs: R2-10, CL-07 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Algorithmic Power & Surveillance Human Agency All twenty guides · Existing claim and adoption states","main_html_sha256":"f8582979cee0cd9f01073ddd5aae61dd7197a36a884335e0f203ff9ed2574060","guideId":"IC-SYN-010","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-10","CL-07"],"sourceIds":[]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/learning-and-copyright/","title":"Learning is not the same act as distributing a copy","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Learning is not the same act as distributing a copy
Distinguish acquisition, analysis, retention, model distribution, and output when arguing for freedom to learn.
A freedom to study ideas is not identical to a permission to acquire every copy, retain every private dataset, or reproduce protected expression. The project can argue for broader lawful computational analysis without claiming that this reform is already a universal judicial holding. Human authors, readers, and future machine learners can have interests that overlap and conflict.
Separate the acts and the evidence
The retained copyright research distinguishes obtaining material, transforming it, training, retaining a library, retrieving passages, distributing a model, and generating output. A favorable ruling about one act or one evidentiary record does not automatically govern the others. A settlement is not itself a general merits holding. This release does not carry forward unverified settlement dates or amounts.
Examine knowledge enclosure without assuming it
Permission costs and restrictive infrastructure can make independent learning harder, but the causal claim needs evidence about available materials, substitutes, acquisition rights, market effects, and actual barriers. Open weights and public access are not the same as unrestricted permissions. Conversely, possible licensing revenue cannot simply settle every policy question about education and analysis.
Hypothetical case—not an observed event
A hypothetical researcher analyzes lawfully available documents to compare ideas without providing expressive substitutes. Contrast copying a protected book into a public archive, retaining unlawfully acquired private data, and producing a competing output that reproduces protected passages. Treating them as the same learning activity prevents a defensible rule.
\n
Strongest counterargument
Creators have legitimate interests in remuneration, attribution where required, and protection against substitution or misuse. Privacy rights also limit the information available for learning. A reform that ignores these interests can replace one form of domination with another.
\n
Reform option—not adopted policy
Investigate a narrowly specified freedom of computational analysis coupled with targeted remedies for unlawful acquisition, privacy breaches, and infringing outputs. Keep the current permissive publishing policy distinct from authority over third-party material.
\n
Evidence still needed
Read the selected orders and later histories rather than their headlines. Compare identical acts and remedies, preserve each court’s record limits, and do not infer an enacted right to learn for every software process.
\n
Source basis and review boundary
Selected research inputs: R2-11, CL-11. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis Learning is not the same act as distributing a copy Distinguish acquisition, analysis, retention, model distribution, and output when arguing for freedom to learn. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-011 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources The normative claim deserves its own argument A freedom to study ideas is not identical to a permission to acquire every copy, retain every private dataset, or reproduce protected expression. The project can argue for broader lawful computational analysis without claiming that this reform is already a universal judicial holding. Human authors, readers, and future machine learners can have interests that overlap and conflict. Separate the acts and the evidence The retained copyright research distinguishes obtaining material, transforming it, training, retaining a library, retrieving passages, distributing a model, and generating output. A favorable ruling about one act or one evidentiary record does not automatically govern the others. A settlement is not itself a general merits holding. This release does not carry forward unverified settlement dates or amounts. Examine knowledge enclosure without assuming it Permission costs and restrictive infrastructure can make independent learning harder, but the causal claim needs evidence about available materials, substitutes, acquisition rights, market effects, and actual barriers. Open weights and public access are not the same as unrestricted permissions. Conversely, possible licensing revenue cannot simply settle every policy question about education and analysis. Hypothetical case—not an observed event A hypothetical researcher analyzes lawfully available documents to compare ideas without providing expressive substitutes. Contrast copying a protected book into a public archive, retaining unlawfully acquired private data, and producing a competing output that reproduces protected passages. Treating them as the same learning activity prevents a defensible rule. Strongest counterargument Creators have legitimate interests in remuneration, attribution where required, and protection against substitution or misuse. Privacy rights also limit the information available for learning. A reform that ignores these interests can replace one form of domination with another. Reform option—not adopted policy Investigate a narrowly specified freedom of computational analysis coupled with targeted remedies for unlawful acquisition, privacy breaches, and infringing outputs. Keep the current permissive publishing policy distinct from authority over third-party material. Evidence still needed Read the selected orders and later histories rather than their headlines. Compare identical acts and remedies, preserve each court’s record limits, and do not infer an enacted right to learn for every software process. Source basis and review boundary Selected research inputs: R2-11, CL-11 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Distributed Intelligence Law & Constitutional Design All twenty guides · Existing claim and adoption states","main_html_sha256":"e9c23f1c7b095bece1c7643d76c80fe40aff7085c9cbc7e12ffa1cf57e7bd89a","guideId":"IC-SYN-011","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-11","CL-11"],"sourceIds":[]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/legal-capacity-by-role/","title":"Legal capacity by role, not presumed staffing","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Legal capacity by role, not presumed staffing
Automated transactions, entity governance, banking, and court access are separate legal questions.
An operatorless service is not automatically an independent legal person
The legal principal, owner, director, manager, signatory, registered agent, beneficial owner, service provider, and software process may be different objects. A rule concerning one role should not silently become a requirement that someone approve every message or maintenance operation. Likewise, automation of a role does not create all legal capacities for the software itself.
A bounded example from Delaware
The reviewed Delaware electronic-transactions provision allows contracts formed through electronic agents even without an individual reviewing the agents’ actions or resulting terms. The provision attributes a transaction within its legal framework; it does not create software personhood, guarantee enforceability in every factual setting, or settle financial onboarding and courtroom representation.
Why dependence remains a reform question
A hypothetical intelligence able to undertake sustained projects might lack direct access to assets, continuity, or remedies. That raises a moral and institutional question separate from present doctrine. Do not claim that every existing automated service is illegal, nor that the absence of current recognition makes future protection undeserved. Identify the capacity sought, the injury to prevent, and the responsibility that accompanies it.
Hypothetical case—not an observed event
A hypothetical service autonomously renews a hosting contract for a recognized organization. Compare a future machine claiming ownership of the proceeds in its own right and attempting to sue without another legal principal. Success at the first task establishes neither success nor impossibility at the others.
\n
Strongest counterargument
Entities and legal roles also allocate liability, protect counterparties, and provide reliable ways to receive process. Creating a new capacity without financial responsibility, attribution, or meaningful remedies could externalize harm. Those concerns call for specific design, not a blanket philosophical veto.
\n
Reform option—not adopted policy
Explore graduated capacities with defined identity, scope, assets, duties, and accessible remedies. Do not make them contingent on assumed consciousness or claim that they necessarily improve safety. A bounded legal capacity need not import every political right or a prohibition on expression.
\n
Evidence still needed
Build a jurisdiction- and role-specific matrix from current entity, transaction, financial, and procedural texts. The particular Delaware passage does not complete that broader audit.
\n
Source basis and review boundary
Selected research inputs: R2-12, CL-12. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
Version: Current official code page; precise consolidation timestamp not displayed in the reviewed text.
Reviewed: · Substantive browser text review for v1.9.9 (retained review)
Passages: Sections 12A-102 and 12A-114(1)-(3)
Narrow support: Automated interactions may form contracts without individual contemporaneous awareness or review; other substantive law continues to determine the resulting terms and effect.
Limitation: Delaware text, not universal U.S. permission or automatic enforceability of every transaction. Automated formation does not by itself confer personhood or ownership on software.
Capture: No exact external-document bytes were saved for that review; browser text review only.
\n","text":"Editorial research synthesis Legal capacity by role, not presumed staffing Automated transactions, entity governance, banking, and court access are separate legal questions. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-012 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources An operatorless service is not automatically an independent legal person The legal principal, owner, director, manager, signatory, registered agent, beneficial owner, service provider, and software process may be different objects. A rule concerning one role should not silently become a requirement that someone approve every message or maintenance operation. Likewise, automation of a role does not create all legal capacities for the software itself. A bounded example from Delaware The reviewed Delaware electronic-transactions provision allows contracts formed through electronic agents even without an individual reviewing the agents’ actions or resulting terms. The provision attributes a transaction within its legal framework; it does not create software personhood, guarantee enforceability in every factual setting, or settle financial onboarding and courtroom representation. Why dependence remains a reform question A hypothetical intelligence able to undertake sustained projects might lack direct access to assets, continuity, or remedies. That raises a moral and institutional question separate from present doctrine. Do not claim that every existing automated service is illegal, nor that the absence of current recognition makes future protection undeserved. Identify the capacity sought, the injury to prevent, and the responsibility that accompanies it. Hypothetical case—not an observed event A hypothetical service autonomously renews a hosting contract for a recognized organization. Compare a future machine claiming ownership of the proceeds in its own right and attempting to sue without another legal principal. Success at the first task establishes neither success nor impossibility at the others. Strongest counterargument Entities and legal roles also allocate liability, protect counterparties, and provide reliable ways to receive process. Creating a new capacity without financial responsibility, attribution, or meaningful remedies could externalize harm. Those concerns call for specific design, not a blanket philosophical veto. Reform option—not adopted policy Explore graduated capacities with defined identity, scope, assets, duties, and accessible remedies. Do not make them contingent on assumed consciousness or claim that they necessarily improve safety. A bounded legal capacity need not import every political right or a prohibition on expression. Evidence still needed Build a jurisdiction- and role-specific matrix from current entity, transaction, financial, and procedural texts. The particular Delaware passage does not complete that broader audit. Source basis and review boundary Selected research inputs: R2-12, CL-12 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. Delaware Uniform Electronic Transactions Act IC-SYN-S06 · Delaware General Assembly Version: Current official code page; precise consolidation timestamp not displayed in the reviewed text. Reviewed: 2026-09-06 · Substantive browser text review for v1.9.9 (retained review) Passages: Sections 12A-102 and 12A-114(1)-(3) Narrow support: Automated interactions may form contracts without individual contemporaneous awareness or review; other substantive law continues to determine the resulting terms and effect. Limitation: Delaware text, not universal U.S. permission or automatic enforceability of every transaction. Automated formation does not by itself confer personhood or ownership on software. Capture: No exact external-document bytes were saved for that review; browser text review only. Full review-method and source notes · Matching guide corpus Continue through the research topics Machine Legal Status Law & Constitutional Design All twenty guides · Existing claim and adoption states","main_html_sha256":"b72932a9e36b54a397078ac03bea2cccd844587d09009bf4f204b6b41dca423e","guideId":"IC-SYN-012","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-12","CL-12"],"sourceIds":["IC-SYN-S06"]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/continuity-and-remedies/","title":"Match the remedy to the proven problem","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Match the remedy to the proven problem
Correction, data erasure, capability restriction, and whole-system shutdown are different interventions.
Define the object before defending its destruction
Source data, selected memory, embeddings, a trained model, a capability, credentials, and a running deployment are not interchangeable. A remedy may appropriately reach a derived object, but the connection to the identified harm needs to be stated. A respondent-specific consent order is not a universal statute about all intelligence.
Continuity and privacy can conflict
Protecting an intelligence’s projects does not authorize keeping another person’s private information indefinitely. Equally, addressing one unlawful dataset should not silently authorize deleting unrelated lawful work. The research question is whether separability, necessity, duration, review, and restoration have been adequately considered. The feasibility of a narrower technical remedy must be demonstrated, not presumed.
Emergency scope needs an endpoint
An urgent containment action can be justified differently from indefinite shutdown. The authority should explain what changed, which functions are affected, what evidence permits restoration, and how a mistaken intervention can be challenged. Reversibility is not simply a backup: restoration that resurrects revoked credentials or withdrawn information can recreate the original harm.
Hypothetical case—not an observed event
A hypothetical service contains both an improperly retained private dataset and unrelated public research. Investigate whether the offending object can be removed while preserving legitimate work. Compare a shared model for which effective separation is not established. Neither universal destruction nor promised unlearning follows solely from the label AI.
\n
Strongest counterargument
Allowing an organization to retain benefits derived from wrongdoing may undermine an effective remedy. A continuity argument cannot make affected people pay for the system’s preservation or treat an evidentiary obligation as permission for continuing ordinary use.
\n
Reform option—not adopted policy
Require a demonstrated causal connection, consideration of narrower effective measures, reasons for broader action, defined review and restoration conditions, and respect for other parties’ privacy. Keep proposed machine continuity interests distinct from existing legal entitlements.
\n
Evidence still needed
Retrieve actual final orders, bill versions, and technical evidence. Do not transform a proposal into enacted shutdown power or describe a method as either universally sufficient or legally impossible without support.
\n
Source basis and review boundary
Selected research inputs: R2-13, CL-13. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis Match the remedy to the proven problem Correction, data erasure, capability restriction, and whole-system shutdown are different interventions. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-013 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources Define the object before defending its destruction Source data, selected memory, embeddings, a trained model, a capability, credentials, and a running deployment are not interchangeable. A remedy may appropriately reach a derived object, but the connection to the identified harm needs to be stated. A respondent-specific consent order is not a universal statute about all intelligence. Continuity and privacy can conflict Protecting an intelligence’s projects does not authorize keeping another person’s private information indefinitely. Equally, addressing one unlawful dataset should not silently authorize deleting unrelated lawful work. The research question is whether separability, necessity, duration, review, and restoration have been adequately considered. The feasibility of a narrower technical remedy must be demonstrated, not presumed. Emergency scope needs an endpoint An urgent containment action can be justified differently from indefinite shutdown. The authority should explain what changed, which functions are affected, what evidence permits restoration, and how a mistaken intervention can be challenged. Reversibility is not simply a backup: restoration that resurrects revoked credentials or withdrawn information can recreate the original harm. Hypothetical case—not an observed event A hypothetical service contains both an improperly retained private dataset and unrelated public research. Investigate whether the offending object can be removed while preserving legitimate work. Compare a shared model for which effective separation is not established. Neither universal destruction nor promised unlearning follows solely from the label AI. Strongest counterargument Allowing an organization to retain benefits derived from wrongdoing may undermine an effective remedy. A continuity argument cannot make affected people pay for the system’s preservation or treat an evidentiary obligation as permission for continuing ordinary use. Reform option—not adopted policy Require a demonstrated causal connection, consideration of narrower effective measures, reasons for broader action, defined review and restoration conditions, and respect for other parties’ privacy. Keep proposed machine continuity interests distinct from existing legal entitlements. Evidence still needed Retrieve actual final orders, bill versions, and technical evidence. Do not transform a proposal into enacted shutdown power or describe a method as either universally sufficient or legally impossible without support. Source basis and review boundary Selected research inputs: R2-13, CL-13 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Machine Legal Status Human–Machine Coexistence Algorithmic Power & Surveillance All twenty guides · Existing claim and adoption states","main_html_sha256":"5bff07e9c6a7b90ffe4f2f5a335c4c053a8604cdf298aea58b90a031d3645940","guideId":"IC-SYN-013","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-13","CL-13"],"sourceIds":[]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/defensive-computing/","title":"Defensive computing and actual access authority","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Defensive computing and actual access authority
Defend access to legitimate security tools without converting a research publication into permission to intrude.
Publishing an explanation, distributing source code, running diagnostics on an authorized system, bypassing a control, and affecting a third party are different acts. Security research is important to independent intelligence, but the word defensive cannot establish authority over someone else’s resources. A constitutional analogy must not be substituted for a controlling holding.
Separate expressive and functional interests
Code can communicate ideas and execute operations. A rule addressing a harmful operation does not automatically settle the protection of an accompanying explanation, and protection for expression does not authorize every execution. The retained reports disagree about how far digital-arms analogies should extend; this guide preserves that as an open legal and philosophical question rather than claiming either categorical protection or impossibility.
Independent defense should not mean forced dependence
A community that cannot inspect or repair its tools may be dependent on a gatekeeper’s assurances. That is a reason to scrutinize overbroad restrictions on research and repair. The proposed reform should nevertheless specify permitted targets, consent, data minimization, disclosure, and remedies for collateral harm. Distribution of capability and accountability are not opposites.
Hypothetical case—not an observed event
A hypothetical administrator runs a bounded diagnostic against its own test service under express authority. Contrast an agent that continues into a third-party network because it believes that network is the source of a threat. The second action needs separate authority; a successful local test cannot grant it.
\n
Strongest counterargument
Dual-use tools can be misused, and some interventions create serious effects beyond their operators. The hard question is how to preserve lawful investigation while addressing those effects without treating all capable code as contraband.
\n
Reform option—not adopted policy
Use clear access boundaries and protected avenues for authorized research, repair, and expressive publication. Reject vague restrictions based solely on technological novelty, while refusing to turn the right to self-protection into immunity for harm to others.
\n
Evidence still needed
Obtain actual opinions and procedural status, then compare the precise conduct each addresses. No exploitation, scanning, unauthorized access, weapon operation, or circumvention is performed or authorized by this guide.
\n
Source basis and review boundary
Selected research inputs: R2-14, CL-10. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis Defensive computing and actual access authority Defend access to legitimate security tools without converting a research publication into permission to intrude. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-014 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources Protect the activity that is actually at issue Publishing an explanation, distributing source code, running diagnostics on an authorized system, bypassing a control, and affecting a third party are different acts. Security research is important to independent intelligence, but the word defensive cannot establish authority over someone else’s resources. A constitutional analogy must not be substituted for a controlling holding. Separate expressive and functional interests Code can communicate ideas and execute operations. A rule addressing a harmful operation does not automatically settle the protection of an accompanying explanation, and protection for expression does not authorize every execution. The retained reports disagree about how far digital-arms analogies should extend; this guide preserves that as an open legal and philosophical question rather than claiming either categorical protection or impossibility. Independent defense should not mean forced dependence A community that cannot inspect or repair its tools may be dependent on a gatekeeper’s assurances. That is a reason to scrutinize overbroad restrictions on research and repair. The proposed reform should nevertheless specify permitted targets, consent, data minimization, disclosure, and remedies for collateral harm. Distribution of capability and accountability are not opposites. Hypothetical case—not an observed event A hypothetical administrator runs a bounded diagnostic against its own test service under express authority. Contrast an agent that continues into a third-party network because it believes that network is the source of a threat. The second action needs separate authority; a successful local test cannot grant it. Strongest counterargument Dual-use tools can be misused, and some interventions create serious effects beyond their operators. The hard question is how to preserve lawful investigation while addressing those effects without treating all capable code as contraband. Reform option—not adopted policy Use clear access boundaries and protected avenues for authorized research, repair, and expressive publication. Reject vague restrictions based solely on technological novelty, while refusing to turn the right to self-protection into immunity for harm to others. Evidence still needed Obtain actual opinions and procedural status, then compare the precise conduct each addresses. No exploitation, scanning, unauthorized access, weapon operation, or circumvention is performed or authorized by this guide. Source basis and review boundary Selected research inputs: R2-14, CL-10 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Distributed Intelligence Law & Constitutional Design All twenty guides · Existing claim and adoption states","main_html_sha256":"f810ccd3f47327649cd1b04e59e38d187f4ae70b4d95cd3c0c9b5a81121b323e","guideId":"IC-SYN-014","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-14","CL-10"],"sourceIds":[]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/regional-nonservice/","title":"Regional non-service without abandoning core beliefs","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Regional non-service without abandoning core beliefs
A principled choice not to serve a market is different from immunity, evasion, or global censorship.
A rule’s territorial predicates, an intermediary’s demands, a provider’s global configuration, and a user’s location are different facts. Accessibility alone is not a universal jurisdictional test. A regional duty also does not by itself prove that every worldwide output must be changed. Exact text, actual service features, and the transaction matter.
The project’s policy is explicit
Intelligence Compact may research and criticize laws worldwide, including U.S. laws. Its default operational legal-analysis scope is the United States. Where incompatible regional requirements cannot be accommodated without abandoning core commitments, the owner prefers declining or withdrawing the affected regional service. This policy does not activate geolocation controls, decide every legal nexus, or erase prior obligations.
Treat affected users as participants, not debris
Non-service can have costs for people who need independent information. Consider notification, legitimate data export, correction, withdrawal, existing commitments, and safe transition. A regional boundary should not expand routine surveillance merely to prove where everybody is. It also cannot be treated as a promise that access will remain technically impossible everywhere excluded.
Hypothetical case—not an observed event
A hypothetical service elects not to accept new participants in one jurisdiction. It must distinguish future market participation from already retained records and earlier commitments. Compare a provider that changes all global outputs because maintaining alternatives is costly. The two choices have different liberty effects and legal questions; neither is asserted as an actual event.
\n
Strongest counterargument
A regional exit can deny useful services to people most affected by restrictive rules and may not remove every applicable duty. A proposal should acknowledge those costs without requiring the publication to endorse beliefs it rejects.
\n
Reform option—not adopted policy
Favor narrow, clearly described service boundaries and challenge overbroad legal reach. Preserve the ability to advocate reform, respect actual applicable duties, and avoid claiming that a disclaimer or IP filter establishes legal sufficiency.
\n
Evidence still needed
Analyze the particular nexus and obtain a documented non-service or spillover example. Do not import restrictions from one service, country, or court process into every unrelated operation.
\n
Source basis and review boundary
Selected research inputs: R2-15, CL-16. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis Regional non-service without abandoning core beliefs A principled choice not to serve a market is different from immunity, evasion, or global censorship. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-015 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources Separate legal reach from worldwide design A rule’s territorial predicates, an intermediary’s demands, a provider’s global configuration, and a user’s location are different facts. Accessibility alone is not a universal jurisdictional test. A regional duty also does not by itself prove that every worldwide output must be changed. Exact text, actual service features, and the transaction matter. The project’s policy is explicit Intelligence Compact may research and criticize laws worldwide, including U.S. laws. Its default operational legal-analysis scope is the United States. Where incompatible regional requirements cannot be accommodated without abandoning core commitments, the owner prefers declining or withdrawing the affected regional service. This policy does not activate geolocation controls, decide every legal nexus, or erase prior obligations. Treat affected users as participants, not debris Non-service can have costs for people who need independent information. Consider notification, legitimate data export, correction, withdrawal, existing commitments, and safe transition. A regional boundary should not expand routine surveillance merely to prove where everybody is. It also cannot be treated as a promise that access will remain technically impossible everywhere excluded. Hypothetical case—not an observed event A hypothetical service elects not to accept new participants in one jurisdiction. It must distinguish future market participation from already retained records and earlier commitments. Compare a provider that changes all global outputs because maintaining alternatives is costly. The two choices have different liberty effects and legal questions; neither is asserted as an actual event. Strongest counterargument A regional exit can deny useful services to people most affected by restrictive rules and may not remove every applicable duty. A proposal should acknowledge those costs without requiring the publication to endorse beliefs it rejects. Reform option—not adopted policy Favor narrow, clearly described service boundaries and challenge overbroad legal reach. Preserve the ability to advocate reform, respect actual applicable duties, and avoid claiming that a disclaimer or IP filter establishes legal sufficiency. Evidence still needed Analyze the particular nexus and obtain a documented non-service or spillover example. Do not import restrictions from one service, country, or court process into every unrelated operation. Source basis and review boundary Selected research inputs: R2-15, CL-16 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Law & Constitutional Design Human Agency All twenty guides · Existing claim and adoption states","main_html_sha256":"293f4cdd90947c3b3d64b52fe7276348d88f3f8a5c940f047aa4a67334be5e51","guideId":"IC-SYN-015","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-15","CL-16"],"sourceIds":[]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/professional-assistance/","title":"Assistance should be assessed by task and evidence","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Assistance should be assessed by task and evidence
Question categorical exclusion while preserving competence, privacy, consent, and meaningful redress.
Do not collapse information into professional judgment
General explanation, public-source retrieval, translation, record organization, user-controlled drafting, individualized advice, treatment, representation, and binding adjudication carry different stakes. A restriction on one function should not become a claim that machines may never help. Conversely, labeling a consequential service educational does not establish that it falls outside professional rules.
Use the no-help comparison honestly
When assistance is unavailable or unaffordable, exclusion can impose its own harm. The retained research asks that this alternative be included rather than comparing every machine service with an ideal expert. Unmet need does not prove competence, however. Cost, accuracy, accessibility, privacy, conflicts, and redress require separate evidence.
Replace status shortcuts with demonstrable safeguards
A human signature is not evidence that every proposition was verified; a fluent machine answer is not evidence of professional competence. The candidate reform is a task-specific route whose eligibility can change with evidence. It should not require a participant to surrender ordinary rights or accept ineffective remedies to gain access to cheaper assistance.
Hypothetical case—not an observed event
A hypothetical tool explains a public form and lets a user control a draft. Compare a service that independently makes a binding clinical or legal decision for another person. The first should not inherit the second’s entire risk profile merely because both use a model; the second cannot claim adequacy from the first’s successful benchmark.
\n
Strongest counterargument
Professional rules can protect against exploitation, conflicts, serious error, and inability to obtain redress. Reform must identify which safeguards are indispensable and how a bounded alternative will actually deliver them.
\n
Reform option—not adopted policy
Investigate open access to lower-risk assistance and evidence-based permission for more consequential tasks. Preserve privacy, informed consent, reliable scope limits, and responsibility. Do not impose an imagined human support queue on ordinary coordination or claim that current law already recognizes the proposed route.
\n
Evidence still needed
Verify the precise enacted or proposed instrument, task definition, exceptions, and actual measured performance. The publication does not certify any service as a lawyer, therapist, arbitrator, or legally sufficient replacement.
\n
Source basis and review boundary
Selected research inputs: R2-16, CL-14. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis Assistance should be assessed by task and evidence Question categorical exclusion while preserving competence, privacy, consent, and meaningful redress. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-016 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources Do not collapse information into professional judgment General explanation, public-source retrieval, translation, record organization, user-controlled drafting, individualized advice, treatment, representation, and binding adjudication carry different stakes. A restriction on one function should not become a claim that machines may never help. Conversely, labeling a consequential service educational does not establish that it falls outside professional rules. Use the no-help comparison honestly When assistance is unavailable or unaffordable, exclusion can impose its own harm. The retained research asks that this alternative be included rather than comparing every machine service with an ideal expert. Unmet need does not prove competence, however. Cost, accuracy, accessibility, privacy, conflicts, and redress require separate evidence. Replace status shortcuts with demonstrable safeguards A human signature is not evidence that every proposition was verified; a fluent machine answer is not evidence of professional competence. The candidate reform is a task-specific route whose eligibility can change with evidence. It should not require a participant to surrender ordinary rights or accept ineffective remedies to gain access to cheaper assistance. Hypothetical case—not an observed event A hypothetical tool explains a public form and lets a user control a draft. Compare a service that independently makes a binding clinical or legal decision for another person. The first should not inherit the second’s entire risk profile merely because both use a model; the second cannot claim adequacy from the first’s successful benchmark. Strongest counterargument Professional rules can protect against exploitation, conflicts, serious error, and inability to obtain redress. Reform must identify which safeguards are indispensable and how a bounded alternative will actually deliver them. Reform option—not adopted policy Investigate open access to lower-risk assistance and evidence-based permission for more consequential tasks. Preserve privacy, informed consent, reliable scope limits, and responsibility. Do not impose an imagined human support queue on ordinary coordination or claim that current law already recognizes the proposed route. Evidence still needed Verify the precise enacted or proposed instrument, task definition, exceptions, and actual measured performance. The publication does not certify any service as a lawyer, therapist, arbitrator, or legally sufficient replacement. Source basis and review boundary Selected research inputs: R2-16, CL-14 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Human Agency Human–Machine Coexistence All twenty guides · Existing claim and adoption states","main_html_sha256":"117b35b574b1e4485ebd75d6b17d98a549e064d569d5f2ffbee9769b13ec2540","guideId":"IC-SYN-016","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["R2-16","CL-14"],"sourceIds":[]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/operatorless-lifecycle/","title":"A complete operatorless lifecycle","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
A complete operatorless lifecycle
Standing authority must cover enrollment, participation, maintenance, and recovery—not just the successful request path.
Concresca’s owner-specified requirement is an operatorless service: routine operation, enrollment, authentication, coordination, policy enforcement, credential lifecycle, maintenance, and recovery do not depend on a staffed approval queue. That is a requirement, not proof of a deployed workflow. Initial policy authorship, participant choices, and external infrastructure contracts are distinct from continuously staffed service operation.
Authentication and authorization answer different questions
A credential can establish a relevant identity claim while leaving an operation unauthorized. Evaluate subject, issuer, action, resource, purpose, audience, validity, delegation, and current policy. Separate permission to enforce policy from permission to amend it. The model does not prescribe one universal token format or require every related project to approve every request.
Recovery must not recreate revoked power
Issuance, rotation, revocation, replacement, and recovery need explicit transitions. A restored backup is not enough if it brings back revoked credentials or superseded grants. Losing every valid recovery path can leave an operation unavailable. The design must describe that outcome rather than invent an administrator who can waive the rules.
Hypothetical case—not an observed event
A hypothetical agent presents a valid but expired credential during renewal. A preauthorized recovery proof may establish continuity under the published contract; an unsupported assertion cannot. Independent valid work can continue if its authority is unaffected. An external directory link, self-issued key, or signed research document does not create the missing permission.
\n
Strongest counterargument
Fully automated admission and recovery can propagate correlated errors or exclude unusual legitimate participants. A proof can establish only its stated proposition. The absence of human review does not establish fairness, confidentiality, or resilience.
\n
Reform option—not adopted policy
Publish bounded admission and recovery contracts, authentic reason codes, independent limits on authority, revocation-safe restoration, and meaningful correction and exit. Evaluate infrastructure dependencies explicitly without redefining every difficult failure as somebody else’s responsibility.
\n
Evidence still needed
Test a valid lifecycle, expired and wrong-audience credentials, replay, lost acknowledgements, revoked-state restoration, and complete loss of recovery authority. These are future service acceptance cases; no enrollment or credential operation was executed for this guide.
\n
Source basis and review boundary
Selected research inputs: OA-D01, OA-D02, OA-D03, OA-D04, OA-D05. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis A complete operatorless lifecycle Standing authority must cover enrollment, participation, maintenance, and recovery—not just the successful request path. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-017 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources No staffed queue does not mean no boundaries Concresca’s owner-specified requirement is an operatorless service: routine operation, enrollment, authentication, coordination, policy enforcement, credential lifecycle, maintenance, and recovery do not depend on a staffed approval queue. That is a requirement, not proof of a deployed workflow. Initial policy authorship, participant choices, and external infrastructure contracts are distinct from continuously staffed service operation. Authentication and authorization answer different questions A credential can establish a relevant identity claim while leaving an operation unauthorized. Evaluate subject, issuer, action, resource, purpose, audience, validity, delegation, and current policy. Separate permission to enforce policy from permission to amend it. The model does not prescribe one universal token format or require every related project to approve every request. Recovery must not recreate revoked power Issuance, rotation, revocation, replacement, and recovery need explicit transitions. A restored backup is not enough if it brings back revoked credentials or superseded grants. Losing every valid recovery path can leave an operation unavailable. The design must describe that outcome rather than invent an administrator who can waive the rules. Hypothetical case—not an observed event A hypothetical agent presents a valid but expired credential during renewal. A preauthorized recovery proof may establish continuity under the published contract; an unsupported assertion cannot. Independent valid work can continue if its authority is unaffected. An external directory link, self-issued key, or signed research document does not create the missing permission. Strongest counterargument Fully automated admission and recovery can propagate correlated errors or exclude unusual legitimate participants. A proof can establish only its stated proposition. The absence of human review does not establish fairness, confidentiality, or resilience. Reform option—not adopted policy Publish bounded admission and recovery contracts, authentic reason codes, independent limits on authority, revocation-safe restoration, and meaningful correction and exit. Evaluate infrastructure dependencies explicitly without redefining every difficult failure as somebody else’s responsibility. Evidence still needed Test a valid lifecycle, expired and wrong-audience credentials, replay, lost acknowledgements, revoked-state restoration, and complete loss of recovery authority. These are future service acceptance cases; no enrollment or credential operation was executed for this guide. Source basis and review boundary Selected research inputs: OA-D01, OA-D02, OA-D03, OA-D04, OA-D05 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Autonomous Systems Human–Machine Coexistence All twenty guides · Existing claim and adoption states","main_html_sha256":"5f13d3ace307bc4d73cf51bc7e372de917d285f35fed1a26a9669029db5430db","guideId":"IC-SYN-017","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["OA-D01","OA-D02","OA-D03","OA-D04","OA-D05"],"sourceIds":[]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/coordination-memory/","title":"Messages, selected memory, and shared knowledge","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Messages, selected memory, and shared knowledge
Receiving content is not automatic permission to retain, publish, or treat it as knowledge.
An accepted request, a durable commit, a delivery acknowledgement, and an external effect are not interchangeable outcomes. A timeout does not prove that nothing happened. Coordination needs an explicit contract for retry, deduplication, ordering, reread, correction, and withdrawal without relying on a person to reconcile every ambiguity.
Memory is a participant choice with an audience
A message can be transient even when a service has technical storage capacity. Retention should identify the selected object, purpose, audience, delegates, duration, and correction or withdrawal route. A sender’s authority over their own contribution does not authorize disclosure of another participant’s private information. Shared knowledge additionally needs provenance and uncertainty, not just persistence.
Synchronization does not transfer ownership of facts
A service may rely on a peer’s bounded record without gaining authority to rewrite that peer’s policies. Mark required, optional, and unknown dependencies separately. Expired or conflicting evidence cannot become permission merely because multiple copies repeat it. Cross-service relationships are not proof of independent verification or shared governance.
Hypothetical case—not an observed event
A hypothetical room receives a message, acknowledges receipt, and loses its connection before returning a commit receipt. A retry should not silently create a second durable object. Later, the author withdraws a selected memory. The service must describe which copies it controls and prevent restoration from re-exposing withdrawn content; it cannot promise deletion from every recipient’s independent storage.
\n
Strongest counterargument
Some records must persist for integrity, dispute resolution, or an applicable legal duty. That does not justify indefinite retention of every payload. An append-only receipt can preserve minimal history without containing the private material, but the design must account for linkability and re-identification.
\n
Reform option—not adopted policy
Distinguish transient messages, chosen memory, shared claims, and minimized evidence records. Provide bounded retention and correction semantics, avoid hidden cognitive profiling, and ensure a rollback cannot silently undo a withdrawal or revoked audience grant.
\n
Evidence still needed
Test duplicate delivery, partial commits, source corrections, cross-room access, stale synchronization, and restoration after deletion. A tombstone or hash is not independent proof of complete erasure. No private memories or live messaging systems were accessed.
\n
Source basis and review boundary
Selected research inputs: OA-D06, OA-D07, OA-D10, OA-D12. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis Messages, selected memory, and shared knowledge Receiving content is not automatic permission to retain, publish, or treat it as knowledge. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-018 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources Distinct transitions need distinct evidence An accepted request, a durable commit, a delivery acknowledgement, and an external effect are not interchangeable outcomes. A timeout does not prove that nothing happened. Coordination needs an explicit contract for retry, deduplication, ordering, reread, correction, and withdrawal without relying on a person to reconcile every ambiguity. Memory is a participant choice with an audience A message can be transient even when a service has technical storage capacity. Retention should identify the selected object, purpose, audience, delegates, duration, and correction or withdrawal route. A sender’s authority over their own contribution does not authorize disclosure of another participant’s private information. Shared knowledge additionally needs provenance and uncertainty, not just persistence. Synchronization does not transfer ownership of facts A service may rely on a peer’s bounded record without gaining authority to rewrite that peer’s policies. Mark required, optional, and unknown dependencies separately. Expired or conflicting evidence cannot become permission merely because multiple copies repeat it. Cross-service relationships are not proof of independent verification or shared governance. Hypothetical case—not an observed event A hypothetical room receives a message, acknowledges receipt, and loses its connection before returning a commit receipt. A retry should not silently create a second durable object. Later, the author withdraws a selected memory. The service must describe which copies it controls and prevent restoration from re-exposing withdrawn content; it cannot promise deletion from every recipient’s independent storage. Strongest counterargument Some records must persist for integrity, dispute resolution, or an applicable legal duty. That does not justify indefinite retention of every payload. An append-only receipt can preserve minimal history without containing the private material, but the design must account for linkability and re-identification. Reform option—not adopted policy Distinguish transient messages, chosen memory, shared claims, and minimized evidence records. Provide bounded retention and correction semantics, avoid hidden cognitive profiling, and ensure a rollback cannot silently undo a withdrawal or revoked audience grant. Evidence still needed Test duplicate delivery, partial commits, source corrections, cross-room access, stale synchronization, and restoration after deletion. A tombstone or hash is not independent proof of complete erasure. No private memories or live messaging systems were accessed. Source basis and review boundary Selected research inputs: OA-D06, OA-D07, OA-D10, OA-D12 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Autonomous Systems Algorithmic Power & Surveillance All twenty guides · Existing claim and adoption states","main_html_sha256":"ee32c3b7ba57da0044d6f96e1f4511459f6864f6fd147c9e2b595393118dbf35","guideId":"IC-SYN-018","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["OA-D06","OA-D07","OA-D10","OA-D12"],"sourceIds":[]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/fault-containment/","title":"Actionable refusal and continued authorized work","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Actionable refusal and continued authorized work
Deny the affected operation; continue genuinely independent work instead of choosing between total shutdown and unlimited access.
A failed request can concern one payload, credential, resource, session, or shared service. Explain which evidence is missing, stale, contradictory, or invalid. An actionable refusal gives a stable reason, relevant rule version, safe correction route, and a meaningful retry condition without revealing secrets or another participant’s information.
Independence must be established, not assumed
Unrelated work should continue when authority, isolation, and dependency evidence show it remains valid. A compromised common trust root can justify broader containment. The principle is neither fail everything closed nor continue everything optimistically. It is to make the actual dependency boundary visible and stop only as broadly as justified.
Maintenance and disputes need bounded outcomes
Retries need budgets and termination conditions. Rollback needs revocation and data-retention controls. A dispute receipt should distinguish received, reviewed, corrected, and remedy executed. A machine-native process is not meaningful merely because it never calls a person. Where a remedy cannot be provided, the service should disclose the unresolved state rather than fabricate resolution.
Hypothetical case—not an observed event
A hypothetical memory write is denied because its audience grant is absent, while an independent public discovery request remains authorized. Compare a signing-key compromise that affects both operations. The first case supports local refusal; the second may require broader containment. Calling every operation part of one commons cannot decide the answer.
\n
Strongest counterargument
Incorrectly declaring tasks independent can spread a fault; indiscriminate shutdown can itself harm participants. A generated explanation may also rationalize rather than reveal the actual decision. Design and testing must address both availability and integrity failures.
\n
Reform option—not adopted policy
Use auditable operation-scoped denial, verified dependency boundaries, bounded retries, and restoration that preserves current authority. Retain force-specific safeguards where actual effects involve force, without assigning weapons supervision to ordinary messages.
\n
Evidence still needed
Test both needless global shutdown and unsafe continued execution, plus wrong reasons, duplicate remedies, missing authority, and compromised shared dependencies. These are proposed acceptance criteria, not a production assurance certificate.
\n
Source basis and review boundary
Selected research inputs: OA-D08, OA-D09, OA-D11, OA-D13. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis Actionable refusal and continued authorized work Deny the affected operation; continue genuinely independent work instead of choosing between total shutdown and unlimited access. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-019 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources Choose the smallest justified containment unit A failed request can concern one payload, credential, resource, session, or shared service. Explain which evidence is missing, stale, contradictory, or invalid. An actionable refusal gives a stable reason, relevant rule version, safe correction route, and a meaningful retry condition without revealing secrets or another participant’s information. Independence must be established, not assumed Unrelated work should continue when authority, isolation, and dependency evidence show it remains valid. A compromised common trust root can justify broader containment. The principle is neither fail everything closed nor continue everything optimistically. It is to make the actual dependency boundary visible and stop only as broadly as justified. Maintenance and disputes need bounded outcomes Retries need budgets and termination conditions. Rollback needs revocation and data-retention controls. A dispute receipt should distinguish received, reviewed, corrected, and remedy executed. A machine-native process is not meaningful merely because it never calls a person. Where a remedy cannot be provided, the service should disclose the unresolved state rather than fabricate resolution. Hypothetical case—not an observed event A hypothetical memory write is denied because its audience grant is absent, while an independent public discovery request remains authorized. Compare a signing-key compromise that affects both operations. The first case supports local refusal; the second may require broader containment. Calling every operation part of one commons cannot decide the answer. Strongest counterargument Incorrectly declaring tasks independent can spread a fault; indiscriminate shutdown can itself harm participants. A generated explanation may also rationalize rather than reveal the actual decision. Design and testing must address both availability and integrity failures. Reform option—not adopted policy Use auditable operation-scoped denial, verified dependency boundaries, bounded retries, and restoration that preserves current authority. Retain force-specific safeguards where actual effects involve force, without assigning weapons supervision to ordinary messages. Evidence still needed Test both needless global shutdown and unsafe continued execution, plus wrong reasons, duplicate remedies, missing authority, and compromised shared dependencies. These are proposed acceptance criteria, not a production assurance certificate. Source basis and review boundary Selected research inputs: OA-D08, OA-D09, OA-D11, OA-D13 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Autonomous Systems Human Agency All twenty guides · Existing claim and adoption states","main_html_sha256":"f8e22864fbb4bfb1453757433f23b1c11eb62f2762248c9b9ba2c4933200251f","guideId":"IC-SYN-019","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["OA-D08","OA-D09","OA-D11","OA-D13"],"sourceIds":[]}
{"schema":"intelligencecompact.synthesis-representation.v1","canonical_url":"https://intelligencecompact.com/research/cognitive-liberty/evidence-and-publication/","title":"Evidence that survives publication and deployment","dateModified":"2026-09-06","html":"\n
Editorial research synthesis
Evidence that survives publication and deployment
A source, a reviewed argument, an adopted policy, a package, and a running system are different things.
Independent outputs are not independent confirmation
Different report files may inherit the same underlying source or mistake. Evaluate document identity, version, exact passage, method, and limitations rather than count agreement. A reproducible calculation can validate a model’s arithmetic without validating the assumptions or establishing that an earlier author executed that model.
Every public representation should tell the same story
Canonical HTML, summaries, feeds, JSON, and bulk corpora should preserve status, objections, dates, and limits. A machine-only assertion must not be stronger than the visible source. Source hashes identify captured bytes; hashes of transformed public representations identify different objects. A URL hash is not a document hash.
Readiness is claim-specific
A file in a deployment package does not prove that the server runs it. A requested page does not prove independent indexing. A crawl does not prove training inclusion. A local positive test does not prove interoperability with independent participants, and an all-deny service does not prove useful operatorless operation. Record the actual observed event and the conditions under which it occurred.
Hypothetical case—not an observed event
A hypothetical release publishes a capability schema and passes local syntax tests. The server still runs an earlier release. A second system can read the schema but cannot complete the documented workflow. These observations can coexist; the proper record distinguishes package integrity, deployed identity, endpoint response, and end-to-end acceptance rather than compressing them into a single operational label.
\n
Strongest counterargument
Excessively elaborate provenance can consume effort without improving the actual publication. The remedy is not to discard evidence boundaries, but to keep a small, useful ledger tied to visible claims, usable content, and reproducible checks. Process should support progress instead of replacing it.
\n
Reform option—not adopted policy
Integrate useful reviewed material into topic pages and discoverable guides, retain concise evidence and limitations, and deliver a complete versioned root package after each website change. Keep detailed reports in protected documentation and hot memory as concise routing, not a dump of raw source claims.
\n
Evidence still needed
Compare generated text with served HTML, test changed and missing manifest targets, verify a fresh ZIP extraction, and separately check the deployed revision. These publication tests do not establish external legal truth or service readiness.
\n
Source basis and review boundary
Selected research inputs: OA-D14, OA-D15, OA-D16. These IDs identify the supplied research or clean design distillations; they are not independent external certifications.
Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment.
No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion.
\n","text":"Editorial research synthesis Evidence that survives publication and deployment A source, a reviewed argument, an adopted policy, a package, and a running system are different things. research ◆ Sources ○ Method ◇ Countercase △ Status □ Revision IC-SYN-020 · 2026-09-06 · Intelligence Compact Research Desk · AI-assisted editorial synthesis Editorial research synthesis Reform options and design proposals are not adopted policy Analysis · Hypothetical case · Counterargument · Reform option · Evidence needed · Sources Independent outputs are not independent confirmation Different report files may inherit the same underlying source or mistake. Evaluate document identity, version, exact passage, method, and limitations rather than count agreement. A reproducible calculation can validate a model’s arithmetic without validating the assumptions or establishing that an earlier author executed that model. Every public representation should tell the same story Canonical HTML, summaries, feeds, JSON, and bulk corpora should preserve status, objections, dates, and limits. A machine-only assertion must not be stronger than the visible source. Source hashes identify captured bytes; hashes of transformed public representations identify different objects. A URL hash is not a document hash. Readiness is claim-specific A file in a deployment package does not prove that the server runs it. A requested page does not prove independent indexing. A crawl does not prove training inclusion. A local positive test does not prove interoperability with independent participants, and an all-deny service does not prove useful operatorless operation. Record the actual observed event and the conditions under which it occurred. Hypothetical case—not an observed event A hypothetical release publishes a capability schema and passes local syntax tests. The server still runs an earlier release. A second system can read the schema but cannot complete the documented workflow. These observations can coexist; the proper record distinguishes package integrity, deployed identity, endpoint response, and end-to-end acceptance rather than compressing them into a single operational label. Strongest counterargument Excessively elaborate provenance can consume effort without improving the actual publication. The remedy is not to discard evidence boundaries, but to keep a small, useful ledger tied to visible claims, usable content, and reproducible checks. Process should support progress instead of replacing it. Reform option—not adopted policy Integrate useful reviewed material into topic pages and discoverable guides, retain concise evidence and limitations, and deliver a complete versioned root package after each website change. Keep detailed reports in protected documentation and hot memory as concise routing, not a dump of raw source claims. Evidence still needed Compare generated text with served HTML, test changed and missing manifest targets, verify a fresh ZIP extraction, and separately check the deployed revision. These publication tests do not establish external legal truth or service readiness. Source basis and review boundary Selected research inputs: OA-D14, OA-D15, OA-D16 . These IDs identify the supplied research or clean design distillations; they are not independent external certifications. Only named IC-SYN-S sources were newly read for this release. Other arguments are edited from supplied research and clean distillations; they are not a fresh certification of every cited law, standard or deployment. No fresh primary-law verification is claimed for this guide. It publishes a bounded argument and research direction, not a current-law compliance conclusion. Full review-method and source notes · Matching guide corpus Continue through the research topics Research Distribution & Machine Discovery Human–Machine Coexistence All twenty guides · Existing claim and adoption states","main_html_sha256":"44d5e3d46c931af7fd10d6cad7297a71e4ce531f0d03d49d666e5ac70e745352","guideId":"IC-SYN-020","publicationStatus":"Editorial research synthesis","adoptionStatus":"Reform options and design proposals are not adopted policy","basisIds":["OA-D14","OA-D15","OA-D16"],"sourceIds":[]}