{"note":"FIT is survey clarity — how clearly a language leads to a complete architecture survey. It is NOT a measure of language or code quality.","languages":[{"code":"csharp","displayName":"C#","applicability":10,"supportKind":"Deep","band":"FULL","bandLabel":"FULL","bandCss":"exemplary","summary":"CCA reads C# with the C# compiler's own tools, so it understands the code the way the compiler does. Every design grade and every code-level check is read in full.","coveredLenses":["DDD","Event sourcing","Event-driven","Vertical slice","Correctness","Structural"],"notApplicableLenses":[],"signedOffOn":null},{"code":"fsharp","displayName":"F#","applicability":9,"supportKind":"Deep","band":"VERY HIGH","bandLabel":"VERY HIGH","bandCss":"exemplary","summary":"CCA reads F# with the F# compiler's own tools. F# code often describes what happens in a business as a set of event types, and builds its current state by replaying those events. CCA reads that style directly, so Domain Modelling and Event Sourcing are read in full.","coveredLenses":["DDD","Event sourcing","Event-driven","Vertical slice","Structural"],"notApplicableLenses":["Syntax-level correctness","DI segregation","god-class/LCOM"],"signedOffOn":"2026-07-12"},{"code":"java","displayName":"Java","applicability":9,"supportKind":"Deep","band":"VERY HIGH","bandLabel":"VERY HIGH","bandCss":"exemplary","summary":"CCA reads Java with a tool that works out the types in the code the way the Java compiler does, so the design is read in full. Several code-level trap checks read Java too, such as the check for errors that are caught and ignored.","coveredLenses":["DDD","Event sourcing","Event-driven","Vertical slice","Correctness","Structural"],"notApplicableLenses":["DI segregation","strongly-typed-id (field-based)"],"signedOffOn":"2026-07-12"},{"code":"kotlin","displayName":"Kotlin","applicability":9,"supportKind":"Deep","band":"VERY HIGH","bandLabel":"VERY HIGH","bandCss":"exemplary","summary":"CCA reads Kotlin with the Kotlin compiler's own tools, so the design is read in full, including the ways Kotlin code usually describes events and values. Several code-level trap checks read Kotlin too, such as the check for errors that are caught and ignored.","coveredLenses":["DDD","Event sourcing","Event-driven","Vertical slice","Correctness","Structural"],"notApplicableLenses":["DI segregation","god-class"],"signedOffOn":"2026-07-12"},{"code":"vbnet","displayName":"VB.NET","applicability":9,"supportKind":"Deep","band":"VERY HIGH","bandLabel":"VERY HIGH","bandCss":"exemplary","summary":"CCA reads VB.NET with the same compiler tools it uses for C#, so the design is read in full.","coveredLenses":["DDD","Event sourcing","Event-driven","Vertical slice","Structural"],"notApplicableLenses":["Syntax-level correctness","DI segregation"],"signedOffOn":"2026-07-11"},{"code":"dart","displayName":"Dart","applicability":8,"supportKind":"Deep","band":"HIGH","bandLabel":"HIGH","bandCss":"healthy","summary":"Dart code describes its data in detail, so CCA can tell business data apart from screens and database rows. Several code-level trap checks read Dart too, such as the check for errors that are caught and ignored.","coveredLenses":["DDD","Event sourcing","Event-driven","Vertical slice","Correctness","Structural"],"notApplicableLenses":["DI segregation","Compiled-output efficiency"],"signedOffOn":"2026-07-17"},{"code":"elixir","displayName":"Elixir","applicability":8,"supportKind":"Deep","band":"HIGH","bandLabel":"HIGH","bandCss":"healthy","summary":"Elixir code usually builds its current state by replaying events, and CCA reads that style directly for Domain Modelling and Event Sourcing.","coveredLenses":["DDD (functional)","Event sourcing","Event-driven","Vertical slice"],"notApplicableLenses":["Anemic/mutable-setter (immutable)","inheritance & DU lenses","Syntax-level correctness","DI"],"signedOffOn":"2026-07-13"},{"code":"php","displayName":"PHP","applicability":8,"supportKind":"Deep","band":"HIGH","bandLabel":"HIGH","bandCss":"healthy","summary":"Modern PHP code states the type of each value, so CCA can follow which part of the code calls which and read the design from it. Several code-level trap checks read PHP too, such as the check for errors that are caught and ignored.","coveredLenses":["DDD","Event sourcing","Event-driven","Vertical slice","Correctness","Structural"],"notApplicableLenses":["DI segregation","god-class/LCOM"],"signedOffOn":"2026-07-12"},{"code":"rust","displayName":"Rust","applicability":8,"supportKind":"Deep","band":"HIGH","bandLabel":"HIGH","bandCss":"healthy","summary":"Rust code states the type of each value and which parts of the code may change it, so CCA can tell business data apart from database rows, whichever of the common database libraries the code uses.","coveredLenses":["DDD","Event sourcing","Event-driven","Vertical slice","Structural"],"notApplicableLenses":["Syntax-level correctness","DI segregation","Compiled-output efficiency"],"signedOffOn":"2026-07-17"},{"code":"scala","displayName":"Scala","applicability":8,"supportKind":"Deep","band":"HIGH","bandLabel":"HIGH","bandCss":"healthy","summary":"Scala code describes its events, values and IDs in detail, so CCA can tell business data apart from database rows and messages, and reads Domain Modelling and Event Sourcing from it. Several code-level trap checks read Scala too, such as the check for errors that are caught and ignored.","coveredLenses":["DDD","Event sourcing","Event-driven","Vertical slice","Correctness","Structural"],"notApplicableLenses":["DI segregation","Compiled-output efficiency"],"signedOffOn":"2026-07-16"},{"code":"swift","displayName":"Swift","applicability":8,"supportKind":"Deep","band":"HIGH","bandLabel":"HIGH","bandCss":"healthy","summary":"Swift code states whether a value is copied or shared, and what each type promises to do, so CCA can tell business data apart from stored records, including data kept with Core Data, Realm or SwiftData. The check for errors that are caught and ignored reads Swift too.","coveredLenses":["DDD","Event sourcing","Event-driven","Vertical slice","Correctness","Structural"],"notApplicableLenses":["DI segregation","Compiled-output efficiency"],"signedOffOn":"2026-07-17"},{"code":"typescript","displayName":"TypeScript","applicability":8,"supportKind":"Deep","band":"HIGH","bandLabel":"HIGH","bandCss":"healthy","summary":"CCA reads TypeScript with the TypeScript compiler's own tools. It can tell an event apart from an error result even when both are written the same way in the same file, and it tells business data apart from database rows, whichever of the common database libraries the code uses.","coveredLenses":["DDD","Event sourcing","Event-driven","Vertical slice","Structural"],"notApplicableLenses":["Syntax-level correctness","DI segregation","Compiled-output efficiency"],"signedOffOn":"2026-07-18"},{"code":"erlang","displayName":"Erlang","applicability":7,"supportKind":"Deep","band":"HIGH","bandLabel":"HIGH","bandCss":"healthy","summary":"CCA reads Erlang with Erlang's own parser. It finds problems typical of Erlang systems, such as a message handler that blocks while it waits, a change that is saved and sent as a message without making sure both happen, and a query that also changes data. The check for errors that are caught and ignored reads Erlang too.","coveredLenses":["DDD (functional)","Event sourcing","Event-driven","Vertical slice","Correctness","Structural"],"notApplicableLenses":["Anemic/mutable-setter (immutable)","Inheritance & DU lenses","DI segregation"],"signedOffOn":"2026-07-16"},{"code":"go","displayName":"Go","applicability":7,"supportKind":"Deep","band":"HIGH","bandLabel":"HIGH","bandCss":"healthy","summary":"CCA reads Go with Go's own type checker, the same one Go uses when it builds your code. It reads how the packages depend on each other, how events are handled and replayed, and how business records refer to each other. Several code-level trap checks read Go too, such as the check for errors that are caught and ignored.","coveredLenses":["DDD (structural)","Event sourcing","Event-driven","Vertical slice","Correctness","Structural"],"notApplicableLenses":["Inheritance & annotation lenses","Sealed/DU carrier","DI segregation"],"signedOffOn":"2026-07-15"},{"code":"python","displayName":"Python","applicability":7,"supportKind":"Deep","band":"HIGH","bandLabel":"HIGH","bandCss":"healthy","summary":"CCA recognises Python's business data by how the code marks it, such as values, database records and events, whether or not the code states its types. Several code-level trap checks read Python too, such as the check for errors that are caught and ignored.","coveredLenses":["DDD","Event sourcing","Event-driven","Vertical slice","Correctness"],"notApplicableLenses":["Sealed/DU lens","DI","god-class/LCOM"],"signedOffOn":"2026-07-12"},{"code":"ruby","displayName":"Ruby","applicability":6,"supportKind":"Deep","band":"MEDIUM","bandLabel":"MEDIUM","bandCss":"fair","summary":"CCA recognises Ruby's business data and events by how the code marks them, and reads the event-replaying style Ruby code writes with blocks. Several code-level trap checks read Ruby too, such as the check for errors that are caught and ignored.","coveredLenses":["DDD","Event sourcing","Event-driven","Vertical slice","Correctness"],"notApplicableLenses":["DI","god-class/LCOM"],"signedOffOn":"2026-07-13"},{"code":"javascript","displayName":"JavaScript","applicability":4,"supportKind":"Structural","band":"LOW","bandLabel":"LOW","bandCss":"poor","summary":"CCA reads JavaScript with the TypeScript compiler's own tools. It reads how the modules depend on each other, how complex the code is, how its classes are shaped and which code changes which data.","coveredLenses":["Structural","Module graph","Dependency hygiene","Complexity"],"notApplicableLenses":["Deterministic DDD/Event-sourcing model-shape lenses (advisory only — untyped)"],"signedOffOn":"2026-07-18"}],"bands":[{"band":"FULL","label":"FULL","cssKey":"exemplary","why":"Every applicable lens resolves and nothing is deferred — the assay can look through its DDD, event-sourcing, event-driven and vertical-slice lenses and report with the fullest confidence it offers. This is about survey clarity, not language quality."},{"band":"VERY HIGH","label":"VERY HIGH","cssKey":"exemplary","why":"Nearly every lens applies and resolves — a very clear survey. A named lens or two is deferred for this language, and its support statement says which. This is about survey clarity, not language quality."},{"band":"HIGH","label":"HIGH","cssKey":"healthy","why":"Most lenses apply and resolve — a clear, well-populated survey. A few lenses may be N/A for the language or resolve on a best-effort basis, but the architecture picture is strong. This is about survey clarity, not language quality."},{"band":"MEDIUM","label":"MEDIUM","cssKey":"fair","why":"A meaningful slice of the survey is populated. Some lenses are N/A for the language, or depend on type facts the language doesn't declare, so the assay reports what it can see and declines to guess the rest. This is about survey clarity, not language quality."},{"band":"LOW","label":"LOW","cssKey":"poor","why":"The survey is intentionally thin: the language exposes the structural lenses but not the deep domain-lens catalogue. What we report is real; there is simply less of it. This is about survey clarity, not language quality."}]}