5 October 2026
Syndical.api repository quality history
This page publishes historical engineering measurements for the Syndical.api source repository. It is not public API documentation and provides no callable service or interface for controlling the desktop application. The linked JSON files are downloadable measurement reports.
Verified clean main reached 100/100 quality and 100/100 maintainability. These scores measure compliance with the named profile.
| Measurement | Quality | Maintainability | Files checked | Native findings | Functions outside limits |
|---|---|---|---|---|---|
Initial complete baseline27ecd43025f4 | 55/100 | 94/100 | 9 | 6 | 7 |
Verified clean main8248a4a2d1dc | 100/100 | 100/100 | 16 | 0 | 0 |
What changed
Code repairs removed six native findings and seven function-limit violations. The operation refactor increased the source inventory from nine to sixteen files. Every selected file is still checked.
The policy hashes differ, so these scores are not an unchanged-policy comparison. The sole policy change independently classified the unchanged PublisherGrant and AttentionEvent declarations as factual wire data. Their executable bodies remain measured.
Limits of 15 complexity, 80 nonempty physical lines and five parameters, native checks, source roots and exclusions, the C# instrument, duplicate settings and all four security rules stayed the same. Each linked report retains its exact source, policy and evidence identity.
What the evidence supports
The final measurement contains 147 compliant functions and 59 compliant executable or reviewed data declarations, with zero detected duplicate tokens. All four configured C# security rules qualified against their fixtures and found zero production matches.
Separate verification passed 48 API tests before and after the refactor, including 14 new causal cases, 49 quality-tool tests and 59 C# instrument qualification cases. These results do not claim comprehensive security certification or superiority over human development.
Download the history and policy explanation