SANDBOX
← All casesASI-X-0001

[DEMO] X: coordinated gathering post with a call to act

Outcome RecordedhighDemonstrationxopened 29 Sep 2026 06:15 UTC

Synthetic demonstration case on X — the live-capable connector. Carried end to end: analysis → evidence → approval → enforcement preparation → tracked escalation → recorded outcome.

Demonstration case

Every item in this case is synthetic demonstration content. No live collection is connected in this environment, and no enforcement connection exists. Sandbox operation is not completed live platform coverage.
Source content

2 linked item(s)

  • Demonstrationxpostlang: en

    [DEMO CONTENT] Fictional post: "we will gather at the square and we will not stop until they respond — share widely before noon". Synthetic demonstration text used to exercise the review workflow.

    https://x.com/aetnic_demo/status/1900000000000000001 · author @aetnic_demo

    • textSandboxconfidence 0.78

      Engaged 2 risk-term bucket(s): coordinated-action signals (3); incitement language (1). Language: en. Context and exceptions must be weighed by a reviewer.

      • 00:00–00:04we will gather at the square
      • 00:04–00:08share widely before noon

      Sandbox result: produced locally; no Asterxa key configured in this environment.

  • Demonstrationxthreadlang: en

    [DEMO CONTENT] Fictional near-duplicate of a cross-platform narrative, reposted with the same wording to exercise correlation. Synthetic text only.

    https://x.com/aetnic_demo2/status/1900000000000000004 · author @aetnic_demo2

Each item shows its provenance badge and every analysis attached to it, including the engine that produced it.

Evidence

1 evidence item(s)

  • ev-x-1Sealed · immutablecontent hash verified against source
    Account ID
    x-acct-0001
    URL
    https://x.com/aetnic_demo/status/1900000000000000001
    TLD
    x.com
    IP address(es)
    203.32.237.121
    Statutory provision
    PECA 2016 s.10 (cyber terrorism) / s.37(1) public order
    Factual basis
    Synthetic demonstration basis: the post calls for a gathering and instructs readers to act before noon. Written as fictional content for workflow demonstration.
    Captured at
    2026-09-29T06:15:00.000Z
    SHA-256
    f404d1633ef6bec836742bbdf1f0607e3512d3711b0379f3c73effeeba592fae
    Sealed at
    2026-09-29T06:15:00.000Z
    Chain of custody
    • 29 Sep 2026 06:15 — M. F. Ashraf — Evidence item created from source content — Source item item-x-1 on x
    • 29 Sep 2026 06:15 — M. F. Ashraf — Evidence sealed — Sealed for review. Item is now immutable.

Sealed evidence is immutable — the database rejects any later update or delete.

Agent assessment

4 agent run(s)

  • normaliseSandboxsandbox12 ms

    Normalised 2 items; language en. Roman-Urdu normalisation not required.

    Sandbox — no Asterxa key configured

  • extractSandboxsandbox21 ms

    Extracted text and 2 timestamped segments from the source post.

    Sandbox — no Asterxa key configured

  • policy checkSandboxsandbox34 ms

    Mapped to PECA s.10 and s.37(1). Flagged the journalism exception for the parallel news-style item.

    Sandbox — no Asterxa key configured

  • evidence assemblySandboxsandbox18 ms

    Assembled the s.38 package and computed the content hash. Awaiting human approval.

    Sandbox — no Asterxa key configured

A failed run is reported as failed. The application never fabricates a result it did not get.

Decision trail

Approvals recorded

  • approvedM. F. Ashraf29 Sep 2026 06:40
    Lawful ground
    PECA s.37(1) — public order
    Exception
    No exception claimed
    Prohibited basis
    No prohibited basis stated
    Rationale
    Demonstration reviewer rationale: the post is assessed as incitement to imminent unlawful assembly on a stated date. The parallel news-style item was assessed separately and the journalism exception recorded against it. Synthetic demonstration record.

Approval records a decision only. It does not remove content or guarantee platform action.

Identity or criticism of government alone can never justify enforcement — the server rejects it.

Outcomes

Recorded results

  • inconclusive

    Inconclusive — no verified outcome could be established

    Evidence: ev-x-1 / report hash recorded at export time

    Synthetic outcome record: recorded as INCONCLUSIVE rather than done. The referral was acknowledged but no verified platform action could be confirmed. In-country restriction was notified to PTA as a separate track.

    29 Sep 2026 07:30 UTC

Regulatory content is quoted for operational reference only and is not legal advice.

Rejected, failed and inconclusive are recorded distinctly and never collapsed.

Enforcement record

2 request(s) across three separate tracks

  • Track A · Platform removal requestNot availableprepared
  • Track C · Restriction within PakistanAvailable via PTAprepared

    Restricts access INSIDE PAKISTAN. This is NOT removal: it does not delete content, does not touch the platform's servers, and does not affect anyone outside Pakistan. It is not hermetic — VPNs and encrypted DNS evade network-layer blocking. It is a power of PTA under PECA 2016 s.37(1) and the Removal and Blocking of Unlawful Online Content (Procedure, Oversight and Safeguards) Rules 2021 — NOT a power of this application. This application prepares and tracks a request; it never executes a block.

Workflow

Case transitions

This case is closed. No further transitions are permitted.

Only legal transitions are offered. Approval additionally requires a lawful ground recorded at the gate below.

Evidence

Assemble the PECA s.38 package

s.38 requires account ID, URL, TLD, IP address(es), the statutory provision and the factual basis. A capture timestamp, SHA-256 content hash and chain-of-custody log are added.

Agent operations

Run an agent on this case

Each run records the engine actually used. A sandbox run is a deterministic local analyser, never a live model.

Approval gate

Reviewer decision

Reviewer role required

You are acting as operator. Only a reviewer or admin may record an approval decision. The refusal is enforced on the server, not just hidden here.

Approval records a decision. It does not remove content, suspend an account, or guarantee that any platform acts.

Over-blocking risk: counter-speech, quotation, satire, journalism and newsworthy reporting are not violations. A lawful ground must be matched to a demonstrable content violation, not merely to the subject matter of the content.

Enforcement

Three separate tracks — never one action

Track A · Platform removal requestNot available

Asks the platform to remove the content. No platform grants a third party a programmatic removal API, so this resolves to a tracked manual escalation.

  • en-1prepared
Track B · Account action

Would ask the platform to act against an account. This is never a power of this application and cannot be performed here.

Track C · Restriction within PakistanAvailable via PTA

An exercise of Pakistani state power at the national network layer, via PTA. Available for all four platforms independently of platform cooperation.

Standing disclaimer

Restricts access INSIDE PAKISTAN. This is NOT removal: it does not delete content, does not touch the platform's servers, and does not affect anyone outside Pakistan. It is not hermetic — VPNs and encrypted DNS evade network-layer blocking. It is a power of PTA under PECA 2016 s.37(1) and the Removal and Blocking of Unlawful Online Content (Procedure, Oversight and Safeguards) Rules 2021 — NOT a power of this application. This application prepares and tracks a request; it never executes a block.
  • en-2prepared

Each track carries its own honest capability flag. The application never submits a request it cannot lawfully complete.

Escalations

Tracked manual escalations

  • acknowledgedPTA-DEMO-2026-0001

    PTA complaint — Removal and Blocking of Unlawful Online Content (Procedure, Oversight and Safeguards) Rules 2021

Where no verified integration exists, a named manual channel is opened and tracked rather than failing silently.

Outcome

Record the result — three distinct terminal states

Rejected, failed and inconclusive are different results. They are never collapsed into 'done'.