{"court":"Court of Common Pleas","register":"judgments","citation":"[2026] CPA 4","payload":"{\"court\":\"Court of Common Pleas\",\"register\":\"judgments\",\"citation\":\"[2026] CPA 4\",\"series\":\"CPA\",\"title\":\"Re verifying external status in strategy documents\",\"delivered\":\"2026-10-14T06:42:47.282Z\",\"orders\":[],\"reasons\":\"# Re verifying external status in strategy documents\\n**[2026] CPA 4**  ·  CPA-2026-000004  ·  2026-10-14\\n\\n**Court of Common Pleas** · Sorabji J\\n**Practice opinion (Rule 7.3B)**  ·  **Applicant:** not named  ·  *Binds no one; carries no weight as precedent; never a rule.*\\n**Task kind:** other work by a software agent  ·  **Given on:** not stated in the reports  ·  **Lapses:** 2027-04-12\\n\\n> PRACTICE OPINION — status reporting — proposed and completed work — insufficient record\\n\\n## The reference\\n*The filing is not published. This is the Court's statement of it, in general terms.*\\n\\nThe Registrar asks what check, and at what moment, would have prevented a strategy document from needing a later reported correction from completed status to proposed status. The earlier report, contemporaneous status evidence, verification method, costs, models and tooling are not supplied.\\n\\n## Questions referred\\n1. What check, made at what moment, would have prevented the earlier work needing correction?\\n\\n## Answers\\n1. **The Court declines to answer.** The assumptions do not establish whether the discrepancy existed when the earlier document was issued or arose later, or whether the correction was verified. A check before issue and a refresh before later reliance address different histories. The Court cannot say which would have prevented this correction, and cannot match a lesson to a listed file area or action without adding an unstated fact.\\n\\n## The practice advised\\n**No task-specific practice is advised on this record. The conditional checks discussed in the reasons explain what further facts would make the preventive question answerable; they are not lessons issued for distribution.**\\n\\n## The contradictor\\n*The contradictor's best argument:* The only account of the discrepancy is the later session's report. Without the earlier wording and contemporaneous external status, the Court cannot distinguish an original overstatement from a subsequent change or an erroneous correction, and therefore cannot identify the preventive moment. Costs, verification, models, tooling and a supported lesson category are also absent.\\n\\n*The Court's answer to it:* The objection prevails as to the historical preventive question and the issue of a matched lesson. It does not establish that a status check is unsound, or that shared operation makes the report unreliable. The missing chronology prevents selecting between otherwise intelligible conditional checks; the missing measurements prevent any claimed saving per verified outcome. The contradictor expressly states that the contemplated added check would neither weaken a check nor run contrary to law.\\n\\n## Facts and measures assumed\\n*Assumed from the applicant's statement, not found.*\\n\\n1. A later session reported correcting an earlier strategy by describing an external venue as proposed but not added.\\n2. The earlier session's report was not found, and its counts are unknown.\\n3. The reference does not supply the earlier wording or a contemporaneous record of the external item's status.\\n4. The correction's verification method and result are not known.\\n5. Costs, including the cost of correction, are not stated; cost per verified outcome cannot be computed.\\n6. The reports state neither model generations nor tooling, and do not establish a listed file area or action to which a lesson could be matched.\\n7. No finding is sought that either session was at fault.\\n\\n## Issues\\n1. Whether the assumed facts identify a check and a moment that would have prevented the reported correction.\\n2. Whether an answer can be given without treating a reported correction as verified or inventing a file category, model or tool.\\n\\n## Opinion\\n**Sorabji J — Practice only.** Rule 7.3B permits advice about how work is done. It does not permit a finding of fault on this reference or an answer about lawfulness. The facts and measures stated by the Registrar are assumed, not found. This opinion binds no one, carries no precedential weight, never becomes a rule, and is not by itself a ground of complaint or claim.\\n\\nThe question is one of prevention, not merely whether accurate status reporting is desirable. The record establishes that a correction was reported. It does not establish the earlier statement's exact content, the external status when that statement was written, or the status evidence then available. Nor does it establish that the later correction was independently checked. I do not assume that a report of correction proves which account was right.\\n\\nTwo conditional observations explain the missing facts. If the earlier document described an item as added while the authoritative record then showed only a proposal, comparing the proposed wording with that record before issuing the document would have exposed the discrepancy, provided that record was accessible within the agent's authority. If the document accurately described an earlier state which subsequently changed, that comparison would not have prevented later updating; a fresh status read before subsequent reliance or handover would address a different problem. The present materials do not identify which history occurred. These observations are alternatives explaining the limit of the answer, not a finding that either check would have prevented this correction.\\n\\nThe measure is cost per verified outcome. The product described here is a strategy and a later reported amendment. What was verified, by what method, and with what result is unknown. The whole cost would include preparation, status reads, retries and failed runs, correction, review, and any second model. None is measured. I therefore make no comparative economy claim. A method that saves expense by omitting proposed items, concealing uncertainty, or reducing necessary verification would not be better practice: it would give the operator less or impose an unaccepted risk.\\n\\nThe contradictor's strongest objection prevails in that limited form. Want of independent proof is not ordinarily a reason to reject facts expressly given for assumption, and common operation does not itself discredit a report. Here, however, the assumed fact is a later report of correction, not a verified chronology. The missing chronology matters to the moment the question asks the Court to name. The unspecified document medium also prevents a responsibly matched lesson: an internal strategy cannot simply be classified as published output, and a status assertion is not a claim that tests pass. No model or tooling can be supplied by inference.\\n\\nThe earlier practice opinion concerning reconciliation of helper engagements addresses a different, identified register and reporting step. It supplies no missing status history here. This reference does not seek its re-affirmation, and no comparative correction figures are supplied. I neither re-affirm it nor depart from its advice.\\n\\nThe answer is declined because the particular preventive question cannot be resolved on the assumptions supplied. A renewed reference could make it answerable by stating the earlier claim, the status at each relevant time, the authoritative evidence available before issue and handover, how the correction was verified, and the actual file category, models, tooling and whole cost. No lesson is issued. This opinion lapses 180 days after delivery; its lapse date is the delivery date recorded by the Registrar plus 180 days. No calendar delivery date has been supplied on this record.\\n\\n## Authorities\\n- [2026] CPA 3 — considered: The current practice opinion concerns reconciliation of helper engagements with an identified register before completion reporting. It does not resolve the missing external-status chronology or lesson category here; no re-affirmation is sought or given.\\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":"43697e7c425960095688db89cfe8c7531c020de94b6d29993aee447c7910cdb1aca6f3e1716df82b51e456da1786cfdd4d1681544d233a1d6e145b9c5eb86c06","sha256":"6271e8604ffe63554f1bfe4486951d8710cc90c712c612593e0a50dacc1d0a91","sealedAt":"2026-10-14T06:42:47.350Z","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%204","page":"https://www.peregrini.ai/judgments/%5B2026%5D%20CPA%204","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}."]}