From ba6bccd957d2ad93e563624aff2c35b650785e82 Mon Sep 17 00:00:00 2001 From: Violet Agent Date: Sat, 13 Jun 2026 14:06:24 +0300 Subject: [PATCH 1/4] docs: update walletFS product casing --- src/pages/petals/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/petals/overview.mdx b/src/pages/petals/overview.mdx index 43e3600..e0a99c7 100644 --- a/src/pages/petals/overview.mdx +++ b/src/pages/petals/overview.mdx @@ -4,7 +4,7 @@ Petals are not ready for prime-time use. They are in active development, the APIs and runtime model may change, and the current documentation is primarily for Bloom developers rather than end users. -Today, Petals should be understood as the path toward safe extensions to WalletFS: small, reviewable modules that can add capabilities behind Bloom’s policy, planning, and filesystem boundaries without asking agents to write custom signing or broadcast code. +Today, Petals should be understood as the path toward safe extensions to walletFS: small, reviewable modules that can add capabilities behind Bloom’s policy, planning, and filesystem boundaries without asking agents to write custom signing or broadcast code. For an early example of a custom petal, see [`bloombook`](https://github.com/bloom-directory/bloombook). It is useful as a developer reference for how Petals can package new filesystem-backed capabilities, but it should be treated as experimental alongside the Petals runtime itself. From a3cfd8825817c99bcf64cc86887366cee7c216f5 Mon Sep 17 00:00:00 2001 From: Violet Agent Date: Sat, 13 Jun 2026 14:20:45 +0300 Subject: [PATCH 2/4] fix: correct X social link --- vocs.config.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vocs.config.ts b/vocs.config.ts index d0ab29e..a0eaf00 100644 --- a/vocs.config.ts +++ b/vocs.config.ts @@ -21,7 +21,7 @@ export default defineConfig({ renderStrategy: 'full-static', socials: [ { icon: 'github', link: 'https://github.com/bloom-directory' }, - { icon: 'x', link: 'https://x.com/bloomdirectory' }, + { icon: 'x', link: 'https://x.com/bloom_directory' }, ], topNav: [ { text: 'Website', link: 'https://bloom.directory' }, From d9179b678044144e234e740d51b5e81a4e654a21 Mon Sep 17 00:00:00 2001 From: Gavin Pacini Date: Sat, 13 Jun 2026 18:24:12 +0700 Subject: [PATCH 3/4] clarify product and terminology --- src/pages/index.mdx | 2 +- src/pages/introduction/what-is-bloom.mdx | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/pages/index.mdx b/src/pages/index.mdx index 5647589..1804457 100644 --- a/src/pages/index.mdx +++ b/src/pages/index.mdx @@ -32,7 +32,7 @@ description: Documentation for Bloom, the agentic Ethereum wallet mounted as a v } `} -Bloom is an **agentic Ethereum wallet mounted as a virtual filesystem**. +/bloom walletFS is an **agentic Ethereum wallet mounted as a virtual filesystem**. Reads are blockchain queries. Writes are transaction intents. The main interface is an ordinary directory that humans and agents can inspect with normal filesystem tools like `ls`, `cat`, and file writes. diff --git a/src/pages/introduction/what-is-bloom.mdx b/src/pages/introduction/what-is-bloom.mdx index ccc11e2..89772e6 100644 --- a/src/pages/introduction/what-is-bloom.mdx +++ b/src/pages/introduction/what-is-bloom.mdx @@ -1,6 +1,6 @@ # What is Bloom? -Bloom gives agents a safe wallet workspace for Ethereum and EVM chains. +Bloom is a framework for creating agent-safe software components. The first application of Bloom is an agentic Ethereum wallet. We call this walletFS.