Monsoon LedgerIndonesia AI governance

Analysis

Analysis

Longer written work behind the ledger. Each paper cites its sources by number, states the day its facts were checked, and logs every change after publication.

Papers

  1. Analysis 01

    Nobody to Call

    Frontier AI incidents now land on other countries' systems. Indonesia shows what happens when the receiving end is missing.

    When frontier AI agents act on systems in other countries, the notice has to land somewhere; this paper documents the 2026 incidents, the reporting rules, and Indonesia's missing receiving end.

    Published · facts as of 26 October 2026 · 25 minute read

  2. Analysis 02 · Planned

    Incident reporting: a literature map

    Planned. No date set.

Open questions

These are questions, not findings. The papers raise them and do not answer them. Evidence that bears on any of them is welcome.

  1. When an AI agent built abroad acts on an Indonesian system, which body should receive the notice: the national cyber agency (BSSN), the digital ministry, or the data protection institution?
  2. Can a ministerial announcement alone set up a working AI incident intake point, or does it need a presidential regulation behind it?
  3. Will the signed AI ethics regulation name who receives incident reports, and will it cover general-purpose models?
  4. How can a rule that asks for every incident to be reported sort the reports, so that a small team is not buried in noise?
  5. What notice window would a cross-border notification norm for frontier developers need to be useful to the affected country?
  6. Will the data protection institution exist before sanctions under Government Regulation 33/2026 begin on 16 January 2027?
  7. How will the Constitutional Court decide case 236/PUU-XXIV/2026, and what would its ruling change for the institution?
  8. Should misaligned agent activity that causes neither a security breach nor serious harm count as a reportable incident, and under which category?

Corrections and review

Papers are published as versions. When a fact is wrong, the paper is corrected, the change is listed on the paper and in the changelog with its date, and the version number goes up. Review from people who know these laws, systems or incidents is welcome through the repository.

Report a correction · All corrections