EXTERNAL POLICY ASSESSMENT
SmolVLA base — external metadata assessment
A non-executing assessment showing why a base VLA checkpoint is not itself deployment-ready evidence.
Known Robot is the metadata assessor. LeRobot (Hugging Face) is the attributed upstream author or organization. Known Robot is not the policy author or evaluator.
- Upstream source
- lerobot/smolvla_base ↗
- Pinned revision
d9f33c94a60fb382c90dea2164c96845bd955e28↗- License
- Apache-2.0 · permissively licensed, not public domain
- Assessment method
metadata_only· validator 1.3.0- Assessment status
- incomplete · 13 missing requirements
- Assessed
Evidence boundary
The validator inspected the listed metadata files only. It did not download weights, import policy code, run inference, control hardware, execute simulation or verify model-card results.
Machine-readable assessment boundary
{
"method": "metadata_only",
"assessor": "Known Robot",
"validator_version": "1.3.0",
"assessed_at": "2026-09-24T15:40:00.000Z",
"executed_policy_code": false,
"evaluated_policy": false,
"established_compatibility": false,
"status": "incomplete"
}Generated portable manifest
This is the validator output, including nulls. The separately pinned Hub revision above establishes this assessment snapshot; it is not rewritten into the raw manifest as if the validator discovered it.
robot-skill manifest
{
"schema_version": "1.0",
"skill": {
"name": "Lerobot Smolvla Base",
"version": null,
"source": {
"type": "local",
"repository": null,
"revision": null
}
},
"policy": {
"framework": "lerobot",
"framework_version": null,
"architecture": "smolvla"
},
"hardware": {
"robot_family": null,
"gripper": null,
"sensors": []
},
"runtime": {
"control_frequency_hz": null,
"observation_shape": {
"observation.state": {
"type": "STATE",
"shape": [
6
]
},
"observation.images.camera1": {
"type": "VISUAL",
"shape": [
3,
256,
256
]
},
"observation.images.camera2": {
"type": "VISUAL",
"shape": [
3,
256,
256
]
},
"observation.images.camera3": {
"type": "VISUAL",
"shape": [
3,
256,
256
]
}
},
"action_shape": {
"action": {
"type": "ACTION",
"shape": [
6
]
}
},
"dependencies": []
},
"dataset": {
"repository": null,
"revision": null,
"schema": null
},
"compatibility": [],
"evaluations": []
}Missing-information report
Missing declarations remain visible. Model-card prose does not silently satisfy portable metadata fields.
skill.version— Artifact version is missing.skill.source.repository— Source repository is missing from inspected metadata.skill.source.revision— Immutable source revision is missing from inspected metadata.policy.framework_version— Framework version is not pinned.hardware.robot_family— Robot family is not declared.hardware.gripper— Gripper is not declared.hardware.sensors— Sensors are not declared.runtime.control_frequency_hz— Control frequency is not declared.runtime.dependencies— Runtime dependencies are not declared.dataset.repository— No task dataset is pinned for this base checkpoint.dataset.revision— Dataset revision is not pinned.dataset.schema— Dataset schema is not declared.dependency.unresolved— Resolved dependency evidence is missing.
Cautions
evaluations— No measured evaluation was found.compatibility— No compatibility evidence was found.
Upstream model-card claims
These are attributed summaries, not Known Robot measurements or endorsements.
- The model card describes SmolVLA as a base model intended to be fine-tuned for a specific use case. Inspect the pinned model card ↗
Inspected file inventory
Hashes make the metadata snapshot auditable without republishing upstream checkpoint weights.
File names, byte counts and SHA-256 digests
[
{
"path": "README.md",
"sha256": "a484071b8d7d0591452f795813fb54af9199fc1c48ef1ee995358d5ba07ee070",
"bytes": 4625
},
{
"path": "config.json",
"sha256": "650584b56c104720f7a3c91d1ec6bec9e8de8ac11e60c92ba2fa82d93eda147d",
"bytes": 2299
},
{
"path": "policy_preprocessor.json",
"sha256": "7683d648280a72f0d51e869fb8dd1596beed90b7f84849330cf1bc26634a4bd6",
"bytes": 1872
},
{
"path": "policy_postprocessor.json",
"sha256": "2b78bb742065288df2ec63b0ee35f97a1f6950171cf2272f7e34b1fe3873b17b",
"bytes": 660
}
]Limitations and next evidence
- Only repository metadata was inspected; weights were not downloaded and policy code was not executed.
- A base checkpoint is not a task-specific deployed policy and no target robot, task dataset or protocol is established here.
- The detected feature shapes do not establish semantic compatibility, safe control or task performance.
A future measured evaluation must be published as a separate evaluation record with an execution protocol, trials, outcomes and evidence. It will not overwrite or retroactively strengthen this assessment.