P13-L08 · P13 · P13-M02
Test a historical allegation and explicitly bound the conclusion
Prerequisites: P13-L07
Learning objectives
- Test a historical allegation and explicitly bound the conclusion
- Reach a claim-specific historical assessment that can stop at partially supported or insufficient evidence.
Why this matters
An official charging publication is important evidence about an allegation’s existence. It is not a substitute for proving the allegation’s underlying transactions, representation or intent.
Explanation
HISTORICAL PROVENANCE WARNING: this exercise assesses the bounded SEC announcement 2023-229 dated 1 November 2023 about SafeMoon. It is an as-of-publication analysis, not a statement of the later case outcome or current legal status. The frozen package contains original bounded paraphrases and locators, not a complaint PDF, native transaction dataset or court judgment.
Decompose the broad hypothesis. H1: the official publication announced charges. H2: it attributes allegations about liquidity-lock representations and withdrawals to its complaint. H3: the underlying withdrawal and lock mismatch actually occurred as described. H4: identified participants acted with fraudulent intent. Each claim requires different evidence. The publication directly supports H1 and H2 at its source boundary. H3 needs original representations, exact assets/pools, time-bound lock state and transactions. H4 requires an admissible intent/control bridge and cannot be inferred from a withdrawal alone.
Use verdicts claim by claim: SUPPORTED when records establish the scoped proposition; PARTIALLY SUPPORTED when only defined elements are supported; NOT ESTABLISHED when the proposed conclusion does not follow from this package; INSUFFICIENT EVIDENCE when decisive records are absent. These are evidential conclusions, not legal verdicts. Preserve the allegation’s attributed status and identify what would change each unresolved result. Do not force either fraud or exoneration.
Key terms
Attributed allegation: a claim reported by an identified source.
SUPPORTED: scoped proposition established by available evidence.
PARTIALLY SUPPORTED: specified components supported, but not all.
NOT ESTABLISHED / INSUFFICIENT EVIDENCE: conclusion unproven or necessary records missing; neither establishes the opposite conclusion.
Historical example
The actual dated SEC publication announces charges and attributes liquidity and trading allegations to its complaint. Frozen rows S1–S3 preserve that publication boundary. This lesson uses no chain records from the underlying case and does not connect the unrelated P13-L03 withdrawal transaction to SafeMoon. The hypothesis “a liquidity withdrawal proves fraud” has no admissible bridge in this package.
Visual specifications
Evidence panel H1–H4 with source locator, required evidence, verdict and missing-record columns. Show supported publication rows and unresolved event/intent rows; no asset fraud score or legal-guilt badge.
Caption: Historical allegation assessment; a charging publication does not independently establish the underlying events or intent.
SPECIFICATION_ONLY — the rendered visual has not been produced or independently reviewed.
What the evidence proves
H1 SUPPORTED: the official dated charging publication exists. H2 SUPPORTED: it contains the specified attributed allegations. The compound claim “an official allegation exists and its underlying events are independently proved here” is PARTIALLY SUPPORTED only for its publication element.
What the evidence does not prove
H3 INSUFFICIENT EVIDENCE: underlying representation, lock and transaction records were not captured. H4 NOT ESTABLISHED: intent and human control are not independently proved. No legal guilt, innocence, later outcome or current status is concluded. Missing proof in this package is not proof that no event occurred.
Common mistakes
Turning a charge into a judgment; calling a publication a native receipt; merging unrelated cases; deriving intent from withdrawal; forcing a binary fraud/exoneration answer.
Practical exercise
Build H1–H4 rows with source, verdict, boundary and next needed record. Assess the compound claim and write two final sentences preserving allegation status without financial or legal guidance.
Show worked correction
H1: S1 / SUPPORTED at the publication boundary. H2: S2–S3 / SUPPORTED as attributed allegations. H3: INSUFFICIENT EVIDENCE; need dated original marketing records, exact asset/pool/lock state and native withdrawal provenance. H4: NOT ESTABLISHED; need admissible control/intent records beyond the technical event, with any legal finding separately attributed. Compound claim: PARTIALLY SUPPORTED only for the announcement element. Final: “The dated SEC announcement records a historical charging allegation; this package inspects the publication, not its underlying transactions. Fraudulent intent and a legal conclusion are not established by these captured records.” No opposite verdict is forced and no later case status is asserted.
Checklist
- Decompose publication, event, control and intent claims.
- Use claim-specific verdicts with boundaries.
- Keep unrelated historical cases separate.
- Do not assert later legal status or force fraud/exoneration.
Summary
The strongest bounded assessment can support an allegation’s publication while finding its underlying event and intent unestablished in the captured package.
Summary
- Charges and judgments are different record types.
- A compound claim can be only partially supported.
- Insufficient evidence does not establish the opposite conclusion.
Next lesson
Program complete; no new runtime, certification or financial action is implied.
Tools
Use the named ZECOIN tool only as an evidence-reading context. This lesson creates no tool output, account session or entitlement. Offline exercise; do not sign, deploy, approve or fund anything.
Sources & claim boundaries
- SEC: SEC announcement 2023-229 — historical allegation publication — Dated 1 November 2023 charging announcement and attributed liquidity/market-activity allegations; not a judgment. Boundary: Historical charging publication only; no complaint PDF, native transactions, original marketing archive, intent proof or later adjudication/current-status claim.
Evidence classifications
HISTORICAL — event dates and retrieval dates are separate. See frozen package and collection gaps.
Observation date
2026-10-02 (retrieval date; not event time)
Content version
1
Review date
null
Review status
needs_review
Visual specifications
P13-L08-V01
Test a historical allegation and explicitly bound the conclusion
Historical allegation assessment; a charging publication does not independently establish the underlying events or intent.
Evidence panel H1–H4 with source locator, required evidence, verdict and missing-record columns. Show supported publication rows and unresolved event/intent rows; no asset fraud score or legal-guilt badge.
Evidence panel H1–H4 with source locator, required evidence, verdict and missing-record columns. Show supported publication rows and unresolved event/intent rows; no asset fraud score or legal-guilt badge.
Stack observations, assumptions, gaps and conclusion at 390 px; retain full IDs and a complete text equivalent. Any wide table scrolls locally.
Prose may follow RTL; IDs, quantities and time axes remain LTR. Preserve dependency direction.
P13-L08-SEC-ALLEGATION-20231101-v1
Sources & claim boundaries
SEC · OFFICIAL_ENFORCEMENT_PUBLICATION
SEC announcement 2023-229 — historical allegation publication
- Supported claim
- Dated 1 November 2023 charging announcement and attributed liquidity/market-activity allegations; not a judgment.
- Verification boundary
- Historical charging publication only; no complaint PDF, native transactions, original marketing archive, intent proof or later adjudication/current-status claim.
- Checked at
- 2026-10-02
https://www.sec.gov/newsroom/press-releases/2023-229
Dataset provenance
id: P13-L08-SEC-ALLEGATION-20231101-v1
dataStatus: HISTORICAL
observedAt: 2026-10-02
timeBasis: Publication 2023-11-01;current retrieval / extraction dated separately
source: docs/academy-2/datasets/p13/allegation.json
scope: Claim-specific assessment of a dated attributed allegation; no independent underlying event or intent validation.