Beyond the Wallet. Beyond the Inbox. A Protocol for Intent.

This paper outlines the architectural philosophy and socio-technical necessity for the Web/A Folio and its Transport protocol. It argues that true digital transformation requires moving from centralized "Push Services" and "Walled Garden Chat" toward a decentralized, context-aware routing network centered on the individual.

1. The Paradox of "Push-Style" Digital Government

Modern digital governments often promise "Push-Style" services—where the state proactively supports citizens without a formal application. However, this vision has largely failed due to two fundamental constraints:

1.1. The Administrative "Purpose" Constraint

Government data linkage is legally and operationally restricted by "Purpose of Use." Data cannot be moved or merged between agencies without a concrete administrative trigger. In most jurisdictions, that trigger is the Application (Shinsei). Without an application, there is no "purpose," and without purpose, data remains siloed.

1.2. The Freshness Gap

The most critical life events—a sudden drop in income, a medical emergency, or a change in household dynamic—are reflected in real-time in private data (bank accounts, family conversations) and the individual's own mind. By the time this data reaches government databases, it is "past data" (e.g., last year's tax returns), often too late for proactive intervention.

1.3. The Long-Tail of Administration and the Limits of Systemization

Administrative procedures are inherently "long-tail." Many inquiries and processes occur only once a year or once in a lifetime, making the cost of building dedicated systems for each one unjustifiable. However, from the perspective of "intent-based" data flow, these processes share similar structures. The current siloing of transport (delivery networks) for each application (procedure) is highly inefficient. We need a system where data flows over established, general-purpose paths under intelligent, context-aware control.

2. Returning to the "Clear File" Model

Before digitization, individuals managed their identities using a "Clear File"—a folder containing physical bank books, pay stubs, and certificates. They brought this folder to city hall, acting as the Human Integration Hub.

Web/A Folio returns to this model. By placing the individual at the center of data integration:

  1. O(N) Connectivity: A person links N services. We avoid the exponential cost of N(N-1)/2 direct API connections between institutions.
  2. Contextual Freshness: Private data (Bank) and Public records (City) can be safely merged under the individual's sovereign control, bypassing administrative silos.

3. The Re-invention of Messaging: Beyond SMTP and Chat

The current state of messaging is caught between a broken past and a restricted present.

3.1. The Failure of Federated SMTP

SMTP, while decentralized, failed because it lacked inherent trust. The cost of filtering SPAM shifted from the protocol to the service provider, leading to the massive centralization of "Gatekeepers" like Gmail and Outlook.

3.2. The Walled Gardens of Chat

Business chat (Slack, Teams) solved internal trust but created silos. While they are great for "communication," they are ill-suited for "Workflow Transport"—the verifiable handoff of critical data across organizational boundaries.

3.3. The Ephemeral Data Hub

Folio Transport defines the server not as a permanent archive (a "Honey Pot" for hackers), but as an Ephemeral Data Hub. It serves as a transient buffer where messages are held only until delivered (best-effort retention). This shifts the master data responsibility to the local Folio, aligning with the "user-centic" philosophy.

4. Context-Aware Routing in the LLM Era

Folio Transport introduces Selective End-to-End Encryption (E2EE). We encrypt the user's data inputs, but we keep the Template and Envelope (metadata) visible to the network agents.

4.1. Intent as the Routing Key

In the 1970s, the OSI model focused on strict layering—downward layers moved bits without understanding the context. In the 2020s, LLMs allow us to route data based on Purpose and Form.

By seeing the "Envelope," an LLM-powered router can determine:

  • "This is a Join Request for the Community."
  • "This is a Verification Proof for an Access Pass."
  • "This is a Claim for a Support Grant."

Routing no longer depends solely on a "Reply-To" DID, but on the Context of the Data.

4.2. From Grooves to Folios

Ray Ozzie’s Groove envisioned cross-organizational collaboration but lacked the "Trust Layer" (DIDs/VCs) and the "Intelligence" to route complex document contexts. Folio combines these decentralized identity standards with modern AI to realize that vision.

5. Conclusion: Designing for Human Agency

Web/A Folio and its Transport protocol are not just tools; they are a manifesto for a society where:

  1. Agency stays with the individual, who holds the only complete record of their life.
  2. Purpose-Driven Integration: Data is integrated based on individual needs (context), overcoming the siloes created by organizational boundaries of responsibility.
  3. Intelligence is interchangeable, where AI agents assist in routing data based on the "intent" of the document, not just the "address" of the sender.

6. Conclusion: Returning to the Fundamental Data Flow

Modern digital ecosystems are often shaped more by economic incentives—such as lock-in through centralization or excessive redundancy for consensus—than by the natural movement of data itself.

Web/A Folio seeks to return to the foundational principles of the early Internet, redefining systems based on the "necessity of flow": where data originates in the context of an individual's life and is delivered toward a specific intent. By combining ephemeral hubs with context-aware routing, we build a system that is robust, scalable, and above all, respectful of human dignity.

Related Documents