Home › The Stack › Layer 4
LAYER 4

Trust Applications

The top layer of the trust stack: end-user applications for creating, joining, and managing trust identities, communities, and networks. The Agent App reference build (web + TUI) is operational — it registers VTAs, founds and administers VTCs, issues and verifies VRCs, manages community rules, sends and accepts invitations, and carries on confidential chats — while the Utility Server covers Community Network Manager functionality. The stack is also being embedded in other test applications.

Active — Reference Apps Built

What is the Trust Applications Layer?

Layer 4 is where the trust stack meets end users. It is the application layer — the UI/UX components, developer tools, and end-user interfaces that make the trust stack accessible to people who are not cryptographers or protocol engineers.

The goal of Layer 4 is to make it as easy to create a Verified Trust Agent, join a Verified Trust Community, and manage your trust relationships as it is to create a social media account today — but with the privacy, sovereignty, and cryptographic guarantees that social media platforms cannot provide.

Layer 4 applications are built on top of Layers 1–3. They use the DID infrastructure (Layer 1), the TSP messaging channel (Layer 2), and the credential/governance framework (Layer 3) to deliver trust-aware features to end users.

Applications at Layer 4

The following applications model how Layer 4 trust applications can be built. The Agent App and Utility Server exist today as working reference and infrastructure components rather than polished products — they exercise real trust flows against the published v0.1.0 stack, and the stack is now being integrated into additional test applications.

👤

Personal Network Manager

The Agent App is a working Personal Network Manager reference build, with both a terminal UI and a web dashboard. It registers VTAs, manages relationships and confidential chats, founds and administers VTCs — including community rules, invitations, and governance proposals — issues, verifies, and revokes VRCs and the wider DTG credential family, and manages multiple profiles (display-layer personas with per-claim disclosure controls) under a human-readable, namespace-scoped agent name. Rather than being released as a standalone product, it serves as a reference for developers building their own PNM-style applications on top of the trust stack.

Operational — web + TUI reference build
🏘️

Community Network Manager

The Utility Server covers Community Network Manager functionality: name registry, credential registry, witness attestation, and VTC governance primitives. Like the Agent App, it is not being released as a standalone product — it demonstrates how CNM-style services can be built on the trust stack and provides the infrastructure needed to bootstrap the first Verified Trust Network, running today against the v0.1.0 stack.

Covered by Utility Server
🛠️

Developer Tooling

Available now in v0.1.0:

  • TypeScript packages published to npm — @p2p-trust-stack/core and @p2p-trust-stack/app-api
  • A typed agent API: createAgentStack(), 10 domains, and a closed event catalogue
  • A module-by-module API Reference and a glossary
  • Two reference applications (web + TUI) demonstrating end-to-end trust flows
Packages available on npm

The Vision

The ultimate goal of Layer 4 is to make the trust stack invisible to end users — in the same way that TLS makes encrypted web connections invisible to people browsing the web. Users should not need to understand cryptography, DIDs, or VRCs to benefit from the trust stack. They should simply experience a more trustworthy internet.

Concretely, this means:

  • For individuals: a personal identity that you own and control, relationships that are cryptographically provable, and the ability to delegate authority to AI agents with confidence that they cannot exceed their mandate.
  • For communities: governance tools that are transparent, tamper-proof, and resistant to capture by bad actors — whether those actors are humans or AI systems.
  • For developers: a simple, well-documented API for adding trust-aware features to any application — without needing to implement cryptography or protocol engineering from scratch.
  • For AI agents: a verifiable identity and a cryptographic record of their authority — so that AI agents can act on behalf of humans with accountability and auditability.

Layer 4 is active: the reference applications are built. The TUI and web dashboards in agent-app are reference tools rather than polished products, but they run real application features end-to-end on the published v0.1.0 stack: registering VTAs, founding and administering VTCs, issuing and verifying VRCs, managing community rules, sending and accepting invitations, confidential chat, multiple profiles with profile claims and disclosure rules, namespaced agent names, and credentials grouped by scenario. The stack is also being integrated into other test applications. What remains is turning these reference applications into polished products — a mobile agent app, and richer in-community collaboration — as tracked on the Roadmap.

← Layer 3: Trust Tasks ← Back to Stack Overview