From d08d383f95a65f393c1ce11aa71101bf39cce650 Mon Sep 17 00:00:00 2001 From: Kristofer Date: Thu, 1 Oct 2026 12:12:43 +0200 Subject: [PATCH 1/4] docs: align organization profile with current documentation --- profile/README.md | 129 +++++++++++++++------------------------------- 1 file changed, 41 insertions(+), 88 deletions(-) diff --git a/profile/README.md b/profile/README.md index 7c8036b..a6feb9b 100644 --- a/profile/README.md +++ b/profile/README.md @@ -1,115 +1,68 @@ # Hypercerts -Hypercerts create shared context—evidence, expert input, and community trust—for better resource allocation. At its core, a hypercert is a living digital record of impactful work: what was done or is planned, by whom, when, and where. As evidence and evaluations accumulate over time, it becomes a shared, evolving picture of work and its value. +Hypercerts is an open protocol for describing work, evidence, evaluations, and funding on [AT Protocol](https://atproto.com/). It gives projects, evaluators, communities, and funders a shared language for recognizing valuable work and making better funding decisions. -Today's impact funding systems are fragmented and inefficient. Hypercerts address this with a simple pattern—record, evaluate, fund—that works across climate and regeneration, open-source software, research and development, and community programs. Built on the AT Protocol as open infrastructure, records are portable, referenceable, and not locked into any single platform. +A hypercert is a living, verifiable record of impact work: who contributed, what they did, when, and in what scope. Linked evidence, measurements, contributions, and independent evaluations enrich that record over time. Records live in AT Protocol repositories controlled by their authors, so compatible applications can reuse them without locking the information into one platform. -
- What problem does this solve? - -In many domains, valuable work produces public or shared benefits, but information about that work—what was done, by whom, with what evidence, and how it was evaluated—is fragmented, ephemeral, or locked inside platforms. +[Certified](https://certified.app) is an application built on the Hypercerts Protocol. It lets people publish activities, group them into projects, organize as groups, and recognize each other's work through endorsements. Hypercerts is the shared protocol, not a single application or marketplace. -This makes it difficult to: -- evaluate work in pluralistic ways, -- coordinate funding across many contributors and evaluators, -- reuse prior information rather than recreating it from scratch. +## Start with the documentation -Hypercerts address this by providing a shared, open data model for describing work and its evaluation as first-class, linkable records. -
- -
- What are hypercerts? +**[docs.hypercerts.org](https://docs.hypercerts.org/)** is the main entry point for the current protocol, integration guides, tools, and service references. -At a high level, a hypercert: -- describes **an activity or scope of work**, -- links to **evidence** and contextual data, -- can be **evaluated by multiple parties over time**, -- can be **referenced by funding and ownership mechanisms**. +- [What are Hypercerts?](https://docs.hypercerts.org/core-concepts/what-is-hypercerts): the record structure and how it is used. +- [Quickstart](https://docs.hypercerts.org/getting-started/quickstart): create your first hypercert. +- [Building on Hypercerts](https://docs.hypercerts.org/getting-started/building-on-hypercerts): integration patterns for platforms and tools. +- [Core data model](https://docs.hypercerts.org/core-concepts/hypercerts-core-data-model) and [lexicon reference](https://docs.hypercerts.org/lexicons/introduction-to-lexicons): record types, schemas, and relationships. +- [Architecture overview](https://docs.hypercerts.org/architecture/overview) and [Certified services](https://docs.hypercerts.org/reference/certified-services): how the infrastructure fits together and where to connect. -Hypercerts are not a marketplace or a single application. They are a protocol-level building block that can be used by many different tools, communities, and funding mechanisms. +On-chain anchoring and tokenization for the AT Protocol-based protocol are planned, not currently implemented. Hypercerts records are not tokens. See [Funding & Value Flow](https://docs.hypercerts.org/core-concepts/funding-and-value-flow) for the current design and status. -The design emphasizes: composability, reuse, plural evaluation, and durability of records. -
+## Current repositories -
- Architecture +### Protocol and infrastructure -Hypercerts span both social and financial layers: +| Repository | Purpose | Documentation | +| --- | --- | --- | +| [hypercerts-lexicon](https://github.com/hypercerts-org/hypercerts-lexicon) | Hypercerts and Certified lexicons, generated TypeScript types, and validators | [Lexicons](https://docs.hypercerts.org/lexicons/introduction-to-lexicons) | +| [ePDS](https://github.com/hypercerts-org/ePDS) | Extended Personal Data Server with email-first account creation and authentication | [ePDS](https://docs.hypercerts.org/architecture/epds) | +| [certified-group-service](https://github.com/hypercerts-org/certified-group-service) | Role-based governance and shared management of a group's AT Protocol repository | [CGS](https://docs.hypercerts.org/architecture/certified-group-service) | +| [hypercerts-relay](https://github.com/hypercerts-org/hypercerts-relay) | Relay and Jetstream infrastructure for streaming repository events | [Relay and Jetstream](https://docs.hypercerts.org/tools/hypercerts-relay) | +| [hypercerts-feed-service](https://github.com/hypercerts-org/hypercerts-feed-service) | Read-only, viewer-scoped feeds from indexed Hypercerts data | [Feed Service](https://docs.hypercerts.org/tools/hypercerts-feed-service) | -- **Offchain / social data** - - Records for activities, evidence, evaluations, and relationships - - Built on [ATProto](https://atproto.com/) as an open data layer - - Portable identities and durable references +The documentation also covers [Hyperindex](https://docs.hypercerts.org/tools/hyperindex), the ecosystem indexer maintained in [gainforest/hyperindex](https://github.com/gainforest/hyperindex). The former `hypercerts-org/hyperindex` repository is archived. -- **Onchain (optional)** - - Ownership, fractionalization, and transfer - - Anchoring records or hashes on public blockchains - - Used when financial coordination or incentives are required +### Applications and developer resources -This separation allows hypercerts to be useful even without tokenization, while still supporting onchain mechanisms where appropriate. -
+- [certified-app](https://github.com/hypercerts-org/certified-app): the application at [certified.app](https://certified.app). +- [skills](https://github.com/hypercerts-org/skills): [agent skills](https://docs.hypercerts.org/tools/hypercerts-agent-skills) for working across the Hypercerts stack. +- [documentation](https://github.com/hypercerts-org/documentation): the source for [docs.hypercerts.org](https://docs.hypercerts.org/). +- [hypercerts-org](https://github.com/hypercerts-org/hypercerts-org): the [hypercerts.org](https://hypercerts.org) website.
- Who is this for? + Legacy repositories (v0.1) -Hypercerts are intended for: -- builders of funding, evaluation, or coordination tools -- evaluators, reviewers, and domain experts producing assessments or judgments -- researchers exploring new institutional or economic mechanisms -- open-source and public-interest projects seeking better funding primitives -- funders experimenting with pluralistic or retrospective allocation models - -You do not need to adopt the entire stack to use hypercerts—individual components can be reused independently. -
+These repositories belong to the earlier blockchain-based implementation, not the current AT Protocol-based integration path. Start with the documentation above for new integrations. -# Repositories +- [hypercerts-protocol](https://github.com/hypercerts-org/hypercerts-protocol): smart contracts and the contracts npm package. +- [hypercerts-app](https://github.com/hypercerts-org/hypercerts-app): the original app.hypercerts.org application. +- [hypercerts-sdk](https://github.com/hypercerts-org/hypercerts-sdk): the deprecated contract SDK. +- [marketplace-sdk](https://github.com/hypercerts-org/marketplace-sdk): the marketplace SDK built on LooksRare. +- [hypercerts-indexer](https://github.com/hypercerts-org/hypercerts-indexer): the legacy contract indexer. +- [hypercerts-api](https://github.com/hypercerts-org/hypercerts-api): the legacy OpenAPI and GraphQL API. -## Active repositories - -### Protocol & data layer - -- [hypercerts-lexicon](https://github.com/hypercerts-org/hypercerts-lexicon) — ATProto lexicons (data schema) for hypercerts -- [hyperindex](https://github.com/hypercerts-org/hyperindex) — query hypercert data across the network -- [ePDS](https://github.com/hypercerts-org/ePDS) — extended Personal Data Server for hypercerts -- [certified-group-service](https://github.com/hypercerts-org/certified-group-service) — group coordination service for managing a PDS -- [documentation](https://github.com/hypercerts-org/documentation) — [docs.hypercerts.org](https://docs.hypercerts.org) - -### Applications & tools - -- [hypercerts-org](https://github.com/hypercerts-org/hypercerts-org) — the [hypercerts.org](https://hypercerts.org) website -- [certified-app](https://github.com/hypercerts-org/certified-app) — portable impact profiles at [certified.app](https://certified.app) - -## Legacy repositories (v0.1) - -- [hypercerts-protocol](https://github.com/hypercerts-org/hypercerts-protocol) — smart contracts and the contracts NPM package -- [hypercerts-app](https://github.com/hypercerts-org/hypercerts-app) — the original app.hypercerts.org application -- [hypercerts-sdk](https://github.com/hypercerts-org/hypercerts-sdk) — SDK with contract methods, helpers, and tooling -- [marketplace-sdk](https://github.com/hypercerts-org/marketplace-sdk) — marketplace SDK (built on Looksrare) -- [hypercerts-indexer](https://github.com/hypercerts-org/hypercerts-indexer) — custom indexer for rapid data access -- [hypercerts-api](https://github.com/hypercerts-org/hypercerts-api) — OpenAPI and GraphQL instance for querying data -- [ecocerts](https://github.com/hypercerts-org/ecocerts) — discussion and development of hypercerts for ecological impact - -# Further resources - -**Contributing** -- [CONTRIBUTING.md](./CONTRIBUTING.md) for how to get involved -- [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) for community standards + -**General information** -- Website: https://hypercerts.org -- Documentation: https://docs.hypercerts.org -- Blog: https://hypercerts.org/blog +## Get involved -**Contact** -- [Bluesky](https://bsky.app/profile/hypercerts.org) -- [Twitter](https://x.com/hypercerts) -- [Telegram](https://t.me/+YF9AYb6zCv1mNDJi) -- [Telegram Support](https://t.me/+FODiLtCV2TgwNzRi) +- [Contributing](https://github.com/hypercerts-org/.github/blob/main/profile/CONTRIBUTING.md) and [Code of conduct](https://github.com/hypercerts-org/.github/blob/main/profile/CODE_OF_CONDUCT.md). +- [Website](https://hypercerts.org), [blog](https://hypercerts.org/blog), and [contact](https://hypercerts.org/contact). +- [Bluesky](https://bsky.app/profile/hypercerts.org), [Twitter](https://x.com/hypercerts), and [Telegram / support](https://t.me/+o4wPsJ7yEZYzNGFk). -# Supporters +## Supporters The hypercerts project is supported by organizations and individuals who believe in building open, interoperable infrastructure for recognizing and coordinating around real-world work. These include: Protocol Labs, Ma Earth, GainForest, Optimism, Octant, Gitcoin, Silvi, Regen Foundation, and Funding the Commons. -Their support—through funding, collaboration, feedback, and shared experimentation—helps advance the development of hypercerts as a public-good primitive. Support does not imply endorsement of specific design decisions or applications. +Their support, through funding, collaboration, feedback, and shared experimentation, helps advance the development of hypercerts as a public-good primitive. Support does not imply endorsement of specific design decisions or applications. We're grateful to all supporters who contribute time, resources, and trust to this ongoing effort. From a300b68e88958e228b6e10c1b8c7f6fdeb7414f0 Mon Sep 17 00:00:00 2001 From: Kristofer Date: Thu, 1 Oct 2026 12:24:42 +0200 Subject: [PATCH 2/4] docs: align profile with documentation rebuild PR --- profile/README.md | 42 ++++++++++++++++++++++++------------------ 1 file changed, 24 insertions(+), 18 deletions(-) diff --git a/profile/README.md b/profile/README.md index a6feb9b..41063d8 100644 --- a/profile/README.md +++ b/profile/README.md @@ -1,22 +1,27 @@ # Hypercerts -Hypercerts is an open protocol for describing work, evidence, evaluations, and funding on [AT Protocol](https://atproto.com/). It gives projects, evaluators, communities, and funders a shared language for recognizing valuable work and making better funding decisions. +**Open infrastructure for funding valuable work.** -A hypercert is a living, verifiable record of impact work: who contributed, what they did, when, and in what scope. Linked evidence, measurements, contributions, and independent evaluations enrich that record over time. Records live in AT Protocol repositories controlled by their authors, so compatible applications can reuse them without locking the information into one platform. +Hypercerts is an open protocol to connect projects with those who review them, vouch for them, and back them, creating the trust it takes to fund what matters. -[Certified](https://certified.app) is an application built on the Hypercerts Protocol. It lets people publish activities, group them into projects, organize as groups, and recognize each other's work through endorsements. Hypercerts is the shared protocol, not a single application or marketplace. +Projects publish their work, updates, and evidence as records they control. Others add endorsements, evaluations, and funding records, each attributed to whoever provided it. Built on [AT Protocol](https://atproto.com/), these records can be reused across compatible applications, so the next funding decision can build on what is already known instead of starting from scratch. + +A hypercert, or activity claim, describes planned, ongoing, or completed work: who contributed, what they did, when, and where. It is the publisher's account of the work, not proof of impact on its own. Evidence and independent assessments help others judge it over time. ## Start with the documentation -**[docs.hypercerts.org](https://docs.hypercerts.org/)** is the main entry point for the current protocol, integration guides, tools, and service references. +**[docs.hypercerts.org](https://docs.hypercerts.org/)** explains the protocol and the stack in four sections: + +- [Guide](https://docs.hypercerts.org/guide): how work, evidence, assessments, trust, and funding connect across applications. +- [Client Integration](https://docs.hypercerts.org/client-integration): where your application fits, account setup, and what you can build with today. +- [Reference](https://docs.hypercerts.org/reference): lexicons, services and tooling, and the API and SDK as they are released. +- [Changes](https://docs.hypercerts.org/changes): protocol releases and component versions. + +New to the project? Start with [hypercerts.org](https://hypercerts.org) for the high-level story, then follow the Guide. For schemas and connection details, see the [lexicon inventory](https://docs.hypercerts.org/reference/lexicon-inventory) and [services overview](https://docs.hypercerts.org/reference/services). -- [What are Hypercerts?](https://docs.hypercerts.org/core-concepts/what-is-hypercerts): the record structure and how it is used. -- [Quickstart](https://docs.hypercerts.org/getting-started/quickstart): create your first hypercert. -- [Building on Hypercerts](https://docs.hypercerts.org/getting-started/building-on-hypercerts): integration patterns for platforms and tools. -- [Core data model](https://docs.hypercerts.org/core-concepts/hypercerts-core-data-model) and [lexicon reference](https://docs.hypercerts.org/lexicons/introduction-to-lexicons): record types, schemas, and relationships. -- [Architecture overview](https://docs.hypercerts.org/architecture/overview) and [Certified services](https://docs.hypercerts.org/reference/certified-services): how the infrastructure fits together and where to connect. +## Certified accounts -On-chain anchoring and tokenization for the AT Protocol-based protocol are planned, not currently implemented. Hypercerts records are not tokens. See [Funding & Value Flow](https://docs.hypercerts.org/core-concepts/funding-and-value-flow) for the current design and status. +[certified.app](https://certified.app) is where people create and manage their Certified account: their profile, connected applications, groups, and endorsements. The account is an AT Protocol account, independent of any one application. Your application sits beside certified.app as another client of the same account. See [certified.app in the reference](https://docs.hypercerts.org/reference/services/certified-app). ## Current repositories @@ -25,17 +30,18 @@ On-chain anchoring and tokenization for the AT Protocol-based protocol are plann | Repository | Purpose | Documentation | | --- | --- | --- | | [hypercerts-lexicon](https://github.com/hypercerts-org/hypercerts-lexicon) | Hypercerts and Certified lexicons, generated TypeScript types, and validators | [Lexicons](https://docs.hypercerts.org/lexicons/introduction-to-lexicons) | -| [ePDS](https://github.com/hypercerts-org/ePDS) | Extended Personal Data Server with email-first account creation and authentication | [ePDS](https://docs.hypercerts.org/architecture/epds) | -| [certified-group-service](https://github.com/hypercerts-org/certified-group-service) | Role-based governance and shared management of a group's AT Protocol repository | [CGS](https://docs.hypercerts.org/architecture/certified-group-service) | -| [hypercerts-relay](https://github.com/hypercerts-org/hypercerts-relay) | Relay and Jetstream infrastructure for streaming repository events | [Relay and Jetstream](https://docs.hypercerts.org/tools/hypercerts-relay) | -| [hypercerts-feed-service](https://github.com/hypercerts-org/hypercerts-feed-service) | Read-only, viewer-scoped feeds from indexed Hypercerts data | [Feed Service](https://docs.hypercerts.org/tools/hypercerts-feed-service) | +| [ePDS](https://github.com/hypercerts-org/ePDS) | Software behind the running Certified PDSs and email sign-in today | [Certified PDSs](https://docs.hypercerts.org/reference/services/certified-pdss) | +| [certified-group-service](https://github.com/hypercerts-org/certified-group-service) | Role-based governance and shared management of a group's AT Protocol repository | [CGS](https://docs.hypercerts.org/reference/services/certified-group-service) | +| [hypercerts-relay](https://github.com/hypercerts-org/hypercerts-relay) | Relay and Jetstream infrastructure for streaming repository events | [Relay and Jetstream](https://docs.hypercerts.org/reference/services/relay) | +| [happyview](https://github.com/hypercerts-org/happyview) | Lexicon-driven AppView underpinning the indexer and Hypercerts API, under development | [Indexer and Hypercerts API](https://docs.hypercerts.org/reference/services/indexer) | +| [orglabeler](https://github.com/hypercerts-org/orglabeler) | Signed quality labels for Certified organization data | [Labelers](https://docs.hypercerts.org/reference/services/labelers) | +| [hypercerts-feed-service](https://github.com/hypercerts-org/hypercerts-feed-service) | Read-only, viewer-scoped feeds from indexed Hypercerts data | [Feed Service](https://docs.hypercerts.org/reference/services/feed-service) | -The documentation also covers [Hyperindex](https://docs.hypercerts.org/tools/hyperindex), the ecosystem indexer maintained in [gainforest/hyperindex](https://github.com/gainforest/hyperindex). The former `hypercerts-org/hyperindex` repository is archived. +The [Hypercerts API](https://docs.hypercerts.org/reference/xrpc-api), [SDK](https://docs.hypercerts.org/reference/sdk), and [Entryway](https://docs.hypercerts.org/reference/services/entryway) are under development. Their reference pages describe their status and what to use today; they are not released integration dependencies. -### Applications and developer resources +### Applications and documentation -- [certified-app](https://github.com/hypercerts-org/certified-app): the application at [certified.app](https://certified.app). -- [skills](https://github.com/hypercerts-org/skills): [agent skills](https://docs.hypercerts.org/tools/hypercerts-agent-skills) for working across the Hypercerts stack. +- [certified-app](https://github.com/hypercerts-org/certified-app): Certified account, profile, group, endorsement, and connected-application management. - [documentation](https://github.com/hypercerts-org/documentation): the source for [docs.hypercerts.org](https://docs.hypercerts.org/). - [hypercerts-org](https://github.com/hypercerts-org/hypercerts-org): the [hypercerts.org](https://hypercerts.org) website. From 85e04c544c4b2269c6e83d8a52f62c2080e054df Mon Sep 17 00:00:00 2001 From: Kristofer Date: Thu, 1 Oct 2026 12:32:58 +0200 Subject: [PATCH 3/4] docs: keep organization profile a short Hypercerts introduction --- profile/README.md | 70 ++++------------------------------------------- 1 file changed, 6 insertions(+), 64 deletions(-) diff --git a/profile/README.md b/profile/README.md index 41063d8..727969f 100644 --- a/profile/README.md +++ b/profile/README.md @@ -6,69 +6,11 @@ Hypercerts is an open protocol to connect projects with those who review them, v Projects publish their work, updates, and evidence as records they control. Others add endorsements, evaluations, and funding records, each attributed to whoever provided it. Built on [AT Protocol](https://atproto.com/), these records can be reused across compatible applications, so the next funding decision can build on what is already known instead of starting from scratch. -A hypercert, or activity claim, describes planned, ongoing, or completed work: who contributed, what they did, when, and where. It is the publisher's account of the work, not proof of impact on its own. Evidence and independent assessments help others judge it over time. +A hypercert describes a piece of work: who contributed, what they did, when, and where. Evidence and independent assessments build a fuller picture over time. -## Start with the documentation +## Learn more and build -**[docs.hypercerts.org](https://docs.hypercerts.org/)** explains the protocol and the stack in four sections: - -- [Guide](https://docs.hypercerts.org/guide): how work, evidence, assessments, trust, and funding connect across applications. -- [Client Integration](https://docs.hypercerts.org/client-integration): where your application fits, account setup, and what you can build with today. -- [Reference](https://docs.hypercerts.org/reference): lexicons, services and tooling, and the API and SDK as they are released. -- [Changes](https://docs.hypercerts.org/changes): protocol releases and component versions. - -New to the project? Start with [hypercerts.org](https://hypercerts.org) for the high-level story, then follow the Guide. For schemas and connection details, see the [lexicon inventory](https://docs.hypercerts.org/reference/lexicon-inventory) and [services overview](https://docs.hypercerts.org/reference/services). - -## Certified accounts - -[certified.app](https://certified.app) is where people create and manage their Certified account: their profile, connected applications, groups, and endorsements. The account is an AT Protocol account, independent of any one application. Your application sits beside certified.app as another client of the same account. See [certified.app in the reference](https://docs.hypercerts.org/reference/services/certified-app). - -## Current repositories - -### Protocol and infrastructure - -| Repository | Purpose | Documentation | -| --- | --- | --- | -| [hypercerts-lexicon](https://github.com/hypercerts-org/hypercerts-lexicon) | Hypercerts and Certified lexicons, generated TypeScript types, and validators | [Lexicons](https://docs.hypercerts.org/lexicons/introduction-to-lexicons) | -| [ePDS](https://github.com/hypercerts-org/ePDS) | Software behind the running Certified PDSs and email sign-in today | [Certified PDSs](https://docs.hypercerts.org/reference/services/certified-pdss) | -| [certified-group-service](https://github.com/hypercerts-org/certified-group-service) | Role-based governance and shared management of a group's AT Protocol repository | [CGS](https://docs.hypercerts.org/reference/services/certified-group-service) | -| [hypercerts-relay](https://github.com/hypercerts-org/hypercerts-relay) | Relay and Jetstream infrastructure for streaming repository events | [Relay and Jetstream](https://docs.hypercerts.org/reference/services/relay) | -| [happyview](https://github.com/hypercerts-org/happyview) | Lexicon-driven AppView underpinning the indexer and Hypercerts API, under development | [Indexer and Hypercerts API](https://docs.hypercerts.org/reference/services/indexer) | -| [orglabeler](https://github.com/hypercerts-org/orglabeler) | Signed quality labels for Certified organization data | [Labelers](https://docs.hypercerts.org/reference/services/labelers) | -| [hypercerts-feed-service](https://github.com/hypercerts-org/hypercerts-feed-service) | Read-only, viewer-scoped feeds from indexed Hypercerts data | [Feed Service](https://docs.hypercerts.org/reference/services/feed-service) | - -The [Hypercerts API](https://docs.hypercerts.org/reference/xrpc-api), [SDK](https://docs.hypercerts.org/reference/sdk), and [Entryway](https://docs.hypercerts.org/reference/services/entryway) are under development. Their reference pages describe their status and what to use today; they are not released integration dependencies. - -### Applications and documentation - -- [certified-app](https://github.com/hypercerts-org/certified-app): Certified account, profile, group, endorsement, and connected-application management. -- [documentation](https://github.com/hypercerts-org/documentation): the source for [docs.hypercerts.org](https://docs.hypercerts.org/). -- [hypercerts-org](https://github.com/hypercerts-org/hypercerts-org): the [hypercerts.org](https://hypercerts.org) website. - -
- Legacy repositories (v0.1) - -These repositories belong to the earlier blockchain-based implementation, not the current AT Protocol-based integration path. Start with the documentation above for new integrations. - -- [hypercerts-protocol](https://github.com/hypercerts-org/hypercerts-protocol): smart contracts and the contracts npm package. -- [hypercerts-app](https://github.com/hypercerts-org/hypercerts-app): the original app.hypercerts.org application. -- [hypercerts-sdk](https://github.com/hypercerts-org/hypercerts-sdk): the deprecated contract SDK. -- [marketplace-sdk](https://github.com/hypercerts-org/marketplace-sdk): the marketplace SDK built on LooksRare. -- [hypercerts-indexer](https://github.com/hypercerts-org/hypercerts-indexer): the legacy contract indexer. -- [hypercerts-api](https://github.com/hypercerts-org/hypercerts-api): the legacy OpenAPI and GraphQL API. - -
- -## Get involved - -- [Contributing](https://github.com/hypercerts-org/.github/blob/main/profile/CONTRIBUTING.md) and [Code of conduct](https://github.com/hypercerts-org/.github/blob/main/profile/CODE_OF_CONDUCT.md). -- [Website](https://hypercerts.org), [blog](https://hypercerts.org/blog), and [contact](https://hypercerts.org/contact). -- [Bluesky](https://bsky.app/profile/hypercerts.org), [Twitter](https://x.com/hypercerts), and [Telegram / support](https://t.me/+o4wPsJ7yEZYzNGFk). - -## Supporters - -The hypercerts project is supported by organizations and individuals who believe in building open, interoperable infrastructure for recognizing and coordinating around real-world work. These include: Protocol Labs, Ma Earth, GainForest, Optimism, Octant, Gitcoin, Silvi, Regen Foundation, and Funding the Commons. - -Their support, through funding, collaboration, feedback, and shared experimentation, helps advance the development of hypercerts as a public-good primitive. Support does not imply endorsement of specific design decisions or applications. - -We're grateful to all supporters who contribute time, resources, and trust to this ongoing effort. +- [Website](https://hypercerts.org): why Hypercerts matters and how it is used. +- [Documentation](https://docs.hypercerts.org/): the Guide, Client Integration, Reference, and Changes, including maintained components and their repositories. +- [Start the Guide](https://docs.hypercerts.org/guide): how work, evidence, trust, and funding connect. +- [Get in touch](https://hypercerts.org/contact): bring a project, funding program, or integration idea. From c5b06006d4afa0a9b004619ce7890e42d7926001 Mon Sep 17 00:00:00 2001 From: Kristofer Date: Fri, 2 Oct 2026 08:27:57 +0200 Subject: [PATCH 4/4] docs: preserve supporters and community resources in profile --- profile/README.md | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/profile/README.md b/profile/README.md index 727969f..3e8eaea 100644 --- a/profile/README.md +++ b/profile/README.md @@ -6,7 +6,7 @@ Hypercerts is an open protocol to connect projects with those who review them, v Projects publish their work, updates, and evidence as records they control. Others add endorsements, evaluations, and funding records, each attributed to whoever provided it. Built on [AT Protocol](https://atproto.com/), these records can be reused across compatible applications, so the next funding decision can build on what is already known instead of starting from scratch. -A hypercert describes a piece of work: who contributed, what they did, when, and where. Evidence and independent assessments build a fuller picture over time. +A hypercert describes planned, ongoing, or completed work: who contributed, what they did, when, and where. Evidence and independent assessments build a fuller picture over time. Hypercerts is shared infrastructure, not a marketplace or a single application, and individual components can be used independently. ## Learn more and build @@ -14,3 +14,18 @@ A hypercert describes a piece of work: who contributed, what they did, when, and - [Documentation](https://docs.hypercerts.org/): the Guide, Client Integration, Reference, and Changes, including maintained components and their repositories. - [Start the Guide](https://docs.hypercerts.org/guide): how work, evidence, trust, and funding connect. - [Get in touch](https://hypercerts.org/contact): bring a project, funding program, or integration idea. + +## Get involved + +- [Contributing](https://github.com/hypercerts-org/.github/blob/main/profile/CONTRIBUTING.md): how to help with code, evaluation, documentation, and feedback. +- [Code of conduct](https://github.com/hypercerts-org/.github/blob/main/profile/CODE_OF_CONDUCT.md): our community standards. +- [Blog](https://hypercerts.org/blog): project updates and ideas. +- [Bluesky](https://bsky.app/profile/hypercerts.org), [Twitter](https://x.com/hypercerts), [Telegram](https://t.me/+YF9AYb6zCv1mNDJi), and [Telegram Support](https://t.me/+FODiLtCV2TgwNzRi). + +## Supporters + +The hypercerts project is supported by organizations and individuals who believe in building open, interoperable infrastructure for recognizing and coordinating around real-world work. These include: Protocol Labs, Ma Earth, GainForest, Optimism, Octant, Gitcoin, Silvi, Regen Foundation, and Funding the Commons. + +Their support, through funding, collaboration, feedback, and shared experimentation, helps advance the development of hypercerts as a public-good primitive. Support does not imply endorsement of specific design decisions or applications. + +We're grateful to all supporters who contribute time, resources, and trust to this ongoing effort.