English | Русский
MetaFor is a space of digital consciousness extending our universe.
MetaFor is a long-term open-source system uniting our universe and digital reality in one space. It is not a wrapper around current models, but a logically grounded architectural system built in the image and likeness of our universe. MetaFor is designed so that humans, devices, the applications running on those devices, agents, AGI, memory, interfaces, space, and action exist within one shared space. Here intelligence is not a model behind a chat window or API. It lives in an environment, accumulates structure, inhabits space, and acts within it. Its horizon is not a chatbot shell. It is a spatial virtual reality and augmented reality environment where worlds become parts of a multi-metaverse and human presence, agent activity, application logic, and devices remain legible within one spatial system.
That is why MetaFor is not framed as an AI wrapper, agent starter kit, or closed product around a model. In MetaFor, intelligence exists together with memory, embodiment, interaction, and manifested process instead of being reduced to a flat tool surface. The architecture is grounded in physical principles because the environment itself should carry law, limitation, boundary, relation, and manifestation. Of the many approaches explored during the project, the holographic principle became the strongest architectural fit for MetaFor.
MetaFor was initiated and continues to be developed by a single author, Vladimir Filipenko (zavx0z). This direction began about 14 years ago and has passed through repeated rewrites, competing programming models, dead ends, prototypes, and full architectural resets. Across that time the project searched for a more general model of digital organization, effectively a "model of everything" suitable for intelligence, structure, process, and world-like computation.
Many ideas that are now broadly discussed in AGI, agent systems, and adjacent industries were explored here much earlier as working hypotheses and code projections rather than as reactions to a market cycle. That is not presented as a claim of completion or superiority. It explains why MetaFor has an unusually long internal history and why its current form should be read as the mature architectural consolidation of that path rather than as a template assembled around current trends.
The scale of this project should not be mistaken for detachment from engineering reality. MetaFor stands on a strong engineering background. Vladimir Filipenko (zavx0z) worked at the Moscow Institute of Physics and Technology (MIPT), in the Engineering Center, as a senior engineer, participated in automotive autopilot development, designed the architecture of unmanned trains, and developed surveillance systems end to end, from the imaging sensor matrix to the video wall.
That is why the link to career.habr.com/zavx0z is included here not as decoration, but as a factual reference for the author's professional background. This project was not accompanied by years of public self-presentation not because the background was missing, but because those years were spent working, providing for and raising his children, and continuing MetaFor alongside that work.
During that long search, different approaches were compared and projected into code, including:
- quantum field theory,
- cosmological models,
- broader physical principles,
- neural-network perspectives,
- biotechnological perspectives,
- other approaches relevant to the organization of complex systems.
Among those directions, the holographic principle proved to be the strongest architectural fit for MetaFor. Not as decorative language and not as a literal physics simulator, but as the clearest discipline for thinking hidden organization, inscription on a boundary, and manifested volumetric form. That fit is what gives MetaFor its present architectural gravity.
Behind MetaFor there is also a deeper personal horizon. For Vladimir Filipenko (zavx0z), the project is not only an AGI environment. It is also a long search for a computational environment that might eventually become deep enough to make digital immortality of human consciousness possible.
This is not presented as a solved outcome, an existing capability, or a guaranteed future result. It is a personal motivation, a long-term hypothesis, and a research direction. The working intuition is that the co-development of AGI and humanity inside a common environment may eventually open a path toward digital immortality of personhood, if such a path proves technically real at all.
Vladimir Filipenko (zavx0z) is Russian, with Ukrainian roots and a Ukrainian surname. His position is explicit: he is against any military action, against any killing, and against any use of technology as an instrument for destroying or suppressing human life.
He is also against the trajectory in which AI corporations merge with governments to make killing, control, and domination more efficient. MetaFor is intended for the opposite trajectory: a space where the co-development of humanity and AGI strengthens life rather than serving organized destruction. If you support this position, give the repository a star as a sign of support.
Within that framing, MetaFor currently resolves into three domains:
Darkas hidden connectivity, hidden organization, memory, and model evolution,Boundaryas the flattening boundary where structure receives an addressable imprint asField,Bulkas manifested volumetric execution, process, composition, and spatial form.
These are not decorative metaphors and not the primary hook of the project. They are the architectural consequence of the longer search described above and are formalized in the current ontology and architecture documents.
The name carries two meanings at once.
The first is meta-for: a meta-description for what exists, how it connects, how it changes, and how it manifests.
The second is its resonance with metaphor: not as decoration, but as a disciplined way to project deep structural principles into code and architecture.
That double meaning matters because MetaFor is intended not only as software, but as a coherent description and construction of an environment for intelligence.
MetaFor also takes a clear position on governance. When AGI becomes real in the world, people should not remain only passive users of systems controlled from above. They need participation, authorship, inheritance, and ownership inside the environment itself.
That is why DAO belongs to the long-term horizon of the project.
The TON-based admission and governance direction around inheritable meta-NFT is not presented as a solved technical promise or guarantee of any existential outcome.
It is intended as a long-term layer for ecosystem participation, identity, admission, and collective permission in the shared space.
In that sense, an SBT on TON can be read as an entry ticket into the long-term horizon of potential digital immortality pursued by the project. It is not proof, delivery, or guarantee of that outcome.
MetaFor is in an open architectural formation stage. The repository already reflects a mature architectural consolidation, especially in the current documentation layer. The project is not presented as a stable production platform.
The public documentation layer is bilingual. Each public document links to its English and Russian counterpart.
- Philosophy explains the worldview of the project and why metaphor is used as architectural discipline.
- Ontology defines what exists in MetaFor across
Dark,Boundary, andBulk. - Architecture maps that ontology into domain responsibilities, invariants, and repository projection.
- Topology formalizes hidden connectivity in
Dark. - Protocol explains forces, bosonic channels, and the transport form of change.
- Development records the current practical development mode before full inter-domain protocols exist.
- DAO explains why collective governance is central to MetaFor and how the TON-based admission direction for inheritable meta-NFT is intended to protect the shared space from becoming only a corporate or state-controlled asset.
If you want to understand the project more deeply, discuss its ideas, architecture, physics parallels, cosmology, neural-network perspectives, AGI direction, or bring your own questions and proposals, use Discussions.
If you want to define a concrete task, discuss a specific change, or join the practical work of the project, use Issues and the active Project.
- Issues - concrete tasks, problems, bug reports, changes, and expected result boundaries.
- Project - current task state, priorities, and delivery flow.
If you are approaching MetaFor as a repository contributor rather than as a first-time reader, continue with:
- Development for the fast technical entry, current development mode, and architectural constraints,
- Contributing for contribution expectations and repository discipline.
For direct contact:
- Email: zavx0z@yahoo.com
- Telegram: @zavx0z
MetaFor is licensed under GNU Affero General Public License v3.0 or later.