# Hosted ledger for teams: synthetic exercise worksheet

Curriculum reviewed: 2026-10-25. Use public or synthetic data only.
Do not include client evidence, credentials, private identifiers or raw receipts.

## Goal
a synthetic two-organisation isolation exercise plus signed envelope/ACK verification; optional live observation remains bounded to approved preview access.

## Outcomes
- Prepare a value-free signed handoff.
- Separate identity, grants and entitlements.
- Validate ACK trust and expiry.
- Read scoped history without overclaiming a portfolio pass.

## Synthetic case
Describe a Sales report built from order headers and order lines. State which grain you intend and which independently established expectation you would compare.

## Review each lesson
### 1. Draw the local/Hosted contract
Identify what stays local and what the closed attestation can disclose.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 2. Prepare a signed qualification handoff
Strictly verify the selected gate and export a bounded attestation.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 3. Enrol people, projects and devices
Use owner-controlled preview workflows without treating membership as a project grant.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 4. Plan and authorise a push
Separate offline planning, local consent, Hosted approvals and producer/device authority.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 5. Verify acknowledgements and recovery
Recognise original-byte replay, uncertainty and the independently pinned ACK key.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

### 6. Operate history and read-only MCP
Explain expired, revoked, missing and current states in the console and assistant tools.
Expected output: a written explanation naming the observation, its scope and its limits.
Your notes:

## Failure case
Generated definitions exist but a required execution observation is missing. Explain why qualification cannot pass and name the next required observation. Do not fabricate a receipt or change a frozen expectation.

## Evidence table
| Claim | Expected observation | Available evidence | Missing/stale | Next owner/action |
| --- | --- | --- | --- | --- |
| | | | | |

## Limitations
This worksheet is a completion check, not live qualification, business acceptance or a professional award. Pro assessment and certification policy remain planned. Keep optional live results in customer-controlled custody.