# Asset register

*The business owner, keeping the list of what they own straight, because a claim is paid against it.*

- Business: Swiftline Couriers Ltd (`swiftline-couriers`), fictional, with synthetic transactions
- Rendered from: https://itspickle.app/register?demo=swiftline-couriers
- As JSON: https://itspickle.app/api/audit?demo=swiftline-couriers

## What only the customer can add

0 of 0 items were put here by a bank
statement: described, categorised and valued at replacement cost with nobody typing anything. What a
bank line cannot say is which unit it is, what an item cost where the ledger never saw it, and what
it is worth where cost cannot say.

- Cost, as the books have it: £0
- Replacement value today: £0
- Insured for: £0

Replacement value is derived by uplifting purchase price. An accounting fixed-asset register holds
cost and depreciated book value, and neither of those is a sum insured.

## The register

This business has no register. Nothing in what was read described an owned item.


## How the list keeps itself

Edits to *this* register live in the URL and nowhere else, because this business belongs to nobody:
every twin renders one of four seeded fixtures, so a stored edit would make one reader's register
into everybody's. A business on a signed-in account keeps its register against the account instead,
and no link out of that page carries anything. A receipt attached to
an item and an email forwarding address are both described on the page and are **not built**: both
need somewhere to put a file, and a database row is not a filestore. Pasting a product page is built, and reads the schema.org/Product
JSON-LD and Open Graph tags a shop already publishes; it produces a draft the customer submits, never
an addition.

---

Illustrative only. This is a statement of demands and needs based on public records and information you confirm, not a personal recommendation or a quote. Prices are banded estimates derived from published rates and are not an offer of cover.