Sovereign Stack: Difference between revisions
Create dated and qualified project register |
Link new source-backed article |
||
| Line 1: | Line 1: | ||
'''Sovereign Stack''' is an index of tools meant to make local operation, diagnosis, repair, and technical ownership possible. It records what exists publicly and what is still a proposal. “Sovereignty” here means practical agency over a device and its data, not legal immunity. | '''Sovereign Stack''' is an index of tools meant to make local operation, diagnosis, repair, and technical ownership possible. It records what exists publicly and what is still a proposal. “Sovereignty” here means practical agency over a device and its data, not legal immunity. | ||
== Testable design question == | |||
* [[What does local-first operation actually mean?]] — a function-by-function offline test with security and recovery requirements. | |||
== Public project record == | == Public project record == | ||
Latest revision as of 18:53, 31 October 2026
Sovereign Stack is an index of tools meant to make local operation, diagnosis, repair, and technical ownership possible. It records what exists publicly and what is still a proposal. “Sovereignty” here means practical agency over a device and its data, not legal immunity.
Testable design question
[edit]- What does local-first operation actually mean? — a function-by-function offline test with security and recovery requirements.
Public project record
[edit]| Work | Status as of 30 October 2026 | Evidence and next step |
|---|---|---|
| Kinetic Torch | Evolving project; public documentation baseline | Public repository has README and safety/provenance files. Archived Kotlin source, verified build, and release are pending; off gesture unresolved. |
| Omni-Link | Design and architecture | Define the local communication interfaces, threat model, prototype, and test results before claiming operation. |
| Eidolon | Design and architecture | Publish bounded specifications and a demonstrable implementation before claiming a working system. |
| The Truth device | Proposed | Scope the device, components, local ownership model, and acceptance tests; no public release established here. |
| DTMB | Design and bench discussion | A consolidated build and measurements are not verified in the current record. |
| Omni-Industrial / Omni-Process | Proposed | Define use cases, safety boundaries, and measurable pilots. |
These descriptions are a dated status register, not a promise of availability. A plan in a private working document is not a public release. No partnership, certification, or deployment is implied by inclusion.
Release evidence
[edit]For each tool, add a public source or hardware design, license for the released files, reproducible build or fabrication steps, test matrix, known failures, and versioned changes. Describe what can run locally, what needs a service, what data leaves the device, and how an owner can diagnose and repair it. Aletheia:Article standards describes the evidence bar.
Related work
[edit]Repair Commons holds repair records. Open Research holds testable ideas and negative results. Systems Worth Building covers broader proposals that have not become deployable tools.