Writing
Technical write-ups and analysis across Korean forensic finance, US export controls, and public-data tooling — how the work is done, what data it uses, and the decisions behind it.
Showing 11–15 of 17 articles
Splitting a Forensic-Finance Monolith into Four Repos: Why and How What started as one repo grew into a coupled mess of ETL, scoring, and statistical validation. The split into four targeted libraries — kr-forensic-core, kr-dart-pipeline, kr-anomaly-scoring, kr-stat-tests — was about being honest with the dependency graph. Read article Sixteen Years of Forensic Accounting Research, in One JSON File The Journal of Forensic & Investigative Accounting has published 469 articles since 2009. None of them are indexed in a way a researcher can search programmatically. Until now. Read article Detectlets: Compiling Forensic Accounting Research Into Computable Detection Modules A 'detectlet' is what an academic paper turns into when you extract its detection rule and make it runnable. This library defines the schema, ships four reference implementations grounded in JFIA literature, and makes the question 'which papers does this rule come from?' answerable in one query. Read article 240 Korean Accounting Violations, Coded Once So Researchers Don't Have to Code Them Again The Financial Supervisory Service and Securities & Futures Commission publish enforcement decisions in PDFs and HWP files. The text is in Korean. The structure varies by source. This dataset codes them — 240 violations across two regulators, with a bias-validated taxonomy and DART-linked Beneish ratios for the named cases. Read article 60 Calendar Days Is 38 Trading Days. The 37% Error Hiding in Korean Market Code. Korean exchanges observe roughly fifteen non-weekend holidays a year. Naively shifting a date by N calendar days to build a price window silently drops a third of the sessions you thought you had. This library is the three functions that fix it. Read article