Modern software systems are increasingly fragmented. Communities coordinate in one place, payments happen in another, messaging in another, and governance somewhere else. Organizations juggle dozens of SaaS tools, APIs, messaging channels, and automation systems. Meanwhile users interact through a mixture of websites, mobile apps, chat platforms, and increasingly AI assistants.
Safebox proposes a different approach: a layered stack where collaboration, automation, economic systems, and assistants operate on top of a shared substrate. Each layer of the stack expands the system’s capabilities while preserving clear boundaries between user interaction, applications, infrastructure, and automation.
At the foundation of this architecture lies Layer 1, the application layer. This layer defines the core primitives that communities and organizations use to interact: users, streams, and embeddable applications. Every other layer in the Safebox stack ultimately builds on these foundations.
Layer 1 is intentionally designed to be accessible everywhere. It can appear inside websites, messaging platforms, email digests, bots, and embedded widgets. People do not need to install software to interact with Layer 1. They can participate using ordinary tools they already use every day.
The goal of Layer 1 is simple but ambitious: enable communities and organizations to run complete economic and coordination systems directly on the web.
Users and Roles
The first fundamental concept in Layer 1 is the user.
Users may represent:
- individuals
- organizations
- teams
- automated agents
- roles within organizations
An organization might define roles such as:
- administrator
- contributor
- moderator
- member
- external participant
Roles allow permissions to be applied consistently across many resources and applications.
This identity model allows Safebox systems to coordinate actions across communities, organizations, and workflows without forcing users into rigid structures. A person may participate simultaneously as:
- a member of multiple communities
- an employee of an organization
- an administrator of a project
- a participant in a contest
The identity model therefore supports complex real-world relationships.
Streams — The Universal Data Primitive
The second foundational concept is the stream.
A stream is the universal unit of activity within Safebox.
Streams represent evolving objects that accumulate messages and relationships over time. A stream may represent many types of entities, such as:
- conversations
- projects
- feeds
- topics
- documents
- workflows
- events
- tasks
- artifacts
- communities
Messages posted to a stream describe operations or updates. Because streams record events rather than static state, the entire history of an object can be reconstructed.
Streams may also relate to other streams. These relationships create a graph of information connecting projects, people, artifacts, and conversations.
This model allows the system to track not only what exists but how it evolved.
Streams therefore form the backbone of collaboration across Safebox systems.
Applications Built on Streams
Streams provide the data model, but communities need tools to act on that data. Layer 1 therefore includes a set of applications built on top of streams.
These applications allow communities to coordinate work, discover prices, distribute resources, and govern themselves.
The Intercoin ecosystem provides a large collection of these applications. Rather than requiring organizations to build custom software for each function, they can assemble applications like modular components.
These applications generally fall into four economic categories.
Markets — Price Discovery and Exchange
Markets allow communities to determine the value of resources through voluntary exchange.
Layer 1 includes several market-oriented applications.
Auctions
Auctions provide transparent price discovery. Communities can sell goods or rights while allowing participants to compete for them.
Different auction formats can be used depending on the situation:
- English auctions where bids increase over time
- Dutch auctions where price decreases until someone buys
- sealed-bid auctions
- time-limited auctions
Auctions can be used for many purposes:
- event tickets
- rare digital items
- sponsorship slots
- advertising placements
- governance rights
- access to limited services
Because auctions can settle on EVM-compatible blockchains, they provide transparent records of bidding and settlement.
Recurring Subscriptions
Subscriptions support ongoing services and memberships.
Communities can charge recurring payments for:
- membership access
- premium content
- SaaS tools
- educational resources
- community services
Subscriptions allow communities to maintain stable funding streams while offering benefits to members.
Marketplaces
Communities may also offer marketplaces where participants can exchange goods or services. These marketplaces can integrate with Safebox workflows, allowing:
- automated fulfillment
- escrow
- community verification
Markets therefore provide the economic engine that powers many community activities.
Coordination — Organizing Work
Not every community activity is about buying or selling. Many activities involve organizing people around a shared goal.
Layer 1 therefore includes applications that help communities coordinate effort.
Contests
Contests allow communities to reward the best solutions to a problem.
A contest typically follows a structured process:
- a challenge is posted
- participants submit solutions
- judges or the community evaluate entries
- winners receive rewards
Contests can be used for:
- hackathons
- research challenges
- design competitions
- community innovation programs
By attaching rewards to contests, communities can encourage people to solve important problems.
Fundraising Campaigns
Communities often need to raise funds for projects or causes.
Fundraising applications allow supporters to contribute resources while tracking progress toward goals.
Campaigns can include:
- funding targets
- reward tiers
- time limits
- contributor recognition
Fundraising tools help communities mobilize resources for collective initiatives.
Community Initiatives
Communities frequently organize events, programs, and volunteer efforts.
Coordination applications allow participants to:
- sign up for activities
- track progress
- contribute work
Streams provide the underlying record of contributions and results.
Governance — Collective Decision Making
Communities must also decide how resources are allocated and how rules evolve.
Layer 1 includes governance applications to facilitate collective decision making.
Voting
Voting applications allow communities to decide on proposals.
Examples include:
- approving budgets
- electing leaders
- choosing projects to fund
- modifying policies
Voting mechanisms can be configured to match the needs of each community.
DAO Governance
Some communities use decentralized governance structures similar to DAOs.
Governance systems may include:
- proposal submission
- discussion periods
- voting thresholds
- quorum requirements
Governance ensures that communities can evolve through transparent processes.
Distribution — Allocating Resources
Once resources are generated or collected, communities must distribute them.
Layer 1 therefore includes distribution mechanisms.
Payouts
Communities can distribute funds to contributors or participants.
Payouts can be used for:
- salaries
- project grants
- contributor rewards
- retroactive funding
Payout systems allow communities to recognize and reward valuable work.
Community Income
Some communities distribute income to members through mechanisms such as:
- stipends
- universal basic income (UBI)
- revenue sharing
Distribution systems ensure that the benefits of collective activity reach participants.
Embeddable Widgets
One of the most important properties of Layer 1 is that these applications are embeddable anywhere on the web.
Communities can integrate applications into their websites using widgets such as:
- buttons
- forms
- chat windows
- dashboards
- embedded application panels
These widgets communicate with Safebox servers while appearing directly within the host website.
For example:
- an auction widget can appear on an event page
- a voting widget can appear on a community portal
- a fundraising widget can appear on a nonprofit website
This approach allows communities to adopt powerful functionality without redesigning their entire websites.
Integration with Messaging Platforms
Layer 1 applications are also accessible through messaging platforms.
Participants may interact with applications via:
- Telegram bots
- Apple Business Messages
- Google Business Messages
- Facebook Messenger
These interfaces can present:
- forms
- buttons
- rich cards
- menus
This allows people to participate in community activities directly from messaging apps.
Email Interfaces
Layer 1 applications can also be accessed through email digests.
Emails may include:
- summaries of activity
- forms for responding
- links that open embedded interfaces in the email client’s browser view
This makes it possible to participate in community activities without visiting a dedicated website.
Why Layer 1 Matters
Layer 1 establishes the economic and coordination foundation of the Safebox ecosystem.
By combining users, streams, and embeddable applications, communities gain the ability to run complex systems that include:
- markets
- governance
- coordination
- resource distribution
All of these systems can operate across websites, messaging platforms, and other interfaces.
The layers above Layer 1 will add additional capabilities, including:
- AI assistants
- browser storage participation
- automation of external platforms
- operating system automation
Together these layers transform Safebox into a comprehensive platform for community coordination and organizational infrastructure.