fix(docs): check validation

Author: stevenj

docs/src/architecture/08_concepts/signed_doc/voting_process/drep_delegation_and_discovery.md

@@ -13,12 +13,9 @@ and how these documents are discovered and validated in a decentralized pub/sub
 
 ## Documents and Roles
 
-* Rep Profile: the representative’s global profile under a brand.
-  See: [Rep Profile](../docs/rep_profile.md).
-* Rep Nomination: contest-specific nomination under contest parameters.
-  See: [Rep Nomination](../docs/rep_nomination.md).
-* Contest Delegation: voter delegation to one or more representatives (nominations) for a contest.
-  See: [Contest Delegation](../docs/contest_delegation.md).
+* Rep Profile: the representative’s global profile under a brand. See: [Rep Profile](../docs/rep_profile.md).
+* Rep Nomination: contest-specific nomination under contest parameters. See: [Rep Nomination](../docs/rep_nomination.md).
+* Contest Delegation: voter delegation to one or more representatives (nominations) for a contest. See: [Contest Delegation](../docs/contest_delegation.md).
 
 Signers:
 
@@ -40,11 +37,9 @@ Signers:
 
 ### Delegation Semantics
 
-* Multiple Delegates: voters may delegate to multiple representatives for a contest (ordered by priority).
-  See: [Contest Delegation](../docs/contest_delegation.md).
+* Multiple Delegates: voters may delegate to multiple representatives for a contest (ordered by priority). See: [Contest Delegation](../docs/contest_delegation.md).
 * Weights: optional payload weights distribute the voter’s (post-scaling) voting power proportionally;
-  non-positive weights are treated as 1.
-  Remainders go to the highest-priority delegate.
+  non-positive weights are treated as 1. Remainders go to the highest-priority delegate.
 * Insufficient Power: if voting power is insufficient to distribute to all delegates, lower-priority delegates may receive 0.
 * Revocation: [`metadata.revocations`](../metadata.md#revocations) can withdraw a delegation
   (set to `true` to withdraw all versions), or a new delegation supersedes the prior one
@@ -65,19 +60,19 @@ that anchors the document via [`metadata.parameters`](../metadata.md#parameters)
 ### Consumer Pipeline
 
 1. Rep Profile intake (by brand)
-   * Verify signature (`Representative`), `metadata.template`,
-     [`metadata.parameters`](../metadata.md#parameters) (brand), and payload schema.
+    * Verify signature (`Representative`), `metadata.template`,
+      [`metadata.parameters`](../metadata.md#parameters) (brand), and payload schema.
 2. Rep Nomination intake (by contest)
-   * Verify signature (`Representative`), [`metadata.ref`](../metadata.md#ref) to Rep Profile,
-     [`metadata.parameters`](../metadata.md#parameters) (contest), and template/payload validity.
-   * Track the latest valid nomination per (representative, contest), excluding revoked items.
+    * Verify signature (`Representative`), [`metadata.ref`](../metadata.md#ref) to Rep Profile,
+      [`metadata.parameters`](../metadata.md#parameters) (contest), and template/payload validity.
+    * Track the latest valid nomination per (representative, contest), excluding revoked items.
 3. Contest Delegation intake (by contest)
-   * Verify signature (`Registered`), [`metadata.ref`](../metadata.md#ref) to one or more nominations,
-     [`metadata.parameters`](../metadata.md#parameters) (contest), and payload (weights) schema.
-   * For multiple references, ignore any invalid nominations;
-     consider the delegation valid if at least one referenced nomination is valid.
-   * Maintain the latest delegation per (delegator, contest);
-     apply [`metadata.revocations`](../metadata.md#revocations) when present.
+    * Verify signature (`Registered`), [`metadata.ref`](../metadata.md#ref) to one or more nominations,
+      [`metadata.parameters`](../metadata.md#parameters) (contest), and payload (weights) schema.
+    * For multiple references, ignore any invalid nominations;
+      consider the delegation valid if at least one referenced nomination is valid.
+    * Maintain the latest delegation per (delegator, contest);
+      apply [`metadata.revocations`](../metadata.md#revocations) when present.
 
 ### Effective Delegation Set
 

docs/src/architecture/08_concepts/signed_doc/voting_process/voting_bulletin_board_and_pubsub_tally.md

@@ -40,7 +40,7 @@ and how ballots and checkpoints are discovered, validated, and tallied in a dece
     * Payload contains `smt-root` (BLAKE3-256 digest) and `smt-entries` (count).
     * Checkpoints are chained via `metadata.chain`; the final checkpoint height is negated.
     * Typically anchored to a blockchain (e.g., encoded `document_ref` in on-chain metadata signed
-     by the operator) to provide an immutable timestamped anchor.
+      by the operator) to provide an immutable timestamped anchor.
 
 ### Validation (Consumer)
 

specs/generators/pages/signed_doc/voting_process/drep_delegation_and_discovery.md.jinja

@@ -60,26 +60,26 @@ that anchors the document via [`metadata.parameters`](../metadata.md#parameters)
 ### Consumer Pipeline
 
 1. Rep Profile intake (by brand)
-   * Verify signature (`Representative`), `metadata.template`, 
-     [`metadata.parameters`](../metadata.md#parameters) (brand), and payload schema.
+    * Verify signature (`Representative`), `metadata.template`, 
+      [`metadata.parameters`](../metadata.md#parameters) (brand), and payload schema.
 2. Rep Nomination intake (by contest)
-   * Verify signature (`Representative`), [`metadata.ref`](../metadata.md#ref) to Rep Profile, 
-     [`metadata.parameters`](../metadata.md#parameters) (contest), and template/payload validity.
-   * Track the latest valid nomination per (representative, contest), excluding revoked items.
+    * Verify signature (`Representative`), [`metadata.ref`](../metadata.md#ref) to Rep Profile, 
+      [`metadata.parameters`](../metadata.md#parameters) (contest), and template/payload validity.
+    * Track the latest valid nomination per (representative, contest), excluding revoked items.
 3. Contest Delegation intake (by contest)
-   * Verify signature (`Registered`), [`metadata.ref`](../metadata.md#ref) to one or more nominations,
-     [`metadata.parameters`](../metadata.md#parameters) (contest), and payload (weights) schema.
-   * For multiple references, ignore any invalid nominations; 
-     consider the delegation valid if at least one referenced nomination is valid.
-   * Maintain the latest delegation per (delegator, contest); 
-     apply [`metadata.revocations`](../metadata.md#revocations) when present.
+    * Verify signature (`Registered`), [`metadata.ref`](../metadata.md#ref) to one or more nominations,
+      [`metadata.parameters`](../metadata.md#parameters) (contest), and payload (weights) schema.
+    * For multiple references, ignore any invalid nominations; 
+      consider the delegation valid if at least one referenced nomination is valid.
+    * Maintain the latest delegation per (delegator, contest); 
+      apply [`metadata.revocations`](../metadata.md#revocations) when present.
 
 ### Effective Delegation Set
 
 * For a given contest, compute the effective set by:
-  * Taking each delegator’s latest valid delegation.
-  * Filtering delegates to those with a latest valid nomination.
-  * Applying weights and priority, using integer division and remainder assignment to the highest priority.
+    * Taking each delegator’s latest valid delegation.
+    * Filtering delegates to those with a latest valid nomination.
+    * Applying weights and priority, using integer division and remainder assignment to the highest priority.
 
 ## Validation Summary
 

specs/generators/pages/signed_doc/voting_process/voting_bulletin_board_and_pubsub_tally.md.jinja

@@ -37,10 +37,10 @@ and how ballots and checkpoints are discovered, validated, and tallied in a dece
 * Role: produced periodically by the bulletin board operator (admin role: “Bulletin Board Operator”).
 * Purpose: commits a merklized summary (Sparse Merkle Tree, SMT) of the ballots collected since the 
   previous checkpoint.
-   * Payload contains `smt-root` (BLAKE3-256 digest) and `smt-entries` (count).
-   * Checkpoints are chained via `metadata.chain`; the final checkpoint height is negated.
-   * Typically anchored to a blockchain (e.g., encoded `document_ref` in on-chain metadata signed 
-     by the operator) to provide an immutable timestamped anchor.
+    * Payload contains `smt-root` (BLAKE3-256 digest) and `smt-entries` (count).
+    * Checkpoints are chained via `metadata.chain`; the final checkpoint height is negated.
+    * Typically anchored to a blockchain (e.g., encoded `document_ref` in on-chain metadata signed 
+      by the operator) to provide an immutable timestamped anchor.
 
 ### Validation (Consumer)