[Zoe] zoe.chainmail concerns

[katelynsills]

This Issue is updating the concerns mentioned in #98 by @DavidBruant for the current Zoe chainmail.

• Explain what a "handle" is (an empty object as an id) and why we use it rather than a numeric id.
• Define an instanceRecord struct and the other record structs from state.js
• Explain why it is helpful to have an installation and install step separately (To have a unique identifier for specific contract code that can be referenced and reused. For example, once you have looked at the atomicSwap contract and saved the installationHandle for that code, you can look at any future invite and know for certain that if it used that installationHandle when the instance was created, it used code you examined.)

[katelynsills]

@DavidBruant, is this something you could take on? If so, comment below (apparently commenting is necessary?) and I'll assign the task to you.

[DavidBruant]

Explain what a "handle" is (an empty object as an id) and why we use it rather than a numeric id.

I added a defintion to the documentation glossary. See Agoric/documentation#109

I think it'll be enough, no need to add something to the chainmail about this

[katelynsills]

Sounds good. What do you think about the other two task items? Also, @tyg is working on related issues writing up his Intro to Zoe.

[DavidBruant]

Define an instanceRecord struct and the other record structs from state.js

I addressed this in #878

Explain why it is helpful to have an installation and install step separately

I'm going to write something somewhere and when the intro to zoe is merged, we can figure out where the best place is for this

[katelynsills]

Sounds great!