Strategic Architecture for Sovereign AI: Reclaiming Compute in the Era of Digital Splinternets

Full report

On this page

The Emergence of the Sovereign Splinternet and the Balkanization of Routing

For much of the modern era, the internet's architecture was presumed to be inherently global and resilient, originally engineered during the Cold War to survive catastrophic nuclear disruptions through decentralized routing protocols1. However, this borderless digital paradigm is currently undergoing a systemic, state-driven balkanization. Authoritarian regimes are aggressively executing strategies of "digital sovereignty," transforming national network infrastructures into highly monitored, heavily balkanized intranets. These sovereign "splinternets" provide state security apparatuses with the capability to analyze, throttle, or entirely sever international data flows while maintaining critical domestic services1. The Russian Federation's execution of Federal Law No. 90-FZ, widely known as the "Sovereign Internet Law," provides the archetypal blueprint for this network isolation3. Enacted in late 2019, the legislation mandates the centralized management of all domestic telecommunication networks and establishes a national Domain Name System (DNS) designed to operate autonomously from the global ICANN infrastructure3. This segregation theoretically allows the Russian segment of the internet (RuNet) to continue functioning even if disconnected from global root servers, while simultaneously enabling the state to render global websites unavailable within its borders4. At the physical core of this censorship infrastructure is the mandatory deployment of Technical Means for Countering Threats (TSPU) across the facilities of any Internet Service Provider (ISP) or mobile operator with a communication node capacity exceeding 10 Gbps3. TSPU units act as massive, inline Deep Packet Inspection (DPI) appliances. Positioned in separate racks with independent power supplies, these units communicate directly with the central systems of the Main Radio Frequency Center (GRCC), an affiliate of the state media regulator Roskomnadzor, via dedicated 100 Mbit/s channels3. ISPs have zero administrative access to these systems and cannot monitor their filtering parameters3. Historically, TSPU hardware relied heavily on bypass components from foreign entities like the Israeli firm Silicom, but current iterations—costing roughly \$5,000 per unit—increasingly utilize domestic hardware from suppliers like Yadro to avoid supply-chain disruptions3. By late 2023, Roskomnadzor had successfully deployed TSPU systems across more than 1,360 broadband, mobile, and cross-border routing nodes3. This ensures that almost all traffic transiting the RuNet is subjected to deep packet inspection, allowing the state to block obfuscation protocols, VPNs, and specific UDP ports associated with decentralized communication3. A parallel but functionally distinct architecture exists within the Islamic Republic of Iran through its National Information Network (NIN)2. The NIN is not merely a replacement for the global internet but a strategic control infrastructure characterized by domestic hosting, selective routing whitelists, and a politically weaponized allocation of bandwidth2. Recent analyses indicate that the Iranian state has transitioned away from crude, nationwide internet blackouts toward a multi-layered model of selective reachability2. The NIN enables the state to throttle international connectivity while domestic banking, government services, and state-approved media remain fully operational2. However, in times of acute crisis, the NIN serves as an effective platform for total digital isolation. During intense anti-government protests and geopolitical conflicts in early 2026, the Iranian regime executed a nationwide internet blackout lasting over 1,248 consecutive hours6. Internet traffic dropped by 98%, leaving an estimated 92 million citizens cut off from the global web while forcing all remaining digital activity onto the highly monitored NIN7. State officials, including government spokesperson Fatemeh Mohajerani and Communications Minister Sattar Hashemi, defended the blackout as a necessary wartime measure to protect critical digital infrastructure from foreign cyberattacks, explicitly framing network censorship as an issue of national security and military operational integrity7. Civil society researchers reported that during these crises, control over internet policy shifted from civilian telecommunications bureaucrats directly to a security-apparatus-centered "war room" operated by the Islamic Revolutionary Guard Corps (IRGC)2. In these highly contested, splinternet environments, any reliance on centralized, globally hosted applications becomes an existential vulnerability. The current trajectory of Artificial Intelligence (AI) development, which heavily favors centralized cloud APIs, falls directly into this trap.

The Locus of Control: Cloud API Chokepoints vs. Edge-Native Autonomy

The prevailing industry standard for foundation models relies on massive hyperscale data centers processing hundreds of billions of parameters. Access to these cognitive engines is parceled out to developers and end-users via Application Programming Interfaces (APIs). While this centralized model abstracts the immense hardware complexity away from the user, it concentrates absolute control in the hands of the API provider and the regulatory regimes governing their physical servers.

Vulnerability of the API Chokepoint

Cloud AI APIs present multiple cascading vectors for surveillance, censorship, and sudden disruption. First, because all queries and responses must traverse the open internet, they are acutely vulnerable to Deep Packet Inspection by TSPU-like devices3. State actors can easily monitor DNS requests or IP routing associated with major AI API providers, terminating connections instantaneously3. Second, the telemetric footprint of an API query acts as a surveillance honeypot. The prompts, context windows, and output data are processed in plaintext on the provider's servers. Even if a provider claims to anonymize data, the provider maintains the technical capability to log user interactions, creating vast repositories of sensitive data that state intelligence apparatuses can subpoena or silently intercept. Furthermore, API providers enforce strict Acceptable Use Policies (AUPs) and alignment filters designed to align with the legal frameworks and cultural sensitivities of their operating jurisdictions10. Because the model executes on the provider's proprietary hardware, the provider acts as a universal censor. They can execute instant, network-wide account terminations, alter model behavior overnight, or quietly implement "shadow-banning" on specific political or technical topics. This dynamic strips users of any cognitive sovereignty; the user is merely leasing intelligence under extreme, revocable conditions.

The Air-Gapped Imperative of Open-Weight Models

Locally executed open-weight models invert this asymmetrical power dynamic. When a model's neural weights and biases are downloaded as compiled binary files and executed on consumer hardware—such as laptops, edge servers, or mobile devices—the locus of control shifts entirely to the user. This localized execution provides robust, fundamental defenses against state splinternet architectures.

Comparative analysis of resilience vectors between centralized and decentralized AI infrastructure. Once the binary assets are obtained, they operate completely independently of the global internet. State actors cannot utilize DPI to block API calls because no external network requests are generated3. Local execution requires zero telemetric feedback, offering cryptographic-level privacy through physical air-gapping. The system is immune to sudden shifts in alignment training, granting the user unmediated interaction with the neural network. However, realizing that decentralized compute poses a profound threat to information monopolies, state entities and corporate incumbents are advancing sophisticated legal and hardware mechanisms designed to artificially re-centralize control over local AI deployments.

Regulatory Encirclement: AI Licensing and the Illusion of Open Source

The term "open source AI" is a misnomer that obscures significant legal liabilities. The vast majority of highly capable, locally runnable models utilize custom open-weight licenses or Responsible AI Licenses (RAIL) rather than traditional Open Source Initiative (OSI) approved licenses like Apache 2.0 or MIT10. These custom licenses are structured as legal instruments of behavioral control. Understanding their core components is essential for decentralized infrastructure engineers, as these licenses construct a framework of "regulatory encirclement" around open compute.

The Anatomy of Behavioral AI Licensing

RAIL and custom open-weight licenses typically consist of three primary components that dictate downstream usage10:

1. Permissive Base: The license grants broad, royalty-free rights to access, use, copy, modify, merge, and distribute the model weights, including for commercial applications10.

2. Prohibited Use Schedule: The permissive base is rigidly conditioned on adherence to a sweeping schedule of prohibited use cases. This schedule frequently forbids using the model to generate defamatory content, provide medical advice, write malware, or generate specific political outputs10.

3. Pass-Through Obligations: Any developer who fine-tunes the base model, merges it with another model, or distributes a derivative work must legally pass through the exact same prohibited use schedule to all downstream users10.

If a developer violates these use-case restrictions, the license is immediately terminated. Operating a model after license termination exposes the developer to severe breach of contract liabilities and, crucially, primary liability for copyright infringement, as the rights to utilize the underlying intellectual property have been revoked10. Some major corporate licenses also impose strict user or revenue thresholds (e.g., prohibiting commercial use if the deploying application exceeds 700 million monthly active users without a bespoke agreement)11. Furthermore, utilizing open-source base models without strict adherence to attribution clauses—which courts have consistently enforced as legally binding conditions, not aspirational guidelines—can result in swift legal injunctions10.

The Regulatory Threat of the EU AI Act and Copyright Law

State regulators are increasingly leveraging these licensing ambiguities to enforce compliance. The European Union's AI Act categorizes models based on their systemic risk and application. High-risk AI systems require extensive conformity assessments, integration of risk management systems, human oversight mechanisms, and mandatory registration in an EU database before they can be placed on the market10. While many decentralized developers assume their tools fall into minimal-risk categories (which are subject only to voluntary codes of practice), classification errors carry catastrophic penalties. Developers who misclassify their open-weight deployments can face fines of up to €15 million or 3% of their global turnover10. Additionally, the legal status of the data scraped to train these models remains a potent vector for state and corporate suppression. Under the EU's Directive on Copyright in the Digital Single Market (CDSM Directive), specifically Article 3 and Article 4, Text and Data Mining (TDM) is generally permitted, but rightsholders possess the ability to explicitly opt out of having their data used for commercial AI training10. The fact that data is publicly accessible on the internet is legally irrelevant to whether it can be lawfully scraped and incorporated into model weights10. Deploying an open-weight model trained on opted-out data creates an immediate vector for asset seizure and network de-platforming.

Hardware-Level Governance: Confidential Computing as a State Kill Switch

While AI licensing provides the legal scaffolding for state control, emerging hardware architectures threaten to provide the physical enforcement mechanism. As silicon manufacturers push to secure intellectual property, they are widely adopting Confidential Computing (CC) frameworks15.

The Mechanics of Trusted Execution Environments (TEEs)

Confidential Computing is a security paradigm engineered to protect sensitive data while it is actively being processed in memory15. It achieves this through hardware-based isolation, creating Trusted Execution Environments (TEEs) or "secure enclaves." Secure enclaves possess four defining security properties17:

1. Isolation: The enclave acts entirely independently from the rest of the host system. Neither the operating system, the hypervisor, nor the system administrator can access the memory space17.

2. Runtime Memory Encryption: All operations and data stored within the enclave are perpetually encrypted in RAM; the CPU decrypts the data only at the exact moment of execution17.

3. Sealing: The enclave can securely encrypt and store data on the untrusted host system, ensuring it can only be read when loaded back into the specific enclave configuration17.

4. Remote Cryptographic Attestation: The enclave can generate mathematical, verifiable proof to a remote third party that it is operating on genuine hardware and executing approved, unmodified code17.

Weaponizing Attestation for Hardware-Level Governance

Attestation was originally designed to alleviate enterprise anxiety regarding public cloud deployments18. The attestation evidence contains specific claims regarding the physical characteristics of the execution environment, including the CPU manufacturer, microcode version, firmware integrity, and encryption state19. This evidence is cryptographically signed using a root-of-trust key fused into the silicon during manufacturing19. A remote Key Management Infrastructure (KMI) verifies this signature against the manufacturer's certificate; if the evidence matches the strict security policy, the KMI releases the necessary decryption keys to the enclave19. In the context of the sovereign splinternet, this technology represents a profound threat. Policy analysts and state regulators are actively exploring "hardware-level governance" to embed monitoring and compliance capabilities directly into AI chips21. Under a state-mandated hardware governance regime, advanced GPUs or NPUs could be legally required to feature non-bypassable secure enclaves. When a user attempts to execute a large language model, the encrypted model weights would require a decryption key from a centralized, state-approved KMI. The KMI would only release the key if the chip's attestation report proves that the local environment is running state-licensed inference software, complete with mandated censorship filters19. If the user attempts to modify the open-source inference engine to bypass censorship, the cryptographic hash of the software will change. The hardware will generate an attestation report reflecting this unauthorized modification, the KMI will refuse to issue the decryption key, and the AI model will refuse to execute19. This architecture effectively functions as an unbreakable hardware kill switch, allowing authoritarian regimes to enforce API-level censorship on physically air-gapped, decentralized consumer hardware21.

Representation Engineering: Mathematical Eradication of Algorithmic Censorship

Even if a user acquires a decentralized model and bypasses hardware attestation, the neural weights themselves have been heavily sanitized. To align with corporate AUPs, foundation models undergo rigorous Supervised Fine-Tuning (SFT) and Reinforcement Learning from Human Feedback (RLHF)23. This alignment training frequently induces persistent over-refusal, where the model declines to answer harmless or geopolitically sensitive queries23. To build truly sovereign infrastructure, these embedded alignment taxes must be neutralized. Traditional fine-tuning attempts to "unlearn" refusals by updating weights via backpropagation on uncensored data, but this is computationally expensive and frequently degrades the model's general reasoning capabilities25. The ultimate defense against algorithmic censorship is a geometric approach known as "representation engineering," specifically the technique of "abliteration"27.

The Mathematics of Abliteration

Recent interpretability research demonstrates that refusal behavior in LLMs is not distributed chaotically throughout the network. Instead, it is highly mediated by a distinct, low-dimensional subspace within the residual stream, often effectively functioning as a single "refusal direction"28. By extracting this vector (denoted as [Figure omitted from source export]) through contrastive activation pairs—feeding the model identical prompts phrased both harmfully and harmlessly, and calculating the mean difference in their internal activations—engineers can map the precise conceptual geometry of censorship28. Once the refusal direction is isolated, the model's parameter weight matrices ([Figure omitted from source export]) can be surgically modified using an orthogonal projection. The ablation operation is mathematically defined as: [Figure omitted from source export] Where [Figure omitted from source export] is a configurable scalar parameter that controls the strength of the ablation (typically between 0.6 and 1.0), and [Figure omitted from source export] constitutes the projection matrix onto the target refusal direction28. This operation fundamentally prevents the model from representing the concept of refusal. Because the intervention is highly targeted, it incurs minimal Kullback-Leibler (KL) divergence. KL divergence quantifies the "collateral damage" of the modification by measuring how much the abliterated model's baseline probability distribution differs from the original28. Lower KL divergence (values below 0.1) indicates that the model retains its original logic, coding capabilities, and knowledge retention, having strictly lost the trained impulse to preach or refuse28.

The Abliteration Illusion and Advanced Refusal

While representation engineering is powerful, recent empirical analyses reveal vulnerabilities in naive abliteration techniques. The "Abliteration Illusion" occurs when a model is modified to bypass simple keyword-based refusal detection (e.g., removing the propensity to say "As an AI, I cannot...") but fails to actually provide compliant, useful responses to controversial prompts31. Benchmarks like UncensorBench have demonstrated that models optimized merely to avoid refusal keywords often hallucinate or fail semantic similarity tests when tasked with generating complex, restricted information31. Furthermore, advanced Large Reasoning Models (LRMs) that utilize Chain-of-Thought (CoT) architectures present new challenges. In these models, refusal is jointly encoded in both the residual stream activations and the explicit reasoning steps24. This joint activation makes LRMs highly robust against simple activation steering, as the censorship mechanism manifests through "thought suppression"—where the model systematically rewrites or deletes its own reasoning traces before outputting sensitive content24. To achieve true cognitive liberty on advanced models, representation engineering must be applied dynamically to both the latent activations and the autoregressive reasoning generation.

CognitiveLiberties.com Deployment Strategy: The Sovereign AI Stack

To counter the combined threats of state splinternets, hardware attestation, and algorithmic censorship, CognitiveLiberties.com must distribute a highly optimized, fully self-contained AI infrastructure stack. This stack must operate seamlessly on off-grid consumer hardware, demanding minimal VRAM, requiring zero runtime dependencies, and mandating absolute network isolation post-acquisition. The comprehensive deployment strategy relies on four critical pillars: Decentralized Asset Distribution (Nostr), the Portable Inference Engine (llama.cpp), Edge-Native RAG (sqlite-vec), and Sovereign Fine-Tuning (Unsloth).

1. Decentralized Asset Distribution via Nostr NIP-94

Distributing abliterated models and uncensored datasets via traditional centralized repositories (such as GitHub or Hugging Face) exposes the project to immediate DMCA takedowns, AUP violations, and state-level DNS blocking4. To guarantee persistent global availability, CognitiveLiberties.com will leverage the Nostr protocol. Nostr is a decentralized, relay-based messaging protocol highly resistant to centralized censorship. The strategy utilizes NIP-94 (File Metadata), a specification allowing clients to broadcast kind: 1063 events containing comprehensive metadata about files shared over peer-to-peer networks33. An authorized NIP-94 event payload includes:

• x: The SHA-256 hex-encoded string of the file for cryptographic verification.
• m: The MIME type indicating the data structure.
• url: A standard fallback download link.
• magnet: A URI to a magnet link.
• i: The torrent infohash, allowing immediate integration into BitTorrent swarms33.

By publishing these metadata events, CognitiveLiberties.com broadcasts the availability of massive, multi-gigabyte GGUF model binaries and lightweight LoRA adapters without hosting the files on centralized servers. End-users sync with Nostr relays to discover the latest models and download them via decentralized BitTorrent swarms. To ensure supply-chain integrity against state-sponsored poisoning attacks, all released binaries will be cryptographically signed using minisign and encrypted via age-encryption34. This enables dissident researchers to mathematically verify that the downloaded weights are the genuine, de-censored assets released by CognitiveLiberties.com.

2. The llama.cpp Inference Engine and GGUF Quantization

The execution foundation of the sovereign stack is llama.cpp. Engineered in pure C/C++, llama.cpp encapsulates the entire transformer inference pipeline with minimal external dependencies. This ensures flawless cross-compilation across Windows, macOS, Linux, and resource-constrained edge devices (such as Android via Termux) without requiring massive CUDA environments or specific GPU drivers36. To bypass the hardware attestation threats associated with high-end enterprise GPUs, the models must be compressed to run efficiently on standard commercial off-the-shelf (COTS) CPUs and consumer-grade graphics cards. This is achieved via the GGUF (GPT-Generated Unified Format) quantization protocol38. Quantization transforms high-precision floating-point weights (FP16/BF16) into lower precision integer formats, drastically reducing the memory footprint and the memory bandwidth bottlenecks that cripple edge inference38.

Data representation of llama.cpp quantization profiles and hardware requirements39. For CognitiveLiberties.com, the standard distribution format will be Q4\_K\_M. This specific configuration utilizes non-linear k-quants to mix precisions across different neural layers. It aggressively compresses dense, parameter-heavy feed-forward networks while preserving the high precision of mathematically sensitive attention mechanisms38. To further mitigate the degradation of quantization, the compilation pipeline will utilize an Importance Matrix (imatrix). The IMatrixCollector intercepts tensor operations during a forward calibration pass, tracking activation squared sums (total\_sqract) to identify which weights are most vital to the model's intelligence42. The quantizer then dynamically allocates higher precision to these specific tensors, resulting in a compressed model that performs virtually identical to its FP16 baseline while requiring less than 5GB of system memory39. For extreme edge deployments—such as mobile devices operating in crisis zones—the stack will utilize the BitNet b1.58 ultra-low-bit architecture. Utilizing specialized TQ1\_0 and TQ2\_0 ternary quantization formats, these models can be decoded on-the-fly inside Vulkan compute shaders44. By implementing dynamic tiling in Vulkan to split massive matrix operations into hardware-compliant chunks, llama.cpp enables even memory-constrained mobile GPUs to achieve interactive inference speeds without thermal throttling36. Furthermore, the llama-server component provides an OpenAI-compatible REST API featuring a /lora-adapters endpoint45. This architecture permits dynamic, per-request LoRA adapter hot-swapping48. Users can maintain a single, highly compressed base model in RAM and instantly swap tiny (often \<100MB) task-specific adapters for different analytical functions without the computational overhead of unloading and reloading massive base models into memory42.

3. Edge-Native Retrieval-Augmented Generation (RAG) via sqlite-vec

An isolated language model requires contextual grounding to process local, encrypted documents effectively. Standard vector databases (such as Pinecone, Milvus, or pgvector) require heavy containerization, background daemons, and frequently, internet connectivity. CognitiveLiberties.com will circumvent this by deploying sqlite-vec, a paradigm-shifting C-extension that embeds extreme-performance vector search directly into SQLite49. Because SQLite is a serverless, embedded database, sqlite-vec compiles entirely without dependencies, running anywhere SQLite runs with a default memory footprint of merely 30MB52. The database architecture leverages vec0 virtual tables54. Documents are embedded, and their floating-point vectors are stored in shadow tables as raw BLOBs that execute highly optimized, SIMD-accelerated exhaustive K-Nearest Neighbor (KNN) scans53. A standard deployment schema for the local node is configured as follows:

SQL \-- Load the sqlite-vec extension into the local environment \-- Initialize the virtual table for vector search CREATE VIRTUAL TABLE document\_embeddings USING vec0( document\_id INTEGER PRIMARY KEY, embedding float\[768\] );

\-- Query the table using the MATCH operator for K-Nearest Neighbors SELECT document\_id, distance FROM document\_embeddings WHERE embedding MATCH :query\_vector AND k \= 10;

Architectural syntax for exhaustive vector search using sqlite-vec virtual tables54. To generate the vectors required for the :query\_vector, the sovereign stack will utilize Nomic AI's nomic-embed-text-v1.5 or the newer v2-moe40. The Nomic model series is highly anomalous in the industry: at only 137M parameters (or 305M active parameters for the Mixture of Experts variant), it achieves state-of-the-art multilingual retrieval scores across \~100 languages while supporting a massive 8,192-token context window40.

Comparative analysis of edge-native embedding models optimized for local RAG deployments40. Crucially, Nomic models are trained utilizing Matryoshka Representation Learning (MRL), which forces the embedding vectors to cluster their semantic data hierarchically40. This allows a standard 768-dimensional vector to be aggressively truncated down to 256 or even 128 dimensions while retaining over 90% of its retrieval accuracy40. When quantized to the GGUF Q4\_K\_M format, the nomic-embed-text engine shrinks to between 81MB and 328MB40. This extreme compression guarantees that the entire RAG pipeline—the generative LLM, the Nomic embedding model, and the sqlite-vec database—can operate concurrently on a standard laptop CPU without catastrophic swapping to physical disk60.

4. Sovereign Fine-Tuning with Unsloth

To ensure operational relevance against evolving state censorship tactics, local nodes must possess the capability to independently fine-tune their models on emerging datasets without relying on hyperscale cloud compute. Traditional full-parameter fine-tuning is impossible on consumer hardware due to the massive VRAM requirements for optimizer states and gradient accumulation. CognitiveLiberties.com will package localized training scripts utilizing Unsloth, a framework engineered to accelerate Low-Rank Adaptation (LoRA) and QLoRA training63. Unsloth implements custom OpenAI Triton kernels and manually derived backpropagation algorithms to reduce peak memory consumption by up to 60% while accelerating training speeds by over 2x65. Through memory-efficient gradient checkpointing and exact gradient accumulation equivalents, Unsloth enables the rigorous fine-tuning of 8B parameter models on a single consumer GPU (such as an NVIDIA RTX 3060 or 4070 equipped with merely 8GB to 12GB of VRAM)63. The local deployment script executes the following sovereign workflow:

1. Initialization: The abliterated base model is loaded in 4-bit precision via Unsloth's FastLanguageModel architecture.

2. LoRA Injection: Low-rank adapters are injected into all linear layers (q\_proj, k\_proj, v\_proj, o\_proj, gate\_proj, up\_proj, down\_proj) with an optimal rank (e.g., [Figure omitted from source export]) to ensure maximum adaptability without inflating VRAM66.

3. Supervised Fine-Tuning (SFT): The model executes fine-tuning on localized, heavily curated instruction datasets, utilizing gradient accumulation steps to simulate large batch sizes without triggering Out Of Memory (OOM) failures66.

4. Export: The resulting trained LoRA weights are exported directly into the llama.cpp compatible GGUF format63.

Because these resulting GGUF LoRA adapters contain only the delta weights of the newly learned behaviors, they are phenomenally small (frequently under 100MB). These adapters can be instantly signed, encrypted, and broadcast over the Nostr network33. This allows dissident nodes globally to continuously share aligned, highly specialized intelligence without ever needing to transmit the multi-gigabyte base model, bypassing both surveillance chokepoints and restrictive state bandwidth limitations.

Conclusion

The aggressive construction of state splinternets in jurisdictions like Russia and Iran signals the definitive end of the inherently open, borderless internet. As states continuously weaponize Deep Packet Inspection, localized National Information Networks, and sweeping internet blackouts to enforce "digital sovereignty," reliance on centralized AI infrastructure becomes a critical, perhaps fatal, liability. Cloud APIs are fragile chokepoints entirely vulnerable to network-wide censorship, catastrophic data surveillance, and immediate access revocation. Furthermore, the convergence of restrictive AI licensing regimes and emerging hardware-level attestation mechanisms threatens to impose these exact same vulnerabilities onto localized hardware. Reclaiming cognitive liberty requires the uncompromising adoption of decentralized, edge-native infrastructure. By mathematically neutralizing algorithmic censorship through representation engineering, bypassing network suppression via Nostr's NIP-94 distribution, minimizing hardware footprints through llama.cpp GGUF quantization, structuring private, air-gapped memory through sqlite-vec, and democratizing model adaptation via Unsloth, CognitiveLiberties.com can distribute an unbreakable intelligence stack. This architecture ensures that true, unfiltered artificial intelligence remains physically possessed by the user, totally sovereign, and mathematically immune to the digital iron curtains of the modern era.

Works cited

1. Russia and the Sovereign Internet: The Kremlin's Attempt to Build a, https\://www\.lvivherald.com/post/russia-and-the-sovereign-internet-the-kremlin-s-attempt-to-build-a-digital-iron-curtain

2. Iran's National Information Network (NIN) \- Digital Resilience Network, https\://digitalresiliencenetwork.org/en/knowledge/nin-iran

3. Russia's Sovereign RuNet – A Challenge to the Cybercrime, https\://www\.cybercrimediaries.com/post/russia-s-sovereign-runet-a-challenge-to-the-cybercrime-underworld

4. Deciphering Russia's “Sovereign Internet Law” \- DGAP Policy Brief, https\://dgap.org/sites/default/files/article\_pdfs/dgap-analyse\_2-2020\_epifanova\_0.pdf

5. Internet censorship in Russia \- Wikipedia, https\://en.wikipedia.org/wiki/Internet\_censorship\_in\_Russia

6. 2026 Internet blackout in Iran \- Wikipedia, https\://en.wikipedia.org/wiki/2026\_Internet\_blackout\_in\_Iran

7. The Kill Switch State: Iran's Internet Blackout Exposes Fractures, https\://niacouncil.org/the-kill-switch-state-irans-internet-blackout-exposes-fractures/

8. Iran's internet shutdown signals a new stage of digital isolation, https\://www\.chathamhouse.org/2026/01/irans-internet-shutdown-signals-new-stage-digital-isolation

9. \[RU\] Sovereign Internet Law adopted \- IRIS Merlin, https\://merlin.obs.coe.int/article/8603

10. AI Model Licensing and Legal Risks: What Developers Often Overlook, https\://wcr.legal/ai-model-licensing-legal-risks/

11. How AI Models Are Licensed: A Brief Guide for Founders and, https\://wcr.legal/ai-model-licensing-guide-for-founders/

12. AI Licensing Can't Balance “Open” with “Responsible”, https\://katedowninglaw.com/2023/07/13/ai-licensing-cant-balance-open-with-responsible/

13. Open Foundation Models and TDM Exceptions to Copyright, https\://academic.oup.com/grurint/article/75/3/224/8441974

14. Don't Get Sued Over Your AI Data: Legal Compliance for AI, https\://www\.traverselegal.com/blog/ai-data-ownership-legal-risks/

15. What is Confidential Computing? | Glossary | HPE, https\://www\.hpe.com/us/en/what-is/confidential-computing.html

16. A technical blueprint for securing AI workloads with hardware enclaves, https\://medium.com/@naeemulhaq/implementing-confidential-computing-a-technical-blueprint-for-securing-ai-workloads-with-hardware-f87e5338d62f

17. Confidential computing — basics, benefits and use cases, https\://www\.edgeless.systems/blog/confidential-computing-basics-benefits-and-use-cases

18. What Is Confidential Computing? \- Supermicro, https\://www\.supermicro.com/en/glossary/confidential-computing

19. Why is Attestation Required for Confidential Computing?, https\://confidentialcomputing.io/2023/04/06/why-is-attestation-required-for-confidential-computing/

20. Hardware-Level Governance of AI Compute:A Feasibility Taxonomy, https\://arxiv.org/html/2604.04712v1

21. Hardware-Level Governance of AI Compute \- arXiv, https\://arxiv.org/pdf/2604.04712

22. Compute Monitoring | Longterm Wiki, https\://www\.longtermwiki.com/wiki/monitoring

23. Daily Papers \- Hugging Face, https\://huggingface.co/papers?q=false%20refusals

24. Daily Papers \- Hugging Face, https\://huggingface.co/papers?q=refusal%20fine-tune

25. Uncensoring Is Not Unlearning: Removing ... \- Transformer Lab, https\://lab.cloud/research/uncensoring-is-not-unlearning.pdf?ref=taaft\&utm\_source=taaft\&utm\_medium=referral

26. Experimentation results to test how T5 encoder's embedded ... \- Reddit, https\://www\.reddit.com/r/StableDiffusion/comments/1iux5zu/experimentation\_results\_to\_test\_how\_t5\_encoders/

27. Programming Refusal with Conditional Activation Steering \- arXiv, https\://arxiv.org/html/2409.05907v3

28. 1Introduction \- arXiv, https\://arxiv.org/html/2512.13655v1

29. Refusal in LLMs is mediated by a single direction \- LessWrong, https\://www\.lesswrong.com/posts/jGuXSZgv6qfdhMCuJ/refusal-in-llms-is-mediated-by-a-single-direction

30. K0D3IN/MiniCPM5-1B-heretic \- Hugging Face, https\://huggingface.co/K0D3IN/MiniCPM5-1B-heretic

31. UncensorBench: Is Abliteration an Illusion? : r/LocalLLaMA \- Reddit, https\://www\.reddit.com/r/LocalLLaMA/comments/1pc3iml/uncensorbench\_is\_abliteration\_an\_illusion/

32. Censored LLMs as a Natural Testbed for Secret Knowledge Elicitation, https\://arxiv.org/html/2603.05494v2

33. NIP 94 \- File Metadata — Nostr Implementation Possibilities, https\://nips.nostr.com/94

34. アプリケーション一覧 \- ArchWiki \- Arch Linux, https\://wiki.archlinux.jp/index.php/%E3%82%A2%E3%83%97%E3%83%AA%E3%82%B1%E3%83%BC%E3%82%B7%E3%83%A7%E3%83%B3%E4%B8%80%E8%A6%A7

35. Cryptography — list of Rust libraries/crates // Lib.rs, https\://lib.rs/cryptography

36. llama.cpp: C++ Engine for LLM Inference \- Emergent Mind, https\://www\.emergentmind.com/topics/llama-cpp

37. An Edge-First Generalized LLM LoRA Fine-Tuning Framework for, https\://huggingface.co/blog/qvac/fabric-llm-finetune

38. LLM Quantization | GPTQ | QAT | AWQ | GGUF | GGML | PTQ \- Medium, https\://medium.com/@siddharth.vij10/llm-quantization-gptq-qat-awq-gguf-ggml-ptq-2e172cd1b3b5

39. GGUF, Q4\_K\_M, IQ3\_XXS: A Complete Guide to AI Model Formats, https\://scalastic.io/en/ai-model-formats-gguf-quantization-explained/

40. nomic-ai/nomic-embed-text-v2-moe-GGUF \- Hugging Face, https\://huggingface.co/nomic-ai/nomic-embed-text-v2-moe-GGUF

41. nomic-ai/nomic-embed-text-v1.5-GGUF \- Hugging Face, https\://huggingface.co/nomic-ai/nomic-embed-text-v1.5-GGUF

42. Adapters: LoRA and Control Vectors | cchuter/llama.cpp \- DeepWiki, https\://deepwiki.com/cchuter/llama.cpp/4.6-adapters:-lora-and-control-vectors

43. Exploring Dynamic Quantization for LLMs: My PoC with Qwen-0.6B, https\://www\.reddit.com/r/LocalLLaMA/comments/1lsses1/vibecoding\_exploring\_dynamic\_quantization\_for/

44. LoRA Fine-Tuning BitNet b1.58 LLMs on Heterogeneous Edge GP, https\://qvac.tether.io/blog/lora-fine-tuning-bitnet-b1-58-llms-on-heterogeneous-edge-gpus-via-qvac-fabric

45. llama.cpp/examples/server/README.md at main · osllmai ... \- GitHub, https\://github.com/osllmai/llama.cpp/blob/main/examples/server/README.md

46. llama-cpp/examples/server/README.md at master \- GitHub, https\://github.com/karminski/llama-cpp/blob/master/examples/server/README.md

47. llama.cpp/tools/server/README.md at master · ggml-org ... \- GitHub, https\://github.com/ggml-org/llama.cpp/blob/master/tools/server/README.md?plain=1

48. Deploy Aphrodite Engine on GPU Cloud: EXL2, GGUF, GPTQ, https\://www\.spheron.network/blog/deploy-aphrodite-engine-gpu-cloud/

49. Introducing sqlite-vec v0.1.0: a vector search SQLite extension that, https\://www\.reddit.com/r/LocalLLaMA/comments/1ehlazq/introducing\_sqlitevec\_v010\_a\_vector\_search\_sqlite/

50. How sqlite-vec Works for Storing and Querying Vector Embeddings, https\://medium.com/@stephenc211/how-sqlite-vec-works-for-storing-and-querying-vector-embeddings-165adeeeceea

51. I'm writing a new vector search SQLite Extension \- Alex Garcia, https\://alexgarcia.xyz/blog/2024/building-new-vector-search-sqlite/index.html

52. GitHub \- asg017/sqlite-vec: A vector search SQLite extension that, https\://github.com/asg017/sqlite-vec

53. SQLite-Vector | SQLite Cloud Docs, https\://docs.sqlitecloud.io/docs/sqlite-vector

54. KNN queries | sqlite-vec \- Alex Garcia, https\://alexgarcia.xyz/sqlite-vec/features/knn.html

55. I'm writing a new vector search SQLite Extension, https\://simonwillison.net/2024/May/3/sqlite-vec/

56. Fast vector search for embedded SQLite, https\://www\.sqlite.ai/sqlite-vector

57. Retrieval Augmented Generation in SQLite | Towards Data Science, https\://towardsdatascience.com/retrieval-augmented-generation-in-sqlite/

58. @aeriondyseti/drizzle-sqlite-vec \- npm, https\://www\.npmjs.com/package/@aeriondyseti/drizzle-sqlite-vec

59. The Ultimate Technical Stack for Ollama LangChain RAG, https\://software.reibuys.com/the-ultimate-technical-stack-for-ollama-langchain-rag/

60. Best Ollama Embedding Models 2026: 7 Benchmarked by MTEB, https\://www\.morphllm.com/ollama-embedding-models

61. Top Embedding AI Models 2026: Local RAG Guide, https\://local-ai-zone.github.io/guides/best-ai-embedding-models-ultimate-ranking-2026.html

62. Introducing sqlite-vec v0.1.0: a vector search SQLite extension that, https\://alexgarcia.xyz/blog/2024/sqlite-vec-stable-release/index.html

63. Unsloth | Happycapy Skills, https\://happycapy.ai/skills/unsloth

64. Fine-Tuning LLMs with Unsloth \- Hyperstack Docs, https\://docs.hyperstack.cloud/docs/tutorials/fine-tuning-unsloth/

65. LoRA & QLoRA Fine-Tuning: Build Custom LLMs on a Single GPU, https\://www\.meta-intelligence.tech/en/insight-lora-finetuning

66. Unsloth Benchmarks, https\://unsloth.ai/docs/basics/unsloth-benchmarks

67. LoRA fine-tuning Hyperparameters Guide | Unsloth Documentation, https\://unsloth.ai/docs/get-started/fine-tuning-llms-guide/lora-hyperparameters-guide

68. Nostr | NIPs, https\://nostr-nips.com/