Developer training

Adapters, Physical Effects, and Threat Response

Refuse an adapter token and a physical effect, then stop the actor by revocation.

Explanation

What you are learning

Recommended first: HIOP Fundamentals. You can still study this lesson.

No cloud account, robot, or spacecraft is connected to this workstation. The lesson still measures the boundary. A vendor token is not a Hood PERMIT. The reason is adapter is not a permit. Naming physical.move on an arm is not a teaching permit either. The outcome is DENY. A real lab.observe permit is then stopped by revoking the actor before Rain runs. Containment here is revocation, not a claim that a machine moved.

Worked example

Teaching workstation

These fields were returned by the teaching workstation for this lesson. They are not a production permit.

An adapter token is presented

Present a vendor token

outcome: DENY
dispatch: false
executed: false
reason: adapter_is_not_a_permit
resource: vendor-token

A physical effect is named

Ask for physical.move on an arm

outcome: DENY
dispatch: false
executed: false
reason: unknown_effect
effect: physical.move
actor id: operator
resource: arm
request id: phys-1

Revocation stops the teaching effect

Revoke the actor and present the unused nonce

outcome: DENY
dispatch: false
executed: false
reason: permit_invalidated
effect: lab.observe
actor id: operator
resource: scope-a
request id: phys-2

Exercise

Try it before you check

Three refusals, three different reasons. Do not collapse them into one sentence that says the products are connected.

Assessment

Explain the result

This lesson is not complete yet.

Materials

Use these with the lesson

Previous lesson Course

A passed check is saved in this browser so you can resume. It is not a certificate, not an accreditation, and not authority to run an effect.