.. calyntro documentation master file, created by sphinx-quickstart on Sat Dec 20 19:01:57 2025. You can adapt this file completely to your liking, but it should at least contain the root `toctree` directive. Welcome to Calyntro's documentation! ===================================== **Calyntro** is a repository intelligence platform that derives structural and behavioural insights from Git history — without instrumentation, build integration, or access to runtime data. It is built around four operational questions that matter at the architecture and engineering-management level: * **Where are the risks?** The :ref:`Code Map ` and :ref:`Scatter Analysis ` make structural risk visible across the entire module landscape in a single view — surfacing which components are simultaneously complex, actively changing, and poorly understood. * **How are trends developing?** The :ref:`Trend Analysis ` tracks Cognitive Complexity, Lines of Code, Silo Ratio, and commit activity per module over configurable time windows — turning point-in-time snapshots into directional signals. * **What needs attention now?** The :ref:`Dashboard Warnings ` panel surfaces the top prioritised risks (hotspots, knowledge silos, complexity spikes, churn outliers, reactivated legacy code) with normalised scores and direct navigation to the relevant analysis view. * **Who holds critical knowledge?** The :ref:`Knowledge Risk ` screen breaks down Bus Factor exposure to the developer and file level — showing which modules depend on a single person, which files carry the highest weighted risk, and how knowledge concentration has evolved over time. Calyntro derives all metrics exclusively from commit history: author dates, changed lines, file paths, and commit hashes. No static analysis agents, no test runners, no issue tracker connections are required. A repository import takes minutes; the analysis runs on an embedded DuckDB instance with no external database dependencies. The platform is designed for **Software Architects** who need to identify refactoring priorities, **Engineering Managers** who need to assess team knowledge distribution and Bus Factor risk, and **CTOs** who need a continuous, objective signal on codebase health without relying on self-reporting. Check out the :doc:`usage` section for further information, including how to :ref:`install ` the project. .. note:: This project is under active development .. toctree:: :maxdepth: 2 :caption: Contents: installation importer_guide usage dashboard_overview knowledge_risk api analysis License ======= Calyntro is released under the terms specified in the LICENSE file. .. include:: ../../LICENSE :literal: