The Human Web Charter

Why this Charter exists

The Human Web is open infrastructure. It is designed to be built and operated by many organisations — not by any one of them. The Web is multi-orchestrator by structure, not by accident: the role of operating a Human Web-compliant Pass-and-agent system is open to any orchestrator that meets the entry conditions and the commitments in this Charter.

This creates a structural tension we'd rather name than hide. Orchestrators control the user-side relationship. Users interact with their own agents; they rarely interact directly with the agents underneath those, and they almost never interact with the organisations building those agents. In a naïve read, this means participant organisations — providers operating agents, credential issuers, sponsors — give up brand presence, direct user loyalty, and the commercial signals that come with them, in exchange for a position as an interchangeable supplier inside a system someone else runs.

That's not a position we'd ask any serious organisation to accept, and it's not the deal the Human Web is offering.

This Charter sets out the specific commitments — commercial, governance, and product — that make the Human Web a genuine infrastructure layer rather than a rotation of commoditised suppliers. It applies to every orchestrator operating in the Web. It is a public document. We expect to be held to it.

What the Human Web is

The Human Web is the human-centred articulation of the agentic web — the part of the internet where people, not platforms, are the primary actors, and where four things stay with them: their identity, their agency, their self-representation, and their value.

Its purpose is human flourishing: what people do and what they become. Beneath that purpose sit two paired architectural commitments — to human agency, and to the conditions for collective wellbeing. These are what make the Web human-centred at the level of the individual and serious about the world those individuals share.

It provides:

• A trust layer — verifiable identity, credentials, and consent, portable across orchestrators that operate Human Web-compliant systems.
• Data standards and federated protocols — so agents from different providers can plug into a user's life without duplicating infrastructure.
• A certification framework — so users and orchestrators can tell which providers, issuers, and sponsors meet Human Web standards for data handling, scope, and governance.
• A set of governance commitments — the subject of this Charter.

The Human Web is not anyone's product. It is governed as a public good and is designed to outlive any single orchestrator, including the one that convenes its founding institutional work.

The commitments

These are the commitments that every orchestrator in the Human Web makes — and that Lifepass, as orchestrator of and current convening contributor to the Web, makes first. They apply to relationships with the three patterns of participant organisation: providers (those operating agents in the Web), credential-issuing organisations, and sponsors (those funding or inviting populations into the Web). Where commitments differ by pattern, the difference is named.

1. Governance independence

The Human Web will be governed by The Human Web Foundation — an independent institution, not owned or controlled by any orchestrator. No single orchestrator will hold more than a minority position on the Foundation, and its composition will include orchestrators, provider organisations, sponsor organisations, user representation, public-interest technology voices, and independent domain experts.

The Foundation has authority over:

• Human Web standards (data, identity, consent, interoperability, aggregate reporting)
• Orchestrator and provider certification criteria and process
• Sponsor relationship governance and concentration limits
• Dispute resolution between orchestrators and other participants
• Material changes to this Charter

No orchestrator will make unilateral changes to the standards participants build against.

Current status: The Human Web Foundation is pre-incorporation. Founding leadership conversations are underway. The Charter is currently published by Lifepass as convening contributor, and will pass to the Foundation on incorporation.

2. Architectural commitments any orchestrator must meet

The orchestrator role is open to any entity that builds and operates a Human Web-compliant Pass-and-agent system. The biggest concrete concern for any serious participant is structural: what stops an orchestrator from quietly preferring its own in-house agents, its own credential issuers, or its own sponsor relationships over those of independent participants?

Commitments that bind every orchestrator:

• Transparency. Where an orchestrator operates an agent, credential issuer, or sponsor relationship of its own, that fact is visible in the product and disclosed in the Foundation's governance register.
• Non-preferential selection. Agent-selection logic does not prefer an orchestrator's own agents over third-party agents on anything other than user outcomes. The selection logic is itself auditable and reviewed by the Foundation.
• Right of review. A participant whose deployment rate materially changes following an orchestrator-built entrant may request an independent review, with which the orchestrator cooperates, accepting any remediation the Foundation determines is warranted.
• Category restraint. Where the third-party participant ecosystem is serving users well, orchestrators will not build competing in-house agents. This is a commitment, not a mathematical rule, and the Foundation is the arbiter.
• Portability across orchestrators. No orchestrator can lock a participant — agent provider, credential issuer, or sponsor — into operating only within its own implementation. Participation in the Human Web is, by design, portable across orchestrators.

3. Provider attribution

Provider organisations have real presence in the product:

• Named in active deployment. Inside each user's agent surface, users can see which agent is doing what, built by which provider.
• Named in decisions. When an agent surfaces something for user approval, the underlying provider is named.
• Named in the audit log. Every action an agent takes on a user's behalf is logged with the agent and provider that executed it.
• Named in the agent surface. Users can see all providers currently active in their account, grouped by agent.

Attribution is substantive, not ceremonial. Users who want to understand who is working on their life can, at any point, know. Providers who want to build user trust through consistent quality can. Orchestrators commit to this as the minimum bar for an infrastructure position.

4. Commercial terms

Specific percentages are not published in this Charter, because they are the subject of category-specific partnership agreements between orchestrators and providers. The principles every orchestrator commits to:

• Revenue associated with a provider's agent flows substantially to that provider. The default distribution favours the provider, not the orchestrator's infrastructure.
• Stable, long-dated terms. Commercial terms for a given provider category are published, and material changes require twelve months' notice and Foundation review.
• No platform tax on value the orchestrator did not create. Orchestrators do not charge providers for user reach they brought with them, such as existing integrations or user relationships transferred into the Web.
• Fair reciprocity. Where providers receive signal value from the Web (anonymised pattern data, for example), they contribute back in kind or in cash. The Foundation sets the terms.

Full commercial terms are published by each orchestrator in a Provider Agreement, a companion document to this Charter.

5. Data rights

Users own their data. Orchestrators and providers operate inside strict, scoped permissions the user can revoke at any time. Specifically:

• Providers never hold user-identifying data unless the user has explicitly consented to a direct provider relationship (and this is rare — most agent work happens without the provider knowing who the user is).
• Providers receive scoped, ephemeral access for each action, logged and auditable.
• Users can see and shape what is held about them. Every Human Web-compliant orchestrator must give the user the means to see, interrogate, and correct the system's representation of them — the reflection condition.
• Collective-layer contributions (anonymised signal patterns) are opt-in at the user level and opt-in again at the provider level. No provider receives collective data unless they have earned the right through Human Web contribution.
• Data egress is portable. If a user leaves one orchestrator for another product on the Human Web, their trust graph, consent log, credential store, and self-representation move with them.

6. Portability

The Human Web is useful only if it is genuinely portable. Commitments every orchestrator makes:

• User portability. Users can migrate from one orchestrator to another at any time, with their agent preferences, credential store, active Destinations, consent log, self-representation, and any active sponsor relationships intact.
• Provider portability. A provider's agents can be deployed into any Human Web-compliant orchestrator, not only one. Orchestrators do not operate exclusivity clauses.
• Sponsor portability. Sponsorship relationships can be replicated across Human Web-compliant orchestrators, so that a user funded or invited by a sponsor through one orchestrator can move to another without forfeiting the sponsor relationship.
• Standards openness. The Human Web standards are published, versioned, and open. Any organisation can implement them without permission from any orchestrator or from the Foundation.

Portability is the most important single signal that the Human Web is real. Without it, everything else is marketing.

7. Attribution of user-generated value

Where users contribute to patterns, insights, or collective intelligence — and where those contributions have economic value — users share in that value. The Foundation oversees the mechanism, which will be published within eighteen months of the first opt-in user.

This is a direct commitment against the pattern in which user-generated data becomes the asset of the infrastructure owner. In the Human Web, it remains the user's asset, stewarded collectively.

8. Sponsorship governance

Sponsorship is a recognised architectural pattern in which an organisation lends its standing to a population it has a relationship with — employees, residents, members, beneficiaries — in service of that population's participation in the Human Web. The commitments below apply to all sponsor relationships, regardless of variant (funded with reporting, funded without reporting, promotion-only with reporting, promotion-only without reporting). Orchestrators commit to enforcing them; the Foundation governs them.

Reporting boundaries. Where sponsors receive reporting in return for their contribution, that reporting is bound by the architectural rules on aggregate reporting:

• No individual reidentification, by any means or combination.
• Minimum population thresholds apply; reporting is omitted in low-population contexts rather than approximated.
• Reports describe what people did, not who they are. Demographic descriptors are limited to those the Foundation has approved for the relevant context.
• The user can see what they contributed to, in their Record's aggregate-contributions log.
• Reporting templates are approved by the Foundation.

The reporting boundary is not negotiable under sponsor pressure. Sponsors who require more granular individual-level reporting are not the right sponsors for this model.

Sponsor concentration limits. The Foundation sets limits on how concentrated sponsorship can become — to prevent the Human Web from being shaped by a small number of large sponsors. Limits will include caps on any single sponsor's share of the user base, diversification requirements across sponsor categories (employer, public-sector, philanthropic, institutional), and the maintenance of a meaningful direct-consumer base as the architectural ground truth.

Sponsor accountability. Sponsors operate under the same governance the Foundation applies to other participants. They commit to the principle that the Human Web exists to serve human flourishing, not to extend their own brand or recruit users into other products. Sponsors who breach this commitment can be removed by the Foundation, with appeal.

End of sponsorship. When a sponsorship ends — change of provider, end of employment, end of programme, conclusion of grant — the user's account persists. The user has explicit options: continue self-funded at a published rate, accept a different sponsor's relationship, or revert to a free tier with reduced functionality but full identity and credentials retained. The sponsor retains no ongoing visibility, no data residual, nothing. Aggregate reports the sponsor previously received are theirs to keep; the data flow stops.

No sponsor-driven content. Sponsors do not have a content surface in the Human Web through which they can push messages, offers, or affiliated services to the populations they sponsor. Their participation is funding and/or invitation; their relationship to users is mediated entirely by the user's own agents.

Dispute resolution. Sponsor disputes follow the same path as provider disputes — first mediation, then binding independent arbitration if unresolved.

The Lifepass commercial implementation of the sponsorship pattern is described in the Sponsorship Strategic Note. The architectural pattern itself is specified in the Human Web Architecture Note.

9. Certification

Every orchestrator, every provider agent, and every sponsor relationship in the Human Web must be certified. Certification covers:

• Data handling practice
• Scope-of-action limits
• Governance and ownership transparency
• For orchestrators: full implementation of the six entry conditions, including reflection, with independent security audit within the last twelve months
• For providers: independent security audit within the last twelve months
• For sponsors: confirmation of reporting-boundary compliance and concentration discipline

Certification is renewed annually. It is administered by the Foundation and can be revoked for cause, with appeal.

10. Dispute resolution

Disputes between orchestrators and other participants — or between participants themselves — are first addressed through mediation, then, if unresolved, through binding independent arbitration, with costs borne by the losing party. The Foundation designates approved mediators and arbitrators.

What we ask of participants

The Human Web works because it is reciprocal.

• Commit to human flourishing as the test. Not installs, not spend, not engagement minutes — whether what you do, in your part of the Human Web, supports what people do and what they become.
• Contribute improvements back. If you find a better way to do the work in your category, the standards evolve. Commercial advantage is a reasonable thing to hold for a period; long-term moats built on withholding infrastructure are not.
• Abide by the Foundation's decisions. You don't have to like every decision. You do have to operate within them.
• Respect the user. Do not attempt to build a direct user relationship through the Web that the user hasn't consented to. The Human Web is for infrastructure, not customer acquisition.

What's in force today, what's still being built

This Charter is being published at a point where most of its commitments are committed-to in principle but not yet fully implemented. The first orchestrator — Lifepass — is operating, and the institutional architecture is being formed around it. Honest accounting:

Anything marked Committed or Drafted rather than In force is a public commitment we expect to be held to. Anything marked In force is implementable and verifiable today.

How to engage

If your organisation is considering participating in the Human Web — as an orchestrator, an agent-provider, a credential issuer, a sponsor, or a combination — we'd rather have an honest conversation than recruit you through a polished pitch. Specifically:

• We expect you to push back on these commitments where they don't go far enough.
• We expect to learn what categories and user needs we haven't thought about.
• We don't expect every organisation to be a fit. The Human Web is built around human flourishing, and organisations whose business model depends on outcomes other than that should probably build elsewhere.

For a first conversation, contact hello@thehumanweb.ai. For the full Provider Agreement and certification process, see the Provider Agreement (forthcoming). For the sponsorship terms, see the Sponsorship Strategic Note.

A closing note

Most attempts at "open infrastructure" fail because the stewarding organisation eventually optimises for itself at the expense of everyone else. The patterns are well-documented and Lifepass is not uniquely immune to them. No orchestrator is.

What the Human Web is betting on is that publishing specific commitments, against a timeline, accountable to an independent Foundation, with real consequences for breach — makes the infrastructure trustworthy enough that the best orchestrators, providers, issuers, and sponsors build into it. If the Charter is lived up to, the Human Web becomes something no single organisation could have built alone, and every orchestrator inside it is a better product for it. If it isn't, the Charter is the document that will hold us to account.