A correct manifest
imsmanifest.xml with the right namespaces, schema version, organization, and file list: generated, not hand-typed.
Strip away the acronym and a SCORM package is a zip file with a contract: an imsmanifest.xml at the root that tells the LMS what the course is called, which file to launch, and which files came along. Most "SCORM export" failures are contract failures: a manifest nested one folder deep, a namespace from the wrong spec version, a launch href pointing at a file the zip does not contain.
The builder exists to make those failures impossible. It writes the manifest against the version you choose: SCORM 1.2 with its adlcp_rootv1p2 namespace, or 2004 3rd Edition with adlcp_v1p3: lists every file you added, marks the launchable resource as a SCO, and zips it with the manifest at the root where the LMS looks first. The result imports and launches.
Launching is not the same as reporting, and the builder is honest about the difference. Completion and score reach the LMS only when the content itself calls the SCORM API from its JavaScript. A packaged slide deck or HTML page will open cleanly in any LMS and report nothing: which is fine for reference material, and not fine for compliance training.
When reporting is the point, package content that speaks SCORM. Mindstamp exports interactive videos as SCORM packages whose player does the API work: completion, score, and each learner’s answers land in the LMS gradebook without your content team writing a line of JavaScript.