Developer notes.

Make the boundaries inspectable.

These notes are written for a developer turning an interface idea into a bounded prototype. One follows selected content through a browser companion; the other follows source passages into a retrieval system. Both begin by describing what data is allowed into the workflow and what the resulting interface should make visible to a reviewer.

Read the permission-first article before specifying broad browser access. Then use the vector-search guide to think about passage size, metadata, authorization, and evaluation. A useful prototype can be deliberately small: a fixed collection, a repeatable task, and a documented failure case are enough to start a meaningful review.