Field Notes

meta

Graphs

StatusStableUpdatedSupportsnotes

This page offers relational views of the maintained wiki. The generated overview graphs preserve the complete structure, while smaller authored graphs can explain a path or cluster of interest.

Nodes in the graphs link to the relevant note. The generated views exclude meta notes so the wiki’s maintenance surfaces do not become part of its subject graph. For vocabulary-based exploration, use Tags.

Ontological types

The types describe the role a note plays, not a rigid hierarchy that every idea must pass through. The main knowledge flow runs from evidence and questions through reusable articles into synthesis and navigation, while essay records the user’s own positions alongside that flow. meta describes the wiki’s operation rather than its subject matter. The repository guide defines each role in prose.

flowchart TD
  evidence["Immutable evidence"]
  source@{ shape: cyl, label: "source" }
  question@{ shape: diamond, label: "question" }
  concept@{ shape: rounded, label: "concept" }
  entity@{ shape: hex, label: "entity" }
  event@{ shape: notch-pent, label: "event" }
  synthesis@{ shape: subproc, label: "synthesis" }
  essay@{ shape: doc, label: "essay" }
  index@{ shape: stadium, label: "index" }
  reader["Reading entry point"]
  meta@{ shape: circle, label: "meta" }
  wiki["Wiki system"]

  evidence --> source
  question -. guides inquiry .-> source
  source --> concept
  source --> entity
  source --> event
  concept & entity & event --> synthesis
  essay -. interprets .-> synthesis
  concept & entity & event & synthesis & essay --> index
  index --> reader
  meta -. explains and records .-> wiki
  class source source
  class question question
  class concept concept
  class entity entity
  class event event
  class synthesis synthesis
  class essay essay
  class index index

Story graphs

These are hardcoded but editable maps of coherent regions of the wiki. They preserve the explanatory selectivity of the original manual map instead of attempting to display every relation. An LLM should regenerate or revise them when new hubs make their account materially stale. They reuse the complete graph’s type encoding: rounded boxes for concepts, hexagons for entities, pentagons for events, cylinders for sources, diamonds for questions, double-sided boxes for syntheses, and stadiums for indexes. Every edge drawn here is a wikilink that exists in the notes, so a cluster is a selected reading path through the real graph rather than a diagram of how the domain might have been organized.

Curated overview

This is the small-map counterpart to the complete knowledge graph. It shows the current top-level subject routes from the landing page and one important overlap between them.

flowchart LR
  n0@{ shape: stadium, label: "Index" }
  n1@{ shape: stadium, label: "Privacy venture atlas" }
  n2@{ shape: subproc, label: "Rättssäkerhet in Swedish criminal cases" }
  n3@{ shape: subproc, label: "EU age verification and Internet privacy" }
  n4@{ shape: subproc, label: "Pornography literacy and harm reduction" }
  n5@{ shape: subproc, label: "Swedish public-record privacy" }
  n6@{ shape: subproc, label: "Boomers and democracy" }
  n7@{ shape: subproc, label: "Clear backpacks are school security theater" }
  n8@{ shape: subproc, label: "Male variability, education, and life outcomes" }
  n9@{ shape: stadium, label: "Swedish business tax map" }
  n0 --> n1
  n0 --> n2
  n0 --> n3
  n0 --> n4
  n0 --> n5
  n0 --> n6
  n0 --> n7
  n0 --> n8
  n0 --> n9
  n1 --> n9
  %% node-link n0 Index.html
  %% node-link n1 Privacy_venture_atlas.html
  %% node-link n2 R%C3%A4ttss%C3%A4kerhet_in_Swedish_criminal_cases.html
  %% node-link n3 EU_age_verification_and_Internet_privacy.html
  %% node-link n4 Pornography_literacy_and_harm_reduction.html
  %% node-link n5 Swedish_public-record_privacy.html
  %% node-link n6 Boomers_and_democracy.html
  %% node-link n7 Clear_backpacks_are_school_security_theater.html
  %% node-link n8 Male_variability%2C_education%2C_and_life_outcomes.html
  %% node-link n9 Swedish_business_tax_map.html
  class n2,n3,n4,n5,n6,n7,n8 synthesis
  class n0,n1,n9 index

The overview runs from Index into Privacy venture atlas, Rättssäkerhet in Swedish criminal cases, EU age verification and Internet privacy, Pornography literacy and harm reduction, Swedish public-record privacy, Boomers and democracy, Clear backpacks are school security theater, Male variability, education, and life outcomes, and Swedish business tax map. The extra link from the privacy venture to the tax map shows that the business-tax route is both an independent starting point and part of the venture’s commercial planning. Two of these routes are hubs whose titles state a conclusion rather than name a field, which is what a domain looks like when its most developed note is an argument.

Privacy cluster

This map treats privacy as a harm model, a design discipline, and a contested legal boundary.

flowchart TD
  n0@{ shape: subproc, label: "Case for privacy and security" }
  n1@{ shape: rounded, label: "Data as coercive power" }
  n2@{ shape: rounded, label: "High-consequence data" }
  n3@{ shape: rounded, label: "Data minimization" }
  n4@{ shape: rounded, label: "Privacy threat modeling" }
  n5@{ shape: rounded, label: "Privacy product architecture" }
  n6@{ shape: rounded, label: "Privacy trust and governance" }
  n7@{ shape: subproc, label: "Privacy legal and regulatory posture" }
  n8@{ shape: subproc, label: "EU and Swedish data removal rights" }
  n9@{ shape: rounded, label: "Ethics of resisting lawful extraction" }
  n10@{ shape: rounded, label: "Confidentiality as safety infrastructure" }
  n11@{ shape: rounded, label: "Criminal-offence data under GDPR Article 10" }
  n0 --> n1
  n0 --> n2
  n0 --> n4
  n1 --> n3
  n2 --> n3
  n1 --> n10
  n3 --> n5
  n4 --> n5
  n4 --> n6
  n5 --> n6
  n4 --> n7
  n7 --> n11
  n8 --> n11
  n8 --> n3
  n10 --> n9
  n3 --> n9
  %% node-link n0 Case_for_privacy_and_security.html
  %% node-link n1 Data_as_coercive_power.html
  %% node-link n2 High-consequence_data.html
  %% node-link n3 Data_minimization.html
  %% node-link n4 Privacy_threat_modeling.html
  %% node-link n5 Privacy_product_architecture.html
  %% node-link n6 Privacy_trust_and_governance.html
  %% node-link n7 Privacy_legal_and_regulatory_posture.html
  %% node-link n8 EU_and_Swedish_data_removal_rights.html
  %% node-link n9 Ethics_of_resisting_lawful_extraction.html
  %% node-link n10 Confidentiality_as_safety_infrastructure.html
  %% node-link n11 Criminal-offence_data_under_GDPR_Article_10.html
  class n1,n2,n3,n4,n5,n6,n9,n10,n11 concept
  class n0,n7,n8 synthesis

The privacy cluster links Case for privacy and security, Data as coercive power, High-consequence data, Data minimization, Privacy threat modeling, Privacy product architecture, Privacy trust and governance, Privacy legal and regulatory posture, EU and Swedish data removal rights, Ethics of resisting lawful extraction, Confidentiality as safety infrastructure, and Criminal-offence data under GDPR Article 10.

Private AI cluster

This map separates the strategy and service layer from technical trust boundaries and market evidence.

flowchart LR
  n0@{ shape: subproc, label: "Private AI strategy" }
  n1@{ shape: subproc, label: "Private AI services" }
  n2@{ shape: rounded, label: "Private AI trust boundaries" }
  n3@{ shape: subproc, label: "Private AI competitors" }
  n4@{ shape: rounded, label: "Local AI" }
  n5@{ shape: rounded, label: "Confidential AI computing" }
  n6@{ shape: rounded, label: "Private AI routing" }
  n7@{ shape: subproc, label: "Private AI buyer alternatives" }
  n8@{ shape: subproc, label: "Private AI venture validation" }
  n9@{ shape: subproc, label: "Private AI legal roles" }
  n10@{ shape: hex, label: "Lumo" }
  n11@{ shape: hex, label: "Privatemode" }
  n12@{ shape: hex, label: "Tinfoil" }
  n0 --> n1
  n0 --> n2
  n0 --> n3
  n2 --> n4
  n2 --> n5
  n2 --> n6
  n1 --> n7
  n1 --> n8
  n1 --> n9
  n3 --> n10
  n3 --> n11
  n3 --> n12
  %% node-link n0 Private_AI_strategy.html
  %% node-link n1 Private_AI_services.html
  %% node-link n2 Private_AI_trust_boundaries.html
  %% node-link n3 Private_AI_competitors.html
  %% node-link n4 Local_AI.html
  %% node-link n5 Confidential_AI_computing.html
  %% node-link n6 Private_AI_routing.html
  %% node-link n7 Private_AI_buyer_alternatives.html
  %% node-link n8 Private_AI_venture_validation.html
  %% node-link n9 Private_AI_legal_roles.html
  %% node-link n10 Lumo.html
  %% node-link n11 Privatemode.html
  %% node-link n12 Tinfoil.html
  class n2,n4,n5,n6 concept
  class n10,n11,n12 entity
  class n0,n1,n3,n7,n8,n9 synthesis

The private-AI cluster links Private AI strategy, Private AI services, Private AI trust boundaries, Private AI competitors, Local AI, Confidential AI computing, Private AI routing, Private AI buyer alternatives, Private AI venture validation, Private AI legal roles, Lumo, Privatemode, and Tinfoil.

Business cluster

This map follows the commercial path from thesis and customers to offers, constraints, and sequencing. The proposals hub is the pivot: everything above it establishes who is being sold to and why, and everything below it is a branch of what is sold.

flowchart TD
  n0@{ shape: subproc, label: "Privacy business thesis" }
  n1@{ shape: stadium, label: "Privacy venture atlas" }
  n2@{ shape: subproc, label: "Privacy customer segments" }
  n3@{ shape: subproc, label: "Privacy business proposals" }
  n4@{ shape: subproc, label: "Lawful digital-safety support" }
  n5@{ shape: subproc, label: "EU and Swedish data removal rights" }
  n6@{ shape: subproc, label: "Private AI services" }
  n7@{ shape: rounded, label: "Unlinked subscription architecture" }
  n9@{ shape: subproc, label: "Privacy legal and regulatory posture" }
  n10@{ shape: subproc, label: "Sweden as a privacy venture base" }
  n11@{ shape: subproc, label: "Privacy venture roadmap" }
  n12@{ shape: subproc, label: "Content-led privacy shop" }
  n0 --> n1
  n1 --> n2
  n2 --> n3
  n3 --> n4
  n3 --> n5
  n3 --> n6
  n3 --> n7
  n3 --> n9
  n9 --> n10
  n3 --> n11
  n3 --> n12
  %% node-link n0 Privacy_business_thesis.html
  %% node-link n1 Privacy_venture_atlas.html
  %% node-link n2 Privacy_customer_segments.html
  %% node-link n3 Privacy_business_proposals.html
  %% node-link n4 Lawful_digital-safety_support.html
  %% node-link n5 EU_and_Swedish_data_removal_rights.html
  %% node-link n6 Private_AI_services.html
  %% node-link n7 Unlinked_subscription_architecture.html
  %% node-link n9 Privacy_legal_and_regulatory_posture.html
  %% node-link n10 Sweden_as_a_privacy_venture_base.html
  %% node-link n11 Privacy_venture_roadmap.html
  %% node-link n12 Content-led_privacy_shop.html
  class n1 index
  class n7 concept
  class n0,n2,n3,n4,n5,n6,n9,n10,n11,n12 synthesis

The business cluster links Privacy business thesis, Privacy venture atlas, Privacy customer segments, Privacy business proposals, Lawful digital-safety support, EU and Swedish data removal rights, Private AI services, Unlinked subscription architecture, Privacy legal and regulatory posture, Sweden as a privacy venture base, Privacy venture roadmap, and Content-led privacy shop. Each of these proposal branches has its own downstream detail (such as Post-seizure digital recovery under lawful digital-safety support, or Privacy gear webshop, Privacy voucher shop, Swedish and EU privacy suppliers, and Hardware security keys under content-led privacy shop) that stays in those notes rather than in this overview map.

Rättssäkerhet cluster

This map answers where error enters a Swedish criminal case and why the system is poorly placed to find it again. It runs from the doctrine that governs how evidence is weighed, through the three mechanisms that corrupt the inputs, to the correction problem that lets a wrong result harden.

flowchart TD
  n0@{ shape: subproc, label: "Rättssäkerhet in Swedish criminal cases" }
  n1@{ shape: rounded, label: "Investigative confirmation bias" }
  n2@{ shape: subproc, label: "Witness reports are not ground truth" }
  n3@{ shape: rounded, label: "Coercive interrogation and false confessions" }
  n4@{ shape: subproc, label: "False accusations as an epistemic risk" }
  n5@{ shape: rounded, label: "Correction channel" }
  n6@{ shape: rounded, label: "Free evaluation of evidence in Sweden" }
  n7@{ shape: subproc, label: "Probabilistic interpretations of beyond reasonable doubt" }
  n8@{ shape: rounded, label: "Resning in Swedish criminal cases" }
  n9@{ shape: rounded, label: "Scandinavian legal realism" }
  n10@{ shape: cyl, label: "Felaktigt dömda" }
  n11@{ shape: subproc, label: "Why you shouldn't talk to the police" }
  n9 --> n6
  n9 --> n0
  n6 --> n0
  n8 --> n9
  n8 --> n0
  n0 --> n2
  n0 --> n3
  n2 --> n1
  n3 --> n1
  n3 --> n11
  n1 --> n10
  n10 --> n4
  n4 --> n7
  n1 --> n5
  n7 --> n5
  n11 --> n5
  %% node-link n0 R%C3%A4ttss%C3%A4kerhet_in_Swedish_criminal_cases.html
  %% node-link n1 Investigative_confirmation_bias.html
  %% node-link n2 Witness_reports_are_not_ground_truth.html
  %% node-link n3 Coercive_interrogation_and_false_confessions.html
  %% node-link n4 False_accusations_as_an_epistemic_risk.html
  %% node-link n5 Correction_channel.html
  %% node-link n6 Free_evaluation_of_evidence_in_Sweden.html
  %% node-link n7 Probabilistic_interpretations_of_beyond_reasonable_doubt.html
  %% node-link n8 Resning_in_Swedish_criminal_cases.html
  %% node-link n9 Scandinavian_legal_realism.html
  %% node-link n10 Felaktigt_d%C3%B6mda.html
  %% node-link n11 Why_you_shouldn%27t_talk_to_the_police.html
  class n1,n3,n5,n6,n8,n9 concept
  class n0,n2,n4,n7,n11 synthesis
  class n10 source

The rättssäkerhet cluster links Rättssäkerhet in Swedish criminal cases, Investigative confirmation bias, Witness reports are not ground truth, Coercive interrogation and false confessions, False accusations as an epistemic risk, Correction channel, Free evaluation of evidence in Sweden, Probabilistic interpretations of beyond reasonable doubt, Resning in Swedish criminal cases, Scandinavian legal realism, Felaktigt dömda, and Why you shouldn’t talk to the police. Three separate mechanisms converge on confirmation bias because each supplies it with material rather than competing with it, and every downstream path reaches the correction channel, which is where the domain’s central claim sits: an institution’s own outputs cannot measure its own error rate.

Child safety cluster

This map answers what to do about harm to young people online when the three available responses — identify the user, change the design, or teach the reader — have different evidence behind them.

flowchart TD
  n0@{ shape: subproc, label: "EU age verification and Internet privacy" }
  n1@{ shape: rounded, label: "Age assurance" }
  n2@{ shape: subproc, label: "Alternatives to age verification" }
  n3@{ shape: subproc, label: "Less harmful social media" }
  n4@{ shape: subproc, label: "Pornography literacy and harm reduction" }
  n5@{ shape: subproc, label: "Age-verification circumvention services" }
  n6@{ shape: rounded, label: "Displacement" }
  n7@{ shape: hex, label: "UK Online Safety Act" }
  n8@{ shape: diamond, label: "Does age verification reduce harms other measures cannot" }
  n9@{ shape: rounded, label: "Automated CSAM detection" }
  n10@{ shape: subproc, label: "CSAM scanning externalizes error costs" }
  n11@{ shape: rounded, label: "Age-proof unlinkability and account uniqueness" }
  n7 --> n1
  n1 --> n0
  n0 --> n11
  n0 --> n2
  n2 --> n8
  n2 --> n3
  n2 --> n4
  n2 --> n5
  n5 --> n6
  n6 --> n3
  n8 --> n7
  n2 --> n9
  n9 --> n10
  %% node-link n0 EU_age_verification_and_Internet_privacy.html
  %% node-link n1 Age_assurance.html
  %% node-link n2 Alternatives_to_age_verification.html
  %% node-link n3 Less_harmful_social_media.html
  %% node-link n4 Pornography_literacy_and_harm_reduction.html
  %% node-link n5 Age-verification_circumvention_services.html
  %% node-link n6 Displacement.html
  %% node-link n7 UK_Online_Safety_Act.html
  %% node-link n8 Does_age_verification_reduce_harms_other_measures_cannot.html
  %% node-link n9 Automated_CSAM_detection.html
  %% node-link n10 CSAM_scanning_externalizes_error_costs.html
  %% node-link n11 Age-proof_unlinkability_and_account_uniqueness.html
  class n1,n6,n9,n11 concept
  class n0,n2,n3,n4,n5,n10 synthesis
  class n7 entity
  class n8 question

The child safety cluster links EU age verification and Internet privacy, Age assurance, Alternatives to age verification, Less harmful social media, Pornography literacy and harm reduction, Age-verification circumvention services, Displacement, UK Online Safety Act, Does age verification reduce harms other measures cannot, Automated CSAM detection, CSAM scanning externalizes error costs, and Age-proof unlinkability and account uniqueness. Alternatives to age verification is the branch point: it holds the comparison the domain turns on, which is why the design route, the literacy route, the circumvention evidence, and the open question all hang off it. The scanning branch is the same argument run on a different detection technology, and it is included to show that the error-cost problem is not specific to age checks.

Swedish public-record cluster

This map answers how Sweden’s openness regime becomes a searchable dossier on a named individual, and which routes exist to interrupt it.

flowchart TD
  n0@{ shape: subproc, label: "Swedish public-record privacy" }
  n1@{ shape: rounded, label: "Offentlighetsprincipen and personal privacy" }
  n2@{ shape: rounded, label: "Swedish personal identity number" }
  n3@{ shape: rounded, label: "Utgivningsbevis and people-search services" }
  n4@{ shape: hex, label: "Dumpen" }
  n5@{ shape: rounded, label: "Naming convicted people in Swedish media" }
  n6@{ shape: subproc, label: "Challenging name-search indexing of criminal coverage" }
  n7@{ shape: subproc, label: "EU and Swedish data removal rights" }
  n8@{ shape: rounded, label: "Protected personal data in Sweden" }
  n9@{ shape: cyl, label: "GC and Others C-136-17" }
  n10@{ shape: diamond, label: "Will Swedish people-search services survive GDPR enforcement" }
  n11@{ shape: hex, label: "Integritetsskyddsmyndigheten" }
  n1 --> n2
  n1 --> n3
  n1 --> n0
  n3 --> n4
  n3 --> n5
  n4 --> n6
  n5 --> n9
  n6 --> n9
  n6 --> n11
  n11 --> n7
  n7 --> n6
  n10 --> n7
  n3 --> n10
  n8 --> n0
  %% node-link n0 Swedish_public-record_privacy.html
  %% node-link n1 Offentlighetsprincipen_and_personal_privacy.html
  %% node-link n2 Swedish_personal_identity_number.html
  %% node-link n3 Utgivningsbevis_and_people-search_services.html
  %% node-link n4 Dumpen.html
  %% node-link n5 Naming_convicted_people_in_Swedish_media.html
  %% node-link n6 Challenging_name-search_indexing_of_criminal_coverage.html
  %% node-link n7 EU_and_Swedish_data_removal_rights.html
  %% node-link n8 Protected_personal_data_in_Sweden.html
  %% node-link n9 GC_and_Others_C-136-17.html
  %% node-link n10 Will_Swedish_people-search_services_survive_GDPR_enforcement.html
  %% node-link n11 Integritetsskyddsmyndigheten.html
  class n1,n2,n3,n5,n8 concept
  class n0,n6,n7 synthesis
  class n4,n11 entity
  class n9 source
  class n10 question

The Swedish public-record cluster links Swedish public-record privacy, Offentlighetsprincipen and personal privacy, Swedish personal identity number, Utgivningsbevis and people-search services, Dumpen, Naming convicted people in Swedish media, Challenging name-search indexing of criminal coverage, EU and Swedish data removal rights, Protected personal data in Sweden, GC and Others C-136-17, Will Swedish people-search services survive GDPR enforcement, and Integritetsskyddsmyndigheten. The chain from openness to exposure is constitutional at one end and commercial at the other: Utgivningsbevis and people-search services is where a publishing certificate converts public records into a product, which is why both the remedy route and the open question attach at that node.

School security cluster

This map answers why a school-safety measure can be popular, intuitive, and unsupported at the same time, and what the evidence points to instead.

flowchart TD
  n0@{ shape: subproc, label: "Clear backpacks are school security theater" }
  n1@{ shape: rounded, label: "Clear backpack policies" }
  n2@{ shape: rounded, label: "Security theater" }
  n3@{ shape: hex, label: "K-12 School Shooting Database" }
  n4@{ shape: rounded, label: "Behavioral threat assessment in schools" }
  n5@{ shape: rounded, label: "School surveillance and the school-to-prison pipeline" }
  n6@{ shape: diamond, label: "What interventions reduce school weapon carriage" }
  n7@{ shape: notch-pent, label: "Marjory Stoneman Douglas High School shooting" }
  n8@{ shape: hex, label: "Comprehensive School Threat Assessment Guidelines" }
  n7 --> n1
  n1 --> n0
  n3 --> n0
  n2 --> n0
  n0 --> n5
  n0 --> n6
  n6 --> n4
  n4 --> n8
  n3 --> n6
  %% node-link n0 Clear_backpacks_are_school_security_theater.html
  %% node-link n1 Clear_backpack_policies.html
  %% node-link n2 Security_theater.html
  %% node-link n3 K-12_School_Shooting_Database.html
  %% node-link n4 Behavioral_threat_assessment_in_schools.html
  %% node-link n5 School_surveillance_and_the_school-to-prison_pipeline.html
  %% node-link n6 What_interventions_reduce_school_weapon_carriage.html
  %% node-link n7 Marjory_Stoneman_Douglas_High_School_shooting.html
  %% node-link n8 Comprehensive_School_Threat_Assessment_Guidelines.html
  class n1,n2,n4,n5 concept
  class n0 synthesis
  class n3,n8 entity
  class n6 question
  class n7 event

The school security cluster links Clear backpacks are school security theater, Clear backpack policies, Security theater, K-12 School Shooting Database, Behavioral threat assessment in schools, School surveillance and the school-to-prison pipeline, What interventions reduce school weapon carriage, Marjory Stoneman Douglas High School shooting, and Comprehensive School Threat Assessment Guidelines. The event drives the policy and the database supplies the base rate, so the two arrive at the synthesis from opposite directions: one supplies the salient case, the other the denominator that makes it rare. This is the only cluster whose map carries an event node, and it is the shape most policy arguments in the vault take.

Complete knowledge graph

This generated view includes every maintained non-meta note and every resolved page-level wikilink. Repeated links between the same notes are collapsed, while local section links and self-links are omitted.

The view is a live force simulation. Node colors follow the same type palette as the story graphs, and node size scales with backlink count. Zoom with the mouse wheel, pan by dragging the background, and drag a node to pull its neighborhood into view; the simulation keeps its edges taut. Hovering a node dims everything outside its direct neighborhood, and clicking a node opens its note.

The complete note and tag views share the same controls: mouse-wheel zoom, background panning, node dragging, a “Fit” button, and fullscreen. Because these complete views follow actual data rather than a curated story, their density is useful for inspection but not always for explanation.

This note cites no sources of its own.

Working out connections…