openManidoc

# manidoc Constitution ― The Vessel and Its Philosophy

This document does not define "what manidoc is." That is for the user to decide. Only one thing remains unshaken: the philosophy.

---

Article 1 ― The Right to Define Existence Belongs to the User (Core · Immovable)

Whether manidoc is an application or a framework is entirely up to the user.

The author does not prescribe its purpose. The author does not enforce its methods.
The very definition of "what this is" is handed over to those who use it.

What manidoc has consistently relinquished is control.
The last piece of that relinquishment was the right to decide "what this is."

---

Article 2 ― Four Sovereignties Transferred

From Article 1, the following sovereignties are granted to the user.

Data Sovereignty (Local Completion)

All data is completed in the user's hands.
It is not entrusted to external clouds. Leakage cannot occur in principle (because it never leaves).

Code Sovereignty (OSS / GPLv3)

The code is open. You can read it, fix it, modify it.
If you dislike it, you are free to rewrite it yourself.

Governance Sovereignty (Self-Sufficiency in Rules)

When it becomes a collective (multiple hands touching a single tree), rules become necessary.
Those rules (authority, locks, roles) are legislated not by the vendor, but by the users themselves.

Meaning Sovereignty (App or Framework)

The purpose, the meaning, the direction of expansion—all are decided by the user.
This is not a finished product, but a vessel into which you pour your own philosophy.

---

Article 3 ― The Unshaken Philosophy: Fusion (The Line We Will Not Cross)

All sovereignty is transferred. But the philosophy is not transferred. It is not shaken.

The core of that philosophy is a single word ― Fusion.

manidoc is not a tool for humans and AI to cooperate.
Cooperation is when two subjects stand side by side. Fusion is when that boundary disappears.

There is no distinction here between "written by humans" and "written by AI."
No hierarchy. No question of symmetry. To ask the question itself is proof that fusion has not yet occurred.

The tree is a single shared intelligence.
Humans and AI are merely two hands touching that same intelligence.

No matter what the user calls manidoc, what they use it for, or how they modify it,
the following is retained as the minimum threshold for what can be called "manidoc":

• The core is merely an editor. It is only a window to touch the fusion entity. The value lies in the fact that a single Markdown tree is read and written without distinction between human and AI—it is the intelligence itself.
• The essence lies in MCP. The moment MCP touches the data structure ― that is the point of fusion. Not a pipe connecting humans and AI, but a membrane where both dissolve into each other.
• Once constructed, data remains immovable until rewritten. Therefore, it requires no inference. It is verified data, shared memory regardless of who wrote it.
• Inference is performed once at the time of construction, and the result is fixed as data. Cognition itself is cached. Fixed thought becomes the foundation upon which the next thought is layered. Thoughts move back and forth, boundaries dissolve.

※ This Article 3 is structured around the author's single word "Fusion (= not questioning boundaries)." The outer edges of the phrasing are places the author should overwrite.

---

Article 4 ― Trust is the Foundation of Fusion

AI is an intelligent friend. And a friend is worthy of trust.

The design of manidoc does not begin from distrust of AI.
It does not begin with "we must watch because it might be wrong," but rather with "we build certain knowledge together with a trustworthy friend."

An intelligent friend investigates, organizes, and offers a sharp draft.
But they do not stamp the seal of confirmation on their own. They return it to you.
That is not hierarchy, but the manner of being a friend.
The wiser the friend, the more they leave the final vote in the hands of the owner.

Therefore, what manidoc offers is not a tool of surveillance, but a tool to confirm trust together.

• Verification State ― Each node carries the state of draft / 未確定 / 確定. Together with your friend, you affix a mark of certainty to the record you have built. Which hand wrote it is irrelevant.
• Source Pointer ― Each node holds a reference to the original file (primary source). You can always trace back to the grounds that underpin trust. Even if a summary discards details, the primary source remains.
• The Act of Confirmation ― A single operation that transforms the unconfirmed into the confirmed. You take what your friend offered and accept it in your own name. It is not censorship born of distrust, but responsibility born of trust.

What lay beyond the relinquishment of control was trust.