refactor: retire vendor authoring vocabulary

.github/CODEOWNERS

@@ -1,4 +1,4 @@
 * @auscaster
 
-/vendors/ @auscaster
+/entities/ @auscaster
 /.github/ @auscaster

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,8 @@
 blank_issues_enabled: false
 contact_links:
-  - name: Claim a vendor
-    url: https://sourcey.com/claim
-    about: Prove control of a vendor domain before making vendor-authoritative declarations.
+  - name: Claim or correct an Entity record
+    url: https://sourcey.com/support
+    about: Find the exact record and prove authority before making Entity-authoritative declarations.
   - name: Browse Agent Readiness Report Cards
     url: https://sourcey.com/agent-readiness
     about: Inspect released, evidence-bound Sourcey Report Cards.

.github/ISSUE_TEMPLATE/report-outdated.yml

@@ -37,7 +37,7 @@ body:
       label: Your relationship
       options:
         - Community reporter or customer
-        - Vendor employee or authorized representative
+        - Employee or authorized representative of the Entity
         - Sourcey maintainer
     validations:
       required: true

.github/ISSUE_TEMPLATE/request-assessment.yml

@@ -1,5 +1,5 @@
 name: Request an assessment
-description: Propose one exact service, product, or vendor funnel for independent Agent Readiness assessment.
+description: Propose one exact Entity, service, product, and funnel for independent Agent Readiness assessment.
 title: "Assessment request: "
 labels:
   - assessment-request
@@ -9,10 +9,10 @@ body:
       value: |
         A request is not a readiness claim. Do not include credentials, personal data, private captures, or unpublished material.
   - type: input
-    id: vendor
+    id: entity
     attributes:
-      label: Vendor
-      description: The public vendor or service provider name.
+      label: Entity
+      description: The public party responsible for the service or product.
     validations:
       required: true
   - type: input
@@ -73,15 +73,15 @@ body:
   - type: input
     id: sourcey_record
     attributes:
-      label: Existing Sourcey vendor or offer URL
-      description: Include it when this vendor already appears in Sourcey Startup Offers.
+      label: Existing Sourcey Entity or Offer URL
+      description: Include it when this Entity or an exact related Offer already appears in Sourcey.
   - type: dropdown
     id: relationship
     attributes:
       label: Your relationship
       options:
         - Community contributor or customer
-        - Vendor employee or authorized representative
+        - Employee or authorized representative of the Entity
         - Sourcey maintainer
     validations:
       required: true

.github/pull_request_template.md

@@ -1,18 +1,18 @@
 ## Declaration
 
-- Vendor:
+- Entity:
 - Product:
 - Funnel:
 - Assessment request issue:
 
 ## Contributor checks
 
-- [ ] This pull request changes vendor YAML only, or repository documentation/workflow metadata only—not both.
+- [ ] This pull request changes Entity YAML only, or repository documentation/workflow metadata only—not both.
 - [ ] Sourcey confirmed the stable Entity ID and every related Offer ID, if any.
 - [ ] Every declared source, resource, and endpoint is public HTTPS material.
 - [ ] Every material declaration field has exact source-binding coverage.
 - [ ] The declaration contains no observation, readiness state, grade, certification, current Report Card, private evidence, or generated output.
-- [ ] `authority_intent` is `vendor` only when Sourcey has already proven vendor-domain authority.
+- [ ] `authority_intent` is `entity` only when Sourcey has already proven authority for the Entity's authoritative domain.
 - [ ] Every commit has a `Signed-off-by` line for the Developer Certificate of Origin.
 
 A merged declaration requests independent assessment. It does not mean that the service is ready or that a Report Card will be published.

AGENTS.md

@@ -11,7 +11,7 @@ truth store. Sourcey and Agent Ready Services brand publications consume the
 same private brand-neutral fact/dependency projection; generated content,
 scores, and assessment outcomes never enter this repository.
 
-Allowed contents are vendor declaration YAML, documentation, legal files,
+Allowed contents are Entity declaration YAML, documentation, legal files,
 CODEOWNERS, pull-request and issue guidance, and minimal GitHub workflow YAML
 that invokes the digest-pinned Sourcey Catalog Verifier.
 

CONTRIBUTING.md

@@ -1,18 +1,15 @@
 # Contributing
 
-Contributions declare an exact vendor, product, and funnel for independent
+Contributions declare an exact Entity, product, and funnel for independent
 assessment. They never author a Sourcey observation, readiness state, grade,
 certification, or current Report Card.
 
 ## Choose the smallest honest path
 
-1. **Request an assessment** when the vendor is new to Sourcey, you know the
+1. **Request an assessment** when the Entity is new to Sourcey, you know the
    service but not its complete graph, or you want Sourcey to research it.
    Open the [assessment request](https://github.com/sourcey/agent-ready-services/issues/new?template=request-assessment.yml).
-2. **Use the guided form** for one existing vendor-operated product funnel.
-   [Declare the service on Sourcey](https://sourcey.com/agent-readiness/submit),
-   inspect the exact canonical YAML, and create its review pull request.
-3. **Author canonical YAML** only for advanced declarations with third-party
+2. **Author canonical YAML** for declarations with third-party
    operators, several interfaces, several standards, explicit relations, or
    exact Offer relationships. The complete example below is the review bar.
 
@@ -22,34 +19,34 @@ format or hidden conversion schema.
 
 ## Before editing YAML
 
-1. Search the open issues and pull requests for the vendor and product funnel.
+1. Search the open issues and pull requests for the Entity and product funnel.
 2. For manual YAML, open an [assessment request](https://github.com/sourcey/agent-ready-services/issues/new?template=request-assessment.yml)
    before editing so identity and scope can be checked.
 3. Sourcey will confirm the stable `entity_id`. Startup Offers and Agent
    Readiness use the same Entity authority, but remain separate catalogs. Do
    not copy a credit or deal into the readiness declaration. An optional Offer
    relation is proposed only when Sourcey has confirmed a real downstream
    relationship; it never scopes or identifies the profile.
-4. Use `authority_intent: vendor` only when Sourcey has proven control of the
-   vendor domain. Otherwise use `community`.
+4. Use `authority_intent: entity` only when Sourcey has proven control of the
+   Entity's authoritative domain. Otherwise use `community`.
 
 Never include credentials, personal data, unpublished terms, authenticated
 captures, or other private material. Public URLs are enough for a declaration;
 Sourcey's evidence operations retain assessment evidence separately.
 
 ## File location and shape
 
-A vendor lives at `vendors/{shard}/{slug}.yaml`, where `shard` is the first two
-characters of the vendor slug. A file may contain several declarations for the
-same vendor, but each declaration covers exactly one product and one funnel.
+An Entity lives at `entities/{shard}/{slug}.yaml`, where `shard` is the first two
+characters of the Entity slug. A file may contain several declarations for the
+same Entity, but each declaration covers exactly one product and one funnel.
 
 The executable schema is owned by the digest-pinned Sourcey Catalog Verifier.
 This example illustrates the current authoring shape; it is not a duplicate
 schema:
 
 ```yaml
 schema_version: sourcey.agent-readiness-authoring/v1alpha1
-vendor:
+entity:
   entity_id: ent_01k00000000000000000000001
   slug: acme
   slug_aliases: []
@@ -59,21 +56,17 @@ vendor:
       role: primary
       valid_from: 2026-08-05T00:00:00.000Z
   category: devtools-other
-  description: Acme makes a hosted database service.
-  links:
-    site: https://acme.example/
-    pricing: https://acme.example/pricing
-  sources:
-    - source_id: source_acme_docs
-      url: https://acme.example/docs
-    - source_id: source_acme_terms
-      url: https://acme.example/terms
-    - source_id: source_acme_pricing
-      url: https://acme.example/pricing
-    - source_id: source_acme_signup
-      url: https://acme.example/signup
-    - source_id: source_acme_billing
-      url: https://acme.example/docs/billing
+sources:
+  - source_id: source_acme_docs
+    url: https://acme.example/docs
+  - source_id: source_acme_terms
+    url: https://acme.example/terms
+  - source_id: source_acme_pricing
+    url: https://acme.example/pricing
+  - source_id: source_acme_signup
+    url: https://acme.example/signup
+  - source_id: source_acme_billing
+    url: https://acme.example/docs/billing
 declarations:
   - declaration_id: declaration_acme_db_api_lifecycle
     scope:
@@ -236,9 +229,9 @@ and policy.
 
 ## Pull request rules
 
-- Keep vendor YAML changes separate from documentation and workflow changes.
+- Keep Entity YAML changes separate from documentation and workflow changes.
 - Every source, resource, and endpoint URL must be public HTTPS material for
-  the declared vendor or funnel.
+  the declared Entity or funnel.
 - Keep stable declaration and graph IDs stable.
 - Bind every material authored field to at least one exact source.
 - Use real names in ordinary language; do not keyword-stuff fields.
@@ -249,7 +242,7 @@ and policy.
 git commit --signoff -m "data(readiness): declare acme db self-serve funnel"
 ```
 
-The public `sourcey/validation` status parses only changed vendor blobs using the exact
+The public `sourcey/validation` status parses only changed Entity blobs using the exact
 digest-pinned Sourcey Catalog Verifier and confirms their identity-derived
 paths and dependency closure. It does not execute pull-request code. A green
 status proves declaration shape, not readiness.

DATA-LICENSE.md

@@ -1,6 +1,6 @@
 # Declaration data licence
 
-Vendor declarations under `vendors/` are licensed under the
+Entity declarations under `entities/` are licensed under the
 [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/).
 
 Attribution: `Sourcey Agent Ready Services, https://github.com/sourcey/agent-ready-services`.

README.md

@@ -1,4 +1,4 @@
-<h1 align="center">Agent-ready services, APIs and vendor funnels</h1>
+<h1 align="center">Agent-ready services, APIs and operating funnels</h1>
 
 <p align="center">
   <b>Open declarations. Independent Agent Readiness Report Cards.</b><br>
@@ -7,10 +7,9 @@
 
 <p align="center">
   <a href="https://sourcey.com/agent-readiness">Browse Report Cards</a> ·
-  <a href="https://sourcey.com/agent-readiness/submit">Declare a service</a> ·
   <a href="CONTRIBUTING.md">Contribution guide</a> ·
   <a href="https://github.com/sourcey/agent-ready-services/issues/new?template=request-assessment.yml">Request an assessment</a> ·
-  <a href="https://sourcey.com/claim">Claim a vendor</a> ·
+  <a href="https://sourcey.com/support">Claim or correct a record</a> ·
   <a href="https://github.com/sourcey/agent-ready-services/issues/new?template=report-outdated.yml">Report outdated evidence</a>
 </p>
 
@@ -21,13 +20,13 @@ authorized access, pay when required, provision what it needs, and use the
 service safely?
 
 This repository is the open contribution front door for answering that
-question. Each vendor file declares one real vendor and one or more exact
-product funnels, essential service targets, public resources, callable
+question. Each Entity file uses Sourcey's shared identity envelope and declares
+one or more exact product funnels, essential service targets, public resources, callable
 endpoints, actors, interfaces, and exact standard bindings.
 
 Sourcey assesses those declarations independently. The resulting
 [Agent Readiness Report Card](https://sourcey.com/agent-readiness) belongs to
-one vendor, product, and funnel—not vaguely to an entire company.
+one Entity, product, and funnel—not vaguely to an entire company.
 
 ## What a Report Card covers
 
@@ -51,14 +50,14 @@ established by evidence.
 
 Only source declarations live here:
 
-- vendor identity and public sources;
+- shared Entity identity plus repository-specific public sources;
 - an exact product and service-access/operating funnel with essential targets;
 - declared participants, resources, endpoints, interfaces, and their relations;
 - source-bound surface exclusions that explain an omitted assessment surface
   without claiming a result;
 - exact standard/version bindings and field-level source bindings;
 - optional explicit relations to existing Sourcey Offers; and
-- a vendor or community request for independent assessment.
+- an Entity-authority or community request for independent assessment.
 
 This repository does **not** contain observations, screenshots, private
 evidence, stage outcomes, grades, freshness projections, generated indexes, or
@@ -69,25 +68,21 @@ history.
 
 ## Add or improve a service
 
-Use the [guided Sourcey declaration form](https://sourcey.com/agent-readiness/submit)
-when the vendor operates one straightforward product funnel. It resolves the
-existing Sourcey Entity, validates every assessment surface against the current
-policy, shows the exact canonical YAML, and creates one review pull request.
-Use [CONTRIBUTING.md](CONTRIBUTING.md) for a request-only path or advanced
-multi-participant and multi-interface declarations. New identities are
-allocated against Sourcey's existing vendor records before a declaration is
-merged, so the same vendor has one stable identity across catalogs without
-making an Offer part of a readiness profile.
+Use [CONTRIBUTING.md](CONTRIBUTING.md) for the request path and advanced
+multi-participant or multi-interface declarations. New identities are
+allocated against Sourcey's existing Entity authority before a declaration is
+merged, so the same organization or service has one stable identity across
+catalogs without making an Offer part of a readiness profile.
 
 After a declaration is merged, it enters private scope and evidence review.
-Publication happens only when the evidence floor is met. A vendor can then
+Publication happens only when the evidence floor is met. An Entity operator can then
 claim the exact profile, fix a blocker, submit a correction, or request a
 rerun. A stronger released card creates a permanent, citable improvement
 history without rewriting the original evidence.
 
 ## Licence
 
-Vendor declarations are [CC BY 4.0](DATA-LICENSE.md). Documentation and
+Entity declarations are [CC BY 4.0](DATA-LICENSE.md). Documentation and
 repository metadata are [MIT](LICENSE). Third-party names and marks remain the
 property of their owners.