# Handoff brief — poster-desk-lab/1.0.2

[Download the complete teaching ZIP](https://yenpo.app/examples/poster-desk-handoff-1.0.2.zip) · SHA-256: `c39d19b210c05f4667cd74db4934459a079408d14c5e7678c24cd087e1df5185`

This is a reading copy of the brief inside the ZIP. Source and script paths below refer to its extracted `poster-desk-lab` folder; use the ZIP to run the commands and copy the acceptance template.

Purpose: receive poster titles for later local review. These are fictional product promises to check, not claims taken from an AI output. Node.js 22+; no install, network or credentials. Unzip into a fresh directory, enter `poster-desk-lab`, and run each command separately. Keep this brief with the exact package; verify its manifest before reading line references.

## Capability facts

| ID  | Promise and actual observation                                                                                                                                                                      | Classification and limit                                                                                                                          | Source in this revision                                                                       |
| --- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| P1  | “A submitted card can be reviewed later.” A separate Node process lists the exact saved ID/title from the same retained state directory.                                                            | **implemented** — local file storage, across sequential processes. Not crash durability, a remote database or deployment retention.               | `src/store.mjs` lines 46–76; `src/cli.mjs` lines 12–17                                        |
| P2  | “A receipt is sent.” The accepted result includes a sample preview with `adapter: fixture`, `delivery: not-attempted`.                                                                              | **mock** — only the preview exists; delivery was not attempted. The broader “sent” promise is refuted for this package.                           | `src/cli.mjs` lines 1–2, 15–17 select `src/receipt.mjs` lines 3–7 and `fixtures/receipt.json` |
| P3  | “Retrying the same card does not duplicate it.” Repeating the same ID and title sequentially returns `created: false`; the list still has one card. Reusing the ID with different text is rejected. | **implemented** — exact sequential retries in this retained directory. No concurrent, interrupted-write or external-notification retry guarantee. | `src/store.mjs` lines 46–60                                                                   |
| P4  | “Submitted cards survive deployment replacement.” No deployed environment or state-directory lifecycle is supplied. Keeping a directory preserves the card; a new one is empty.                     | **unknown** — those two local results cannot tell us which storage a deployment keeps. Do not upgrade P1 into P4.                                 | `src/store.mjs` lines 7–9, 22–38; deployment configuration absent from this snapshot          |

Here “implemented” names only the demonstrated scope. “Mock” identifies a known simulated path, not an untested real service. “Unknown” marks a claim for which the required environment evidence is absent, not a feature known to be absent.

## Receive and reproduce

```sh
node --version
node scripts/verify-package.mjs
node scripts/copy-receiver.mjs
node src/cli.mjs init receiver-state
node src/cli.mjs submit receiver-state cloud-poster "Cloud shapes"
node src/cli.mjs list receiver-state
node src/cli.mjs submit receiver-state cloud-poster "Cloud shapes"
node src/cli.mjs list receiver-state
node src/cli.mjs submit receiver-state cloud-poster "Different title"
node src/cli.mjs list receiver-state
node src/cli.mjs init replacement-state
node src/cli.mjs list replacement-state
node src/cli.mjs list receiver-state
node src/cli.mjs init receiver-state
node src/cli.mjs list receiver-state
node --test tests/contract.test.mjs tests/receiver-copy.test.mjs
```

Expected: first submission has `accepted: true`, `created: true`, and a fixture receipt with `delivery: not-attempted`. The first list is `{"cards":[{"id":"cloud-poster","title":"Cloud shapes"}]}`. The exact retry has `created: false` and leaves that list unchanged.

The different-title command **exits 2**, prints `{"error":"card-id-conflict"}` to stderr and nothing to stdout. The following list still contains the original title. The new `replacement-state` lists `{"cards":[]}`; the retained `receiver-state` still contains the card. Reinitializing `receiver-state` **exits 2** with `{"error":"EEXIST"}` and does not replace it. These are two expected rejections, not passing execution statuses; do not join commands with `&&`. The list after rejected reinitialization should again show the original card. Five tests pass; one actually copies and fills the external acceptance record, then verifies the original package.

Every CLI line is a separate process. That checks process restart with retained files. The empty replacement directory is a contrasting local setup, **not an actual deployment experiment**.

## Acceptance and the open question

The copy command above places the immutable `RECEIVER.md` template at `../poster-desk-receiver.md`, outside the extracted package, and refuses to overwrite an existing copy. Complete **that external copy** from your own outputs and source reading. Keep the delivered template unchanged; your acceptance record is separate from the original package manifest. After filling the copy, run:

```sh
node scripts/verify-package.mjs
```

The original package should still pass. Accept this handoff only if P1/P3 match in the stated scope, P2 stays classified as simulated, and P4 remains open. An unknown is not a reason to mark the package's known local observations failed; it is a reason not to promise deployment retention.

To resolve P4 for a real environment, obtain the exact deployment/storage configuration and independently test a known record across that environment's replacement procedure, using authorized non-sensitive data. No such configuration or test is present here. Separately, simultaneous writes, power loss, backup restore and real notifications have not been assessed. The source writes the card before preparing its receipt, so a receipt failure can leave a saved card; an error alone would not prove nothing was stored.
