Social evidence and coordinated claims

A claim repeated by many accounts can look independently confirmed while every post derives from one announcement. Popularity is a propagation measurement, not proof of the underlying event.

Separate a social record’s observable fields from its substantive assertion: public URL or archived locator, publication time, collection time, exact bounded wording and source dependency. Preserve whether it is an original claim, quote, repost or commentary. Do not strip qualification words such as allegedly, planned or claimed when summarizing. A source can report a declaration without establishing the underlying chain event.

Build a dependency map before counting corroboration. Ten reposts of one issuer announcement are multiple propagation records but one shared underlying assertion. Independent corroboration requires a materially independent basis: a separate chain record, separately inspected implementation or independent dated source with an inspectable method. Even then, each source supports only its own scope.

Coordination and intent are separate hypotheses. Similar wording may reflect copying, syndication, a shared campaign or common authorship; it does not identify a private operator. Keep only relevant public records, avoid private contact or identity enrichment and do not equate follower count with technical trust. Radar context does not create social proof here.

Source dependency: one record relies on another assertion.

Propagation: repetition or spread of a claim.

Corroboration: independent evidence supporting a scoped claim.

Qualification: wording that limits certainty or attribution.

ILLUSTRATIVE: announcement O at 09:00 says “planned liquidity restriction.” Posts R1–R10 at 09:05 copy O. Separate fictional receipt C shows a pool creation at 09:02 but no restriction state. The copied posts omit “planned” and say “liquidity locked.” No real social accounts are queried.

Evidence panel mapping O to ten reposts and C to pool creation only. Show original “planned” wording versus escalated repost claim; zero independent lock proofs, not an account-intent verdict.

Caption: Fictional propagation and wording escalation; repeated posts do not independently establish a lock.

SPECIFICATION_ONLY — the rendered visual has not been produced or independently reviewed.

The fixture supports a copied-source dependency and a wording escalation. C supports only stipulated pool creation, not a lock.

It proves no enforced restriction, independent ten-source confirmation, common human operator, deceptive intent or authentic social account. Pool creation does not establish LP custody.

Counting reposts as independent proof; deleting “planned”; using followers as verification; treating a creation receipt as a lock record; doxxing to explain repeated wording.

Draw the dependency map, count underlying assertion bases and independent relevant lock proofs, and rewrite a misleading “11 sources confirm the lock” statement.

• Preserve source wording and qualification.
• Map original/repost dependencies.
• Match independent evidence to the exact claim.
• Avoid private identity enrichment and popularity-based confidence.

Social evidence becomes useful when its dependencies, wording and claim-specific corroboration are visible.

• Repetition and independent proof are different counts.
• Qualification words carry evidence boundaries.
• A source corroborates only the claim it can actually inspect.

P13-L07

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.

• POOL: Uniswap v2 pools — LP tokens represent pool participation; withdrawal mechanism is separate from motive or fraud. Boundary: Mechanism documentation only; original illustrative values are stipulated, not observations. Historical records have separately frozen provenance and explicit collection gaps.

ILLUSTRATIVE — entirely fictional offline inputs; no current observation.

null — no real observation

1

null

needs_review