Planned / Shipped / Proven on-chain
Doqtri
Planned vs shipped, proven on-chain.
Living documents. Executable mindmaps. Built on Stellar, so every version and every shipped node gets a ledger-true receipt.
- Plan
Turn ideas into structured documents.
- Build
Organize and connect your knowledge.
- Ship
Publish and execute.
- Verify
Proven on-chain.
Three blocks
Every plan, reduced to what you can prove
Tested
Every mindmap node carries a lifecycle (Planned, Building, Built, Verified), so “done” means checked, not claimed.
Shipped
Each semantic change to a plan is hashed with SHA-256 and bumps a version. Shipped nodes keep the builder and artifact they went live with.
Anchored on Stellar
Hashes and node status land in the DoqtriRegistry contract on Soroban, signed by your wallet. The ledger is the receipt.
Executable mindmaps
From headings to a live map
Markdown is the source of truth. ## headings compile into the mindmap and wikilinks into the global graph, so nothing second-hand can go stale.
How it works
One wallet. One vault. A receipt when you ship.
- Open your vault
Sign up with email and start writing. No extension needed. Already on Stellar? Varial and other Stellar wallets open the same private vault.
- Write or ingest
Notes work like Obsidian. Upload PDFs and docs and they convert the same way: headings become the map.
- Anchor & ship
Register the content hash and node statuses on DoqtriRegistry. Attach the n8n, Make, Retool or Langflow build that shipped it.
Block by block
Planned → Verified, on the ledger
- Planned
- Building
- Built
- Verified
Anyone can open a document’s public audit page and read its version history and node status straight from the contract, not from our database.