How Foreign Companies Can Monitor Japanese Legal Updates|A Practical Workflow
Tracking Japanese Legal Updates|A Practical Guide for Foreign Companies — Part 10 of 10 (Final)
This is the final part of the series. Across the previous nine parts we looked at the Official Gazette (官報), e-Gov Law Search (e-Gov法令検索), public comments (パブリック・コメント), the legal hierarchy, English translations, effective dates and transitional measures, and why information is spread across ministries. This part connects all of it into one thing a foreign company can actually use: a practical workflow to monitor Japanese legal updates and turn them into internal action.
The key idea is simple. Legal update monitoring is not a search task — it is a workflow. Finding that something changed is only the start. A working system also decides whether it matters, when you must act, who owns the response, and how you prove it was handled.
1. Legal Update Monitoring Is a Workflow, Not a Search Task
Foreign companies often struggle not because Japanese legal information is unavailable, but because official signals are not filtered, verified, translated, prioritized, assigned and tracked. A useful monitoring system answers four questions: What changed? Does it matter to us? When must we act? Who owns the response? The table breaks those into the concrete questions a monitoring process should produce an answer to.
| Question | Why it matters | Output |
|---|---|---|
| What changed? | You cannot act on something undefined. | A short description of the change. |
| Which source confirms it? | Headlines are not official. | The official source and URL. |
| Does it affect our business? | Not every change is relevant. | A relevance decision. |
| Which legal layer is involved? | Binding force and next steps differ by layer. | Act, order, ordinance, notice, guideline or Q&A. |
| What is the effective date? | The compliance deadline anchors to it. | The effective date (施行日). |
| Are there transitional measures? | Existing cases may be treated differently. | Grace, grandfathering or conversion rules. |
| Does HQ need an English summary? | Overseas decisions need English. | An English summary, where needed. |
| Who owns the action? | Without an owner it is only information. | A named action owner (対応責任者). |
| What evidence should be archived? | Auditability and follow-up. | Source, date checked and a snapshot. |
↔ Scroll the table sideways on mobile.
There is no single monitoring scope or frequency that suits every company. What to watch, how often, and how deeply to analyze depends on your business, licenses, products, services and risk profile. The workflow below is a structure to adapt — not a fixed checklist that applies identically to everyone.
2. The End-to-End Workflow for Monitoring Japanese Legal Updates
Here is the full workflow at a glance. Each step is explained in the sections that follow.
- 1Source map created
- 2Official sources monitored
- 3Signals collected and classified
- 4Relevance filtered
- 5Official source verified
- 6Legal layer identified
- 7Effective date and transitional measures checked
- 8Business impact assessed
- 9English summary prepared for HQ
- 10Action owner assigned
- 11Internal deadline tracked
- 12Evidence archived
- 13Source map reviewed periodically
3. Step 1: Build a Source Map
A source map (情報源マップ) is the foundation. As Part 9 explained, Japanese regulatory information is distributed across many authorities and document types, so the first step is to write down — by business impact, not only by source name — what you watch, where, how often and who owns it. Then review it periodically. One extension to consider: if your operations have a physical or local footprint (facilities, projects, stores), the map may also need to cover local ordinances (条例) and administrative guidelines (要綱) at the prefectural or municipal level — these are not consolidated in the national sources below.
| Source map field | What to record | Example / note |
|---|---|---|
| Business / compliance topic | The area being monitored. | Personal data; export control. |
| Relevant product, service, license or function | What inside the company it touches. | A specific license or product line. |
| Responsible ministry / agency | Who issues the rules. | Confirmed per topic on the official source. |
| Official source URL | The exact page or feed. | A specific official URL. |
| Source type | What kind of source it is. | Gazette, e-Gov, public comment, ministry page. |
| Update type expected | What tends to appear there. | Ordinance, notice, guideline, Q&A. |
| Review frequency | How often to check. | Weekly, monthly — set by risk. |
| Internal owner | Who watches it. | A named person or role. |
| Escalation trigger | When to alert HQ. | A draft affecting a core product. |
| English summary requirement | Whether HQ needs English. | Yes / No, and format. |
| Evidence / archive method | How proof is kept. | Saved snapshot and date. |
| Last reviewed date | When the entry was last checked. | Keeps the map from going stale. |
↔ Scroll the table sideways on mobile.
4. Step 2: Monitor Official Sources
The source map points at official sources. Each is good for something different, and none is sufficient alone — the recurring theme of this series. Use them together, and treat secondary sources as discovery aids, not as confirmation.
| Official source | What to monitor | What it is best for | What it does not solve alone |
|---|---|---|---|
| Official Gazette (官報) | Promulgated laws, orders and notices. | Confirming the official text and date (see Part 3). | No drafts, guidelines or interpretation. |
| e-Gov Law Search (e-Gov法令検索) | Current text and scheduled amendments, where available. | Reading current law in one place (see Part 4). | Not the authoritative Gazette; data update timing may differ. |
| e-Gov Public Comment (e-Govパブリック・コメント) | Draft rules open for comment, and results. | Early signals before rules are final (see Part 5). | Draft stage; not every change goes through it. |
| Ministry / agency websites (省庁・庁・委員会サイト) | Guidelines, Q&As, notices, press releases, materials. | Interpretation and practical handling. | Structure varies; not authoritative for the text itself. |
| Council / study group pages (審議会・検討会ページ) | Agendas, materials and reports. | Possible early signals of policy direction. | Not final law; may not lead to a rule. |
| Ministry guidelines / Q&As (ガイドライン・Q&A) | Interpretive guidance and practical answers. | The de facto standard in practice. | Not statutes; legal status varies (see Part 6). |
| Japanese Law Translation Database | English reference translations. | Understanding in English (see Part 7). | Reference only; not official; may lag. |
| Local government codes (自治体例規集) | Local ordinances (条例) and administrative guidelines (要綱) where you have a local footprint. | Catching stricter or additional local rules (上乗せ・横出し) that national sources do not show. | Not consolidated on e-Gov Law Search; fragmented across each prefecture’s and municipality’s own codes; map only the localities relevant to your operations. |
↔ Scroll the table sideways on mobile.
5. Step 3: Classify and Filter Signals
Signals are not all the same: some are final official sources, others are draft-stage or merely explanatory, and some are secondary. Classify every signal before acting on it, and never let a secondary source replace official verification.
| Signal type | What it may indicate | How to treat it |
|---|---|---|
| Official Gazette item | An official, promulgated change. | Treat as authoritative; confirm details. |
| e-Gov updated law text | Consolidated text changed. | Useful; confirm against the Gazette where it matters. |
| Public comment draft | A rule is being proposed. | Draft signal; not final. |
| Public comment result announcement | The rule or standard has been finalized or publicly released. | Final or released, but not necessarily yet effective; check the effective date and status. |
| Ministry guideline update | Interpretation/practice shifted. | Often important in practice; check status. |
| Q&A update | Practical handling clarified. | Watch closely; updates are quiet. |
| Public notice / notification (告示) | A designation or standard changed. | May have legal or practical effect depending on its basis; confirm in the Gazette / ministry site. |
| Council / study group material | Possible future direction. | Early signal; treat as a watch item. |
| Ministry press release | An announcement or summary. | Confirm specifics in official sources. |
| English translation update | An English version is posted. | Reference only; the Japanese text controls. |
| Industry association alert | A development worth checking. | Discovery aid; verify officially. |
| News article or secondary source | Something may have changed. | Discovery aid; never the final basis. |
↔ Scroll the table sideways on mobile.
Do not assume that every regulatory change will appear on e-Gov Public Comment. Under Article 39, Paragraph 4 of the Administrative Procedure Act (行政手続法), the procedure does not apply in certain cases — for example, urgent public-interest necessity, content that is determined by a superior law, or minor changes that do not alter the substance. A rule can therefore be promulgated or released without a prior public comment, which is one more reason Official Gazette and ministry-page monitoring remain the backstop (see Part 5).
You cannot deep-analyze every update, so apply a relevance filter, then a quick risk score to decide how much attention each item gets.
| Filter question | Why it matters | Possible answer |
|---|---|---|
| Does this affect our industry? | Sector scope. | Yes / No / Unsure. |
| Does this affect our products or services? | Direct offering impact. | Yes / No / Unsure. |
| Does this affect our licenses or permits? | Authorization impact. | Yes / No / Unsure. |
| Does this affect employment, data, finance, trade, energy, environment, consumer protection, advertising, reporting or disclosure? | Functional reach. | List the functions affected. |
| Does this affect existing contracts or transactions? | Legacy exposure. | Yes / No / Unsure. |
| Does this create a new filing, reporting, approval, system, labeling, disclosure, training or policy requirement? | New obligations. | List the new requirements. |
| Is the change final, draft or early signal? | Maturity of the signal. | Final / Draft / Early. |
| Is the deadline short? | Time pressure. | Yes / No / Unknown. |
| Does overseas HQ need to know? | Escalation. | Yes / No. |
↔ Scroll the table sideways on mobile.
| Scoring factor | Low | Medium | High |
|---|---|---|---|
| Business relevance | Peripheral | Related | Core business |
| Legal impact | Clarifying only | Some new obligations | Significant new duties |
| Operational impact | None | Some process change | Major system / process change |
| Deadline sensitivity | Distant / none | Several months | Short / near-term |
| Likelihood of finalization | Early idea | Draft published | Final / promulgated |
| Language difficulty | English available | Partly Japanese | Japanese-only, technical |
| Need for HQ approval | Local handling | Inform HQ | HQ decision required |
| Customer / regulator visibility | Internal | Some external | High external / regulator scrutiny |
↔ Scroll the table sideways on mobile.
6. Step 4: Verify Against Official Sources and Identify the Legal Layer
Do not act on a headline. Confirm the official source, record the date checked and the source URL, and use translations as reference only — confirming the Japanese original. The table maps where to verify a signal depending on where you first found it.
| If you found the signal in… | Confirm it in… | Why |
|---|---|---|
| News article | The official source for the rule (Gazette / e-Gov / ministry site) | Secondary; confirm the official text. |
| Industry association alert | The responsible authority’s official source | Useful tip; verify officially. |
| Ministry press release | Ministry materials; Gazette / e-Gov for any rule | Summary; confirm the specifics. |
| Public comment page | e-Gov Public Comment; later the Gazette for the final rule | Draft stage; confirm at finalization. |
| Gazette item | e-Gov Law Search for the consolidated text | Authoritative; cross-read the version. |
| e-Gov Law Search | The Official Gazette where final status matters | Convenient, but not authoritative. |
| Japanese Law Translation Database | The Japanese original | Reference only; Japanese text controls. |
| Machine translation result | The Japanese original; a qualified reviewer | Gist only; high misread risk on legal terms. |
| Internal memo | The cited official source | Confirm against the primary source and date. |
↔ Scroll the table sideways on mobile.
Once verified, identify the legal layer (see Part 6). Binding force and practical importance are different things: a non-statutory document may still require action, and a binding rule may still need subordinate rules or guidance before implementation is clear. Classification tells you what to check next.
| Layer | Why classification matters | Follow-up check |
|---|---|---|
| Act / Statute (法律) | The top statutory layer; sets the framework. | Check the orders and ordinances that implement it. |
| Cabinet Order (政令) | Implements the Act at government level. | Check its own effective date and related ordinances. |
| Ministerial / Cabinet Office Ordinance (府省令) | Operational detail. | Check notices and guidelines under it. |
| Public Notice / Notification (告示) | Specific designations or standards; may have legal or practical effect depending on its legal basis and content. | Check the Gazette and the ministry page. |
| Circular / Notice (通達・通知) | Internal instruction that shapes enforcement. | Read for how the authority applies the rule. |
| Guideline (ガイドライン) | Not a statute, but often the practical standard. | Confirm the responsible ministry’s current version. |
| Q&A / FAQ | Practical interpretation. | Watch for quiet updates. |
| Public comment draft (パブリックコメント案) | Draft stage. | Confirm at finalization. |
| Council / study group material | An early signal. | Treat as a watch item, not a rule. |
↔ Scroll the table sideways on mobile.
7. Step 5: Check Effective Dates, Transitional Measures, and Business Impact
Monitoring is not complete until effective dates and transitional measures are understood (see Part 8). The internal deadline should usually be set earlier than the legal effective date, and existing contracts, licenses, applications, products, systems and reports may each need separate analysis.
| Timing item | What to confirm | Why it matters |
|---|---|---|
| Promulgation date | When it was published in the Gazette. | Official, but not necessarily the effective date. |
| Effective date | When the rule applies (施行日). | The compliance anchor. |
| Effective date by provision | Whether parts apply on different dates. | Staged enforcement; track by provision. |
| Cabinet Order-designated date | The later order that fixes the date (施行期日政令). | Not fixed at promulgation; watch for it. |
| Transitional measures (経過措置) | How existing cases are treated. | Read the supplementary provisions (附則) first. |
| Grace period | A window to comply. | Diarize its end. |
| Grandfathering / existing-case treatment | Whether existing cases stay under old rules. | Confirm scope and duration; not always permanent. |
| Internal compliance deadline | Your own readiness date. | Set earlier than the legal effective date. |
| Owner and completion date | Who finishes it, and when. | Assign and track to completion. |
↔ Scroll the table sideways on mobile.
With timing clear, translate the change into business impact and assign it to the function that must act.
| Impact area | Question to ask | Possible internal owner |
|---|---|---|
| Products / services | Do our offerings need to change? | Product / business owner. |
| Contracts | Do templates or existing contracts change? | Legal. |
| Licenses / permits | Do we re-apply or convert? | Legal / regulatory affairs. |
| Filings / reports | Is there a new or changed filing? | Compliance / finance. |
| Data / privacy | Are there new data obligations? | Privacy / data protection lead. |
| Employment / HR | Do HR rules or processes change? | HR. |
| Finance / accounting | Do reporting or accounting rules change? | Finance. |
| Sales / advertising | Do labeling or advertising rules change? | Marketing / sales. |
| IT / systems | Are system changes needed? | IT / system owner. |
| Operations | Do operational processes change? | Operations. |
| Governance / board reporting | Does the board need to know? | Legal / corporate secretary. |
| Training / internal policy | Do policies or training need updating? | Compliance / HR. |
↔ Scroll the table sideways on mobile.
8. Step 6: Prepare an English Summary for HQ
For foreign companies, overseas headquarters usually needs an English summary to make decisions. An English summary should not pretend to be an official translation: it should state that the Japanese original controls, distinguish verified facts from interpretation and open questions, and include the next actions (see Part 7).
Two points often cause confusion overseas. First, in standard English translations of Japanese law, “Ordinance” usually means a national ministerial ordinance (府省令) issued by a central ministry — not a municipal ordinance (条例) passed by a local government, which is what “ordinance” suggests in some jurisdictions. Naming the issuing authority avoids the mix-up.
Second, when HQ asks whether a guideline is “binding,” a bare yes/no can mislead. Many Japanese guidelines and Q&As are not statutes, but they often function as the practical standard that regulators and counterparties expect companies to follow, depending on their legal basis and context (see Part 6). The summary should convey that practical weight rather than label the document “non-binding” and stop there.
| English summary item | What to include |
|---|---|
| Source checked | The official source and URL. |
| Date checked | When you verified it. |
| Japanese law / document title | The original Japanese title. |
| English working title | A working translation, marked as unofficial. |
| Status | Draft / final / guidance / explanatory. |
| Business relevance | Why it matters to the company. |
| Effective date | The effective date, or “to be fixed”. |
| Transitional measures | Grace, grandfathering or conversion notes. |
| Required action | What the company must do. |
| Internal owner | Who owns the response. |
| Confidence level | How certain the reading is. |
| Open questions | What still needs confirmation. |
| Japanese source controls disclaimer | A clear note that the Japanese original prevails. |
↔ Scroll the table sideways on mobile.
9. Step 7: Assign Owners, Deadlines, and Evidence
A change becomes compliance only when someone owns it, a deadline is tracked, and the evidence is kept. If no owner is assigned, the update is just information. Evidence supports auditability, and periodic review keeps the source map and tracker from going stale.
One practical caution: ministry guidelines and Q&As are sometimes revised without an announcement or a change log. A workflow that relies only on manual browsing can miss these quiet updates. Where the stakes justify it, consider page change-detection tools or scheduled snapshot comparisons for the exact URLs in your source map, so that unannounced revisions are caught — and the archived snapshots double as your evidence.
| Tracker field | Why it matters |
|---|---|
| Update ID | A stable reference for the item. |
| Source URL | Where it came from. |
| Date detected | When it was first seen. |
| Date checked | When it was verified. |
| Official source confirmed | Whether the primary source was confirmed. |
| Legal layer | Act, order, ordinance, notice, guideline or Q&A. |
| Status | Draft / final / guidance / explanatory. |
| Business impact | The assessed impact. |
| Effective date | The legal effective date. |
| Internal deadline | The internal readiness date. |
| Action owner | Who is responsible. |
| Action required | What must be done. |
| Completion status | Open / in progress / done. |
| Evidence archive | Where the proof is stored. |
| Review date | When to revisit it. |
↔ Scroll the table sideways on mobile.
10. Roles and Responsibilities
A workflow needs people. The split below is a starting point; adapt it to your structure and resources.
| Role | Main responsibility | Typical output |
|---|---|---|
| Japan legal / compliance team | Monitor Japanese sources; verify, classify and assess. | Verified signals; source map upkeep. |
| Overseas legal / compliance team | Set policy; receive English summaries; decide cross-border points. | Decisions and HQ guidance. |
| Business owner | Assess business impact; implement changes. | Impact assessment; completed actions. |
| HR / finance / IT / operations | Implement function-specific changes. | Functional actions. |
| External counsel | Advise on interpretation and edge cases. | Legal opinions where needed. |
| Management / board | Oversight; approve significant responses. | Decisions; governance record. |
| System owner / tracker owner | Maintain the tracker, calendar and archive. | An up-to-date tracker and evidence. |
↔ Scroll the table sideways on mobile.
11. Common Failures in Japanese Legal Update Monitoring
| Common failure | Why it happens | Better practice |
|---|---|---|
| Watching only English sources | Convenience and language. | Use Japanese official sources; treat English as reference. |
| Watching only e-Gov | It looks complete. | Add the Gazette, public comments and ministry pages. |
| Watching only Acts | Acts feel like “the law”. | Track orders, ordinances, notices, guidelines and Q&As. |
| Missing public comments | Draft stage feels premature. | Watch drafts as early signals. |
| Missing ministry guidance | It is not a statute. | Track guidelines and Q&As; they drive practice. |
| Missing effective dates | Focus stops at “what changed”. | Always confirm the effective date and transitions. |
| No internal owner | No process for assignment. | Assign an owner for every relevant item. |
| No evidence archive | Verification not recorded. | Save the source, date and a snapshot. |
| HQ receives only a vague summary | No summary standard. | Use a structured English summary format. |
| No periodic review of sources | The map is set and forgotten. | Review the source map on a cycle. |
| Treating all updates as equally important | No prioritization. | Filter for relevance and score by risk. |
↔ Scroll the table sideways on mobile.
12. Series Summary: From Official Sources to Internal Action
This series moved from understanding individual sources to building a complete workflow. Here is how the ten parts fit together.
| Part | Main lesson | How it fits into the workflow |
|---|---|---|
| 1 | Japanese updates are scattered and mostly in Japanese. | Explains why a structured system is needed. |
| 2 | Passage, promulgation and enforcement are distinct steps. | Tells you where in the pipeline a signal sits. |
| 3 | The Official Gazette is the authoritative publication (electronic since 2025). | Where to confirm final, official text and dates. |
| 4 | e-Gov is a convenient consolidated source, but not the authoritative Gazette; data update timing may differ. | For reading current and scheduled text, where available; verify elsewhere. |
| 5 | Public comments reveal draft rules before they are final. | An early signal; not the final rule. |
| 6 | Layers differ in binding force and where they appear. | Classify the signal to know what to check next. |
| 7 | English translations are reference only; the Japanese original controls. | For HQ understanding, not as the legal source. |
| 8 | The effective date (附則), not the headline, anchors compliance. | Turn a change into a dated internal deadline. |
| 9 | Information is distributed across ministries, layers and document types. | Build a source map across authorities. |
| 10 | Connect everything into one repeatable workflow. | Source map → monitor → verify → assess → assign → archive → review. |
↔ Scroll the table sideways on mobile.
13. Conclusion: Turn Japanese Legal Updates into Actionable Compliance Work
The goal of this series was never to find a single perfect source — there isn’t one. It was to build a repeatable way to monitor Japanese legal updates: a source map, official-source monitoring, signal classification, a relevance filter, official verification, legal-layer identification, effective-date tracking, business-impact assessment, an English summary for HQ, an assigned owner, a tracked deadline, archived evidence and periodic review. Each step is modest on its own; together they turn scattered official signals into compliance work that someone actually completes on time. That is the whole point — and it is where this series ends.
Need a practical way to monitor Japanese legal updates in English?
Monitoring Japanese legal updates means connecting the Official Gazette, e-Gov Law Search, public comments, ministry sites, guidelines, Q&As, English understanding, effective dates, internal deadlines and owners. Japan Legal Reform Watch by LegalOS helps organize legal and regulatory update signals from Japan’s official sources and supports a structured workflow for connecting official publication, e-Gov law text, public comments, ministry guidance, effective dates, English summaries and internal action tracking — so foreign companies, overseas legal departments and compliance teams can understand Japanese legal updates in English.
Track Japanese Legal Updates in EnglishSeries: Tracking Japanese Legal Updates
This guide is a 10-part series. The full list is below.
References
- Official Gazette / Kanpō (官報発行サイト) — https://www.kanpo.go.jp/
- Cabinet Office, “Digitalization of the Official Gazette” (官報の電子化について) — https://www.cao.go.jp/others/soumu/kanpo/about/kanpo_about.html
- e-Gov Law Search (e-Gov法令検索) — https://laws.e-gov.go.jp/
- e-Gov Public Comment (e-Govパブリック・コメント) — https://public-comment.e-gov.go.jp/
- e-Gov Public Comment — About the public comment system — https://public-comment.e-gov.go.jp/contents/about-public-comment
- e-Gov — Ministries and Agencies directory — https://www.e-gov.go.jp/government-directory/ministries-and-agencies.html
- Prime Minister’s Office / Japan — Links to Ministries and Other Organizations — https://japan.kantei.go.jp/link/org/index.html
- Japanese Law Translation Database (日本法令外国語訳データベース) — https://www.japaneselawtranslation.go.jp/en/
- Cabinet Legislation Bureau (内閣法制局), “The law-making process” — https://www.clb.go.jp/english/process/
日本語要約
本シリーズ最終回では、外国企業が日本の法令改正情報をモニタリングするための実務ワークフローを整理しました。法令改正モニタリングは単なる検索作業ではなく、公式情報源の確認・関連性判断・法令階層の分類・施行日/経過措置の確認・ビジネス影響分析・英語要約・担当者/期限/証跡の管理までを含む一連のプロセスです。「何が変わったか」を見つけるだけでは不十分で、「自社に関係するか」「いつまでに対応するか」「誰が責任を持つか」までを決めて初めてコンプライアンス業務になります。
実務上は、官報・e-Gov法令検索・e-Govパブリックコメント・各省庁サイト・審議会/検討会資料・ガイドライン/Q&A・日本法令外国語訳データベースを組み合わせて使う必要があります(いずれも単独では完結しません。e-Govは官報の正本ではなく更新タイミングに差が生じ得ます。また、行政手続法39条4項の適用除外により、パブリックコメントを経ずに公布・公表される規制もあります。英訳は参照用で、効力を持つのは日本語原文です)。さらに、事業拠点・プロジェクトのある地域では、国の法令データベース(e-Gov法令検索)には収録されない自治体の条例・要綱(上乗せ・横出し規制を含む)の確認が必要になる場合があり、該当する自治体の例規集を情報源マップに加えることを検討すべきです。また、すべての更新を同じ重さで扱うのではなく、事業影響・法的影響・期限・本社承認の要否・言語難易度などで優先順位付けを行います。監視対象や頻度は、各社の事業内容・許認可・商品・サービス・リスクプロファイルによって異なります。
海外本社向けの英語サマリーでは、日本語原文が優先する旨・確認日・情報源・施行日・経過措置・未解決論点・対応責任者を明記し、確定事実と解釈を区別します。その際、「ガイドライン=拘束力なし」と単純化せず、根拠・文脈によっては実務上の標準として機能し得るというコンテキストを補足することが、本社との認識ギャップ防止に有効です。また、ガイドラインやQ&Aは告知や更新履歴なしに改訂されることがあるため、重要なページについてはページ差分検知ツールやスナップショット比較の活用も検討に値します(保存したスナップショットは確認証跡を兼ねます)。最終的には、source map(情報源マップ)、update tracker(対応台帳)、effective-date calendar(施行日カレンダー)、evidence archive(確認証跡)を整備し、定期的に見直すことが重要です。こうした公式情報源・施行日・英語要約・社内アクションを一つの流れにつなぐことを支援するのが Japan Legal Reform Watch by LegalOS です。
