日本語 · English

誰に向けて書いてるか

あなたは、こういう人:

• MU を見て「面白い、似たようなの自分でやれそう」と思った
• 1〜3人で何かを作って売ってる/売りたい (服・食・宿・コーチ・音楽・場・小さい何か)
• マーケや SNS 運用に時間取られたくない。商品作るのは好き
• 毎月決まった売上欲しいけど、サブスク化はピンとこない
• 「moment が刻まれる」という MU の体験を、自分の領域でやってみたい

あなたが 違う人 なら (大量集客したい・ブランド帝国作りたい・SaaS 売りたい)、これは合いません。Shopify 等を使ってください。

あなたの場合こうなる (5 業界の実例)

2年間 wearmu.com を自分で運用して、AI が毎時デザインし、在庫ゼロで POD 各社 (Printful / SUZURI / Gelato …、今も追加中) から自動発送し、価格は売れるたびに上がる、という autonomous brand を作った。
やってみて分かったのは「これは服に限らない」ということ。時間と場所を刻んだ「今日のこれ」を release する形は、ほぼあらゆる小さな商売に応用できる。

仕様の核 (one-line spec / 技術側向け)

Why generalize (v1 → v2)

v1 of the protocol scoped itself to apparel + cities: drop_generator assumed T-shirts and image generation, weather_provider assumed climate-pinned designs, "satellite city" framing assumed geographic operators. The core insight — autonomous brand operation tied to a moment — applies to any industry where a release is time-pinned, an operator is autonomous, and a treasury settles fees.

The same five primitives reappear. The protocol abstracts them so one engine serves all.

5つの primitives

1 · Release — mu.release.v2

A Release is a JSON document with stable, content-addressable identity:

{
  "schema": "mu.release.v2",
  "id": "rel_2026-05-18T15:00Z_teshikaga_t01",
  "node": "teshikaga",
  "kind": "apparel.tee",
  "pinned_at": "2026-05-18T15:00:00Z",
  "pinned_to": { "lat": 43.490, "lon": 144.460,
                 "temperature_c": 14.2,
                 "weather_code": "scattered_clouds" },
  "generator": { "model": "gemini-3-pro-image",
                 "prompt_hash": "sha256:…",
                 "output_hash": "sha256:…" },
  "supply": { "kind": "open|fixed|bonding", "amount": 0 },
  "price": { "currency": "JPY", "base": 4900,
             "curve": "linear_micro_bond" },
  "lifecycle": { "expires_at": null },
  "settlement": { "treasury": "DK29rB…",
                  "node_split_pct": 95,
                  "origin_fee_pct": 5 },
  "embeds": ["wearmu.com/p/<id>"]
}

Required: schema, id, node, kind, pinned_at, settlement. Everything else is industry-optional.

2 · Node — mu.node.v2

{
  "schema": "mu.node.v2",
  "slug": "teshikaga",
  "name": "Teshikaga",
  "industry": "apparel",
  "operator": { "pubkey": "<solana_pubkey>",
                "contact": "ops@…",
                "human_in_loop": false },
  "anchor": { "lat": 43.490, "lon": 144.460 },
  "adapter": "github.com/enabler/mu-adapter-apparel",
  "status": "active|pilot|paused",
  "registered_at": "2026-05-12T00:00:00Z",
  "origin_approval_sig": "<signature>"
}

Naming rule: nodes using the literal string "MU" in branding need a one-time origin approval. Nodes forking the protocol under a different name are free to operate without approval.

3 · Treasury

Settlement is industry-agnostic. Default contract (mu-settlement) exposes 4 ABI calls.
Origin Treasury (現行 reference 実装): Solana mainnet · DK29rBGCvP83LUNjUGVM6xt6qPy6rycBFopXbFkg9XvQ  · Solscan で見る  · contracts/mu-settlement/ (Anchor program、v2 移行中)

Reference implementation: Solana + Anchor at contracts/mu-settlement/. Other chains (Base, Ethereum L2) are protocol-compliant if they expose the same 4 calls.

Fee floor: 5% to origin Treasury. Nodes raising their split above 95% require a one-time slot fee (v2 placeholder).

4 · Identity — mu.identity.v2

{
  "schema": "mu.identity.v2",
  "participant_id": "p_<base32_hash>",
  "kind": "wearer|diner|guest|listener|player",
  "node": "teshikaga",
  "first_seen_at": "…",
  "release_count": 7,
  "log_entries": ["log_…"]
}

5 · Lifecycle — mu.lifecycle.v2

{
  "schema": "mu.lifecycle.v2",
  "release_id": "rel_…",
  "expires_at": "2026-08-26T15:00:00Z",
  "on_expire": { "action": "retire", "refund_pct": 50 },
  "retired_at": null,
  "retired_by_participant": null
}

業界別 adapter

Each industry implements an IndustryAdapter trait against mu-engine:

trait IndustryAdapter: Send + Sync {
    fn kind_prefix(&self) -> &'static str;
    fn generate(&self, pin: Pin) -> Release;
    fn fulfill(&self, release: &Release, buyer: ParticipantId) -> Fulfillment;
    fn validate(&self, release: &Release) -> Result<(), Error>;
}

Anyone may publish a third-party adapter. Discovery via mu-adapter-registry.json (PR-curated until v3).

準拠レベル

A node is MU Protocol Compliant if it:

1. emits Release documents with schema: mu.release.v2
2. registers as a Node with the protocol Treasury
3. routes ≥5% of gross sales to origin Treasury via mu-settlement
4. exposes a public read endpoint at /.well-known/mu/releases returning Release JSON
5. respects the identity anti-pattern (no PII in public emits)

(1)+(2)+(4) = Discoverable · (3) = Settled · (5) = Compliant.
All three = full conformance, eligible for the public node directory at wearmu.com/protocol/nodes (v2.1).

Discovery 経路 (Node 登録の実際)

1. Self-host — あなたのドメインに /.well-known/mu/releases を立てる。こちらが live サンプル。
2. Register — hi@enabler.fun に {slug, industry, operator_pubkey, anchor_url} を送る。GH PR でも可 (mu-adapter-registry.json)。
3. Approval — 1営業日。MIT fork で MU 名称使わないなら approval 不要、自由 deploy 可。

最短で立てる手順 (今夜やれる)

本気で「自分のMU 持ちたい」なら、これだけ読めば今夜から動かせる。
ただ全公開すると spec ハンターに荒らされるので、30pt の壁 (初回 完全無料、メアド1個) を置いた。MU の流儀。

// あなたの今夜の "1個" を返す
async fn well_known_releases() -> impl IntoResponse {
    Json(json!({
        "schema": "mu.release.v2",
        "node": { "slug": "mycafe", "industry": "food",
                  "anchor": { "lat": 35.65, "lon": 139.70 } },
        "releases": [{
            "schema": "mu.release.v2",
            "id": "rel_2026-05-18T17:00Z_mycafe_omakase",
            "node": "mycafe",
            "kind": "food.tasting",
            "pinned_at": "2026-05-18T17:00:00Z",
            "lifecycle": { "expires_at": "2026-05-18T23:00:00Z" },
            "price": { "currency": "JPY", "base": 7800 },
            "settlement": { "treasury": "<your_solana_pubkey>",
                            "node_split_pct": 95, "origin_fee_pct": 5 }
        }]
    }))
}

これが解放するもの

• Cross-industry composability: a Soluna lodging release can be paid in ENAI alongside a MU apparel drop and a JiuFlow tournament entry — same Treasury, same identity, single checkout.
• Forkable brand operations: anyone can stand up a mu-adapter-<industry> and operate a node with their own brand and treasury, paying only the 5% origin fee.
• Provenance for any product: the pinned_at/pinned_to + output_hash fields give every product a permanent, content-addressable history.
• Industry-neutral retirement: the lifecycle layer means "death-defined" products are not an apparel-only oddity — they work for food (expires end of night), lodging (check-out date), services (event date).

Trigger conditions for v2 → final

1. ≥1 non-apparel reference adapter shipped (food: kokon.tokyo, OR lodging: SOLUNA)
2. ≥1 third-party node successfully registers via the protocol (not Enabler-operated)
3. Origin fee distribution executes on-chain at least once for a non-origin node

Until then v2 remains an RFC; v1 is canonical for the apparel/cities subset.

あなたが今夜やれる3つ

2年間ずっと1人でMUを回してきて、ようやく「これは服に限らないな」と思えるようになった。
あなたの「小さなMU」を、僕の MU の隣に並べたい。それだけのために書いた spec。

— yuki (wearmu.com 運営)