Adding Orchestration Documentation Index Page

main/guides/agoric-cli/agd-query-tx.md

@@ -9,7 +9,7 @@ This section focusses on commands relevant to developing and deploying smart con
 
 - [Validators topics \- Agoric Community Forum](https://community.agoric.com/c/validators/9)
 - [Governance topics \- Agoric Community Forum](https://community.agoric.com/c/governance/6)
-- [Delegator Guide \(CLI\) \| Cosmos Hub](https://hub.cosmos.network/main/delegators/delegator-guide-cli.html)
+- [Delegator Guide \(CLI\) \| Cosmos Hub](https://hub.cosmos.network/delegators/delegator-guide-cli.html)
 
 :::
 

main/guides/coreeval/index.md

@@ -4,7 +4,7 @@ Until mainnet enters the Mainnet-3 phase of the [multi-phase mainnet rollout](ht
 permissionless [contract installation with Zoe](/guides/zoe/#contract-installation)
 is limited to development environments.
 
-Until then, permission to deploy contracts can be granted using an Agoric extension to [Cosmos SDK Governance](https://hub.cosmos.network/main/delegators/delegator-guide-cli.html#participating-in-governance) called `swingset.CoreEval`. As discussed in [governance using Hardened JavaScript: swingset\.CoreEval](https://community.agoric.com/t/bld-staker-governance-using-hardened-javascript-swingset-coreeval/99),
+Until then, permission to deploy contracts can be granted using an Agoric extension to [Cosmos SDK Governance](https://hub.cosmos.network/delegators/delegator-guide-cli.html#participating-in-governance) called `swingset.CoreEval`. As discussed in [governance using Hardened JavaScript: swingset\.CoreEval](https://community.agoric.com/t/bld-staker-governance-using-hardened-javascript-swingset-coreeval/99),
 if such a proposal passes, its JavaScript code is run with ocaps extracted using the proposal's permitted capabilities, which the code can combine to perform privileged tasks.
 
 To make a proposal to deploy a contract:

main/guides/coreeval/proposal.md

@@ -122,7 +122,7 @@ There are also several more promise spaces one level down, including:
 - `powers.issuer`
 - `powers.brand`
 
-The `installContract` helper calls `E(zoe).installBundleID(bundleID)` to create an `Installation`, much like our earlier discussion of [Contract installation](http://localhost:8080/guides/zoe/#contract-installation).
+The `installContract` helper calls `E(zoe).installBundleID(bundleID)` to create an `Installation`, much like our earlier discussion of [Contract installation](../zoe/#contract-installation).
 It also calls `powers.installation[name].resolve(installation)`.
 
 ```js

main/guides/integration/chain-integration.md

@@ -47,4 +47,4 @@ However they do have a sequence number and may be invalidated if another transac
 - How are addresses generated?
 [Cosmos SDK v0.45 Docs - Accounts](https://docs.cosmos.network/v0.45/basics/accounts.html)
 - How is the blockchain queried?
-JSON-RPC, gRPC, REST  [Cosmos SDK v0.45 Docs - Interact with Node](https://docs.cosmos.network/v0.45/run-node/interact-node.html)
+JSON-RPC, gRPC, REST  [Cosmos SDK v0.45 Docs - Interact with Node](https://docs.cosmos.network/v0.45/run-node/interact-node.html)

main/guides/orchestration/index.md

@@ -0,0 +1,19 @@
+# Orchestration Overview
+
+
+Orchestration is a core concept within the Agoric platform designed to empower entrepreneurs. It enables the creation of smart contracts that seamlessly interact with applications deployed on various blockchains. This composability allows for the development of user-centric applications that leverage the unique strengths of different blockchain ecosystems.
+The Agoric Orchestration API simplifies interactions between multiple networks, particularly those using the Inter-Blockchain Communication (IBC) protocol within Cosmos. The API acts as an abstraction layer, streamlining multi-step processes while maintaining requestor authority. Smart contracts involved gain no additional privileges. 
+Orchestration integrates with existing Agoric components (SwingSet, Cosmos modules) and introduces the vat-orchestration vat. This vat manages Inter-Chain Account (ICA) identities and connections to host chains, ensuring proper transaction authorization.
+The orchestration client handles asynchronous tasks and complex workflows, including those spanning multiple chains. This empowers smart contracts for actions like inter-chain staking and multi-hop transfers, facilitated by notifications from the transfer vat and IBC middleware updates. Orchestration simplifies complex cross-chain interactions within a secure and user-controlled environment on the Agoric platform.
+
+
+## Example API Usage
+
+```javascript
+const amount = coins(100, 'utia');
+const celestiaChain = E(orchestration).getChain('celestia');
+const icaCelestia = await E(celestiaChain).createAccount();
+await E(icaOsmosis).send(icaCelestia.receiver, amount);
+await E(timerService).delay(6000n);
+return E(icaCelestia).delegate(amount, celestiaValidator);
+```

main/guides/zoe/contracts/otc-desk.md

@@ -7,9 +7,9 @@
 
 ![Building a Composable DeFi Contract](./assets/title.jpg)
 
-This is the OTC Desk contract from the ["Building a
-Composable DeFi Contract" episode of Cosmos Code With
-Us](https://cosmos.network/series/code-with-us/building-a-composable-defi-contract).
+This is the OTC Desk contract from the "Building a
+Composable DeFi Contract" episode of [Cosmos Code With
+Us workshop](https://www.youtube.com/watch?v=e9dMkC2oFh8).
 
 [Watch the replay of the
 workshop](https://www.youtube.com/watch?v=faxrecQgEio):

main/reference/ertp-api/ertp-data-types.md

@@ -71,7 +71,7 @@ A **DisplayInfo** data type is associated with a **[Brand](./brand)** and gives
 to display that **Brand**'s **[Amounts](#amount)**. **DisplayInfo** has one optional property,
 **decimalPlaces**, which takes a non-negative integer value.
 
-The **decimalPlaces** property tells the [display software](/~https://github.com/Agoric/agoric-sdk/tree/master/packages/ui-components)
+The **decimalPlaces** property tells the [display software](/~https://github.com/Agoric/ui-kit)
 how many places to move the decimal point over to the left so as to display the value
 in the commonly used denomination (e.g., display "10.00 dollars" rather than "1000 cents").
 

main/reference/zoe-api/zoe.md

@@ -364,8 +364,7 @@ Every **Keyword** in **give** must have a corresponding **payment**.
 const paymentKeywordRecord = harden({ Asset: quatloosPayment });
 ```
 
-<a href="offerargs"></a>
-
+<a id="offerargs"></a>
 ### Offer Arguments
 
 **offerArgs** is an optional CopyRecord that can be used to pass additional arguments to the