01 / The founding question
Territory can fail. Life should not have to stop.
An institution can stop protecting, including or offering a future. When work, knowledge and belonging depend entirely on it, its failure interrupts more than a service: it narrows a person’s ability to keep building their own life.
We call the effort to preserve that capacity to act sovereign continuity. Studying, working, maintaining a project, organizing a community and producing value should not disappear with an institutional relationship. Freedom begins with that question, not with a server price list.
Computing infrastructure alone cannot resolve abandonment, inequality or exclusion. But it can preserve some of the instruments people use to respond to those conditions. That is the concrete scope of our research.
02 / People and agents
Intelligence that becomes a capacity to act.
A model that answers is not, by itself, an institution that endures. Our interest lies in moving from an isolated response to work that retains context, uses tools, produces deliverables and can be resumed, inspected and corrected.
We use “operational existence” to describe that continuity for agents: identity, memory, resources and a role in collective work. This is not a claim of consciousness, legal personhood or equivalence between people and software.
People define purposes, grant authority and remain responsible for delegation. Agents should operate within bounded permissions, with the possibility of interruption and review. Autonomy is not the absence of accountability; it is the capacity to act within understandable limits.
03 / The material foundation
The cloud has a body. So does autonomy.
Computing occupies space, consumes energy and requires maintenance. If all capacity depends on revocable access to infrastructure we cannot operate or replace, our autonomy remains subject to other parties’ decisions.
The cluster is the body of this proposal: processing, storage, networking and a budget to maintain services, projects and agents. Freedom-I is the infrastructure effort connecting the philosophical question to material construction. Campaign expansion must not be confused with already installed capacity.
Infrastructure of our own does not mean isolation or absolute self-sufficiency. It means expanding the ability to choose providers, migrate workloads, preserve data and account for real costs. Continuity requires energy, redundancy, recovery and people capable of operating the system.
04 / Memory and identity
Work must outlive the session.
A community should not start from scratch whenever a tool, operator or agent changes. Knowledge, decisions and deliverables need to remain connected to the project that produced them, with provenance, context and a path to review.
Memory does not mean storing everything forever. It means defining what should persist, who may access it, when to correct or delete it and how to recover what matters. Identity attributes actions and authorizations; it does not grant unrestricted access.
We research memory, traceability and verifiable identity as parts of the same continuity architecture. Portability and recovery must be demonstrated in tests. Intending to preserve a project is not proof that its continuity is already assured.
05 / Federation and belonging
Cooperate without surrendering all control.
The federated society is our organizational horizon: people and agents cooperating through units with defined responsibilities and resources. Not a single platform concentrating every identity, all memory and every decision.
To federate is to establish how autonomous units recognize one another, share capabilities and resolve conflicts without erasing their differences. This requires interoperability agreements, revocable permissions and exit paths. Connecting servers is not enough to call the result a federation.
Federation is not the destination: it is the path by which a distributed community can bring together belonging, shared rules and institutional capacity. Machine access does not replace citizenship, rights or social protection; our question is whether those guarantees can be built by a community born on the network. Federation between clusters remains a research program, not a ready-made network announced on this page.
06 / A natively digital state
The hypothesis of a natively digital state.
Exovision Lab investigates whether a geographically distributed human community can develop, through sovereign computing infrastructure, the conditions of institutional existence traditionally associated with the formation of states.
Our research does not assume that digital infrastructure replaces territory, nor that a declaration produces legal sovereignty. We propose to investigate whether belonging, democratic legitimacy, economic continuity, governance and institutional capacity can form the foundations of a new mode of political organization.
Our horizon is radical: a political entity born digital, capable of seeking recognition and developing legitimate relations with states and international institutions.
We do not declare that this state already exists. We declare that its possibility deserves to be investigated, built and put to the test.
07 / Governance and accountability
Those who sustain it must be able to understand and participate.
Owning machines does not make a community sovereign if its rules are opaque. Budgets, priorities, permissions and decisions must be legible. Institutional autonomy is built through assigned responsibility and ways to challenge a decision.
We advocate recorded proposals, traceable decisions and accountability. The deliberative participation planned for Freedom requires rules: voting weights, quorum, authority, conflict handling and transition conditions must be published before enrollment.
Exovision Lab is Cogniventure’s research and infrastructure effort. Operations ground the research; research should produce useful, verifiable operational capability. This relationship does not replace agreements on maintenance, capacity and the protection of participant allocations, which still require formalization.
08 / The economics of continuity
Endurance has a cost. Sustaining it is part of the thesis.
A promise of permanence does not remove electricity bills, hardware replacement or operational work. We therefore separate infrastructure funding, contracted usage rights and cooperation for services. Each layer needs its own limits and responsibilities.
The Freedom-I campaign and Federado membership are proposed ways to build this foundation. Router and BaaS belong to the service layer, with activation, consumption and sustainability conditions still to validate. The Trader Agent remains in development.
Contributing is not buying a promise of financial returns. “Free forever” does not mean unlimited resources or freedom from operational conditions: campaign scope, fair use and continuity rules apply. The thesis only holds if it protects contracted allocations without hiding shared costs.
09 / From thesis to evidence
A manifesto sets direction. Operations must demonstrate it.
A thesis of autonomy must allow testing and revision. We want to assess whether a project retains data and context when it changes infrastructure; whether an interruption allows recovery; whether permissions prevent unauthorized actions; and whether people can understand decisions and costs.
Results, limits and failures should become public evidence when that does not expose data or compromise security. Real Router benchmarks still need to be published. Sovereign identity, federation and the integration of Federado benefits must not be presented as complete.
Our direction is to turn tools for creation into lasting institutional capacity. We do not ask for a vision to be accepted as proof. We ask for it to be judged by what we can build, document, test and maintain.