
Everything Has a Place
THE TOWER / COVER CONCEPT
Susan enters the Tower files.
This is Susan's cover concept. Her engineering chapter follows after we verify the implementation and choose what can be shown publicly.
Read the concept boundary01 / THE QUESTION
How does a growing collection stay useful without losing its history?
Susan's cover imagines the catalog as a place you can walk into: sources, editions, media, licenses, and availability each have a place. That is a visual direction for her chapter, not evidence that a Tower-based catalog or shop is deployed.
02 / THE QUESTIONS
What the chapter needs to answer.
- 01Source
What is this item, and where did it come from?
- 02Edition
Which version or form is being handled?
- 03Rights
What license or use boundary travels with it?
- 04Availability
Can the right person find and use it now?
03 / THE CURRENT RECORD
What we can say today.
This is an approved cover direction for Susan. Existing project notes describe a catalog role, but this page has not verified a running Susan service, an integrated Tower catalog, or a public shop workflow.
04 / THE LIMIT
What the cover cannot prove.
The artwork is storytelling. Its shelves, counter, tags, and characters are not screenshots or proof of implemented inventory, rights enforcement, or delivery.
05 / NEXT RECEIPT
What belongs beside this chapter.
Inspect Susan's current code and runtime, then attach a small, redacted example that follows one item from source through edition, rights, and retrieval. The engineering chapter can be written from that record.