[drk-ram]

Summary

Fixes #58 (goals A and the "registry JSONPath / checklist location match emitted JSON" acceptance criteria). The optional per-field provenance view (B) is not included.

UI terminology (result.html, Human-Friendly View)

Before	After	Source
Type	Component type (CycloneDX)	components[0].type
Architecture	Model family (HF model_type)	modelCard.modelParameters.modelArchitecture
(not shown)	Model implementation (HF architectures) (only when present)	architectures component property

For the Nanbeige4.1-3B example: machine-learning-model / llama / LlamaForCausalLM.

The emitted AIBOM is unchanged, so this is backward compatible: components[].type, modelArchitecture (from model_type) and the architectures component property keep their names and values.

Registry JSONPath vs. emitted JSON

Auditing every field_registry.json jsonpath against a generated BOM showed several paths using a singular $.component. root that does not exist in the output (primaryPurpose, suppliedBy, intendedUse, ethicalConsiderations, technicalLimitations, datasets), plus paper pointing at $.metadata.component.externalReferences. Same class of bug as #76. Effects on main:

• primaryPurpose, suppliedBy (both critical) and intendedUse were scored missing even when present, because the fallback checker does not know those names
• the Field Checklist showed a location (e.g. component.modelCard...) that does not match the JSON

All paths now use $.components[0]... (the ethicalConsiderations leaf is name, the key actually emitted). Scoring note: BOMs that emit those three fields will now correctly gain their points.

The two externalReferences location edits and the paper path are identical to those in #120, so the PRs merge cleanly in either order.

Small cleanup

model_type / architectures component properties are no longer emitted with a "None" or empty value when config.json lacks them (the UI row is skipped in that case).

Not changed / follow-up

modelArchitecture still falls back to <name>Model when model_type is unknown; changing that affects scoring and is left for a separate discussion. Mapping architectures[] into a CycloneDX field (e.g. architectureFamily) is also left out to keep the output stable.

Tests

tests/test_model_type_semantics.py (new):

• no registry jsonpath/location uses the singular $.component. root
• registry jsonpath resolves against a generated BOM for every emitted field
• those fields are checked off in the Field Checklist, and the checklist path matches the emitted JSON location
• emitted type / modelArchitecture / architectures stay distinct and backward compatible
• rendered result page shows the new labels, the implementation row only when present, and not the old labels
• no placeholder properties for empty model_type / architectures

The registry and UI tests fail against the previous src/.

Validation

• pytest --no-cov (Python 3.11): 191 passed