@meddleware/docs 0.0.2 → 0.0.4

package/CHANGELOG.md

@@ -2,6 +2,28 @@
 
 All notable changes to `@meddleware/docs` are documented here.
 
+## [0.0.4] — 2026-09-17
+
+Heading cleanup and naming improvements.
+
+- Renamed `using.md` → `walkthrough.md` across all three tool sections (Walrus Storage, Sealed Storage, Access Gate); URLs updated accordingly
+- Replaced all `# Feature — noun` H1 patterns with clean unhyphenated titles (`# Using Walrus Storage`, `# DAO reference`, `# Sealed Storage policies`, etc.)
+- Sidebar and "Next" section links updated to "Walkthrough"
+- Removed "fundraising/" qualifier from DAO governance placeholder copy
+
+## [0.0.3] — 2026-09-17
+
+Restructured to a blockchain-agnostic architecture with Sui as the first active chain.
+
+- All Sui content moved under `/blockchain/sui/` URL hierarchy
+- New blockchain-agnostic home page — hero + Sui card + "more blockchains coming soon" card
+- New `/blockchain/` chain picker landing page
+- New `/blockchain/sui/` Sui section landing page
+- Navbar: `Blockchain` dropdown (Active / Coming soon groups) + `Sui Tools` dropdown
+- Sidebar: per-path keyed — full Sui sidebar under `/blockchain/sui/`, minimal chain sidebar under `/blockchain/`
+- Removed all references to the inactive `dev.meddleware.co.uk` URL; replaced with "forthcoming developer documentation"
+- Bumped gen-api autodoc output paths to match new `/blockchain/sui/` hierarchy
+
 ## [0.0.1] — 2026-09-17
 
 Initial release. VitePress documentation site for `docs.meddleware.co.uk` covering the four

package/docs/.vitepress/config.ts

@@ -1,15 +1,15 @@
 import { defineConfig } from 'vitepress'
 import { fileURLToPath } from 'node:url'
 
-// User-facing documentation for the Meddleware Sui tools. One site, one section per service.
-// Output is pinned to the repo-root dist/ so the Dockerfile's `COPY --from=build /app/dist`
-// (the shared static-server image pattern) works unchanged.
+// User-facing documentation for the Meddleware developer tools. Blockchain-agnostic site with
+// per-chain sections; Sui is the first active chain. Output is pinned to the repo-root dist/ so
+// the Dockerfile's `COPY --from=build /app/dist` (shared static-server pattern) works unchanged.
 const outDir = fileURLToPath(new URL('../../dist', import.meta.url))
 
 export default defineConfig({
   title: 'Meddleware Docs',
   description:
-    'How to use the Meddleware Sui tools — the DAO console, Walrus Storage, Sealed Storage, and Access Gate.',
+    'Developer tools for decentralised applications — documentation for the Meddleware Sui platform and beyond.',
   lang: 'en-GB',
   outDir,
   cleanUrls: true,
@@ -25,13 +25,21 @@ export default defineConfig({
     search: { provider: 'local' },
 
     nav: [
-      { text: 'Start here', link: '/getting-started' },
-      { text: 'DAO', link: '/dao/' },
-      { text: 'Walrus Storage', link: '/walrus-storage/' },
-      { text: 'Sealed Storage', link: '/sealed-storage/' },
-      { text: 'Access Gate', link: '/access-gate/' },
       {
-        text: 'Tools',
+        text: 'Blockchain',
+        items: [
+          {
+            text: 'Active',
+            items: [{ text: 'Sui', link: '/blockchain/sui/' }],
+          },
+          {
+            text: 'Coming soon',
+            items: [{ text: 'More blockchains', link: '/blockchain/' }],
+          },
+        ],
+      },
+      {
+        text: 'Sui Tools',
         items: [
           { text: 'Tools hub', link: 'https://sui.meddleware.co.uk' },
           { text: 'DAO console', link: 'https://sui-dao.meddleware.co.uk' },
@@ -43,49 +51,58 @@ export default defineConfig({
     ],
 
     sidebar: {
-      '/': [
+      '/blockchain/sui/': [
         {
-          text: 'Introduction',
+          text: 'Sui',
           items: [
-            { text: 'Overview', link: '/' },
-            { text: 'Getting started', link: '/getting-started' },
-            { text: 'How the tools fit together', link: '/architecture' },
+            { text: 'Overview', link: '/blockchain/sui/' },
+            { text: 'Getting started', link: '/blockchain/sui/getting-started' },
+            { text: 'How the tools fit together', link: '/blockchain/sui/architecture' },
           ],
         },
         {
           text: 'DAO',
           collapsed: false,
           items: [
-            { text: 'Overview', link: '/dao/' },
-            { text: 'Reference', link: '/dao/reference' },
+            { text: 'Overview', link: '/blockchain/sui/dao/' },
+            { text: 'Reference', link: '/blockchain/sui/dao/reference' },
           ],
         },
         {
           text: 'Walrus Storage',
           collapsed: false,
           items: [
-            { text: 'Overview', link: '/walrus-storage/' },
-            { text: 'Using it', link: '/walrus-storage/using' },
-            { text: 'Reference', link: '/walrus-storage/reference' },
+            { text: 'Overview', link: '/blockchain/sui/walrus-storage/' },
+            { text: 'Walkthrough', link: '/blockchain/sui/walrus-storage/walkthrough' },
+            { text: 'Reference', link: '/blockchain/sui/walrus-storage/reference' },
           ],
         },
         {
           text: 'Sealed Storage',
           collapsed: false,
           items: [
-            { text: 'Overview', link: '/sealed-storage/' },
-            { text: 'Using it', link: '/sealed-storage/using' },
-            { text: 'Policies', link: '/sealed-storage/policies' },
-            { text: 'Reference', link: '/sealed-storage/reference' },
+            { text: 'Overview', link: '/blockchain/sui/sealed-storage/' },
+            { text: 'Walkthrough', link: '/blockchain/sui/sealed-storage/walkthrough' },
+            { text: 'Policies', link: '/blockchain/sui/sealed-storage/policies' },
+            { text: 'Reference', link: '/blockchain/sui/sealed-storage/reference' },
           ],
         },
         {
           text: 'Access Gate',
           collapsed: false,
           items: [
-            { text: 'Overview', link: '/access-gate/' },
-            { text: 'Using it', link: '/access-gate/using' },
-            { text: 'Reference', link: '/access-gate/reference' },
+            { text: 'Overview', link: '/blockchain/sui/access-gate/' },
+            { text: 'Walkthrough', link: '/blockchain/sui/access-gate/walkthrough' },
+            { text: 'Reference', link: '/blockchain/sui/access-gate/reference' },
+          ],
+        },
+      ],
+      '/blockchain/': [
+        {
+          text: 'Blockchains',
+          items: [
+            { text: 'Overview', link: '/blockchain/' },
+            { text: 'Sui', link: '/blockchain/sui/' },
           ],
         },
       ],
@@ -94,7 +111,7 @@ export default defineConfig({
     socialLinks: [{ icon: 'github', link: 'https://github.com/meddleware-org' }],
 
     footer: {
-      message: 'Documentation for the Meddleware Sui tools.',
+      message: 'Documentation for the Meddleware developer tools.',
       copyright: 'Meddleware · 0BSD',
     },
   },

package/docs/blockchain/index.md

@@ -0,0 +1,18 @@
+# Blockchains
+
+Meddleware builds developer tools across blockchain ecosystems. This page is your starting point for
+blockchain-specific documentation.
+
+## Available now
+
+### Sui
+
+Four tools, one connected platform — decentralised storage, threshold encryption, NFT access control,
+and a transparent DAO console. Built for Sui's object model and Walrus decentralised storage.
+
+**[Go to the Sui docs →](/blockchain/sui/)**
+
+## Coming soon
+
+More blockchain ecosystems are being evaluated. The platform is designed from the ground up to be
+blockchain-agnostic, so new chains can be added without changing the existing tooling.

package/docs/{access-gate → blockchain/sui/access-gate}/api/index.md

@@ -5,6 +5,7 @@
 - [AccessGateConfig](interfaces/AccessGateConfig.md)
 - [AccessProof](interfaces/AccessProof.md)
 - [Challenge](interfaces/Challenge.md)
+- [CoreObject](interfaces/CoreObject.md)
 - [GateAdminContext](interfaces/GateAdminContext.md)
 - [OwnedAccessNft](interfaces/OwnedAccessNft.md)
 - [OwnedGate](interfaces/OwnedGate.md)

package/docs/blockchain/sui/access-gate/api/interfaces/CoreObject.md

@@ -0,0 +1,31 @@
+# Interface: CoreObject
+
+Defined in: types.ts:104
+
+A single owned/read object as returned by the unified core API (`SuiGrpcClient`): the id and
+Move struct type are top-level; the struct fields come back under `json` (opt-in). Kept as a
+structural subset so any client exposing the core API satisfies it without importing the SDK.
+
+## Properties
+
+### json?
+
+> `optional` **json?**: `Record`\<`string`, `unknown`\>
+
+Defined in: types.ts:107
+
+***
+
+### objectId
+
+> **objectId**: `string`
+
+Defined in: types.ts:105
+
+***
+
+### type?
+
+> `optional` **type?**: `string`
+
+Defined in: types.ts:106

package/docs/{access-gate → blockchain/sui/access-gate}/api/interfaces/OwnedObjectsClient.md

@@ -14,7 +14,7 @@ Defined in: types.ts:112
 
 #### listOwnedObjects()
 
-> **listOwnedObjects**(`options`): `Promise`\<\{ `cursor`: `string`; `hasNextPage`: `boolean`; `objects`: `CoreObject`[]; \}\>
+> **listOwnedObjects**(`options`): `Promise`\<\{ `cursor`: `string`; `hasNextPage`: `boolean`; `objects`: [`CoreObject`](CoreObject.md)[]; \}\>
 
 ##### Parameters
 
@@ -46,4 +46,4 @@ Defined in: types.ts:112
 
 ##### Returns
 
-`Promise`\<\{ `cursor`: `string`; `hasNextPage`: `boolean`; `objects`: `CoreObject`[]; \}\>
+`Promise`\<\{ `cursor`: `string`; `hasNextPage`: `boolean`; `objects`: [`CoreObject`](CoreObject.md)[]; \}\>

package/docs/{access-gate → blockchain/sui/access-gate}/api/interfaces/SuiObjectClient.md

@@ -14,7 +14,7 @@ Defined in: types.ts:125
 
 #### getObject()
 
-> **getObject**(`options`): `Promise`\<\{ `object`: `CoreObject`; \}\>
+> **getObject**(`options`): `Promise`\<\{ `object`: [`CoreObject`](CoreObject.md); \}\>
 
 ##### Parameters
 
@@ -34,4 +34,4 @@ Defined in: types.ts:125
 
 ##### Returns
 
-`Promise`\<\{ `object`: `CoreObject`; \}\>
+`Promise`\<\{ `object`: [`CoreObject`](CoreObject.md); \}\>

package/docs/blockchain/sui/access-gate/api/typedoc-sidebar.json

@@ -0,0 +1 @@
+[{"text":"Interfaces","collapsed":true,"items":[{"text":"AccessGateConfig","link":"/docs/blockchain/sui/access-gate/api/interfaces/AccessGateConfig.md"},{"text":"AccessProof","link":"/docs/blockchain/sui/access-gate/api/interfaces/AccessProof.md"},{"text":"Challenge","link":"/docs/blockchain/sui/access-gate/api/interfaces/Challenge.md"},{"text":"CoreObject","link":"/docs/blockchain/sui/access-gate/api/interfaces/CoreObject.md"},{"text":"GateAdminContext","link":"/docs/blockchain/sui/access-gate/api/interfaces/GateAdminContext.md"},{"text":"OwnedAccessNft","link":"/docs/blockchain/sui/access-gate/api/interfaces/OwnedAccessNft.md"},{"text":"OwnedGate","link":"/docs/blockchain/sui/access-gate/api/interfaces/OwnedGate.md"},{"text":"OwnedObjectsClient","link":"/docs/blockchain/sui/access-gate/api/interfaces/OwnedObjectsClient.md"},{"text":"SuiObjectClient","link":"/docs/blockchain/sui/access-gate/api/interfaces/SuiObjectClient.md"}]},{"text":"Type Aliases","collapsed":true,"items":[{"text":"PersonalMessageSigner","link":"/docs/blockchain/sui/access-gate/api/type-aliases/PersonalMessageSigner.md"}]},{"text":"Functions","collapsed":true,"items":[{"text":"buildAccessProof","link":"/docs/blockchain/sui/access-gate/api/functions/buildAccessProof.md"},{"text":"buildAirdropTx","link":"/docs/blockchain/sui/access-gate/api/functions/buildAirdropTx.md"},{"text":"buildConsumeTx","link":"/docs/blockchain/sui/access-gate/api/functions/buildConsumeTx.md"},{"text":"buildCreateGateTx","link":"/docs/blockchain/sui/access-gate/api/functions/buildCreateGateTx.md"},{"text":"buildMakeGateImmutableTx","link":"/docs/blockchain/sui/access-gate/api/functions/buildMakeGateImmutableTx.md"},{"text":"buildPurchaseTx","link":"/docs/blockchain/sui/access-gate/api/functions/buildPurchaseTx.md"},{"text":"buildSetAutoBurnAtZeroTx","link":"/docs/blockchain/sui/access-gate/api/functions/buildSetAutoBurnAtZeroTx.md"},{"text":"buildSetDefaultUsesTx","link":"/docs/blockchain/sui/access-gate/api/functions/buildSetDefaultUsesTx.md"},{"text":"buildSetNftDescriptionTx","link":"/docs/blockchain/sui/access-gate/api/functions/buildSetNftDescriptionTx.md"},{"text":"buildSetNftImageUrlTx","link":"/docs/blockchain/sui/access-gate/api/functions/buildSetNftImageUrlTx.md"},{"text":"buildSetNftNameTx","link":"/docs/blockchain/sui/access-gate/api/functions/buildSetNftNameTx.md"},{"text":"buildSetPausedTx","link":"/docs/blockchain/sui/access-gate/api/functions/buildSetPausedTx.md"},{"text":"buildSetPaymentRecipientTx","link":"/docs/blockchain/sui/access-gate/api/functions/buildSetPaymentRecipientTx.md"},{"text":"buildSetPriceTx","link":"/docs/blockchain/sui/access-gate/api/functions/buildSetPriceTx.md"},{"text":"buildSetSoulboundTx","link":"/docs/blockchain/sui/access-gate/api/functions/buildSetSoulboundTx.md"},{"text":"decodeAccessProof","link":"/docs/blockchain/sui/access-gate/api/functions/decodeAccessProof.md"},{"text":"encodeAccessProof","link":"/docs/blockchain/sui/access-gate/api/functions/encodeAccessProof.md"},{"text":"fetchAccessNftById","link":"/docs/blockchain/sui/access-gate/api/functions/fetchAccessNftById.md"},{"text":"fetchAccessNfts","link":"/docs/blockchain/sui/access-gate/api/functions/fetchAccessNfts.md"},{"text":"fetchAdminCaps","link":"/docs/blockchain/sui/access-gate/api/functions/fetchAdminCaps.md"},{"text":"fetchChallenge","link":"/docs/blockchain/sui/access-gate/api/functions/fetchChallenge.md"},{"text":"fetchGate","link":"/docs/blockchain/sui/access-gate/api/functions/fetchGate.md"},{"text":"fetchOwnedGates","link":"/docs/blockchain/sui/access-gate/api/functions/fetchOwnedGates.md"},{"text":"ownsAccessNft","link":"/docs/blockchain/sui/access-gate/api/functions/ownsAccessNft.md"},{"text":"parseAdminCap","link":"/docs/blockchain/sui/access-gate/api/functions/parseAdminCap.md"},{"text":"parseGate","link":"/docs/blockchain/sui/access-gate/api/functions/parseGate.md"},{"text":"parseOwnedAccessNft","link":"/docs/blockchain/sui/access-gate/api/functions/parseOwnedAccessNft.md"},{"text":"personalMessageForNonce","link":"/docs/blockchain/sui/access-gate/api/functions/personalMessageForNonce.md"}]}]

package/docs/{access-gate → blockchain/sui/access-gate}/index.md

@@ -19,8 +19,8 @@ There are two perspectives:
 
 - You want to **sell access** — a paid community, premium content, a members' area.
 - You want to **gate an API or app** behind on-chain ownership (pair it with the
-  [nft-gate gateway](/access-gate/reference), which puts any HTTP service behind a gate).
-- You want to gate **encrypted content** — combine it with [Sealed Storage](/sealed-storage/), where
+  [nft-gate gateway](/blockchain/sui/access-gate/reference), which puts any HTTP service behind a gate).
+- You want to gate **encrypted content** — combine it with [Sealed Storage](/blockchain/sui/sealed-storage/), where
   a pass becomes the key.
 - You want **single-use tickets** or **memberships** represented as NFTs.
 
@@ -52,10 +52,10 @@ identity and not resold. The non-transferability is enforced at the contract lev
 
 Every purchase routes a commission (in basis points, capped on-chain at 10%) to the platform
 treasury; the rest goes to the operator. The rate is set in shared on-chain config and shown in the
-[DAO console](/dao/). Operators don't set the commission — only the price.
+[DAO console](/blockchain/sui/dao/). Operators don't set the commission — only the price.
 
 ## Next
 
-- **[Using it](/access-gate/using)** — create and manage a gate; buy and use a pass.
-- **[Reference](/access-gate/reference)** — objects, entry functions, events, the gateway, and the
+- **[Walkthrough](/blockchain/sui/access-gate/walkthrough)** — create and manage a gate; buy and use a pass.
+- **[Reference](/blockchain/sui/access-gate/reference)** — objects, entry functions, events, the gateway, and the
   SDK API.

package/docs/{access-gate → blockchain/sui/access-gate}/reference.md

@@ -1,4 +1,4 @@
-# Access Gate — reference
+# Access Gate reference
 
 The on-chain `access_gate` contract, its gateway, and the client SDK. Move tables are curated from
 source; the TypeScript SDK reference is [auto-generated](#sdk-api).
@@ -67,7 +67,7 @@ Owned capability authorising management of one gate (`{ gate_id }`). Authorisati
 ::: warning Event pruning
 Sui testnet prunes old events after ~3 months. Systems that need a reliable gate list should read
 **`AdminCap` ownership → `Gate`** rather than replaying `GateCreatedEvent` (this is what the
-[DAO console](/dao/) does).
+[DAO console](/blockchain/sui/dao/) does).
 :::
 
 ## Error codes
@@ -94,7 +94,7 @@ signed proof and on-chain pass ownership, failing **closed** on any ambiguity.
 
 The gateway consumes the nonce immediately (single-use replay protection) and, for single-use passes,
 verifies the on-chain consumption by digest. Two wire-identical implementations exist (Cloudflare
-Workers and Rust); running one is a [self-host / `dev.`](#developer-note) topic.
+Workers and Rust); running one is covered in the forthcoming developer documentation.
 
 ## SDK API
 
@@ -105,7 +105,6 @@ airdrop, admin setters), ownership reads, and the challenge/proof helpers — is
 
 ## Developer note
 
-Deploying the gateway, integrating the SDK into your own app, and white-label operation are
-`dev.meddleware.co.uk` topics, planned in the `access-gate-sui`, `nft-gate`, and `nft-gate-client`
-package docs. This page is the on-chain contract and wire-protocol reference users and bots can rely
-on.
+Deploying the gateway, integrating the SDK into your own app, and white-label operation are covered
+in the forthcoming developer documentation. This page is the on-chain contract and wire-protocol
+reference users and bots can rely on.

package/docs/{access-gate/using.md → blockchain/sui/access-gate/walkthrough.md}

@@ -1,11 +1,11 @@
-# Access Gate — using it
+# Using Access Gate
 
 Two audiences: **operators** who run gates, and **buyers** who hold passes.
 
 ## For operators
 
 Manage gates in the [operator console](https://sui-access-gate.meddleware.co.uk). You'll need a
-[Sui wallet](/getting-started).
+[Sui wallet](/blockchain/sui/getting-started).
 
 ### Create a gate
 
@@ -53,7 +53,7 @@ receive the pass NFT. Overpayment is refunded automatically.
 
 ### Use a pass to unlock encrypted content
 
-If content was sealed to a gate with [Sealed Storage](/sealed-storage/), holding a valid pass lets you
+If content was sealed to a gate with [Sealed Storage](/blockchain/sui/sealed-storage/), holding a valid pass lets you
 **decrypt** it — provide your pass when unlocking.
 
 ## Common questions

package/docs/{architecture.md → blockchain/sui/architecture.md}

@@ -1,4 +1,4 @@
-# How the tools fit together
+# How the Sui tools fit together
 
 The four tools are useful on their own, but they're designed to compose. This page shows how.
 
@@ -13,7 +13,7 @@ The four tools are useful on their own, but they're designed to compose. This pa
 
 ## Sealed Storage = Walrus + Seal + Access Gate
 
-The clearest example of composition is **[Sealed Storage](/sealed-storage/)**. When you seal a file:
+The clearest example of composition is **[Sealed Storage](/blockchain/sui/sealed-storage/)**. When you seal a file:
 
 1. **Seal** encrypts it in your browser, under a **policy** you choose.
 2. **Walrus** stores the resulting ciphertext — publicly, because it's useless without the key.
@@ -36,14 +36,14 @@ So an Access Gate pass can act as the key to encrypted Walrus content — three
 
 ## How gated Walrus uploads work
 
-**[Walrus Storage](/walrus-storage/)** can route uploads through a **relay**. Meddleware's relay can
+**[Walrus Storage](/blockchain/sui/walrus-storage/)** can route uploads through a **relay**. Meddleware's relay can
 be **gated** by an Access Gate NFT: you prove you hold a valid pass, and the relay accepts your
 upload. A commission on gate purchases funds the service. If you don't need the gated relay, uploads
 fall back to the public relay.
 
 ## Where the DAO fits
 
-The **[DAO console](/dao/)** doesn't create anything — it *observes*. It reads the platform's
+The **[DAO console](/blockchain/sui/dao/)** doesn't create anything — it *observes*. It reads the platform's
 on-chain configuration: the treasury address, the **commission rate** charged on Access Gate
 purchases, the community gates the treasury controls, and a live feed of gate activity (passes sold,
 used, burned). It's the transparency window over the Access Gate economics.
@@ -57,5 +57,5 @@ capability can. This is the pattern throughout: **economics live in the smart co
 
 ## Next
 
-- [DAO](/dao/) · [Walrus Storage](/walrus-storage/) · [Sealed Storage](/sealed-storage/) ·
-  [Access Gate](/access-gate/)
+- [DAO](/blockchain/sui/dao/) · [Walrus Storage](/blockchain/sui/walrus-storage/) · [Sealed Storage](/blockchain/sui/sealed-storage/) ·
+  [Access Gate](/blockchain/sui/access-gate/)

package/docs/{dao → blockchain/sui/dao}/index.md

@@ -23,7 +23,7 @@ You do **not** need to connect a wallet to browse it — everything shown is pub
 - You hold a platform admin capability and want to confirm the tool **detects** it (see
   [Governance](#governance)).
 
-If you want to *create* a gate, that's the [Access Gate](/access-gate/) tool, not this one.
+If you want to *create* a gate, that's the [Access Gate](/blockchain/sui/access-gate/) tool, not this one.
 
 ## The tabs
 
@@ -41,7 +41,7 @@ name, price, and object ID (linked to a Sui explorer).
 ### Proposals
 
 Reserved for on-chain governance proposals. This is a **placeholder** today — the governance module
-isn't deployed yet, so the tab shows an empty state. It will list fundraising/governance proposals
+isn't deployed yet, so the tab shows an empty state. It will list governance proposals
 when that module ships.
 
 ### Governance
@@ -62,7 +62,7 @@ The console finds gates by looking up the **admin capabilities** the treasury ow
 gate each one controls — rather than replaying historical events. This matters because Sui testnet
 **prunes** old events after a few months, which would otherwise make a naive event-based count read
 as zero. The capability-based approach always reflects live reality. (The technical details are in
-[Reference](/dao/reference).)
+[Reference](/blockchain/sui/dao/reference).)
 
 ## Commission, in one line
 

package/docs/{dao → blockchain/sui/dao}/reference.md

@@ -1,4 +1,4 @@
-# DAO — reference
+# DAO reference
 
 Shapes and identifiers the DAO console reads. These are **on-chain** objects and events from the
 `access_gate` package; the console only displays them.
@@ -81,14 +81,8 @@ Example (as decoded JSON):
 The console queries each event type independently and merges them, sorted by checkpoint
 (newest first), tolerating any single type being pruned or unavailable.
 
-## Roadmap: `vault_dao`
-
-The **Proposals** and **Governance actions** are placeholders pending an on-chain `vault_dao` module.
-When it ships, proposals will be read from its registry; the console's display shapes are already
-stable so wiring it in won't change the UI.
-
 ::: tip Developer note
-Full SDK/contract API reference (entry functions, exhaustive event schemas) is being consolidated for
-`dev.meddleware.co.uk`. The [Access Gate reference](/access-gate/reference) already lists the gate
-contract's entry points and events, which is the on-chain source these DAO views read.
+Full SDK/contract API reference (entry functions, exhaustive event schemas) is covered in the
+forthcoming developer documentation. The [Access Gate reference](/blockchain/sui/access-gate/reference) already
+lists the gate contract's entry points and events, which is the on-chain source these DAO views read.
 :::

package/docs/{getting-started.md → blockchain/sui/getting-started.md}

@@ -1,4 +1,4 @@
-# Getting started
+# Getting started with Sui
 
 Everything here runs on [Sui](https://sui.io). You interact with each tool through its hosted web app
 using a **Sui wallet**. This page covers the basics that apply to all of them.
@@ -41,7 +41,7 @@ Each tool has its own subdomain, and they're all linked from the **tools hub**:
 Click **Connect** and approve the connection in your wallet. The tools hub shares one wallet
 connection across every tool embedded in it.
 
-- **Browsing** the [DAO console](/dao/) needs **no wallet** — it's read-only.
+- **Browsing** the [DAO console](/blockchain/sui/dao/) needs **no wallet** — it's read-only.
 - **Uploading, encrypting, buying, or managing** needs a connected wallet to sign transactions.
 
 ## 4. Understand what's on-chain
@@ -54,6 +54,6 @@ the chain says. Anything an app displays can be independently verified on a
 
 ## Next steps
 
-- **[How the tools fit together](/architecture)** — the big picture.
-- Jump into a tool: [DAO](/dao/) · [Walrus Storage](/walrus-storage/) ·
-  [Sealed Storage](/sealed-storage/) · [Access Gate](/access-gate/).
+- **[How the tools fit together](/blockchain/sui/architecture)** — the big picture.
+- Jump into a tool: [DAO](/blockchain/sui/dao/) · [Walrus Storage](/blockchain/sui/walrus-storage/) ·
+  [Sealed Storage](/blockchain/sui/sealed-storage/) · [Access Gate](/blockchain/sui/access-gate/).

package/docs/blockchain/sui/index.md

@@ -0,0 +1,41 @@
+# Sui
+
+Meddleware's Sui platform is a set of four connected tools — each useful on its own, designed to
+compose. They run against Sui's object model and use Walrus for decentralised storage where needed.
+
+## The tools
+
+| Tool | What it does |
+| --- | --- |
+| [DAO](/blockchain/sui/dao/) | A read-only console showing the platform's treasury, commission rate, community access gates, and live on-chain activity |
+| [Walrus Storage](/blockchain/sui/walrus-storage/) | Upload files to Walrus (decentralised blob storage on Sui) and manage how long they live |
+| [Sealed Storage](/blockchain/sui/sealed-storage/) | Client-side encryption layered on Walrus, with the access rule enforced on-chain by a policy you choose |
+| [Access Gate](/blockchain/sui/access-gate/) | Create NFT passes that gate access to content, APIs, or apps — ownership checked on-chain |
+
+## How they fit together
+
+The tools are designed to compose. [Sealed Storage](/blockchain/sui/sealed-storage/) uses Walrus for
+storage and optionally [Access Gate](/blockchain/sui/access-gate/) passes as the decryption key. The
+[DAO](/blockchain/sui/dao/) reads the live economics of the Access Gate platform — commission rate,
+treasury, active gates.
+
+See **[How the tools fit together](/blockchain/sui/architecture)** for the full picture.
+
+## Apps
+
+Each tool has a hosted web app:
+
+| Tool | App |
+| --- | --- |
+| Tools hub | [sui.meddleware.co.uk](https://sui.meddleware.co.uk) |
+| DAO console | [sui-dao.meddleware.co.uk](https://sui-dao.meddleware.co.uk) |
+| Walrus Storage | [sui-walrus.meddleware.co.uk](https://sui-walrus.meddleware.co.uk) |
+| Sealed Storage | [sui-seal.meddleware.co.uk](https://sui-seal.meddleware.co.uk) |
+| Access Gate | [sui-access-gate.meddleware.co.uk](https://sui-access-gate.meddleware.co.uk) |
+
+New here? **[Getting started with Sui →](/blockchain/sui/getting-started)**
+
+::: tip Developer documentation
+This site covers using the tools. SDK integration, self-hosting, and white-label deployment are
+covered in the forthcoming developer documentation.
+:::

package/docs/blockchain/sui/sealed-storage/api/typedoc-sidebar.json

@@ -0,0 +1 @@
+[{"text":"Classes","collapsed":true,"items":[{"text":"PolicyRegistry","link":"/docs/blockchain/sui/sealed-storage/api/classes/PolicyRegistry.md"},{"text":"SealController","link":"/docs/blockchain/sui/sealed-storage/api/classes/SealController.md"}]},{"text":"Interfaces","collapsed":true,"items":[{"text":"EncryptResult","link":"/docs/blockchain/sui/sealed-storage/api/interfaces/EncryptResult.md"},{"text":"FieldSpec","link":"/docs/blockchain/sui/sealed-storage/api/interfaces/FieldSpec.md"},{"text":"FieldSuggestion","link":"/docs/blockchain/sui/sealed-storage/api/interfaces/FieldSuggestion.md"},{"text":"KeyServerConfig","link":"/docs/blockchain/sui/sealed-storage/api/interfaces/KeyServerConfig.md"},{"text":"NftGateParams","link":"/docs/blockchain/sui/sealed-storage/api/interfaces/NftGateParams.md"},{"text":"PolicyDescriptor","link":"/docs/blockchain/sui/sealed-storage/api/interfaces/PolicyDescriptor.md"},{"text":"SealControllerConfig","link":"/docs/blockchain/sui/sealed-storage/api/interfaces/SealControllerConfig.md"},{"text":"SealedContentInput","link":"/docs/blockchain/sui/sealed-storage/api/interfaces/SealedContentInput.md"},{"text":"SealedContentPointer","link":"/docs/blockchain/sui/sealed-storage/api/interfaces/SealedContentPointer.md"},{"text":"SealedManifest","link":"/docs/blockchain/sui/sealed-storage/api/interfaces/SealedManifest.md"},{"text":"SealPolicyProvider","link":"/docs/blockchain/sui/sealed-storage/api/interfaces/SealPolicyProvider.md"},{"text":"SealSuggestClient","link":"/docs/blockchain/sui/sealed-storage/api/interfaces/SealSuggestClient.md"},{"text":"SuggestContext","link":"/docs/blockchain/sui/sealed-storage/api/interfaces/SuggestContext.md"},{"text":"TimeLockParams","link":"/docs/blockchain/sui/sealed-storage/api/interfaces/TimeLockParams.md"}]},{"text":"Type Aliases","collapsed":true,"items":[{"text":"SignPersonalMessage","link":"/docs/blockchain/sui/sealed-storage/api/type-aliases/SignPersonalMessage.md"}]},{"text":"Variables","collapsed":true,"items":[{"text":"nftGateProvider","link":"/docs/blockchain/sui/sealed-storage/api/variables/nftGateProvider.md"},{"text":"timeLockProvider","link":"/docs/blockchain/sui/sealed-storage/api/variables/timeLockProvider.md"}]},{"text":"Functions","collapsed":true,"items":[{"text":"buildPublishSealedContentTx","link":"/docs/blockchain/sui/sealed-storage/api/functions/buildPublishSealedContentTx.md"},{"text":"bytesToHex","link":"/docs/blockchain/sui/sealed-storage/api/functions/bytesToHex.md"},{"text":"concatBytes","link":"/docs/blockchain/sui/sealed-storage/api/functions/concatBytes.md"},{"text":"createDefaultRegistry","link":"/docs/blockchain/sui/sealed-storage/api/functions/createDefaultRegistry.md"},{"text":"createNftGateProvider","link":"/docs/blockchain/sui/sealed-storage/api/functions/createNftGateProvider.md"},{"text":"hexToBytes","link":"/docs/blockchain/sui/sealed-storage/api/functions/hexToBytes.md"},{"text":"objectIdBytes","link":"/docs/blockchain/sui/sealed-storage/api/functions/objectIdBytes.md"},{"text":"randomBytes","link":"/docs/blockchain/sui/sealed-storage/api/functions/randomBytes.md"},{"text":"sealedContentEventType","link":"/docs/blockchain/sui/sealed-storage/api/functions/sealedContentEventType.md"},{"text":"u64beBytes","link":"/docs/blockchain/sui/sealed-storage/api/functions/u64beBytes.md"}]}]

package/docs/{sealed-storage → blockchain/sui/sealed-storage}/index.md

@@ -1,6 +1,6 @@
 # Sealed Storage
 
-Encrypt a file in your browser, store the ciphertext on [Walrus](/walrus-storage/), and let only the
+Encrypt a file in your browser, store the ciphertext on [Walrus](/blockchain/sui/walrus-storage/), and let only the
 right people decrypt it — with the access rule enforced **on-chain**. Open the app at
 [sui-seal.meddleware.co.uk](https://sui-seal.meddleware.co.uk).
 
@@ -10,7 +10,7 @@ Sealed Storage combines three things:
 
 - **[Seal](https://seal-docs.wal.app/)** — threshold encryption where the decryption keys are held by
   a committee of independent **key servers**, not by any single party (or by Meddleware).
-- **[Walrus](/walrus-storage/)** — decentralised storage for the encrypted bytes.
+- **[Walrus](/blockchain/sui/walrus-storage/)** — decentralised storage for the encrypted bytes.
 - A **policy** — an on-chain rule that decides who is allowed to decrypt.
 
 You encrypt under a policy, share a small **manifest** (a pointer), and anyone who satisfies the
@@ -20,11 +20,11 @@ policy can decrypt. Nobody else can — even though the ciphertext itself is sto
 
 - You want to store something **private** on public/decentralised storage.
 - You want access tied to an **on-chain condition** — for example, "only holders of this
-  [Access Gate](/access-gate/) pass" or "only after a certain time".
+  [Access Gate](/blockchain/sui/access-gate/) pass" or "only after a certain time".
 - You want to **share** encrypted content without running your own key server or handing anyone a raw
   key.
 
-When plain [Walrus Storage](/walrus-storage/) is enough: if the content isn't sensitive, skip
+When plain [Walrus Storage](/blockchain/sui/walrus-storage/) is enough: if the content isn't sensitive, skip
 encryption.
 
 ## How it works, in three steps
@@ -48,7 +48,7 @@ encryption.
 Sealing produces a small **manifest** — the portable pointer you share or save. It records the policy
 type, the encryption **identity**, the Walrus blob ID, the network, and any non-secret parameters
 (like which gate). It contains **no secrets**; it's just enough to locate the ciphertext and rebuild
-the on-chain access check. See [Reference](/sealed-storage/reference).
+the on-chain access check. See [Reference](/blockchain/sui/sealed-storage/reference).
 
 ## Who holds the keys?
 
@@ -63,6 +63,6 @@ committee is available — the app shows a clear notice until then.
 
 ## Next
 
-- **[Using it](/sealed-storage/using)** — encrypt, share, and decrypt step by step.
-- **[Policies](/sealed-storage/policies)** — the access rules you can choose, and when to use each.
-- **[Reference](/sealed-storage/reference)** — manifest shape and the SDK API.
+- **[Walkthrough](/blockchain/sui/sealed-storage/walkthrough)** — encrypt, share, and decrypt step by step.
+- **[Policies](/blockchain/sui/sealed-storage/policies)** — the access rules you can choose, and when to use each.
+- **[Reference](/blockchain/sui/sealed-storage/reference)** — manifest shape and the SDK API.

package/docs/{sealed-storage → blockchain/sui/sealed-storage}/policies.md

@@ -1,4 +1,4 @@
-# Sealed Storage — policies
+# Sealed Storage policies
 
 A **policy** is the on-chain rule that decides who may decrypt sealed content. You choose one when you
 encrypt. Each policy is a self-contained on-chain module with a matching option in the app.
@@ -7,7 +7,7 @@ encrypt. Each policy is a self-contained on-chain module with a matching option
 
 ### Access-gate NFT (`nft-gate`)
 
-**Only holders of a valid pass for a chosen [Access Gate](/access-gate/) can decrypt.**
+**Only holders of a valid pass for a chosen [Access Gate](/blockchain/sui/access-gate/) can decrypt.**
 
 - **Encrypt with:** the gate's object ID.
 - **Decrypt with:** the pass NFT you hold for that gate (and whether it's soulbound).
@@ -47,6 +47,6 @@ policy picker automatically as they ship.
 
 ::: tip Developer note
 The mechanics of writing a new policy (the on-chain `seal_approve` module + the matching client
-provider) are `dev.meddleware.co.uk` material, planned in the `seal-policies` and `seal-client`
-package docs. The [Reference](/sealed-storage/reference) lists the current policy identifiers.
+provider) are covered in the forthcoming developer documentation. The
+[Reference](/blockchain/sui/sealed-storage/reference) lists the current policy identifiers.
 :::

package/docs/{sealed-storage → blockchain/sui/sealed-storage}/reference.md

@@ -1,4 +1,4 @@
-# Sealed Storage — reference
+# Sealed Storage reference
 
 Shapes and identifiers behind Sealed Storage. The **exhaustive, always-current API** is auto-generated
 from the `@meddleware/seal-client` SDK — see [SDK API](#sdk-api).
@@ -74,6 +74,6 @@ providers, and the manifest/byte helpers — is generated here:
 - [Seal client API](./api/)
 
 ::: tip Writing your own policy?
-That's `dev.meddleware.co.uk` material (a `seal_policies` Move module + a matching client provider),
-planned in the package docs.
+That's covered in the forthcoming developer documentation (a `seal_policies` Move module + a matching
+client provider).
 :::

package/docs/{sealed-storage/using.md → blockchain/sui/sealed-storage/walkthrough.md}

@@ -1,13 +1,13 @@
-# Sealed Storage — using it
+# Using Sealed Storage
 
 A walkthrough of the [Sealed Storage app](https://sui-seal.meddleware.co.uk). You'll need a
-[Sui wallet](/getting-started); browsing policies needs nothing, but decrypting requires a signature.
+[Sui wallet](/blockchain/sui/getting-started); browsing policies needs nothing, but decrypting requires a signature.
 
 ## Encrypt and store
 
 1. Open the **Encrypt** tab.
 2. **Choose a file.**
-3. **Pick a policy** (see [Policies](/sealed-storage/policies)). The form adapts to the policy — for
+3. **Pick a policy** (see [Policies](/blockchain/sui/sealed-storage/policies)). The form adapts to the policy — for
    an Access Gate policy you select the gate; for a time-lock you pick an unlock time.
 4. Encrypt. The file is sealed **in your browser** and the ciphertext is uploaded to Walrus.
 5. You receive a **manifest** — save or share it. It's the pointer needed to decrypt later, and it