majidbenk/interfaz-virtual-control-remoto-instrumentos-rigol

Capability surface

Classes this package can plausibly bind, derived from its catalogue role, interfaces and bounded static scan. A binding is not a claim that the capability is implemented or conformance-tested.

Interfaces detected

Languages

Integration plan

1. Read the family recipe. scpi-visa recipe shows the bridge, launch shape, unit handling and typical mapping for this family.
2. Pin the native entry point. Record module/class/function or process invocation; do not rely on undocumented internals. If you must, set stability: fragile.
3. Write the adapter manifest. Validate mhs-adapter.json against adapter.schema.json; declare units, safety, mode and fidelity gaps honestly.
4. Run the bridge and the suite. Start an endpoint, reach CL0, then run the conformance suite for the declared profile and level.
5. Publish evidence. Attach the report digest to a registry claim. Until then, the record stays contract checked.

Blockers

No catalog blocker recorded. That is not a guarantee that integration is easy.

Registry recipe path: families/scpi-visa.md · Profile target: MHS-Device · Effort: E1

Adapter mapping

No attested mhs-adapter.json is present in this build. The sketch below is generated from the registry fields to show the shape of the mapping; it is not a manifest, not validated, and must not be treated as one.

{
  "mhs_adapter": "1.0",
  "adapter_id": "registry.gh.majidbenk/interfaz-virtual-control-remoto-instrumentos-rigol",
  "family": "scpi-visa",
  "source": {
    "repo": "https://github.com/majidbenk/interfaz-virtual-control-remoto-instrumentos-rigol",
    "license": "NOASSERTION"
  },
  "runtime": {
    "kind": "python",
    "entry": "record the native module, class or launch command before promoting this adapter"
  },
  "devices": [
    {
      "device_id": "mhs://localhost/scpi-visa-interfaz-virtual-control-remoto-instrumentos-rigol",
      "mode": "hardware",
      "capabilities": [
        "cap.device.describe.v1"
      ]
    }
  ],
  "conformance_target": {
    "profile": "MHS-Device",
    "level": "CL0"
  },
  "evidence": {
    "state": "contract_checked",
    "source": "generated from registry record; not an attested manifest"
  }
}

Evidence and trust

No evidence note recorded.

Provenance references

No provenance references recorded.