Coming soon ChenAIle — agentic microservices: agents, AI tool calls, machine learning and a metrics-driven rules engine Learn more →
Code, tests & documentation

Chenile by the numbers

How much code, tests and documentation make up the 11 Chenile repositories — measured from the source, not estimated.

Measured October 25, 2026 from the working copies of the 11 repositories, including the in-progress 2.1.31 work.

35238
Lines of production Java
812 source files
23137
Lines of test Java
66 test lines per 100 production lines
76
Maven modules
across 11 repositories, one release train
105392
Words of documentation
site articles + repository guides

Code, repository by repository

Lines are non-blank, non-comment Java lines; Javadoc is counted separately. Tests are everything under src/test. Front-end lines cover the React consoles (Admin UI, process dashboard, PlantUML viewer).

RepositoryModulesJava filesProduction linesTest linesJavadoc linesGherkin featuresFront-end linesCommits
chenile-parent1000000110
chenile-core12488130137326273641693160
chenile-query-workflow-blueprints132115936378475191379129
chenile-process-management1318753494576361872295
chenile-service-registry4311130721422055
chenile-proxies2346585281040051
chenile-security1177286219071320059
chenile-messaging8113273623474490071
chenile-bdd3115610880047
chenile-others571202013261651045
cconfig4359736221602051
All 11 repositories76125835238231374988263794873

Alongside the Java there are 369 configuration and schema files (XML, JSON, YAML, properties, SQL — state machines, query metadata, process definitions, migrations) and 2284 lines of Gherkin across 26 feature files.

Where the weight sits
chenile-core — the exchange, the interception pipeline, HTTP binding, the state machine and workflow runtime, Owiz, MCP and the Admin UI — holds roughly two-fifths of the production code. The application blueprints (chenile-query-workflow-blueprints, chenile-process-management) are next; the integration repositories (security, messaging, registry, proxies) are deliberately small, because they plug into the same pipeline rather than re-implementing it. chenile-parent is a build baseline with no Java.

Tooling outside the release train

chenile-gen (JGen) adds 3775 production and 1761 test Java lines in 34 Maven modules, plus 391 Mustache templates that make up its 12 built-in blueprints — see the blueprint reference.

Documentation

SourcePages / filesWords
chenile.org — Concept articles1611542
chenile.org — Developer guides2218132
chenile.org — Release notes76421
chenile.org — Video episode pages134625
chenile.org — Other site pages52317
Repository guides & READMEs (Markdown in the 11 repos)7462355
Total written documentation137105392

On top of the prose:

  • 4988 lines of Javadoc in the source, published as API reference.
  • 791 automated framework tests (plus 22 in JGen) passing for the 2.1.31 release, with zero failures — see the release process.
  • 26 executable Gherkin specifications — documentation that is also a test (see BDD).
  • The video series — 12 narrated episodes, about 21 minutes in total, with captions and full scripts on each episode page.
  • Interactive explainers on the concept pages, and generated workflow diagrams from every state machine.

How these numbers are produced

The figures come from scripts/codebase-stats.py in this site’s repository, which walks the 11 repository checkouts and writes _data/codebase.yml; this page renders that file. Build output (target, dist, node_modules), shared site styling and IDE folders are ignored. To refresh after a release:

cd cheniledocs.github.io
python3 scripts/codebase-stats.py ..     # path to the folder holding the 11 repos