I'm picking up an Inspired integration next week and I have about three hours
before the kickoff. Here is the Inspired integration library — six works.

Plan my three hours, and then execute the reading for me:

1. Look at the collection's reading order and its two routes. I am shipping a
   server-side integration, not running an agent, so tell me which members I can
   skip entirely and say why rather than hedging.
2. Read what you recommend and give me a one-page briefing: how the pipeline
   works, why a read is minutes, how the allowance is spent, and what the result
   object contains.
3. Pull out every constraint that would change an architectural decision — the
   things I would be annoyed to discover in week two. I am expecting something
   about durable jobs and something about when quota is charged.
4. Give me the ten-point checklist out of the guide as a checklist I can paste
   into our tracker, with one line each on what it means.
5. Tell me the vocabulary rules from the handbook's last chapter as a list of
   banned and permitted words, because I will have to argue about that with
   whoever writes our UI copy.

Skip the article unless something in it changes how I should call the API — I
am not building an extraction pipeline. And do not summarise the dataset's
columns at me; just tell me whether I will need it and when.