Authority & autonomy
How can increasing technical capability remain within explicit human authority?
Study whether clearly defined permission and resource boundaries reduce unauthorized actions in controlled computational settings.
Research / P0 — Founder · Project · Research
The Web∞ — Web Infinity research direction explores Governed Evolvable Technological Systems (GETS): how systems can evolve while keeping their meaning, responsibilities and evidence open to examination.
01 — Program overview
Technological systems change through new software, AI models, infrastructure, policies and people. Our research direction asks how these changes can be assessed without losing accountability or continuity.
Web∞ is the upstream technology architecture and systems-engineering framework originated by Kunakorn Sinkasem. Lumora provides the public context for this Founder-led research and future-institution development at P0.
GETS is a working research concept. The current foundation is a theory candidate and research-design baseline; it is not an established or externally validated scientific theory.
Lumora is currently a Founder-led future-institution project. It is not yet a Swiss legal person or nonprofit research institute. Research lead describes a project responsibility, not an accredited academic appointment.
02 — Current questions
Authority & autonomy
Study whether clearly defined permission and resource boundaries reduce unauthorized actions in controlled computational settings.
Change & compatibility
Investigate how to detect changes in meaning or behavior when implementations are substituted, and which compatibility conditions matter.
Failure & recovery
Examine whether preserved evidence and explicit conflict handling improve the reconstruction of failures and the evaluation of recovery.
Independent contexts
Explore the isolation of purpose, authority and data across systems that reuse a common technological foundation.
03 — Methodology
The research design separates engineering checks from scientific evaluation. These steps describe the intended method, not a completed experimental program.
Review prior work, define terms, identify assumptions and state what would count as a counterexample.
Set hypotheses, comparison conditions, measurements and exclusion criteria before inspecting outcomes.
Use synthetic computational cases and contrasting system contexts. Examine failure conditions and rival explanations alongside successful cases.
Record methods, versions, observations and limitations. Distinguish an internal engineering result from support for a broader research claim.
Develop disclosure-appropriate materials for future reproduction, independent study and peer scrutiny. Those stages remain pending.
04 — Selected public outputs
These public notes explain the research direction and its boundaries. They are project-authored summaries, not peer-reviewed papers or released experimental evidence.
Research note · 01 · September 2026
A concise account of the problem, research questions and proposed evaluation approach.
Read the research noteStatus note · 02 · September 2026
What is described here, what remains unvalidated, and how future findings should be distinguished from design intentions.
Read the evidence note05 — Research status