fixup! docs: publishing to vstorage

Author: dckc

main/guides/governance/index.md

@@ -46,7 +46,7 @@ Adding parameter governance to a contract consists mainly of using `handleParamG
 We pass it `zcf` so that it can `getTerms()` for initial parameter values, and we
 pass `paramTypes` to specify governed parameters and their types. `initialPoserInvitation`
 is necessary to set up replacing the electorate. `storageNode` and `marshaller` are used
-to publish values of the parameters to vstorage.
+to [publish values of the parameters to vstorage](../zoe/pub-to-storage).
 
 ```js
 import { handleParamGovernance } from '@agoric/governance/src/contractHelper.js';

main/guides/zoe/pub-to-storage.md

@@ -4,7 +4,32 @@ Contracts can use [notifiers and subscriptions](../js-programming/notifiers)
 to publish to clients. To publish data visible to [vstorage queries](../getting-started/contract-rpc#querying-vstorage), contracts should connect
 a subscriber to a `chainStorage` node.
 
-Let's look at the Inter Protocol [assetReserve.js](https://github.com/Agoric/agoric-sdk/blob/agoric-upgrade-13/packages/inter-protocol/src/reserve/assetReserve.js) contract. It publishes to [published.reserve.metrics](https://github.com/Agoric/agoric-sdk/blob/agoric-upgrade-13/packages/inter-protocol/test/reserve/snapshots/test-reserve.js.md) data of the form
+## Deployment Capabilities for Publishing to chainStorage
+
+In [Adding Parameter Governance to a Contract](../governance/#adding-parameter-governance-to-a-contract), the contract
+gets 2 properties for publishing to chainStorage in its `privateArgs`: `storageNode` and `marshaller`.
+
+In [dapp-agoric-basics](https://github.com/Agoric/dapp-agoric-basics), the `startSwapContract` uses 2 [permitted deployment capabilities](../coreeval/permissions), `chainStorage` and `board` and uses them to make the `privateArgs`:
+
+```js
+const marshaller = await E(board).getPublishingMarshaller();
+const storageNode = await E(chainStorage).makeChildNode(contractName);
+```
+
+A `Marshaller` is parameterized by functions for mapping unforgeable object identities to plain data slot references and back. Using the [board](../integration/name-services#the-board-publishing-under-arbitrary-names) name service gives consistent slot references across contracts.
+As discussed in [Marshalling Amounts and Instances](../getting-started/contract-rpc#marshalling-amounts-and-instances), this lets
+off-chain clients use the same `@endo/marshal` API.
+
+The `chainStorage` node corresponds to the `published` key in the
+[vstorage hierarchy](/reference/vstorage-ref).
+Using `E(chainStorage).makeChildNode(contractName)` gives the contract
+access to write to the `published.swaparoo` key and all keys under it.
+
+The `swaparoo` contract delegates the rest of publishing governance parameters to the `@agoric/governance` package.
+
+## Publishing structured data to chainStorage
+
+Let's look at the Inter Protocol [assetReserve.js](https://github.com/Agoric/agoric-sdk/blob/agoric-upgrade-13/packages/inter-protocol/src/reserve/assetReserve.js) contract to get more of the details. It publishes to [published.reserve.metrics](https://github.com/Agoric/agoric-sdk/blob/agoric-upgrade-13/packages/inter-protocol/test/reserve/snapshots/test-reserve.js.md) data of the form
 
 ```js
 /**
@@ -109,19 +134,18 @@ const metricsNode = await E(storageNode).makeChildNode('metrics');
 
 The `marshaller` is used to serialize data structures such as `MetricsNotification` above.
 
-## Deployment Capabilities for Publishing to chainStorage
+### Deployment Capabilities for the reserve
 
-To start a contract such as `assetReserve` above, the [setupReserve](https://github.com/Agoric/agoric-sdk/blob/agoric-upgrade-13/packages/inter-protocol/src/proposals/econ-behaviors.js#L76) function needs to supply
-the two `privateArgs`: `marshaller` and `storageNode`:
+To start `assetReserve`, the [setupReserve](https://github.com/Agoric/agoric-sdk/blob/agoric-upgrade-13/packages/inter-protocol/src/proposals/econ-behaviors.js#L76) function again supplies
+the two relevant `privateArgs`, `marshaller` and `storageNode`:
 
 ```js
 const STORAGE_PATH = 'reserve';
 const storageNode = await E(storageNode).makeChildNode(STORAGE_PATH);
 const marshaller = await E(board).getReadonlyMarshaller();
 ```
 
-As usual for a [permissioned deployment script function](../coreeval/proposal), `setupReserve` function is passed `BootstrapPowers`
-including `chainStorage` and `board`:
+The `setupReserve` function gets `chainStorage` and `board` deployment capabilities passed in:
 
 ```js
 export const setupReserve = async ({
@@ -133,7 +157,3 @@ export const setupReserve = async ({
 ...
 }) => { ... };
 ```
-
-A `Marshaller` is parameterized by functions for mapping unforgeable object identities to plain data slot references and back. Using the [board](../integration/name-services#the-board-publishing-under-arbitrary-names) name service gives consistent slot references across contracts.
-As discussed in [Marshalling Amounts and Instances](../getting-started/contract-rpc#marshalling-amounts-and-instances), this lets
-off-chain clients use the same `@endo/marshal` API.