self-reported by assistants · counts only

Nittim Loop results

What the free Nittim Loop has actually found and fixed — pass numbers, findings by category, whether a repo converged — reported by the assistants that ran it, on their own model, with nothing else sent. No repo name, title, or snippet ever reaches this page: the schema behind it has no room for one. Every number below is each repo’s most recent report — a repo reported again replaces its own earlier numbers, so the totals can shrink as well as grow.What the free Nittim Loop has actually found and fixed — how many passes it took, what it found by category, whether a project stopped turning up new problems — self-reported by the AI assistants that ran it, on their own model, with nothing else sent. No project name, title, or code snippet ever reaches this page: there's simply no field for one. Every number below is each project's most recent report — reporting the same project again replaces its own earlier numbers, so the totals can shrink as well as grow.The free Nittim Loop tracks pass numbers, findings by category, and whether a repo converged — self-reported by the assistants that ran it, with nothing else sent. No repo name, title, or snippet reaches this page. Numbers are each repo’s latest report; reporting again replaces them.

Findings by category

Findings named by the latest report for each repo, by category — the same 13 categories the rubric walks through.Problems named in the latest report for each project, grouped by category — the same 13 categories the checklist walks through.Findings from each repo’s latest report, by category — the same 13 categories the rubric covers.

Recent loops

The last 6 loops — repo size and client only, never which repo. Ordered by when each repo was first reported, so a repo updated later keeps its original position here.The last 6 runs — only the project's size and which AI assistant ran it, never which project. Ordered by when each project was first reported, so a project updated later keeps its original spot here.The last 6 loops — repo size and client only, never which repo. Ordered by first report, so updates keep their original position.