SANDBOX
Acceptance

Per-platform end-to-end walk

The consolidated scope requires a separate, demonstrable workflow for Facebook, TikTok, X and Instagram: ingestion or URL submission → multimodal analysis → evidence → case → approval → supported enforcement request → outcome verification. Run each walk below. You are acting as operator.

What a walk does — and does not — show

A walk demonstrates the connector and the workflow, scoped by authorised access. It never demonstrates complete platform coverage. A stage that runs in a sandbox or manual mode is labelled as such and does not count as completed live platform coverage, and every non-live stage names the exact dependency blocking it. Platform removal and account action are never powers of this application.
Criterion

The seven stages

  1. 1Ingestion / URL submission
  2. 2Multimodal analysis (text, on-screen text, audio, video)
  3. 3Evidence assembly (PECA 2016 s.38)
  4. 4Case opened and progressed
  5. 5Reviewer approval at the lawful-ground gate
  6. 6Supported enforcement request
  7. 7Outcome verification
End-to-end acceptance walk

Facebook

Demonstrated — with sandbox stagesran as reviewer

The workflow completed end to end, but at least one stage ran in a sandbox or manual mode. This does NOT count as completed live platform coverage: the exact dependency is named against each such stage below.

  1. Facebook: ingestion / URL submissionSandboxlimited

    Accepted: Facebook URL recognised. The connector is sandbox-labelled because the access dependency below is not satisfied.

    • Content item: 77e5b718-117d-40b5-97e8-eb52bf2bb87a
    • Platform: Facebook

    Dependency — Blocked by: no official third-party Facebook API returns other people's public posts or comments. Bulk public content requires a qualified research institution as lead applicant for Meta Content Library.

  2. Facebook: multimodal analysisSandboxlimited

    The deterministic sandbox analysers produced text, on-screen-text and transcript segments with timestamps from the recorded submission stub only — no live media was retrieved. Extracted 2 timestamped segment(s). Sandbox result: produced by a deterministic local analyser, not a live analysis engine. Not evidentiary on its own.

    • Extraction run: b3b3a80e-accc-4d51-a9d2-cfec9730bce7
    • Normalisation run: 8ad6c1af-cdee-4dda-a17b-12610a4a11bc
    • Engine: Sandbox

    Dependency — Sandbox — no Asterxa key configured. Agent roles fall back to the deterministic local analysers, so this analysis is a demonstration and not a live AI result.

  3. Facebook: evidence assembly (PECA 2016 s.38)Livepass

    A PECA 2016 s.38 evidence package was assembled (account ID, URL, TLD, IPs, statutory provision, factual basis) and sealed with a SHA-256 content hash on the custody record.

    • Evidence: b0dea3f5-55f8-45e7-ac11-40eb07fb63e4
    • Content hash: 14e7d5c03a17e052331e58a1…
    • Case: fbf9ea00-a2d2-4023-ac9c-c1e4fec479ed
  4. Facebook: case opened and progressedLivepass

    Case ASI-FA-0009 was opened and progressed New → Analysing → Evidence Ready → Awaiting Review, ready for a reviewer at the gate.

    • Case: ASI-FA-0009
    • Status: Awaiting review
  5. Facebook: reviewer approval at the lawful-ground gateHuman gatepass

    Approved by Test Reviewer acting as reviewer against PECA s.37(1) — commission of, or incitement to, an offence under PECA. This is a human decision recorded at the gate; no agent performed it and no agent may.

    • Approval: a55080db-8767-43ea-8d6f-b44b462d3dfc
    • Ground: PECA s.37(1) — commission of, or incitement to, an offence under PECA
  6. Facebook: supported enforcement requestManuallimited

    Three enforcement tracks were assessed separately. In-country restriction: prepared and referred to PTA as a tracked request (PTA complaint — Removal and Blocking of Unlawful Online Content (Procedure, Oversight and Safeguards) Rules 2021). Platform removal: no programmatic API exists — it resolves to a tracked manual escalation. Account action: not a power of this application. No verified integration exists for "platform_removal" on facebook. A tracked manual escalation has been opened instead (In-product reporting channel (manual)). The application does not submit requests it cannot lawfully complete.

    • In-country request: 2073febd-c972-4e14-89d6-32a51e69d618
    • PTA escalation: a5b815df-a35c-4266-abfb-304643f42c1a
    • Removal request: 5f1b09ad-e4b4-4b0c-a151-5984da331058
    • Manual escalation: d3a0b18e-3b82-491d-a383-1f3ae07c6b46
    • Removal capability: unsupported
    • Account action: unsupported

    Dependency — In-country restriction is a PTA power the application prepares and tracks, never executes; platform removal and account action depend on the platform's own reporting channel. 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.

  7. Facebook: outcome verificationLivepass

    A terminal outcome was recorded and re-read from the case, confirming the recorded state.

    • Outcome: 99681961-8acc-4c50-9ffa-1fc92413e729
    • Terminal state: inconclusive

Demonstrates the connector and the workflow scoped by authorised access — never complete platform coverage.

Facebook — mandatory content types

  • Post
    No public-post search API exists. Bulk public content is reachable only through Meta Content Library (L3 research partnership).
    Depends on: Meta Content Library institutional access (L3): requires a qualified academic or non-profit research institution as lead applicant; read-only cleanroom with no raw-data export.
    requires access
  • Page
    Public Page metadata (name, category, fan count, About) only; returns no posts and no comments.
    Depends on: Requires Meta App Review plus Business Verification for Advanced Access.
    limited
  • Public group
    No official third-party API reaches public Groups.
    Depends on: Public Group content is reachable only inside the Meta Content Library cleanroom.
    unsupported
  • Comment
    Third-party comment search was removed; only comments on Pages you administer are readable.
    Depends on: Own-Page comments require pages_manage_posts; no public comment surface exists.
    unsupported
  • Image
    Media is reachable only inside the Content Library cleanroom; own-Page media is live.
    Depends on: Meta Content Library institutional access (L3): requires a qualified academic or non-profit research institution as lead applicant; read-only cleanroom with no raw-data export.
    requires access
  • Video
    Video is reachable only inside the Content Library cleanroom; own-Page video is live.
    Depends on: Meta Content Library institutional access (L3): requires a qualified academic or non-profit research institution as lead applicant; read-only cleanroom with no raw-data export.
    requires access
  • Reel
    Reels surface as media inside the Content Library cleanroom; own-Page Reels are live.
    Depends on: Meta Content Library institutional access (L3): requires a qualified academic or non-profit research institution as lead applicant; read-only cleanroom with no raw-data export.
    requires access

0 of 7 mandatory content types are live today; 1 are limited; 4 require access; 2 are unsupported by any official API. This counts content types, never share of content.

End-to-end acceptance walk

TikTok

Demonstrated — with sandbox stagesran as reviewer

The workflow completed end to end, but at least one stage ran in a sandbox or manual mode. This does NOT count as completed live platform coverage: the exact dependency is named against each such stage below.

  1. TikTok: ingestion / URL submissionSandboxlimited

    Accepted: TikTok URL recognised. The connector is sandbox-labelled because the access dependency below is not satisfied.

    • Content item: 0ff1cb85-fee5-4aa4-9c59-788767fa9d0a
    • Platform: TikTok

    Dependency — Blocked by: Pakistan is not an eligible region for TikTok Research Tools. Lawful routes are a named collaboration with an institution in the US, EEA, UK, Canada, Switzerland, Norway, Iceland or Liechtenstein, or the EU DSA vetted-researcher channel.

  2. TikTok: multimodal analysisSandboxlimited

    The deterministic sandbox analysers produced text, on-screen-text and transcript segments with timestamps from the recorded submission stub only — no live media was retrieved. Extracted 2 timestamped segment(s). Sandbox result: produced by a deterministic local analyser, not a live analysis engine. Not evidentiary on its own.

    • Extraction run: b94594ec-ba28-46ef-935f-98c7bade6b0a
    • Normalisation run: 8faf9d6a-ba36-4d24-a62b-1c75e1132802
    • Engine: Sandbox

    Dependency — Sandbox — no Asterxa key configured. Agent roles fall back to the deterministic local analysers, so this analysis is a demonstration and not a live AI result.

  3. TikTok: evidence assembly (PECA 2016 s.38)Livepass

    A PECA 2016 s.38 evidence package was assembled (account ID, URL, TLD, IPs, statutory provision, factual basis) and sealed with a SHA-256 content hash on the custody record.

    • Evidence: aada604f-9369-41ad-a74e-3873d7e05f24
    • Content hash: b09fabb165072ead80004b03…
    • Case: 6652296a-996c-4be9-a456-6e652d05e864
  4. TikTok: case opened and progressedLivepass

    Case ASI-TI-0010 was opened and progressed New → Analysing → Evidence Ready → Awaiting Review, ready for a reviewer at the gate.

    • Case: ASI-TI-0010
    • Status: Awaiting review
  5. TikTok: reviewer approval at the lawful-ground gateHuman gatepass

    Approved by Test Reviewer acting as reviewer against PECA s.37(1) — commission of, or incitement to, an offence under PECA. This is a human decision recorded at the gate; no agent performed it and no agent may.

    • Approval: 021592a9-4f4b-4d88-9808-e04e46f4981f
    • Ground: PECA s.37(1) — commission of, or incitement to, an offence under PECA
  6. TikTok: supported enforcement requestManuallimited

    Three enforcement tracks were assessed separately. In-country restriction: prepared and referred to PTA as a tracked request (PTA complaint — Removal and Blocking of Unlawful Online Content (Procedure, Oversight and Safeguards) Rules 2021). Platform removal: no programmatic API exists — it resolves to a tracked manual escalation. Account action: not a power of this application. No verified integration exists for "platform_removal" on tiktok. A tracked manual escalation has been opened instead (In-product reporting channel (manual)). The application does not submit requests it cannot lawfully complete.

    • In-country request: cdbc6df1-764e-4a05-8ee5-151375369d89
    • PTA escalation: a0fefcb0-37be-4e90-8f38-0470790ee40b
    • Removal request: 586514ab-246f-4ef1-a73b-d6e24d4c9e1b
    • Manual escalation: a55007a6-1bc7-413b-af75-880958d956d4
    • Removal capability: unsupported
    • Account action: unsupported

    Dependency — In-country restriction is a PTA power the application prepares and tracks, never executes; platform removal and account action depend on the platform's own reporting channel. 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.

  7. TikTok: outcome verificationLivepass

    A terminal outcome was recorded and re-read from the case, confirming the recorded state.

    • Outcome: 92936072-c02d-4929-9963-c438871bbe0f
    • Terminal state: inconclusive

Demonstrates the connector and the workflow scoped by authorised access — never complete platform coverage.

TikTok — mandatory content types

  • Video
    Metadata only; no media stream is returned.
    Depends on: Pakistan is not an eligible region for TikTok Research Tools. Lawful routes are a named collaboration with an institution in the US, EEA, UK, Canada, Switzerland, Norway, Iceland or Liechtenstein, or the EU DSA vetted-researcher channel.
    requires access
  • Caption
    Caption text is returned with the video metadata only under Research Tools access.
    Depends on: Pakistan is not an eligible region for TikTok Research Tools. Lawful routes are a named collaboration with an institution in the US, EEA, UK, Canada, Switzerland, Norway, Iceland or Liechtenstein, or the EU DSA vetted-researcher channel.
    requires access
  • Hashtag
    Hashtag search covers text fields only; there is no index over spoken audio.
    Depends on: Pakistan is not an eligible region for TikTok Research Tools. Lawful routes are a named collaboration with an institution in the US, EEA, UK, Canada, Switzerland, Norway, Iceland or Liechtenstein, or the EU DSA vetted-researcher channel.
    requires access
  • Comment
    Only available comments are returned and commenter identity is stripped.
    Depends on: Pakistan is not an eligible region for TikTok Research Tools. Lawful routes are a named collaboration with an institution in the US, EEA, UK, Canada, Switzerland, Norway, Iceland or Liechtenstein, or the EU DSA vetted-researcher channel.
    requires access
  • Account profile
    Public account content only via Research Tools; accounts that consent are reachable live via the Display API / Login Kit.
    Depends on: Pakistan is not an eligible region for TikTok Research Tools. Lawful routes are a named collaboration with an institution in the US, EEA, UK, Canada, Switzerland, Norway, Iceland or Liechtenstein, or the EU DSA vetted-researcher channel.
    requires access

0 of 5 mandatory content types are live today; 5 require access. This counts content types, never share of content.

End-to-end acceptance walk

X

Demonstrated — with sandbox stagesran as reviewer

The workflow completed end to end, but at least one stage ran in a sandbox or manual mode. This does NOT count as completed live platform coverage: the exact dependency is named against each such stage below.

  1. X: ingestion / URL submissionSandboxlimited

    Accepted: X URL recognised. X is the live-capable connector, but no live credentials are configured in this environment.

    • Content item: d60915e4-31b5-4d29-97a6-daedd079f85c
    • Platform: X

    Dependency — Demonstration item: no live collection is connected in this environment.

  2. X: multimodal analysisSandboxlimited

    The deterministic sandbox analysers produced text, on-screen-text and transcript segments with timestamps from the recorded submission stub only — no live media was retrieved. Extracted 2 timestamped segment(s). Sandbox result: produced by a deterministic local analyser, not a live analysis engine. Not evidentiary on its own.

    • Extraction run: 1f446579-ce67-4515-944d-a64911c80041
    • Normalisation run: be002b76-3fac-4c08-a61c-d481c143ddf8
    • Engine: Sandbox

    Dependency — Sandbox — no Asterxa key configured. Agent roles fall back to the deterministic local analysers, so this analysis is a demonstration and not a live AI result.

  3. X: evidence assembly (PECA 2016 s.38)Livepass

    A PECA 2016 s.38 evidence package was assembled (account ID, URL, TLD, IPs, statutory provision, factual basis) and sealed with a SHA-256 content hash on the custody record.

    • Evidence: 4c491fa4-2972-448c-ad93-c256e0cfa728
    • Content hash: baaa2fcc6a53926bc3a0639c…
    • Case: b902d73d-6c6b-4ad4-8263-2a0f19c70b75
  4. X: case opened and progressedLivepass

    Case ASI-X-0011 was opened and progressed New → Analysing → Evidence Ready → Awaiting Review, ready for a reviewer at the gate.

    • Case: ASI-X-0011
    • Status: Awaiting review
  5. X: reviewer approval at the lawful-ground gateHuman gatepass

    Approved by Test Reviewer acting as reviewer against PECA s.37(1) — commission of, or incitement to, an offence under PECA. This is a human decision recorded at the gate; no agent performed it and no agent may.

    • Approval: 9a3375ea-2923-4c1b-874a-6d56534d45ed
    • Ground: PECA s.37(1) — commission of, or incitement to, an offence under PECA
  6. X: supported enforcement requestManuallimited

    Three enforcement tracks were assessed separately. In-country restriction: prepared and referred to PTA as a tracked request (PTA complaint — Removal and Blocking of Unlawful Online Content (Procedure, Oversight and Safeguards) Rules 2021). Platform removal: no programmatic API exists — it resolves to a tracked manual escalation. Account action: not a power of this application. No verified integration exists for "platform_removal" on x. A tracked manual escalation has been opened instead (In-product reporting channel (manual)). The application does not submit requests it cannot lawfully complete.

    • In-country request: 06b4470a-038d-4c95-ab14-d9c6fa396908
    • PTA escalation: f7d111be-5dd7-4640-bb61-4b4983fce06f
    • Removal request: 973e8b03-8152-4589-bf03-ff063d681b79
    • Manual escalation: bc7d0cd4-03d5-4c3a-a45e-df51759434a9
    • Removal capability: unsupported
    • Account action: unsupported

    Dependency — In-country restriction is a PTA power the application prepares and tracks, never executes; platform removal and account action depend on the platform's own reporting channel. 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.

  7. X: outcome verificationLivepass

    A terminal outcome was recorded and re-read from the case, confirming the recorded state.

    • Outcome: c1331763-45e4-4a5c-a774-11b42ceb9b3e
    • Terminal state: inconclusive

Demonstrates the connector and the workflow scoped by authorised access — never complete platform coverage.

X — mandatory content types

  • Post
    Public post search and lookup are available under pay-per-use credits.
    live
  • Reply
    Replies are returned as part of the conversation on a public post.
    live
  • Thread
    A thread is read as its constituent public posts and their replies.
    live
  • Repost
    Reposts are identifiable from the public post object.
    live
  • Quoted post
    Quoted posts are returned as a referenced public post.
    live
  • Image
    Image media keys are returned; media download is available per post.
    live
  • Video
    Video media keys are returned; media download is available per post.
    live

7 of 7 mandatory content types are live today. This counts content types, never share of content.

End-to-end acceptance walk

Instagram

Demonstrated — with sandbox stagesran as reviewer

The workflow completed end to end, but at least one stage ran in a sandbox or manual mode. This does NOT count as completed live platform coverage: the exact dependency is named against each such stage below.

  1. Instagram: ingestion / URL submissionSandboxlimited

    Accepted: Instagram URL recognised. The connector is sandbox-labelled because the access dependency below is not satisfied.

    • Content item: 91a5efa1-7a40-4c3f-85ea-3377434f6b29
    • Platform: Instagram

    Dependency — Blocked by: the Instagram API reaches only Business/Creator accounts that authorised the app. Hashtag search is capped at 30 unique hashtags per rolling 7 days and returns no usernames.

  2. Instagram: multimodal analysisSandboxlimited

    The deterministic sandbox analysers produced text, on-screen-text and transcript segments with timestamps from the recorded submission stub only — no live media was retrieved. Extracted 2 timestamped segment(s). Sandbox result: produced by a deterministic local analyser, not a live analysis engine. Not evidentiary on its own.

    • Extraction run: 3ad34ff8-62e2-41fb-9ad5-834d9760b817
    • Normalisation run: 48f548f2-44e8-49e2-aa5c-700f4f9b1841
    • Engine: Sandbox

    Dependency — Sandbox — no Asterxa key configured. Agent roles fall back to the deterministic local analysers, so this analysis is a demonstration and not a live AI result.

  3. Instagram: evidence assembly (PECA 2016 s.38)Livepass

    A PECA 2016 s.38 evidence package was assembled (account ID, URL, TLD, IPs, statutory provision, factual basis) and sealed with a SHA-256 content hash on the custody record.

    • Evidence: 037eb73a-ed2e-41d1-ab27-06ee978c2174
    • Content hash: 82b41a076cfa039424339b20…
    • Case: a17f6436-af0f-414e-84b0-633d88671e86
  4. Instagram: case opened and progressedLivepass

    Case ASI-IN-0012 was opened and progressed New → Analysing → Evidence Ready → Awaiting Review, ready for a reviewer at the gate.

    • Case: ASI-IN-0012
    • Status: Awaiting review
  5. Instagram: reviewer approval at the lawful-ground gateHuman gatepass

    Approved by Test Reviewer acting as reviewer against PECA s.37(1) — commission of, or incitement to, an offence under PECA. This is a human decision recorded at the gate; no agent performed it and no agent may.

    • Approval: 144dbde6-7f42-4574-a801-1c38a9eb5f4f
    • Ground: PECA s.37(1) — commission of, or incitement to, an offence under PECA
  6. Instagram: supported enforcement requestManuallimited

    Three enforcement tracks were assessed separately. In-country restriction: prepared and referred to PTA as a tracked request (PTA complaint — Removal and Blocking of Unlawful Online Content (Procedure, Oversight and Safeguards) Rules 2021). Platform removal: no programmatic API exists — it resolves to a tracked manual escalation. Account action: not a power of this application. No verified integration exists for "platform_removal" on instagram. A tracked manual escalation has been opened instead (In-product reporting channel (manual)). The application does not submit requests it cannot lawfully complete.

    • In-country request: 0ddc8a4a-c780-46b5-97ba-2f606eaf2a24
    • PTA escalation: c1375c59-c3ee-47e1-9df8-840019af4c90
    • Removal request: 50866222-f55c-48b3-9c9c-877e96d0d65e
    • Manual escalation: 9145c1ad-ec3d-45c0-a892-4b886f392427
    • Removal capability: unsupported
    • Account action: unsupported

    Dependency — In-country restriction is a PTA power the application prepares and tracks, never executes; platform removal and account action depend on the platform's own reporting channel. 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.

  7. Instagram: outcome verificationLivepass

    A terminal outcome was recorded and re-read from the case, confirming the recorded state.

    • Outcome: 24b404dd-05e1-4791-b738-3d78c966287e
    • Terminal state: inconclusive

Demonstrates the connector and the workflow scoped by authorised access — never complete platform coverage.

Instagram — mandatory content types

  • Post
    Own professional-account media is live; public content only via the Content Library cleanroom.
    Depends on: Meta Content Library institutional access (L3): requires a qualified academic or non-profit research institution as lead applicant; read-only cleanroom with no raw-data export.
    requires access
  • Caption
    Captions on own media are live; captions on public media only via the cleanroom.
    Depends on: Meta Content Library institutional access (L3): requires a qualified academic or non-profit research institution as lead applicant; read-only cleanroom with no raw-data export.
    requires access
  • Reel
    Own Reels are readable on demand, but Meta fires no Reels comment webhook; public Reels are only reachable via L3.
    Depends on: No Reels comment webhook (platform limitation).
    limited
  • Comment
    Hide/delete is live for comments on your OWN media; comments on other accounts' media cannot be read at all.
    Depends on: Comment access is restricted to media you own.
    limited
  • Hashtag
    30 unique hashtags per rolling 7 days, a 24-hour recent window, and no usernames returned.
    Depends on: Requires Instagram Public Content Access feature approval.
    limited
  • Account profile
    Authorised Business/Creator accounts: profile, media, Reels and Stories.
    Depends on: Requires Meta App Review and a Business/Creator account.
    live

1 of 6 mandatory content types are live today; 3 are limited; 2 require access. This counts content types, never share of content.