update docs for lexicon usage (coderabbit comment)

Author: Kzoeps

pages/architecture/data-flow-and-lifecycle.md

@@ -60,11 +60,11 @@ Contributors are embedded in the activity claim's `contributors` array. For rich
 
 #### Attachment Records
 
-`org.hypercerts.claim.attachment` records attach supporting documentation. Attachments can be URLs, file uploads, or structured data. Each attachment record includes a strong reference to the claim it supports.
+`org.hypercerts.context.attachment` records attach supporting documentation. Attachments can be URLs, file uploads, or structured data. Each attachment record includes a strong reference to the claim it supports.
 
 #### Measurement Records
 
-`org.hypercerts.claim.measurement` records provide quantitative data. A measurement specifies what was measured, the value, the unit, and the methodology. Multiple measurements can track different metrics.
+`org.hypercerts.context.measurement` records provide quantitative data. A measurement specifies what was measured, the value, the unit, and the methodology. Multiple measurements can track different metrics.
 
 #### Rights Records
 
@@ -98,7 +98,7 @@ at://did:alice/...               at://did:bob/...                at://did:carol/
 
 Third parties assess the work by creating evaluation records on their own servers.
 
-An evaluator creates an `org.hypercerts.claim.evaluation` record on their PDS. The evaluation includes a `subject` field with a strong reference to the activity claim. Strong references include both the AT-URI and the CID (content hash), ensuring the evaluation references a specific version of the claim.
+An evaluator creates an `org.hypercerts.context.evaluation` record on their PDS. The evaluation includes a `subject` field with a strong reference to the activity claim. Strong references include both the AT-URI and the CID (content hash), ensuring the evaluation references a specific version of the claim.
 
 The evaluation record includes the evaluator's assessment. This can be a score, a category, structured feedback, or a link to a detailed report. The lexicon allows flexible evaluation formats.
 

pages/core-concepts/hypercerts-core-data-model.md

@@ -49,9 +49,9 @@ The diagram includes a **token** entity — tokenization (anchoring a hypercert
 
 | Record type | What it adds | Who creates it | Lexicon |
 |-------------|-------------|----------------|---------|
-| **Attachment** | Supporting documentation — URLs, uploaded files, IPFS links. Can link to any record type, not only activity claims. | Anyone with additional data | `org.hypercerts.claim.attachment` |
-| **Measurement** | Quantitative data — "12 pages written", "50 tons CO₂ reduced" | E.g. a third-party measurer or the project (self-reported) | `org.hypercerts.claim.measurement` |
-| **Evaluation** | An (independent) assessment of the work | E.g. a third-party evaluator, community members, beneficiaries | `org.hypercerts.claim.evaluation` |
+| **Attachment** | Supporting documentation — URLs, uploaded files, IPFS links. Can link to any record type, not only activity claims. | Anyone with additional data | `org.hypercerts.context.attachment` |
+| **Measurement** | Quantitative data — "12 pages written", "50 tons CO₂ reduced" | E.g. a third-party measurer or the project (self-reported) | `org.hypercerts.context.measurement` |
+| **Evaluation** | An (independent) assessment of the work | E.g. a third-party evaluator, community members, beneficiaries | `org.hypercerts.context.evaluation` |
 
 ### Additional notes
 

pages/getting-started/working-with-evaluations.md

@@ -21,15 +21,15 @@ await agent.login({
 // Create an evaluation of an activity claim
 const evaluation = await agent.com.atproto.repo.createRecord({
   repo: agent.session.did,
-  collection: "org.hypercerts.claim.evaluation",
+  collection: "org.hypercerts.context.evaluation",
   record: {
     subject: {
       uri: "at://did:plc:xyz789/org.hypercerts.claim.activity/3k2j4h5g6f7d8s9a",
       cid: "bafyreiabc123...",
     },
     evaluators: ["did:plc:evaluator123"],
     summary: "Verified documentation updates. All 15 examples tested and working. High quality contribution with clear impact on developer experience.",
-    $type: "org.hypercerts.claim.evaluation",
+    $type: "org.hypercerts.context.evaluation",
     createdAt: new Date().toISOString(),
   },
 });
@@ -46,7 +46,7 @@ Measurements provide quantitative data that supports your evaluation:
 ```typescript
 const measurement = await agent.com.atproto.repo.createRecord({
   repo: agent.session.did,
-  collection: "org.hypercerts.claim.measurement",
+  collection: "org.hypercerts.context.measurement",
   record: {
     subject: {
       uri: "at://did:plc:xyz789/org.hypercerts.claim.activity/3k2j4h5g6f7d8s9a",
@@ -60,7 +60,7 @@ const measurement = await agent.com.atproto.repo.createRecord({
     methodURI: "https://example.com/analytics-methodology",
     evidenceURI: ["https://example.com/analytics-report.pdf"],
     comment: "Page view data collected over the first 30 days after publication.",
-    $type: "org.hypercerts.claim.measurement",
+    $type: "org.hypercerts.context.measurement",
     createdAt: new Date().toISOString(),
   },
 });

pages/tools/scaffold.md

@@ -180,9 +180,9 @@ ATProto has no built-in reverse lookup — given a hypercert URI, there is no na
 
 Constellation indexes ATProto records and returns all records that reference a given subject URI. The scaffold queries three source paths:
 
-- Attachments: `org.hypercerts.claim.attachment:subjects[com.atproto.repo.strongRef].uri`
-- Evaluations: `org.hypercerts.claim.evaluation:subject.uri`
-- Measurements: `org.hypercerts.claim.measurement:subject.uri`
+- Attachments: `org.hypercerts.context.attachment:subjects[com.atproto.repo.strongRef].uri`
+- Evaluations: `org.hypercerts.context.evaluation:subject.uri`
+- Measurements: `org.hypercerts.context.measurement:subject.uri`
 
 The query hooks follow a two-step pattern: fetch backlink URIs from Constellation, then fetch each record's full data via Server Actions. This split is necessary because Constellation returns record identifiers, not record contents.
 
@@ -294,4 +294,4 @@ hypercerts-scaffold/
 └── vendor/                           # Packed dependency tarballs (pre-release)
 ```
 
-`app/` contains pages (server components by default) and API routes. `lib/` is split: top-level files are server-only, while `lib/api/` is the client-side fetch layer that browser code calls. `providers/` has one server component (`SignedInProvider`, which handles the auth gate and renders the Navbar) and one client component (`AllProviders`, which sets up the TanStack Query client). `queries/` is entirely client-side TanStack Query hooks. `components/` is entirely client-side React components.
+`app/` contains pages (server components by default) and API routes. `lib/` is split: top-level files are server-only, while `lib/api/` is the client-side fetch layer that browser code calls. `providers/` has one server component (`SignedInProvider`, which handles the auth gate and renders the Navbar) and one client component (`AllProviders`, which sets up the TanStack Query client). `queries/` is entirely client-side TanStack Query hooks. `components/` is entirely client-side React components.

public/raw/architecture/data-flow-and-lifecycle.md

@@ -60,11 +60,11 @@ Contributors are embedded in the activity claim's `contributors` array. For rich
 
 #### Attachment Records
 
-`org.hypercerts.claim.attachment` records attach supporting documentation. Attachments can be URLs, file uploads, or structured data. Each attachment record includes a strong reference to the claim it supports.
+`org.hypercerts.context.attachment` records attach supporting documentation. Attachments can be URLs, file uploads, or structured data. Each attachment record includes a strong reference to the claim it supports.
 
 #### Measurement Records
 
-`org.hypercerts.claim.measurement` records provide quantitative data. A measurement specifies what was measured, the value, the unit, and the methodology. Multiple measurements can track different metrics.
+`org.hypercerts.context.measurement` records provide quantitative data. A measurement specifies what was measured, the value, the unit, and the methodology. Multiple measurements can track different metrics.
 
 #### Rights Records
 
@@ -98,7 +98,7 @@ at://did:alice/...               at://did:bob/...                at://did:carol/
 
 Third parties assess the work by creating evaluation records on their own servers.
 
-An evaluator creates an `org.hypercerts.claim.evaluation` record on their PDS. The evaluation includes a `subject` field with a strong reference to the activity claim. Strong references include both the AT-URI and the CID (content hash), ensuring the evaluation references a specific version of the claim.
+An evaluator creates an `org.hypercerts.context.evaluation` record on their PDS. The evaluation includes a `subject` field with a strong reference to the activity claim. Strong references include both the AT-URI and the CID (content hash), ensuring the evaluation references a specific version of the claim.
 
 The evaluation record includes the evaluator's assessment. This can be a score, a category, structured feedback, or a link to a detailed report. The lexicon allows flexible evaluation formats.
 

public/raw/core-concepts/hypercerts-core-data-model.md

@@ -49,9 +49,9 @@ The diagram includes a **token** entity — tokenization (anchoring a hypercert
 
 | Record type | What it adds | Who creates it | Lexicon |
 |-------------|-------------|----------------|---------|
-| **Attachment** | Supporting documentation — URLs, uploaded files, IPFS links. Can link to any record type, not only activity claims. | Anyone with additional data | `org.hypercerts.claim.attachment` |
-| **Measurement** | Quantitative data — "12 pages written", "50 tons CO₂ reduced" | E.g. a third-party measurer or the project (self-reported) | `org.hypercerts.claim.measurement` |
-| **Evaluation** | An (independent) assessment of the work | E.g. a third-party evaluator, community members, beneficiaries | `org.hypercerts.claim.evaluation` |
+| **Attachment** | Supporting documentation — URLs, uploaded files, IPFS links. Can link to any record type, not only activity claims. | Anyone with additional data | `org.hypercerts.context.attachment` |
+| **Measurement** | Quantitative data — "12 pages written", "50 tons CO₂ reduced" | E.g. a third-party measurer or the project (self-reported) | `org.hypercerts.context.measurement` |
+| **Evaluation** | An (independent) assessment of the work | E.g. a third-party evaluator, community members, beneficiaries | `org.hypercerts.context.evaluation` |
 
 ### Additional notes
 

public/raw/getting-started/working-with-evaluations.md

@@ -21,15 +21,15 @@ await agent.login({
 // Create an evaluation of an activity claim
 const evaluation = await agent.com.atproto.repo.createRecord({
   repo: agent.session.did,
-  collection: "org.hypercerts.claim.evaluation",
+  collection: "org.hypercerts.context.evaluation",
   record: {
     subject: {
       uri: "at://did:plc:xyz789/org.hypercerts.claim.activity/3k2j4h5g6f7d8s9a",
       cid: "bafyreiabc123...",
     },
     evaluators: ["did:plc:evaluator123"],
     summary: "Verified documentation updates. All 15 examples tested and working. High quality contribution with clear impact on developer experience.",
-    $type: "org.hypercerts.claim.evaluation",
+    $type: "org.hypercerts.context.evaluation",
     createdAt: new Date().toISOString(),
   },
 });
@@ -46,7 +46,7 @@ Measurements provide quantitative data that supports your evaluation:
 ```typescript
 const measurement = await agent.com.atproto.repo.createRecord({
   repo: agent.session.did,
-  collection: "org.hypercerts.claim.measurement",
+  collection: "org.hypercerts.context.measurement",
   record: {
     subject: {
       uri: "at://did:plc:xyz789/org.hypercerts.claim.activity/3k2j4h5g6f7d8s9a",
@@ -60,7 +60,7 @@ const measurement = await agent.com.atproto.repo.createRecord({
     methodURI: "https://example.com/analytics-methodology",
     evidenceURI: ["https://example.com/analytics-report.pdf"],
     comment: "Page view data collected over the first 30 days after publication.",
-    $type: "org.hypercerts.claim.measurement",
+    $type: "org.hypercerts.context.measurement",
     createdAt: new Date().toISOString(),
   },
 });

public/raw/tools/scaffold.md

@@ -180,9 +180,9 @@ ATProto has no built-in reverse lookup — given a hypercert URI, there is no na
 
 Constellation indexes ATProto records and returns all records that reference a given subject URI. The scaffold queries three source paths:
 
-- Attachments: `org.hypercerts.claim.attachment:subjects[com.atproto.repo.strongRef].uri`
-- Evaluations: `org.hypercerts.claim.evaluation:subject.uri`
-- Measurements: `org.hypercerts.claim.measurement:subject.uri`
+- Attachments: `org.hypercerts.context.attachment:subjects[com.atproto.repo.strongRef].uri`
+- Evaluations: `org.hypercerts.context.evaluation:subject.uri`
+- Measurements: `org.hypercerts.context.measurement:subject.uri`
 
 The query hooks follow a two-step pattern: fetch backlink URIs from Constellation, then fetch each record's full data via Server Actions. This split is necessary because Constellation returns record identifiers, not record contents.
 
@@ -294,4 +294,4 @@ hypercerts-scaffold/
 └── vendor/                           # Packed dependency tarballs (pre-release)
 ```
 
-`app/` contains pages (server components by default) and API routes. `lib/` is split: top-level files are server-only, while `lib/api/` is the client-side fetch layer that browser code calls. `providers/` has one server component (`SignedInProvider`, which handles the auth gate and renders the Navbar) and one client component (`AllProviders`, which sets up the TanStack Query client). `queries/` is entirely client-side TanStack Query hooks. `components/` is entirely client-side React components.
+`app/` contains pages (server components by default) and API routes. `lib/` is split: top-level files are server-only, while `lib/api/` is the client-side fetch layer that browser code calls. `providers/` has one server component (`SignedInProvider`, which handles the auth gate and renders the Navbar) and one client component (`AllProviders`, which sets up the TanStack Query client). `queries/` is entirely client-side TanStack Query hooks. `components/` is entirely client-side React components.