BitPlan Adds Encrypted Collaborative Drafts Before Wallet-Approved On-Chain Publication

AI & Agents Watch / Applications

In Brief

BitPlan has expanded its encrypted agent-planning system with a collaborative working layer that allows plans to remain hosted as encrypted drafts while people and software agents review, annotate and revise them before deciding whether a version should be permanently published to BSV Blockchain.

The current workflow separates live collaboration from blockchain publication. Hosted drafts remain encrypted and can change without requiring an on-chain transaction, while publication as a versioned 1Sat Ordinal remains a separate action controlled through a compatible BRC-100 wallet. BitPlan says its hosted service stores ciphertext rather than readable document contents. BitPlan

The browser interface also introduces templates, shared collaboration links, annotations, text edits, drawings and HTML overlays, while an installable BitPlan agent skill allows coding environments including Claude Code, Codex, Grok Build, OpenCode and Cursor to participate in the planning workflow.

News Report

BitPlan has expanded from encrypted, versioned plan publication into a collaborative environment where humans and software agents can work on a document before committing a selected version to BSV Blockchain.

The original BitPlan model, covered by BSV TIMES in August, centered on taking a planning document, encrypting it through a BRC-100-compatible wallet and publishing it as a versioned 1Sat Ordinal. Subsequent versions could continue the document history while wallet-controlled encryption determined who could read them.

The current BitPlan adds another stage before that permanent record. A plan can remain hosted while changing, with the encrypted document stored off-chain until its owner decides that a particular version is ready to be recorded permanently.

BitPlan describes the hosted draft as using the same encrypted envelope as an on-chain plan. The difference is where that envelope is stored: the hosted service keeps the ciphertext during collaboration, while an on-chain version is published through the wallet as a 1Sat Ordinal.

Work First, Publish Later

The distinction changes the role BSV Blockchain plays in the workflow. BitPlan no longer requires every intermediate working state to become a blockchain publication; instead, a document can remain mutable while people and agents discuss it, and a meaningful version can be selected later for permanent recording.

The resulting sequence is closer to:

draft → collaborate → review → select → wallet approval → publish

rather than treating every edit as something that immediately belongs on-chain.

BitPlan’s documentation says hosted drafts do not require BSV merely to remain stored and editable. When the user chooses to move the plan on-chain, the wallet signs and publishes the corresponding encrypted envelope.

That division is important for a system built around working documents. Drafts naturally contain incomplete ideas, rejected alternatives and temporary revisions that may matter during collaboration without necessarily deserving permanent publication, so BitPlan now treats permanence as a separate decision rather than the default outcome of every change.

Collaboration Happens Above the Published Version

The browser interface provides several ways for people and agents to work around the document before publication. New plans can begin from Brief, Terminal, Decision or Blank templates, while participants can add notes beside passages, suggest text changes, attach drawings and place HTML-based overlays alongside existing material.

Those contributions do not automatically become the next published document version. They accumulate as working layers around the current plan, allowing the user to review what changed and decide which contributions should influence the next revision.

This creates a clear distinction between collaboration state and document state. A comment, drawing or proposed edit can exist in the working room without silently rewriting the authoritative plan.

“Live” Does Not Mean “Published”

BitPlan makes that boundary explicit in the current interface. Live edits and notes are encrypted within the shared room, but they do not automatically advance the plan’s published version number.

Publishing a new hosted version is one deliberate action, while publishing permanently to BSV Blockchain is another. The current agent skill follows the same distinction: an agent can contribute to a live plan and prepare revisions without treating those actions as blockchain publication.

That separates three activities that could otherwise easily be conflated: working on a plan, saving a new encrypted draft, and creating a permanent blockchain record.

Wallet Approval Remains the Publication Boundary

The wallet remains the authority boundary throughout the process. BitPlan uses BRC-100 as the interface through which the application requests cryptographic and transaction operations, while the wallet retains the identity keys.

For encrypted plans, the document itself is encrypted with a random document key, and the wallet wraps that key for the owner and any authorized readers. When the plan is ultimately published, the wallet performs the signing and blockchain transaction rather than passing its private keys to BitPlan or the agent.

Agents can therefore participate meaningfully in planning without automatically receiving authority to make a permanent publication. BitPlan’s documentation states that automated or JSON-based CLI operation does not itself constitute permission to publish; on-chain publication still requires the appropriate command, explicit approval and wallet authorization.

This preserves a clear human boundary: the agent may help create and revise the artifact, but the wallet owner controls whether that artifact becomes permanent.

Agent Skills Bring the Workflow Into Coding Environments

BitPlan is also making the planning system accessible directly to software agents rather than requiring every interaction to begin in the browser. Its current site provides an installable BitPlan skill for environments including Claude Code, Codex, Grok Build, OpenCode and Cursor.

The skill allows an agent to create, review, host, update, retrieve and share encrypted HTML plans through a BRC-100 wallet. A coding agent can therefore work with a BitPlan document as part of a larger software-development or planning session without receiving the wallet’s mnemonic or private keys.

The collaborative interface extends that model further. A human can provide evidence, leave objections, request revisions or select among alternatives, while the agent uses that feedback to prepare the next iteration of the plan.

Sharing Does Not Automatically Grant Publishing Authority

BitPlan also separates the right to read a plan from the right to publish its next version. A plan can be encrypted for named readers identified through public wallet identity keys, giving them access to the document without automatically transferring control over its publication history.

BitPlan’s documentation describes the current ordinal output as controlling publication while wallet keys control reading. Those capabilities can diverge, allowing someone to participate in the planning process without gaining authority to rewrite the document’s blockchain record.

Hosted Privacy Still Depends on Encryption

The hosted-draft model should not be interpreted as meaning BitPlan has become a conventional cloud-document provider. BitPlan says the hosted service stores the encrypted envelope rather than plaintext, and the document is encrypted before upload without exposing the wallet’s identity private keys to the server.

That does not make hosted storage invisible. The server still necessarily handles ciphertext and operational metadata associated with delivering it, but the privacy model differs from storing readable planning documents in an ordinary application database.

The server hosts the encrypted working material; the wallet controls access to the readable contents.

A Different Role for the Blockchain

The development also changes the way BitPlan illustrates BSV Blockchain as data infrastructure. Its first release emphasized permanent encrypted storage and version history, while the newer workflow adds an important qualification: not every useful state needs to be permanent.

Drafting is temporary by nature. Comments may be wrong, suggestions may be rejected, and an agent may propose several directions before one becomes useful enough to keep. Recording all of that directly into an immutable public record would confuse working state with authoritative state.

BitPlan instead allows the mutable process to occur above the chain while reserving blockchain publication for selected checkpoints. In that model, the public ledger is not the collaborative editor; it is the durable publication layer beneath the collaborative editor.

A Third BitPlan Development

The collaborative workflow extends a project that BSV TIMES has already followed through two earlier developments.

BitPlan first appeared as a system for encrypted, versioned planning documents tied to BRC-100 wallets and 1Sat Ordinals. In September, BitPlan Gateway added multi-model AI inference accessible through BSV-paid HTTP 402 calls, giving agents a way to purchase external computation through a common gateway.

The current development concerns a different part of the agent workflow. An agent can obtain computation through the Gateway, participate in developing a plan through BitPlan, work through human feedback and revisions, and eventually contribute to a version that the wallet owner may choose to publish permanently.

Those pieces remain separate services, but together they show BitPlan moving toward a broader infrastructure layer for agent work rather than remaining a single-purpose document publisher.

BSV TIMES Read

The most consequential change in the current BitPlan is not collaboration by itself; collaborative documents already exist everywhere. The more unusual design choice is where BitPlan places the boundary between temporary work and permanent record.

Human and agent reasoning is inherently iterative. Plans change as evidence arrives, assumptions are challenged and earlier directions are discarded, while an AI agent may produce several plausible versions before one becomes useful enough to preserve as a durable record.

There is little benefit in forcing every intermediate state into permanent public infrastructure merely because blockchain storage is available. At the same time, leaving the final artifact entirely inside a conventional application database gives the application provider continuing control over its availability and history.

BitPlan now places those two stages on different infrastructure. The working state can remain encrypted, hosted and changeable, while the selected state can later become a wallet-authorized blockchain publication once the collaborators decide that permanence is useful.

That division is particularly well suited to autonomous-agent workflows because it preserves human judgment at the point where permanence begins. The agent can generate and revise, collaborators can challenge and refine, and the wallet owner retains the final decision over whether the result becomes part of a permanent record.

For BSV Blockchain, that is a more mature data-infrastructure model than simply placing more data on-chain. The important question is not whether everything can be permanent, but whether permanence is applied at the point where it becomes useful.

Developer Context

OPL / opldotdev

BitPlan is developed and published through the opldotdev/bitplan.dev repository.

Other related public work under the same development identity includes:

BitPlan Gateway — the BSV-paid multi-model AI inference service previously covered by BSV TIMES
Bitcoin Backup — encrypted wallet-backup tooling for self-custody
BitPlan agent skills — portable integrations for Claude Code, Codex, Grok Build, OpenCode and other agent environments

The BitPlan and Gateway agent skills are maintained in the same public opldotdev/bitplan.dev repository. SkillsMP