Language metric atlas

Published snapshot: 2026-09-11 (KST).

Open the language metric atlas.

The atlas maps existing language-development obligations, concepts, metric identifiers, symbolic definitions and Gooo activity declarations. Games and other consumer projects are downstream use cases, not a replacement language-completion denominator.

Source boundary

The catalog is pinned to core source commit ab91e6ec8ae7d587acbfc3d041f6edacefc02f05. It is a source snapshot, not a live report of the latest dev or main conformance.

The committed page was adopted from source-export run 34499603540. Site PR #7 merged at 9f259e72955cd9a44065f938e800ca26a503a94f; deployment run 34502700292 passed its check and deploy jobs.

What the counts mean

Exported item	Count	Boundary
Language-development concepts	29	Registered source concepts, not 29 completed features
Development obligations	24	Separate language, toolchain, meta and autonomy obligations
Assurance obligations	12	A different denominator; do not add it to readiness
Metric IDs and candidates	1,094	Includes literals and local helper identities; not all are active global metrics
Lexical Gooo activity declarations	378	Source declarations, not compiler-verified semantic bindings
Scanned source files	6,429	The export's selected file scope
Excluded files	102	Exclusions remain part of the catalog boundary
Concept narratives with Korean translations	29/29	Translation-entry presence, not translation accuracy or language completion
Source use cases with Korean translations	57/57	Includes historical expectations, not current successful executions

The supported-scope constructor analysis resolves 593 of 690 calls; 97 remain unresolved. There are 47 metric labels with untranslated or opaque tokens. These gaps remain visible instead of becoming fabricated definitions or passing states.

Reading the map

1. Start with an obligation or concept and its intended problem, effect and use cases.
2. Follow its registered metric IDs and source locations.
3. Inspect the symbolic constructor arguments, result fields and producer/helper references where available.
4. Keep original English narratives beside their Korean explanation when interpreting a historical expectation.
5. Require a matching source/contract/CI receipt before treating a declaration as an observed capability.

Search covers Korean explanations, identifiers and source paths. The embedded catalog can be downloaded. The UI also exposes assurance contracts and lexical activity declarations; a matching activity name alone is not a semantic binding proof.

States that must stay separate

• A registry stage is a source declaration.
• A fixture's expected outcome is a test expectation.
• A CI receipt is an observation with its own source and execution identity.
• External user utility needs user evidence; an internal pass does not establish it.
• A before/after improvement claim needs a defined, comparable observation pair.

Current language conformance is UNASSESSED in this atlas. Full metric/formula translation, complete semantic bindings and current CI-result ingestion are not closed by this publication. Website CI covers static structure and local links; it is not browser-interaction or accessibility validation.

This first publication makes the existing evidence landscape inspectable. It does not assert whole-language completeness or autonomous self-improvement completion.

실제 실행 증거를 함께 읽기

실제 CI 증거로 읽는 언어 지표는 문법의 고정 사례 60/60과 그래프 관찰 UNKNOWN을 서로 다른 코드 기준점으로 설명합니다. 소스 목록, 실행 증거, 전체 완성 여부를 합산하지 않습니다. 이 링크는 공개 지도에 최신 CI를 자동 연동했다는 뜻이 아닙니다.

수치와 증거를 읽는 법

언어 개발 지표와 증거를 읽는 법은 지표 정의·판정 원장·검증 사례의 단위를 구분하고, #772의 실제 병합 증거와 아직 후보인 변경을 연결한다. 서로 다른 소스 시점과 분모를 합쳐 언어 완성률로 표현하지 않는다.