This page preserves why the public site changed, when material changes entered the repository, and which commit supports each entry. It is a selected architecture record—not a claim about traffic, ranking, deployment, or business performance.
Entries are selected from the Git history when they materially change public information architecture, language access, responsive use, editorial governance, measurement, or a reader-facing tool. Each abbreviated commit ID identifies the repository evidence without exposing a private repository link.
The repository records the initial application scaffold and style guide, followed on the same day by the home page, navigation, the Insights pipeline, company pages, SEO groundwork, and formal Korean routes.
2ea11b2Scaffold + design system6a23e14Formal /ko/ launchThe CBRN-AI board, scheduled publishing route, and syndication work established the first repeatable editorial pipeline. This entry records the software change only; it does not assert reach or publishing performance.
4939d33OSMU board + publishing workflowThe design tokens added fluid typography, Korean line-height handling, iOS safe-area treatment, and 44-pixel interaction targets as repository-level responsive defaults.
d3eb28fResponsive typography + safe areaThe repository adds the GA4 measurement code. A code connection is not presented here as evidence of traffic quality, audience growth, or commercial results.
2388925GA4 measurement codeEnglish and Korean Build, Publications, Developers, and Trust sections were introduced, followed by canonical-host alignment and a publication catalogue populated from recorded book data.
2408373EN/KO renewal sections4c8c03aCanonical host alignmentb585d0fRecorded book catalogueThe repository records a new home-page journey, a five-item navigation model, an Open Studio entry point, a product ecosystem surface, and a civil-first public framing with a slimmer footer.
eaba0deHome + navigation renewal02ceee6Civil-first identity55e6e75Footer information architectureThe site adds an editorial hub intended to support advertising-review readiness, then adds analytics and measurement controls. The commits document implementation intent, not advertising approval or revenue.
6d8beb9Editorial hub2bcbb08Analytics controlsThe repository records public QA tools, an evidence-workflow companion, renewed trust architecture and navigation, a reviewed publishing board, and a first batch of reviewed columns.
a78b26fSprayOps QA toolkit6eecdcfMission Companion workflow89379aaTrust architecture + navigation03da13eReviewed Insights batchThirty Korean Insight translations, a drone-retirement decision service, Korean drone tools, and search/analytics funnel connections appear in the repository as separate reviewable changes.
3fdc428Korean Insight translations082525eDrone-retirement decision service4a48c68Korean drone tools5795d5cSearch + GA4 funnelsThe current evidence snapshot records repaired bilingual navigation, an Open Studio source and release-note surface, five English/Korean UAV thesis article pairs with bounded evidence graphics, and responsive publication-catalogue and site-history surfaces.
4d527acBilingual navigation repair70608aeOpen Studio source + release notes2ecc5eeBilingual UAV thesis series1d4b395Bookshelf + responsive site historyThe record is intentionally narrower than a release log. These rules keep a redesign rationale useful without turning implementation metadata into unsupported outcome claims.
A milestone needs a dated commit that identifies the material change. Current route and component code may clarify scope, but memory or promotional copy is not treated as proof.
Navigation, localization, responsive access, trust controls, publishing systems, measurement connections, and public tools qualify. Routine content and maintenance commits normally do not.
A connected analytics tag does not prove traffic; an advertising-readiness change does not prove approval or revenue; a Git commit alone does not prove a production deployment.
If an entry is incomplete or wrong, update it with a dated corrective commit and retain the evidence trail. Do not silently replace a historical claim with a stronger one.