[DEMO] Instagram: authorised-account Reel and on-image text

AnalysinglowDemonstrationinstagramopened 29 Sep 2026 06:15 UTC

Synthetic demonstration case on Instagram. Runs against an authorised professional account, because comments on other accounts' media cannot be read through the API at all.

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)

Demonstrationinstagrampostlang: en
[DEMO CONTENT] Fictional Instagram caption with the extracted on-image text "JOIN US AT THE SQUARE". Synthetic image OCR demonstration.
https://www.instagram.com/p/DEMO0000001/ · author aetnic.demo.studio
Sandbox: this is an authorised-account demonstration, not public search.
- image_ocrSandboxconfidence 0.44
  Sandbox OCR: 1 text line recovered with positional timestamps.
  - 00:00–00:04JOIN US AT THE SQUARE
  Sandbox result: OCR produced without a live engine; character accuracy not measured.
Demonstrationinstagramreellang: en
[DEMO CONTENT] Fictional Reel caption. Demo note: Reels comment webhooks are not supported by Meta, so no real-time comment monitoring is possible here.
https://www.instagram.com/reel/DEMOREEL001/ · author aetnic.demo.studio
Sandbox: Reels comment webhooks are explicitly unsupported by Meta.

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

Evidence

0 evidence item(s)

No evidence assembled yet.

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

Agent assessment

1 agent run(s)

correlationSandboxsandbox27 ms
Correlation prepared; similarity only — no identity attribution produced.
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

No approval decision recorded yet.

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

Outcomes

Recorded results

No outcome recorded yet.

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

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

Workflow

Case transitions

Move to

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

Evidence

Assemble the PECA s.38 package

Source contentAccount IDContent URL

Statutory provisionFactual basisAt least 10 characters. Describe what the content does, not what it is about.

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

Agent roleOptional content overrideLeave blank to run against this case's linked content.

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.

DecisionLawful ground (PECA 2016 s.37(1))A lawful ground is mandatory. No other basis may be selected.

Exception consideredIs the sole stated basis a prohibited one?Religious identity or criticism of government alone can never justify enforcement.

Demonstrable content violationAt least 20 characters. State the violation, not the subject matter.

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 request

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.

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 Pakistan

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.

If submitting, name the verified integrationA submission is only recorded against an integration that actually exists.

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

Escalations

Tracked manual escalations

No escalations recorded for this case.

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

Terminal stateEvidence referenceWhich evidence item or export hash this outcome relates to.

Notes

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