Human agency.
Your data. Your permissions.
A meaningful way to leave.
The Web,
made human.
An open protocol for independent people, nodes and services. Common rules. No mandatory centre.
An open protocol. Independent systems.A more human Web
01 / THE SHIFTHuman agency, by design.
From attention
to intention.
A better Web does not need
a more captive human.
AudiencePerson
PlatformPersonal space
EngagementMeaningful action
No attention tax.
Our reference environment avoids ads.
Providers disclose their own policies.
Open by design.
Documented interfaces.
Independent implementations.
Voluntary, always.
Participate. Disagree. Build.
No required worldview.
02 / IDENTITYGeometry gives structure. Motion reveals it.
The whole idea
is in the name.
Nothing is added.
The hidden structure is revealed.
01 / NAMEWEB V
02 / ESSENCEWV
03 / REVEALThree V forms
Three parts. One human.
A metaphor for wholeness.
Not a belief system required to participate.
SpiritDirection.
SoulConnection.
BodyAction.
03 / THE ECOSYSTEMWhy → What → How
One ecosystem.
Distinct roles.
01 / MEANING
Vilnism
A voluntary philosophy. Freedom, ethics and human agency; no required worldview.
02 / PROTOCOLWEB V
Open rules for identity, discovery, content and resource exchange.
03 / IMPLEMENTATIONTOS
One implementation for authorised tasks and resources, alongside independent compatible systems.
Civilization OS is the shared horizon — not a finished product. Explore the horizon
Explore all 22 projects and directions
Foundation, digital tools, research and culture. Each direction has a current stage, next step and connected projects.
Foundation
Stewards specifications, discussion and interoperability checks. It does not own the network or hold a general power to switch off other operators’ nodes.
DeskOS
An interface to the workspace: applications, files, AI and permissions. The protocol is not tied to one interface.
Civilization OS
A long-term application of open coordination to organisations, communities and physical resources.
THE WEBV PROTOCOLSpecification in development
Independent systems.
Shared contracts.
Independent addresses, verifiable content versions and voluntary interaction among people, nodes and services over available communication channels.
Identity and versions
A service keeps a verifiable identity while each content version has its own hash. Updates are signed; lost, replaced and revoked keys require separate procedures. A key is not a person or a right to govern others.
Directories that can be replaced
Home, the optional ID 0, search and bootstrap help participants find each other. They must not become permission authorities: direct addresses, independent directories and a choice of entry points are required.
Available communication channels
Discovery is separate from delivery. Internet, LAN, supported mesh and radio links have different limits. Delay-tolerant delivery stores a packet until a route exists; offline access covers locally available data and permitted operations.
Voluntary resources
A personal node, server or data centre may offer compute, storage or delivery with explicit consent and limits. Price, privacy, result verification and rental termination must be clear. Buying capacity does not buy political authority.
WebV compatibility does not require adopting Vilnism, using TOS, registering with this site or buying a mandatory token. Providers retain control of their own resources.
RESILIENCE AND CRITICAL MASSSpecification in development
Enough independence.
A real way to continue.
Critical mass means enough independent operators, replicas, routes, energy and local data. Registration counts do not demonstrate it. A network becomes autonomous within a tested scope when it can lose its initial site, bootstrap or provider and retain the required functions.
A meaningful independence test
Can independent operators still find a known service, verify its version and use available replicas after the original site or directory disappears? Can a separate client join from documentation? These are proofs to obtain, not claims established by this landing page.
Honest limits of autonomy
Without a channel there is no instant communication. Without a replica there is no available content. A key revocation may not yet have reached an isolated node; shared scarce resources cannot be spent twice. An ordinary HTTPS gateway retains its own DNS and hosting dependencies.
A data centre may be useful and efficient without becoming indispensable. Replicas that share one owner, electricity supply or upstream route may fail together.
04 / THE LEARNING LOOPIdeas meet lived experience.
DiscussResearchProposeBuildTestLearnHUMAN
EXPERIENCE
HUMANEXPERIENCE
A forum is
the beginning.
Not the boundary.
Turn a question into a system.
A question becomes a proposal. A prototype meets human experience. The evidence comes back.
Explore the discussion format01 / EXPERIENCE
People report.
Signals retain their source.
02 / CANON STUDIO
Knowledge remembers.
Proposals keep their history.
03 / AI FACTORY
Agents assist.
Humans approve public decisions.
One knowledge loop. No invisible authority. Proposed integration.
05 / DISCUSSIONNot a feed. A place to think together.
Discussion
with memory.
Not the loudest opinion.
The clearest path from question to decision.
WEB V / DISCUSSIONInteractive conceptTHE QUESTIONWho should own
Who should own
personal AI?
Can a person move their AI, memory and permissions without losing control or becoming locked in?
Explore the concept noteTHE QUESTIONCan identity exist
Can identity exist
without captivity?
How do we make identity portable and recoverable without turning every interaction into a permanent public record?
Explore the concept noteTHE QUESTIONCan media thrive
Can media thrive
without advertising?
What pays for creation, moderation and distribution when attention and purchased ranking are not for sale?
Explore the concept noteTHE QUESTIONCan your device become
Can your device become
infrastructure?
How can ordinary devices share useful capacity while their owners keep control of resources, privacy and participation?
Explore the concept note- 01Problem
- 02Evidence
- 03Trade-offs
- 04Proposal
- 05Review
A preview of the format, not a live forum. Posting and accounts will arrive with the discussion platform.
These founding concept notes are retained for context. Read the current protocol overview for the developed architecture.
06 / CONCEPT NOTESWorking positions. Open to challenge.
Papers that can
be challenged.
A starting point for research,
not a set of adopted standards.
WEBV–001The Human-Centered WebConcept note
Start with the person, not the platform.
What would the Web look like if human intention, rather than time spent, defined success?
Working position
People should understand what a system does, choose how it serves them, and retain a meaningful way to leave. Identity, data and permissions should be legible rather than hidden behind an account.
Open trade-off
Convenience can pull decisions back into central services. The work is to make human control usable, including for people who do not want to manage technical infrastructure.
Founding concept · Open for future review · Not an adopted standard
Related direction: The WebV protocolWEBV–002Personal Node ArchitectureConcept note
Your device can be part of the infrastructure.
How can an ordinary computer or supported phone contribute useful services without surrendering control?
Working position
A node should have an explicit role, visible resource limits and revocable permissions. Local work should remain useful when the wider network is unavailable. Shared resources must be opt-in.
Open trade-off
Battery, bandwidth, availability and trust differ between devices. A phone is not a server, and distributed capacity is not automatically free or reliable.
Founding concept · Open for future review · Not an adopted standard
Related direction: Personal Nodes & ComputeWEBV–003User-Owned IdentityConcept note
Continuity without captivity.
Can identity move between services without forcing people to give every service the same personal information?
Working position
Identity should support selective disclosure, explicit consent and recoverable access. People should be able to keep different roles and contexts separate where appropriate.
Open trade-off
Recovery, privacy and abuse prevention can conflict. No single key, biometric or identity model should be presented as a complete solution.
Founding concept · Open for future review · Not an adopted standard
Related direction: TOS Wallet conceptWEBV–004Advertising-Free EnvironmentsConcept note
No attention tax.
Can useful media and social spaces operate without selling attention or purchased ranking?
Working position
Value should come from useful tools, services and infrastructure. Creators should choose how their work is shared. Recommendations should serve declared interests and goals, not an undisclosed auction.
Open trade-off
Storage, moderation and distribution still cost money. An advertising-free model needs a visible, sustainable way to pay for them.
Founding concept · Open for future review · Not an adopted standard
Related direction: Personal Space & Creator MediaWEBV–005Personal AI SovereigntyConcept note
Assistance without invisible authority.
Can a person move their AI, memory and permissions without losing control or becoming locked in?
Working position
Personal AI should work within understandable permissions. Important actions need review proportional to their consequences. People should be able to inspect, correct and export relevant memory.
Open trade-off
Local models, remote models and sensitive data need different boundaries. Human approval must be meaningful, not a button people are trained to ignore.
Founding concept · Open for future review · Not an adopted standard
Related direction: AI Factory07 / CIVILIZATION OSA long horizon, not a promised outcome.
From a personal node
to a shared horizon.
01
PersonPersonal tools, data and agency.
02
CommunityShared knowledge. Voluntary coordination.
03
CivilizationA research horizon we build toward together.
PERSON → COMMUNITY → CIVILIZATIONOne self-hosted implementation connecting people, permitted resources and AI. DeskOS provides its workspace interface.
Personal nodesAI FactoryWork + GoalsWallet + PayMedia + SocialAutomation
Modules are at different stages. This is a direction map, not a release checklist.
08 / TRUSTThe name is a responsibility.
A foundation
earns trust.
Not a certificate of neutrality.
We are a founding-stage initiative.
Governance must develop in the open.
01
Visible decisions.
Who proposes, reviews and decides?
02
Visible funding.
Who pays, and what influence do they have?
03
Real participation.
Can others disagree, contribute and build?
NOW
Open specification.
Published principles, architecture and independent implementation goals.
NEXT
Independent evidence.
Compatible clients. Replaceable directories. Recovery after disconnection.
OVER TIME
Resilient participation.
Independent operators, replicas, channels and accountable stewardship.
QUESTIONSSpecification in development
Understand the choices.
Must I adopt Vilnism or hold a token?
No. Protocol compatibility is not ideological membership. Basic access must not require a mandatory token; particular resources may have a price and their owner’s terms.
Will every node store every publication?
No. Owners decide what to store and relay. Availability depends on permitted replicas, retention periods and payment or voluntary support. Independent publication does not impose a hosting obligation on someone else’s server.
Can AI change the rules or replicate itself?
AI acts only within delegated authority. Genesis means permitted deployment and updates on authorised resources. Publishing a rule does not replace adoption by a community; consequential decisions require explanations and a path to appeal.
Is the decentralised global network already running?
Constitutional principles, architecture and an implementation direction are published. An open global network, interchangeability of independent clients and all transport modes still require practical validation. This site is an information entry point, not a membership registry or network centre.
STATUS AND PARTICIPATIONSpecification in development
Explore. Challenge.
Build independently.
Constitutional principles, architecture and an implementation direction are published. An open global network, interchangeability of independent clients and all transport modes still require practical validation. This site is an information entry point, not a membership registry or network centre.
People and communities
Read the constitutional principles, challenge unclear rules and test whether consent, explanation and exit remain usable. You can use compatible technology without joining a philosophy.
Implementers
Build independent clients from open contracts. Document addressing, recovery, interoperability, disconnects and reconciliation. A passing integrity check is not proof that a rule is legitimate.
Operators and data centres
Prepare opt-in pilots for compute, storage or relay capacity. Set resource limits, pricing, privacy boundaries and termination rules. This informational site does not enrol machines or accept payments.
Researchers and stewards
Contribute evidence, reproduce results and improve specifications. The discussion interface is a concept preview; published documents are not automatically adopted rules.
DOWNLOADSSpecification in development
Read the vision.
Explore the sources.
Download the current protocol overview · Markdown ↓
Download full Ukrainian specification · Markdown ↓ · Download Ukrainian test criteria · Markdown ↓
The presentation and overview are companion material. Constitutional text, research notes and local adoption retain their separate authority and status.
Explore. Challenge.
Build.
Inspired by Vilnism.
Open to independent thought.