The eternal chronicle of thought
Living Manuskript
What do I want to build?
A research platform around the discrete space-time model (QoQ) and how it can be developed.
We transform theory into a living manuscript: a network of nodes (statements, definitions, mechanisms) and branches (proofs, tests, alternatives, critiques), where each step has an origin, context, and reference discipline.
Why is that?
The usual paper workflow does not work well for:
- long, multi-level models where the structure of dependencies is important;
- parallel lines of development (alternative conclusions, different assumptions);
- a combination of canon (the minimum that is fixed) and R&D (which changes constantly).
We are creating a different outline: not a static article, but a structured protocol for knowledge growth.
The main idea
- Concept QoQ sets the initial framework and language.
- Any statement is highlighted in Node.
- Any development/testing/dispute is highlighted in Branch.
- Each publication is recorded as a versioned artefact with a verifiable link to the content.
What are Node and Branch?
- Node — the meaningful unit: definition, postulate, rule, mechanism, observational conclusion, hypothesis.
- Branch — node development: calculation, simulation, verification, criticism, alternative interpretation, connection with the experiment.
How do I invite researchers?
No need to ‘believe’ — you can get involved in the development:
- propose a branch (alternative explanation / verification / criticism),
- clarify the node (formalisation / terms / dependencies),
- add a test (observations, calculations, simulations),
- build a bridge to existing theories and data.
The contribution is presented as a branch linked to specific nodes. This allows for constructive debate: it is clear what is being attacked and what is being proposed in its place.
How are verifiability and immutability organised? Blockchain?
The entire on-chain text is not stored byte by byte — it is expensive and unnecessary.
But we record cryptographic fingerprints (hash) and content addressing so that file substitution is visible.
Each artefact (Node / Branch) is published as:
content_hash,content_uri,- metadata: parents, version, commit date, status (canon / branch / R&D).
This makes the history unalterable: if the file is changed, the hash will change and will no longer match what is recorded in the registry.
What about monetisation?
Monetisation here is not a ‘promise of profitability,’ but rather a model of access and artefacts:
- licensing for derivative products (courses, visualisations, interactive demos).
- paid collectible artefacts (Node / Branch NFTs as cultural objects),
- sponsorship of specific branches (bounty for verification / simulation),
- paid ‘curated editions’ (collections of branches on a specific topic),
- share your ideas…
Living Manuskript
The eternal chronicle of thought