Build record · practice
The Sovereign Stack
Proposal · independently initiated, not adopted
A technical stack can be local, open and place-based and still leave the questions of authority, knowledge boundaries, accountability, withdrawal and refusal with nowhere to live.
Controlled visual demonstration
Current live interface
This sandboxed preview shows the current public interface. Open the full site to use the build in its intended window.
Verified build record
What is actually running, and what it is not.
ProposalProposal · independently initiated, not adopted
The problem. A technical stack can be local, open and place-based and still leave the questions of authority, knowledge boundaries, accountability, withdrawal and refusal with nowhere to live.
What it does. Demonstrates a possible decision protocol, a living system record, a bounded pilot path and an optional learning translation, organised around the governance questions a community-authorised process would still have to answer.
Built on. A prototype application on Vercel, grounded in the recipient organisation's own published descriptions of its work.
What it does not establish. An independently prepared working proposal. It is not the recipient's product, policy, endorsement, approved protocol or community consent, and the substantive values and permissions would be theirs to define, not the author's.
This record is generated from the same inventory as the complete build index: the production URL was checked at the last regeneration, and the status line above repeats what the build reports about itself rather than restating an intention.