One source, every page
Where the catalog and engine numbers come from
The object count, the successor count, the A–D distribution, the engine and rule version — wherever this site states one of them in public, it reads from this same data. If a page ever shows a different number for one of these, that page is wrong, not this one.
Clean-Core.io as of v3.0.x
As of v3.0.19 (released 2026-10-21), Clean-Core.io is a free, independent web workspace for deciding what happens to one custom ABAP program. A deterministic engine reads the code before any language model does and reconstructs the business process as BPMN, with a line anchor on every element or the reason it has none, including the business rules hard-coded in the program. Each SAP object the code uses gets a Level A–D under a versioned rule, read from SAP’s published Cloudification Repository and object classification, or Unknown where neither holds an answer. On that evidence the Management view asks for one decision — keep, rebuild, move to SAP standard or retire — and Design, Transformation and Testing carry the same evidence to a target design, a code draft and test scenarios, each marked as a Model proposal for a person to review. Every completed analysis is stored as an immutable run signed by the server with HMAC; the audit pack exported from it is signed with HMAC and Ed25519, and its Ed25519 signature can be verified offline. What the engine could not determine is listed as not determined, not guessed.
What changed in Clean-Core.io 3.0?
Clean-Core.io 3.0, released 2026-10-03, gives every project one workspace, and the seven stages are no longer the product: they are tools inside it. A project opens on the business process reconstructed from its ABAP code as BPMN, shown in three views of the same facts — Business, IT and Management. A view orders what is shown; it changes no result and is never stored on a run or a signature. The Management view leads with the decision — keep, rebuild, move to SAP standard or retire. Also new in 3.0: a BPMN editor in which every save is an immutable revision and the reconstruction stays revision 1, with BPMN 2.0 XML files in and out and no connection to a Signavio workspace; documentation written from the engine’s reading of the code, no longer by a model reading only the start of it; and a demo project with a guided tour in every account. Sign-up and accounts did not change. The releases since then, up to v3.0.19 (2026-10-21), refine 3.0; the release notes are in CHANGELOG.md of the public repository, github.com/sonnyfrenzel-rgb/clean-core.io.
How the chain works, step by step, and where it stops: /how-it-works.
Level A–D distribution
A census of SAP's own published data — not of any customer's code. The rule that produces it, with its version and the two source files, is at /method/levels.
The two synced SAP files
Both the object count and the A–D rule are derived from these two files SAP publishes. Each carries the hash of the raw file as fetched and the date it was synced, so a reader can check that a figure has not drifted from what SAP actually served.
A–D rule version
levels 3c38976c5841 · latest@407843e4 · classifications-sap@70a9e6f4
The fingerprint (3c38976c5841) is a hash over the rule's own decision table — it moves when the rule moves, not on a schedule. Old runs stay stamped with the rule version that produced them.
Reference run
One reproducible run over 889 lines of legacy ABAP (ZLEGACY_ORDER_FULFILLMENT_AUDIT_1000LOC.abap): 40 findings, split 16 settled · 20 needing a decision · 4 handed back, Clean Core Score 40 (far from clean core, 5–59 in Clean-Core.io's bands). Full breakdown and the file to reproduce it: /reference-analysis.