Roadmap 0.11, Super 0.1 booklet (Duncan) · level of development
BK.18 Content rules for libraries, templates and packs: LOD means the same everywhere
[GREAT EIGHT · FROM SUPER 0.1 BOOKLET · BK · moved 2026-11-10] Lives in bim; Super gets it by hosting the app.
Content rules for libraries, templates and packs: LOD means the same everywhere.
BUILT 2026-11-11 (bk-r3-library-10). Every item can state its LOD (100-500) and a classification code; a licence is required on every item, always; the format check (LibraryItemFormat and its JS twin) refuses with a plain reason. The Public Add-on Uploader checker applies the content rules to any item file in a package, checks CHANGELOG.md and warns on 1.0.0 without the owner's adoption (BK.153). The Library submission form has LOD and classification fields.
Tests: bin/test-library-content 138/0 (incl. the PHP / JS same-words check), test-addon-uploader 91/0. In /lab (a Discord member) only, not released. Not hand-tried by a person; English only; not run inside SuperCad Studio. The Library itself enforces LOD and code only when .env LIBRARY_CONTENT_RULES=1 (off: the 321 existing items carry neither and their re-upload would be refused); LIBRARY_IFC_REQUIRED from the last round is off for the same reason.
closing 2026-11-16: Built → Partly built. LIBRARY_CONTENT_RULES is off and checkContent runs only on type packs read from a file, not on Library items or templates.
Community comments
No comments yet
Add detail as we go: how you would use it, files or steps that show the problem, what other programs do. The team reads every comment.
Sign in or create a free account to add a comment.