A narrow, dated note on Japanese instruments relevant to AI-agent oversight. Japan's first AI statute is a promotion law without penalties; each entry names the instrument's exact status. A promotion statute, ministry guidelines and data-protection law are different things, and this note keeps them apart.
These pages describe the product and cite public instruments. They are not legal advice, not a certification, and not a statement that any instrument applies to your organisation. The official source is authoritative; applicability questions belong to your advisers.
Instruments, by status
| Instrument | Status | What it addresses |
|---|---|---|
| Act on the Promotion of Research and Development, and Utilization of AI-Related Technology (AI Promotion Act) | Binding statute, in full effect 1 September 2025, but a promotion law. Passed 28 May 2025, promulgated 4 June 2025. The Act itself creates no penalties and no prohibitions. Other Japanese law still applies in full. Article 7 calls on business operators to endeavor to develop and use AI-related technology appropriately, and to cooperate with national and local government measures promoting it. The government's published overview states the Act also covers foreign business operators whose AI activities target Japan. | National AI policy infrastructure: the AI Strategic Headquarters chaired by the Prime Minister, the AI Basic Plan, and authority for ministries to issue guidelines and request cooperation in incident inquiries. |
| AI Basic Plan · Cabinet Office | Cabinet-decided strategy, not binding on private parties. First plan adopted 23 December 2025; a new plan adopted 14 July 2026 superseded it. | Government objectives and coordination. Relevant as direction-of-travel, not as an obligation. |
| AI Utilization Guidelines (December 2025) and AI Guidelines for Business v1.2 (MIC / METI, March 2026) | Non-binding guidance. The Utilization Guidelines were issued in December 2025 under Article 13 of the Act; the Guidelines for Business consolidate earlier ministry guidance. | Voluntary expectations across the AI lifecycle: human involvement, transparency, risk management, and record-keeping practices. |
| Act on the Protection of Personal Information (APPI) · PPC | Binding law. | Personal data handling, including by AI systems. Using AAES does not discharge the business operator's duties; a vendor can itself be a personal-information-handling business operator depending on its role. |
What AAES records may contribute
| Expectation | AAES contribution | Capability status |
|---|---|---|
| Named accountability for AI use (AI Guidelines for Business; governance expectations under the Basic Plan) | Every registered agent has a named accountable manager, a configured association rather than a statutory appointment; approvals are attributable to a named person; agent identities cannot act as approvers through the supported AAES approval path. | Implemented. |
| Human involvement in consequential actions (AI Utilization Guidelines) | Actions the operator registers as irreversible (a registration classification, not an independent assessment of effects) require approval by an authorized person, bound to one intent and the exact payload, with expiry. An approval record does not by itself show the approver had adequate information, time or practical power to intervene. | Implemented. |
| Material for responding to incident inquiries (Act, Article 7; ministry information requests) | Sealed, hash-chained decision records with offline integrity verification by the client's own reviewer. | Implemented. An independently controlled witness can be configured separately; that is not an external assessment, and the default deployment has none. |
AAES decision records may support review of access and approval controls. They do not establish lawful processing, model fairness, suitability, or compliance with any instrument as a whole.
Within the configured trust model, integrity verification checks the exported records; it does not establish that every action was recorded, that an external action succeeded, or that recorded assertions are true. Approval records do not by themselves establish meaningful human oversight. Enforcement depends on control of the credential path, and actions bypassing AAES are not recorded.
Residual responsibility and explicit gaps
- The client remains the regulated entity. Whether the Act's cooperation duties or ministry guidelines reach your organisation is your adviser's question, not this page's.
- Work outside AAES is invisible to AAES. Records cover actions routed through AAES; they say nothing about actions on bypass paths.
- No independent certification or assessment of AAES exists. No SOC 2 report, no penetration test.
- Status changes. Ministry guidelines under the Act are still being issued; re-check the primary source before relying on the status shown here.
Bring the instruments your risk team cites to a scoped evaluation.
Related pages:
This note: https://aaes.ai/library/jurisdictions/japan.html
Hong Kong note: https://aaes.ai/library/jurisdictions/hong-kong.html
Singapore note: https://aaes.ai/library/jurisdictions/singapore.html
Trust model: https://aaes.ai/library/trust-model.html
Scope an evaluation: https://aaes.ai/contact.html?ref=library-evaluation