Back to together.ng

A network for helping people become more capable.

Together — Vision Document

Vision Explainer — coming soon.

Executive Summary

Together envisions a world where every person has a genuine opportunity to develop toward their full potential. The basic premise is simple: people do not become capable in isolation. They need access to knowledge, skills, mentorship, tools, equipment, spaces, relationships, and other forms of productive capacity. Yet much of this capacity already exists around us while remaining unused, inaccessible, or difficult to find.

The problem is therefore not only scarcity. It is also coordination. A person may be capable of progressing but blocked by a missing resource, while someone nearby—or an institution—has exactly what is needed but does not know the need exists. Today, much of this potential is trapped behind geography, money, social distance, fragmented institutions, and poor information.

Together is a non-monetary coordination network designed to connect people’s goals and unmet needs with people and institutions that can contribute knowledge, skills, resources, access, mentorship, collaboration, and other productive capacity. People can ask without shame and contribute without creating a debt. Help can flow through the network: need → capability → contribution → outcome, allowing people who become more capable to eventually contribute to others.

Over time, Together can operate beyond individual matching. When many people repeatedly express the same unmet need, the network can reveal collective capability gaps. Persistent demand for computers, books, laboratories, workshops, mentorship, equipment, or other resources can become a signal for libraries, companies, foundations, NGOs, universities, communities, and governments to create shared infrastructure rather than repeatedly addressing the same need one person at a time. In this sense, Together can become a coordination layer for turning collective unmet needs into collective capacity.

This becomes especially important in an age of abundance created by AI. AI may dramatically increase humanity’s ability to produce intelligence, software, services, and eventually many other goods at lower cost. But abundant productive capacity does not automatically mean universal access to it. People can have powerful AI and still lack the physical resources, infrastructure, capital, workspace, equipment, energy, or relationships required to turn intelligence into real-world outcomes. If access to the new productive economy remains concentrated, technological abundance could coexist with a permanent underclass that has access to intelligence but not to the means of using it.

Together’s long-term role is to help reduce that risk by making productive capacity more broadly accessible and more efficiently coordinated. Underused resources can be shared, lent, scheduled, and connected to people who can put them to productive use. AI agents can eventually participate directly in this coordination—representing people and organizations, discovering capabilities, checking availability, coordinating routine logistics, and helping resources move toward useful work within clearly delegated permissions.

The ambition is therefore larger than a platform for helping people. Together is an attempt to build social infrastructure for an abundant world: a network through which people can access the capabilities they need to develop, communities can see what they collectively lack, institutions can respond to persistent gaps, and increasingly capable AI can help coordinate the physical and human resources required for more people to participate in the productive economy.

Everyone should have an opportunity to develop to their full potential. As technology expands what humanity can produce, Together aims to make sure more people can access and participate in that expanding capacity.

何よりも、みんなを守ろう

1. The Vision

Together is a non-monetary network for people to help one another become more capable.

People have knowledge, skills, books, tools, equipment, experience, time, access, and institutional knowledge that other people need. Much of this capacity is unused or difficult to discover.

Together exists to connect those needs with people who are willing and able to help.

A person should be able to say:

“I need help becoming better at this.”

without feeling ashamed, without having to beg, and without owing the person who helps them.

Likewise, someone should be able to say:

“I can help with this.”

and easily discover people who could benefit from what they know or have.

Together is built around a simple idea:

Help received does not create a debt to the giver. It creates an opportunity for the receiver to eventually help someone else.

2. The Problem

There is enormous human capacity in the world that is poorly coordinated.

People have:

  • Knowledge they could teach
  • Skills they could share
  • Books they no longer use
  • Tools that sit idle
  • Equipment that could help someone learn or build
  • Professional experience
  • Mentorship they could provide
  • Institutional and local knowledge
  • Access to resources that others cannot easily find
  • Time they are willing to contribute

At the same time, people encounter barriers that prevent them from learning, building, creating, or progressing.

Someone may need:

  • A book
  • A mentor
  • An explanation
  • Feedback
  • A tool
  • Temporary access to equipment
  • Guidance from someone experienced
  • A learning resource
  • Help navigating an unfamiliar process
  • Someone nearby who knows how to do something
  • Someone far away with specialized knowledge

Often, the resource exists. The person who can help exists.

The problem is that they cannot find each other.

Together is intended to become a coordination layer between these two sides.

3. What Together Is Not

The distinction between Together and other forms of assistance is fundamental.

Together is not a begging platform.

People should not have to frame their needs as pleas for charity.

The platform should encourage requests that help people learn, build, create, solve problems, and increase their future capabilities.

Together is not a marketplace.

There is no requirement that help be exchanged for money.

There is no marketplace price for knowledge, mentorship, books, tools, or skills.

Together is not a barter system.

A person who receives help does not owe an equivalent amount of help to the person who provided it.

Together is not a popularity contest.

Followers, likes, wealth, and social status should not determine someone's value.

Together is not a charity ranking system.

A person's dignity should not depend on how much they have to give.

A person may join Together with nothing to offer and still be fully welcome.

4. The Core Principle: Capability Over Consumption

Together should prioritize requests that increase a person's ability to do something.

There is an important difference between:

“I need money.”

and:

“I want to learn software development but don't have access to a computer.”

The first is primarily a request for consumption.

The second is a request for access to a capability-building resource.

Together is primarily concerned with the second kind of problem.

This does not mean people's immediate needs are unimportant. It means Together has a specific mission:

Reduce the barriers that prevent people from learning, building, creating, and becoming more capable.

5. Asking for Help Is a Feature, Not a Failure

One of Together's most important cultural principles is that asking for help should carry no shame.

A person should be able to join the platform without having anything to contribute.

They should be able to ask for help without being treated as inferior.

There should be no expectation that someone must first prove their usefulness before receiving assistance.

Together should communicate:

You are allowed to need help.

People become capable through other people.

A student learns from a teacher.

An apprentice learns from a craftsperson.

An engineer learns from another engineer.

A founder learns from someone who has done it before.

A person who receives help today may become the person helping others tomorrow.

6. The Network Is Not an Exchange

Together should deliberately avoid creating a system where every act of help creates an obligation.

If Alice helps Bob learn Python, Bob does not owe Alice an equivalent amount of help.

If Alice gives Bob a book, Bob does not owe Alice a book.

If Alice lends Bob a camera, Bob does not gain a debt measured in points or credits.

Instead:

Alice → Bob → Charlie → David

Help flows through the network.

The social principle is:

Pay it forward, not pay it back.

A person can contribute whenever they are able.

This creates the possibility of a compounding network of generosity and capability.

7. What People Can Ask For

Together should support many forms of productive help.

Knowledge

  • Explanations
  • Research guidance
  • Local knowledge
  • Institutional knowledge
  • Practical knowledge
  • Advice from experience

Education

  • Mentorship
  • Tutoring
  • Study groups
  • Learning resources
  • Guidance on what to learn
  • Feedback on learning projects

Skills

  • Learning a skill
  • Teaching a skill
  • Reviewing someone's work
  • Pairing or collaborating
  • Practical instruction

Resources

  • Books
  • Tools
  • Equipment
  • Devices
  • Educational materials
  • Other useful physical or digital resources

Access

Sometimes the scarce resource is not an object but access to something.

Examples include:

  • A laboratory
  • Workshop equipment
  • Specialized software
  • Professional communities
  • Institutions
  • People with relevant experience

Collaboration

People may need others to help them:

  • Build something
  • Research something
  • Test something
  • Create something
  • Solve a difficult problem
  • Start a project

The common thread is not the category.

The common thread is:

Does this help someone move forward?

8. Asking Well

A major feature of Together should be helping people formulate useful requests.

A vague request such as:

“I need a laptop.”

does not provide enough information for the community or matching system.

Together can guide the person toward something like:

“I'm learning backend development and currently only have access to my phone. I need a computer capable of running VS Code and Docker so I can complete a 12-week course. I live in Ibadan and can pick it up locally.”

A good request communicates:

  • What the person is trying to accomplish
  • What is preventing them from progressing
  • What kind of help would solve the problem
  • Relevant constraints
  • Location when relevant
  • Duration when relevant
  • The desired outcome

Better requests improve both human discovery and automated matching.

Together should help users turn:

“I need help.”

into:

“This is what I'm trying to accomplish, this is the barrier, and this is the specific help that would move me forward.”

9. Matching

When users register, they can specify areas in which they are willing to help.

These should initially come from a predefined taxonomy of categories.

Users can then provide more specific capabilities within those categories.

For example:

Category: Software Development

Can help with:

  • JavaScript
  • Python
  • Backend architecture
  • PostgreSQL
  • Linux
  • Code review

A person does not need to offer anything.

They can leave their contribution profile empty and simply participate as someone seeking help.

When a new request is created, Together can identify people whose stated capabilities are relevant.

Potential contributors can receive notifications when requests matching their interests appear.

Matching should eventually consider:

  • Skills
  • Resource type
  • Location
  • Availability
  • Duration
  • User preferences
  • Request quality
  • Previous successful contributions
  • Other relevant context

The goal is not to maximize notifications.

The goal is to maximize useful connections.

10. Discovery Beyond Matching

Not every contribution will happen through automated matching.

Together should provide public discovery surfaces.

There can be:

A general feed of requests that the community can discover.

Category Feeds

Requests within areas such as:

  • Education
  • Technology
  • Science
  • Arts
  • Engineering
  • Business
  • Trades
  • Books
  • Tools
  • etc.

Voting

People can upvote requests they want to see receive attention.

An upvote does not represent money, reputation currency, or an obligation.

It can simply mean:

“I think this is worth helping.”

This creates a second way of contributing.

Someone who cannot personally satisfy a request can still increase its visibility.

The ranking system should eventually combine factors such as:

  • Community interest
  • Recency
  • Request quality
  • Category relevance
  • Potential matches
  • Urgency

rather than relying solely on popularity.

11. Reputation Without Currency

Together should have reputation, but reputation should never become money.

There should be no:

  • Coins
  • Credits
  • Points that represent exchange value
  • Follower counts
  • Pay-to-increase reputation

Instead, reputation should describe a person's history of contribution and trust.

Potential signals include:

Contributor since

When the person joined the contributing community.

People helped

The number of people who report successfully receiving help.

Contributions

A record of completed contributions.

Verified skills

Skills for which there is meaningful evidence or community verification.

Trust signals

Evidence of reliable participation.

Badges

Badges can recognize patterns of contribution without becoming a currency.

Examples:

  • Helpful Mentor
  • Book Sharer
  • Community Contributor
  • Skill Contributor
  • Resource Lender
  • Consistent Contributor
  • Early Contributor

Badges should celebrate behavior rather than create a competitive hierarchy.

The objective is:

Trust, not status.

12. Everyone Can Be a Receiver and a Contributor

Together should avoid creating a permanent distinction between:

people who give

and

people who receive.

People are likely to move between these roles throughout their lives.

Someone may join with several needs and no contributions.

Later they may learn something.

Then they can teach it.

Someone may have knowledge but no physical resources.

Someone else may have resources but little specialized knowledge.

Someone may be highly skilled professionally but need help with something completely unrelated.

This is what makes the network fundamentally different from charity.

Everyone has something they need, and almost everyone has something they can eventually contribute.

13. Physical Resources and Lending

Physical resources introduce additional trust and safety concerns.

Together should treat lending differently from low-risk forms of help such as advice or knowledge sharing.

Examples include:

  • Books
  • Tools
  • Electronics
  • Cameras
  • Computers
  • Musical instruments
  • Workshop equipment

Risk should increase with the value and sensitivity of the resource.

Possible safeguards include:

  • Progressive identity verification
  • Trust requirements for higher-value lending
  • Lending history
  • Clear lending agreements
  • Photos documenting condition before handoff
  • Photos documenting condition on return
  • Both parties confirming handoff and return
  • Reporting and dispute mechanisms
  • Restrictions on newly created accounts accessing high-value resources

A new account may be able to ask:

“Can someone teach me Python?”

without being allowed to immediately borrow an expensive camera.

Trust should be earned through behavior.

14. Accountability

Reputation is useful, but reputation alone is not sufficient protection.

Someone who intentionally damages or steals a resource should not simply be able to delete an account and start again.

Together should therefore distinguish between:

Public reputation

and

internal trust and safety records.

For serious violations, Together can:

  • Suspend accounts
  • Restrict access to lending
  • Require additional verification
  • Prevent new accounts from immediately accessing high-risk activities
  • Investigate disputes
  • Preserve relevant incident records
  • Cooperate with appropriate authorities where legally required

The platform should prefer accountability over public shaming.

The goal is to protect the community rather than create a public punishment system.

15. Insurance

Insurance should not be a requirement for the basic Together experience.

The initial platform should focus on building the community and validating whether people actually want to share resources.

If physical lending becomes significant, Together could eventually explore partnerships with insurance providers for higher-value resources.

This could become an optional layer:

Community lending For low-risk resources and trusted participants.

Protected lending For higher-value resources where additional protection is useful.

Insurance is therefore infrastructure that may emerge as the network grows, rather than the foundation of the product.

16. Institutions Are Part of the Network

Together should not limit itself to individuals.

Organizations may have enormous amounts of unused capacity.

Potential contributors include:

  • Schools
  • Universities
  • Libraries
  • Companies
  • Workshops
  • Laboratories
  • Community organizations
  • Professional associations
  • Makerspaces
  • Nonprofits

An institution might provide:

  • Equipment
  • Books
  • Training
  • Mentorship
  • Facilities
  • Access
  • Expertise

This expands the network from:

person ↔ person

to:

people ↔ people ↔ institutions ↔ resources

This could become particularly important for expensive or specialized resources.

17. The Human Capability Graph

Over time, Together could develop into more than a collection of requests.

It could become a graph connecting:

People ↓ Skills ↓ Resources ↓ Projects ↓ Needs ↓ People

For example:

A person wants to learn electronics.

They find a mentor.

The mentor recommends a book.

Someone nearby has the book.

Another person has a soldering station.

The learner builds a project.

They eventually acquire enough knowledge to help another beginner.

This creates a network where knowledge, skills, resources, and people continuously connect.

The long-term opportunity is not merely helping people find answers.

It is making human capability more discoverable.

18. AI as a Coordination Layer

AI can eventually make Together substantially more useful, but AI should not replace the human contribution at the heart of the network.

AI can help users:

  • Formulate better requests
  • Identify what they actually need
  • Break large goals into specific needs
  • Match requests to skills and resources
  • Recommend relevant contributors
  • Recommend relevant resources
  • Summarize or structure requests
  • Detect duplicate or related requests
  • Improve search and discovery
  • Help contributors understand how they can help

For example, a user might say:

“I want to learn electronics but I don't know where to start.”

Together could transform this into:

Goal: Learn basic electronics Level: Beginner Needs: Learning path + mentor + practical resources Location: Ibadan Desired outcome: Build a first working circuit

It can then search the network for people, books, tools, institutions, and other resources.

AI becomes the coordination layer.

Humans remain the source of many of the scarce things that matter:

  • Experience
  • Trust
  • Mentorship
  • Physical resources
  • Local knowledge
  • Access
  • Relationships
  • Judgment

19. The Product Flywheel

Together's ideal cycle is:

A person has a goal ↓ They encounter a barrier ↓ They ask for specific help ↓ Together finds relevant people/resources ↓ Someone contributes ↓ The person progresses ↓ The contribution is recorded as successful ↓ Trust increases ↓ The recipient becomes more capable ↓ They eventually contribute to someone else

The most important transition is:

Need → Capability → Contribution

That is the behavior Together wants to encourage.

20. What Success Looks Like

Together should not primarily measure success through registered users, followers, page views, or likes. Those are secondary.

The first question is whether useful contributions actually happen:

Does a meaningful need become a useful contribution that helps someone move forward?

But contribution volume is not the whole story. A healthy network must also understand the relationship between demand and capacity.

Together should therefore learn from:

  • Requests created
  • Requests receiving useful responses
  • Time to first useful response
  • Successful contributions
  • Repeat contributors
  • Repeat recipients
  • Percentage of recipients who later contribute
  • Unmet requests
  • Categories with persistent unmet demand
  • Local versus remote contribution activity
  • Resource and capability bottlenecks

An early community that helps ten people meaningfully may be more valuable than a much larger community with little useful interaction. At the same time, a large volume of legitimate unmet requests can reveal something important about where the network's capacity is insufficient.

The objective is not to make every request disappear. It is to make useful help easier to find while learning where help is scarce.

21. Need, Capacity, and the Limits of the Network

Together should not promise that every legitimate request will be fulfilled.

The network's capacity is determined by what people and institutions are actually willing and able to contribute.

There may be many more requests than contributors. Some requests may remain unmet for a long time. This is not automatically a failure of the platform or of the person making the request.

A request can be legitimate and still have no available contributor.

Together should therefore distinguish between:

Need — what someone is trying to accomplish and what is preventing them.

Supply — what people and institutions are willing and able to contribute.

Match — whether there is a plausible contributor for a particular need.

Fulfillment — whether the contribution actually happened.

Unmet demand — legitimate needs for which the network has not found an adequate contribution.

This distinction matters because the answer to persistent unmet demand may not be another individual contributor. It may be a library, laboratory, training centre, community workshop, equipment pool, scholarship program, public service, or other form of shared infrastructure.

Together can help reveal those gaps without claiming that it alone can solve them.

22. A Living Map of Expressed Needs

As Together grows, the collection of requests may become useful in its own right.

Every request describes something a person is actively trying to do:

  • Learn something
  • Complete an education
  • Build a project
  • Access a resource
  • Acquire a skill
  • Find mentorship
  • Solve a practical problem
  • Reach an institution or community
  • Continue an opportunity that might otherwise be lost

Aggregated across many people and locations, these requests can reveal patterns that are difficult to see from individual interactions.

Together could eventually show where particular capabilities, resources, and forms of access are repeatedly being requested and where those needs remain underserved.

Location is important because a resource gap in one place may not exist in another. A concentration of requests for computers, laboratory access, technical books, workshops, or particular skills can suggest that the most effective intervention may be shared infrastructure rather than many isolated acts of assistance.

This should be understood as a map of expressed demand among Together participants, not a statistically representative survey of an entire population. The platform should not claim to speak for everyone simply because many people use it.

The value comes from the fact that the information is tied to real, active goals and barriers rather than only abstract opinions.

23. From Individual Help to Collective Infrastructure

Together can operate at two levels.

At the individual level:

A person needs something. Another person or organization can help.

At the collective level:

Many people need similar things, and the pattern suggests a larger intervention.

Imagine a community repeatedly requesting:

  • Computers for technical learning
  • Books that local libraries do not stock
  • Access to laboratory equipment
  • Engineering tools
  • Skilled mentorship
  • A place to build or practice

The appropriate response may eventually be to create a shared resource rather than fulfill hundreds of individual requests separately.

A library could acquire frequently requested books.

A university could open underused laboratory capacity.

A company could establish an equipment-lending program.

A foundation could fund a community technology lab.

A professional association could create a mentorship program.

A government or development organization could investigate a persistent regional capability gap.

Together's role is not to decide which intervention should happen. Its role can be to make patterns of expressed need easier to see and easier for relevant institutions to respond to.

24. Assistance History as Community Memory

Together should preserve useful history around requests and contributions.

A person should not have to repeatedly start from zero when explaining what they have previously received or what they have already tried.

With appropriate privacy controls, a contributor or participating organization could see relevant assistance history before deciding whether to help.

For example, if someone has previously received a computer for a particular educational goal, a later organization considering a similar request could see that history and ask what happened before providing another intervention.

This does not mean a previous contribution makes a person ineligible for future help. Circumstances change. Equipment can break, be lost, become inadequate, or be needed for a different purpose.

History provides context; it does not make the decision.

This persistent memory can also reduce some forms of duplicate assistance and make repeated claims easier to identify. It may help participating organizations coordinate assistance that would otherwise be fragmented across separate databases.

The same principle applies to organizations. If an organization records assistance through Together, participating funders or partners could eventually inspect the relevant chain of request, authorization, contribution, and outcome rather than relying entirely on isolated internal records.

Together should be an accountability and coordination layer, not an authority that declares a person or organization truthful or deserving.

25. Transparency Without Public Exposure

A history of assistance can be useful without making every private detail public.

Together should distinguish between:

  • Public information that helps the community discover useful needs
  • Private information needed for coordination
  • Sensitive information that requires stronger protection
  • Authorized information available to participating organizations or auditors

The objective is not to create a public database of vulnerable people.

The objective is to create trustworthy memory around assistance while preserving dignity and privacy.

A public view might show that a type of educational resource is repeatedly requested in a region. An authorized organization might have access to more detailed records needed to coordinate a program. Private identity, contact information, documents, and sensitive circumstances should not become public merely because a request exists.

26. A Broader Development Role

The long-term value of Together may therefore extend beyond individual matching.

At scale, the network could help connect three kinds of activity:

People helping people

Individual contributions of knowledge, time, resources, skills, and access.

Institutions responding to needs

Libraries, schools, companies, foundations, nonprofits, professional organizations, laboratories, community groups, and governments using aggregated signals to understand where intervention may be useful.

Communities building shared capacity

Shared infrastructure that addresses recurring unmet needs rather than repeatedly treating the same need as an isolated individual problem.

The aspiration is a system in which assistance can move from the individual level to the infrastructure level when patterns justify it.

27. The Product Flywheel

Together's ideal cycle is:

A person has a goal ↓ They encounter a barrier ↓ They ask for specific help ↓ Together finds relevant people or resources ↓ Someone contributes ↓ The person progresses ↓ The contribution is recorded ↓ The network becomes more informative and trustworthy ↓ The recipient becomes more capable ↓ They may eventually contribute to someone else

At larger scale, another loop can emerge:

Many expressed needs ↓ Patterns become visible ↓ Persistent capability gaps are identified ↓ Institutions respond ↓ Shared capacity grows ↓ Some unmet needs disappear

Together should be capable of supporting both loops without assuming that either will happen automatically.

28. The Long-Term Vision

The long-term vision for Together is a world where access to human capability is less constrained by money, geography, or the limits of one's immediate social circle.

A person should not have to already know the right person to find:

  • A teacher
  • A mentor
  • A book
  • A tool
  • A skill
  • An explanation
  • A collaborator
  • A local expert
  • A useful resource
  • Someone willing to help

The internet has connected people socially.

Marketplaces have connected people economically.

Search engines have connected people to information.

Together aims to help connect people to each other's capacity to help.

Not through money.

Not through debt.

Not through status.

Through contribution.

And when individual contribution is not enough, the patterns created by the network can help communities and institutions see where greater shared capacity may be needed.

29. AI, Abundance, and Shared Physical Capacity

AI may unlock a period of extraordinary productivity. As intelligent systems make more kinds of work cheaper, faster, and easier to perform, society may move toward a future in which many goods and services are more abundant than they are today. That future is not guaranteed, and greater productive capacity will not automatically mean that everyone can access what they need.

Abundance is not only a question of how much can be produced. It is also a question of who can access the tools, materials, machines, spaces, infrastructure, and productive capacity that make new things possible.

A person may have access to powerful AI and still lack a computer capable of running a workflow, a workshop, a camera, a vehicle, specialist equipment, a reliable workspace, or the physical materials needed to turn an idea into reality. AI can lower the cost of thinking and coordination, but it cannot make every physical constraint disappear. In some cases, the missing piece will be an object; in others, it will be temporary access, machine time, a place to work, energy, logistics, or a person who can operate or maintain the equipment.

Together can help coordinate access to this wider pool of productive capacity. Instead of every person or organization needing to own every tool, more resources could be shared, lent, scheduled, maintained, and put to use by the people and projects that can benefit from them. The aim is not sharing for its own sake. It is to reduce the amount of useful capacity that sits idle while other people are prevented from learning, building, repairing, researching, or creating because they cannot access it.

Beyond cash transfers

Universal Basic Income (UBI) is one proposal for sharing the gains of automation by giving people an income they can use to meet their needs. Together explores a different, and potentially complementary, route: make useful capabilities and productive resources easier to access directly through a coordinated network.

Money can help people acquire things, but it does not guarantee that a needed resource exists nearby, is available at the right time, or can be found and used. Where the barrier is access to an underused tool, facility, skill, or service, coordinating access may address the barrier more directly than transferring money alone. Together is therefore not simply a cash-distribution mechanism. It is an attempt to make the productive capacity already distributed across people, organizations, and communities more accessible.

This should not be read as a claim that resource sharing can replace income support or public services in every circumstance. People need freedom and purchasing power, and some needs are best met through money, markets, public provision, or other institutions. Together's role is to develop another layer of social infrastructure: one that can complement those systems and make abundance useful in practical, everyday ways.

AI agents as participants in coordination

As AI agents become capable of taking actions on behalf of people and organizations, they should be able to interact directly with Together—not only as tools that help a human write a request, but as authorized participants in coordination.

For example, an agent acting for a learner could identify the equipment needed for a project, find nearby resources, check availability, and propose a borrowing window. An agent acting for a library, workshop, company, or individual could publish available capacity, answer routine questions, coordinate schedules, arrange handoffs, and update availability. Agents representing different participants could exchange structured information and resolve routine coordination steps, bringing a human in when judgment, consent, risk, or a meaningful commitment requires it.

This could make the network more useful as the number of people, resources, and possible matches grows. People should not have to manually coordinate every detail, and an organization should not need a staff member to answer every routine question about a resource. AI agents can lower those coordination costs while the actual resources, decisions, and accountability remain grounded in people and institutions.

Agent participation must remain permissioned and accountable. An agent should act within the authority its human or organization has granted; its identity and represented party should be clear; consequential actions should require appropriate confirmation; and resource access, privacy, safety, and lending rules should still apply. Agents can coordinate and make proposals, but should not silently commit someone else's property, disclose private information, or override a person's choices.

The long-term possibility is a network in which people and organizations make their capabilities discoverable, AI agents help locate and coordinate those capabilities, and physical and digital resources move toward useful work with less friction. AI would not be the source of generosity or the owner of the resources. It would help the network recognize opportunities and act on them.

The abundance question

If AI makes it possible to produce more with less human labor, a central social question will be how the benefits of that productivity become real in people's lives. Together's contribution to that question is practical: can a person use the network to access the equipment, knowledge, space, materials, infrastructure, or collaboration needed to turn increased productive potential into actual capability?

The vision is not merely that people receive a share of abundance. It is that more people can participate in creating it—and that the useful capacity already around us is less likely to remain inaccessible or idle.

30. Trust, Lending, and Open Protocols

As Together expands from knowledge and mentorship into physical resources, a different kind of coordination problem appears. It may be possible to discover a useful resource without personally knowing the person who owns it, but discovery alone does not create enough trust for every kind of handoff.

A person may be willing to lend a camera, laptop, tool, vehicle, machine, or other resource to someone they do not already know, provided there is a reasonable way to establish the terms and manage the risk.

Together does not need to become the financial or settlement system for these interactions. Its role can remain the intent and coordination layer: understanding what someone is trying to accomplish, finding relevant people and resources, and bringing the participants together. Other open protocols or specialized services could eventually provide the infrastructure for higher-risk arrangements.

A future interaction could therefore look like:

Human goal ↓ AI understands the required capability ↓ Together discovers a relevant person, organization, or resource ↓ A trust or lending protocol establishes permitted terms ↓ Agents coordinate the practical details ↓ The physical resource is used ↓ The handoff, return, and outcome are recorded

Such a protocol could eventually support mechanisms such as:

  • Lending agreements
  • Deposits or collateral where appropriate
  • Escrow
  • Identity or capability attestations
  • Delegated trust between participants
  • Condition records
  • Return and settlement rules
  • Dispute and recovery mechanisms

Blockchain or other decentralized infrastructure may be useful for some of these functions because agreements, attestations, or settlement rules can potentially be made portable and independently verifiable. But blockchain is not the point of Together, and it should not be required for ordinary requests, matching, contribution, or coordination. The technology should follow the trust problem rather than define the product.

The important distinction is between contribution and risk management. Together can remain a network where receiving help does not create a social debt while still allowing a particular physical lending arrangement to have a deposit, collateral requirement, insurance, or other protection. Those mechanisms protect the resource and the participants; they do not turn the wider network into a system of reciprocal debt.

This also creates a path toward participation by people who are only semi-acquainted. A person does not need to personally know every other participant if the network can provide enough context, history, permissions, and appropriate safeguards for them to make their own decision.

The long-term architecture could therefore separate three layers:

Together — intent and coordination

Needs, capabilities, resources, discovery, matching, AI agents, and human coordination.

Trust and exchange protocols — agreements and settlement

Lending, escrow, collateral, attestations, insurance, delegated trust, dispute conditions, and settlement where needed.

The physical world — actual productive capacity

Computers, books, laboratories, workshops, tools, vehicles, machines, spaces, materials, and the people who operate or maintain them.

Together's ambition is to make the first layer good enough that the other layers can connect to it. A person should be able to express an intention, and the network should increasingly be able to discover the capabilities and resources that could make that intention possible.

31. Product Principles

Together should be guided by several principles.

Dignity first

Asking for help should never be treated as shameful.

Capability over consumption

Prioritize help that enables people to learn, build, create, and progress.

Contribution without debt

Receiving help never creates an obligation to repay the giver.

Trust over popularity

Reputation should communicate reliability and contribution, not social status.

Human contribution over transactional value

The platform should make it easier for people to contribute things that markets often fail to coordinate.

Specificity improves generosity

Better-defined needs make it easier for people to recognize that they can help.

Everyone belongs

A person can contribute nothing at first and still be welcome.

Start open, become trusted

Low-risk participation should remain accessible while higher-risk activities require stronger trust.

Attention is also contribution

Helping a useful request become visible can itself be valuable.

The platform should facilitate, not dominate

Together should coordinate people rather than make itself the center of every interaction.

History should create context, not stigma

Past assistance should help people and organizations make better decisions without turning history into a permanent judgment of worthiness.

Data should serve people first

Information should be collected because it improves coordination, safety, accountability, or understanding. The potential future value of aggregate data should never become an excuse to collect unnecessary personal information.

32. The Core Statement

Together is a network for helping people become more capable.

Ask for what you need to learn, build, create, or progress. Share what you know, what you can do, or what you have.

You don't have to pay back the person who helped you. When you're able, help someone else.

Together, we make human capability easier to find and easier to share.