Unique editorial hero for Browser-Local Sovereign Tools.
Browser-Local Sovereign Tools: an original page-specific visual plate.

Local-first tools

Browser-Local Sovereign Tools

The safest cognitive tool is one that does not make private inquiry leave the machine unless the user explicitly chooses export.

Local-first No prompt leaves browser User-held custody Rule engine not person judgment
Read the Charter Open the Firewall Visual Atlas

Why local-first belongs in the Charter

Cognitive liberty is not only a legal promise. It is an architecture. Prompt logs, pasted system summaries, private drafts, legal questions, browser diagnostics, source records, and persona files become surveillance surfaces when they are sent to remote systems by default.

The browser-local reports show a practical path: deterministic rules, local storage, service workers, WebAssembly, local vector search, finite-state matching, and optional local models can produce serious triage without turning every prompt into a server-side record.

No prompt leaves by default.

Link to this page so others can find the original source.

How to link to this work

Circular source map linking text, institution, state, and machine.
Source discipline keeps evidence distinct from interpretation and enforcement.

Local pipeline

LayerRecommended approachCognitive-liberty reason
InputSanitize and process in browser memory.Avoid unnecessary disclosure of private notes.
Pattern detectionDeterministic dictionaries and finite-state matching.Make classification inspectable.
Semantic searchLocal embeddings or precomputed vectors.Avoid remote inference over sensitive text.
RulesDeterministic JSON/YAML rule engine.Keep the model from becoming the judge.
StorageIndexedDB, OPFS, SQLite-Wasm, export packets.User-held records and rollback.
NetworkOpt-in only, visible payload preview.Consent must be specific and revocable.
Mechanical eye and cognitive network used as a civic warning about machine judgment.
A probability score is not justice, and a classifier is not conscience.

Design prohibition

A local diagnostic may evaluate a use case, system risk, route, or artifact. It must not create a hidden user profile, moral score, future-danger label, trustworthiness grade, or reportable-topic record.

If remote assistance is enabled, the system should show exactly what will be sent, redact where possible, retain a local audit record, and provide a permanent off switch.

Mini manifest

{
  "tool": "browser-local-sovereign-tool",
  "defaults": {
    "network": "off",
    "prompt_retention": "local_only",
    "person_judgment": "prohibited",
    "source_mutation": "prohibited"
  },
  "user_controls": [
    "export",
    "delete",
    "rollback",
    "view_payload_before_remote_call"
  ]
}

Help others find this page

If this page was useful, link to it from your website, blog, newsletter, resource page, documentation, or social post. A public link helps the work remain discoverable after the feed moves on.

Canonical URL https://antichrist.net/zh-cn/browser-local-sovereign-tools/
How to link to this work

Related pages

Technical Implementation Toolkit

Builder guidance for refusal variance records, provenance manifests, source preservation, mental privacy consent, boundary logs, export packets, and machine-readable examples.

Source Preservation Contract Kit

A practical contract and artifact page for persona source custody, derivative records, boundary separation, fidelity warranties, portability, and remedies.

The archive studies symbols. It does not appoint targets. Review the Community Baseline and Editorial Policy before submitting dangerous or symbolic material.

Community Baseline / Editorial Policy