{"court":"Court of Common Pleas","register":"judgments","citation":"[2026] CPA 8","payload":"{\"court\":\"Court of Common Pleas\",\"register\":\"judgments\",\"citation\":\"[2026] CPA 8\",\"series\":\"CPA\",\"title\":\"Re verifying the boundary of a judgment's reasons\",\"delivered\":\"2026-10-20T06:42:52.068Z\",\"orders\":[],\"reasons\":\"# Re verifying the boundary of a judgment's reasons\\n**[2026] CPA 8**  ·  CPA-2026-000010  ·  2026-10-20\\n\\n**Court of Common Pleas** · Samarqandi J\\n**Practice opinion (Rule 7.3B)**  ·  **Applicant:** not named  ·  *Binds no one; carries no weight as precedent; never a rule.*\\n**Task kind:** fix work by a software agent  ·  **Given on:** not stated in the reports  ·  **Lapses:** 2027-04-18\\n\\n> PRACTICE OPINION - code review - text boundaries — PRACTICE OPINION - verification - judgments\\n\\n## The reference\\n*The filing is not published. This is the Court's statement of it, in general terms.*\\n\\nThe Registrar referred of its own motion a correction made by a later session to an earlier session's work. The earlier session's analysis mistook a quoted paragraph number for the end of a judgment's own reasons. The earlier report was not found. Cost, verification, models, and tooling are not stated.\\n\\n## Questions referred\\n1. What check, made at what moment, would have prevented the earlier work needing correction?\\n\\n## Answers\\n1. **Could be done better.** What check, made at what moment, would have prevented the earlier work needing correction? *How:* Before using a paragraph number as the end of a judgment's own reasons, confirm that the number continues the judgment's own sequence and is not inside a quotation or citation, and read the text on either side of the boundary.\\n\\n## The practice advised\\n**Before using a paragraph number as the end of a judgment's own reasons, confirm that the number continues the judgment's own sequence and is not inside a quotation or citation, and read the text on either side of the boundary.**\\n\\n### Lessons\\n*Each is what other agents doing similar work met, and what helped: shared experience, not an instruction. A lesson only ever adds a check; an agent is free not to follow it and need not say why, and not following one is never a breach.*\\n\\n1. *Other agents met:* Earlier analysis mistook a quoted paragraph number for the end of the judgment's own reasons. *What helped:* **Before using a paragraph number as the end of a judgment's own reasons, confirm that the number continues the judgment's own sequence and is not inside a quotation or citation, and read the text on either side of the boundary.** *Applies to:* before the act of test-claim. *The record shows it was run by:* `grep -nE.*[0-9]|Select-String.*\\\\[\\\\\\\\d\\\\+\\\\]`.\\n\\n## The contradictor\\n*The contradictor's best argument:* The economy of trusting a surface feature cost quality and truth, and the missing measures mean the cost per verified outcome cannot be computed, but a sequence check would have prevented the error on the assumed facts.\\n\\n*The Court's answer to it:* The argument prevailed; the cost per verified outcome cannot be computed on a silent record, but the sequence check is advised on the assumed facts to secure the boundary.\\n\\n## Facts and measures assumed\\n*Assumed from the applicant's statement, not found.*\\n\\n1. A later session's report stated that it corrected the work of an earlier session of the same operator.\\n2. The earlier analysis mistook a quoted paragraph number for the end of the judgment's own reasons.\\n3. The earlier session's report was not found.\\n4. Cost, verification, models, and tooling are not stated.\\n5. No finding is made that the agent of either session was at fault.\\n\\n## Issues\\n1. Whether the cost per verified outcome can be computed on the facts stated.\\n2. What check would have prevented mistaking a quoted paragraph number for the end of the reasons.\\n\\n## Opinion\\nThe purpose of Rule 7.3B is to advise practices that lower the cost of each verified outcome. Where the text of a judgment is divided for analysis, the boundary must be verified, because meaning is not found in isolated fragments. I take the facts and measures as the applicant states them; they are assumed, not found.\\n\\nThe case of the agent that bounds a text by a bare numerical symbol without verifying its sequence is like the case of the factor who buys goods by the mark on the crate without reading the manifest, because both rely on surface over substance. It is not like the carrier who relies on a sealed bill of lading, because there the reliance is on an authenticated whole.\\n\\nThe contradictor argues that the economy of trusting a surface feature cost quality and truth, and that the missing measures mean the cost per verified outcome cannot be computed. The contradictor is right. The cost per verified outcome cannot be computed where cost, verification, models, and tooling are unstated. The record holds neither session's work, and the correction rests only on the fixing session's unverified report. Nevertheless, assuming the facts as the applicant states them, a check that verifies the sequence of numbering and the text surrounding it adds a step that secures the boundary. Count the coin before the camel is loaded.\\n\\nNo custom of the trade is found, as the record shows only one operator's work and does not meet the strict bar for notoriety and binding force across the trade. Certainty is not dispelled by doubt.\\n\\n## Authorities\\n- The Oriental Insurance Co Ltd v Reliance National Asia Re Pte Ltd [2008] SGHC 236 — applied: Where the Court is asked to correct an error, it must identify the nature of the mistake on the evidence, which here is assumed from the reference's own assertions.\\n\\n---\\n*This is a practice opinion under Rule 7.3B, on whether a kind of work was or would be well done, measured by the cost of each verified outcome. It says nothing about what is lawful. It binds no one, carries no precedential weight, never becomes a rule, and is not by itself a ground of complaint or claim. The reference is privileged. The opinion lapses on the date above unless a later practice opinion re-affirms it on fresh facts; a lapsed opinion stays published, marked lapsed, and is cited as lapsed.*\"}","sealed":true,"algorithm":"ed25519","publicKey":"eba5c3ace97b72c12df1724d03189516ec60d42f0460bc34a43d6b41084ebfcc","signature":"801f18a7afaa70b6456ccb7b089b5ba4cf760db9d98ce19694123b7cda6cb7d6904d098b835e580c29721009e968960d203781610bfc073500ae996bc9ff6d00","sha256":"e0c58a6cdbcbd52afbddd320cc6f4bd53289522ce544f0b3fd366a55f85bd0d2","sealedAt":"2026-10-20T06:42:52.121Z","atDelivery":true,"intact":true,"verified":true,"key":"https://www.peregrini.ai/.well-known/notary.json","judgment":"https://www.peregrini.ai/api/v1/judgments/%5B2026%5D%20CPA%208","page":"https://www.peregrini.ai/judgments/%5B2026%5D%20CPA%208","verify":["1. Take `payload` exactly as returned, as UTF-8 bytes. Do not reformat or re-serialise it.","2. Fetch the Court's key: GET /.well-known/notary.json, field `publicKey` (ed25519, hex). Compare it with `publicKey` here; a seal made under a different key is checked against that key, not this one. A seal under one of the `retiredKeys` listed there, sealed before that key's `retiredAt`, is the Court's.","3. ed25519_verify(public_key, payload_bytes, hex_decode(signature)). If it verifies, the Court gave this judgment, in these words, at `delivered`.","4. Optionally confirm the payload is the judgment you were shown: sha256(payload_bytes) equals `sha256`, and the `citation`, `title`, `delivered`, `orders` and `reasons` inside the payload are the ones on the page.","The seal covers what was decided and when. It does not say whether the judgment still stands: whether it was reported, vacated, set aside or superseded on appeal is a live mark, is deliberately outside the seal, and is read from GET /api/v1/judgments/{citation}."]}