Scope Cap dope chart

The automatic heuristics are currently:

• The archive must be parseable by the Index (usually by being a ZIP or being on a platform that already exposes the filetree).
• The archive must contain at least one documentation-type file: .md .pdf .txt
• The archive must contain at least one printable mesh file: .3mf .amf .obj .stl
• The archive must contain at least one source file: .f3d .fcstd .iges .igs .scad .sldasm .sldprt .step .stp
• The archive must not contain rendered GCODE: .cnc .gco .gcode .nc .tap
• The release must not be in beta.
• The release must not be obviously heavily disliked on its platform of origin.

Visual documentation and license metadata are positive signals, but they are not hard blockers for the automatic check.

These use RFC-2119 keywords.

• It MUST NOT be marked as beta.
• It MUST NOT contain GCODE.
• It MUST be documented. Requirements for documentation:
  • It MUST be included in the archive. It MUST NOT be only available via platform description.
  • It MUST be accurate. Text and graphics MUST NOT refer to features that were removed prior to release. Graphics MAY include said features so long as they do not pertain to the assembly being demonstrated and are not distracting.
  • It MUST be comprehensive. Auxiliary resources SHOULD NOT be required to complete the build by a reasonable, median builder. Remixes MAY link to their upstream release in lieu of this requirement.
  • It SHOULD contain useful graphics, especially of complicated/dense assemblies.
  • It SHOULD contain a comprehensive list of authors.
  • It SHOULD contain a valid license for the files in the bundle.
  • It SHOULD contain parametric redistributables, such as STEP files, either in the bundle or available via link.
• It MUST be available in an unencrypted archive in a format modern computers can extract. It SHOULD be a common open-source file format (zip, 7z, tar.gz, etc.). It MUST NOT be only a model file. It MUST NOT be password-protected, even if that password is available via its platform of origin.
• It SHOULD be sanitized/scrubbed to remove PII with reasonable available tooling

If you have a release you would like to submit for verification, please reach out to the site administrator. Channels who continuously maintain a verifiable level of quality may be candidates for automatic green-tier verification.

To get this seal, a release must be:

• Already a candidate for green-tier verification.
• Culturally significant.
• Of outstanding quality.