RFC 0001
← RFC 0001
Off the Bit Section 6: Curriculum Vitae Category: Informational Access: CONTROLLED
M. Imran Token lifetime: 86400 s Single use, revocable X-Robots-Tag: noindex

6. Curriculum Vitae

Access controlled, for reasons that are about other people's privacy rather than about mine

6.1. Rationale

Sections 3 through 5 of RFC 0001 are a more useful record than any résumé. They carry numbers, named failures, revision dates, and claims you can check against people who were in the room.

The document itself carries client names, reference contacts and a phone number that belong to other people's privacy as much as to my convenience. So it goes out on a signed link rather than sitting at a guessable path in a public bucket.

6.2. Request

POST /api/cv

Not built yet. The endpoint ships with Section 6 and this form is inert until it does. Principle 4.1 says a service must degrade loudly, so it says so here rather than accepting an address and dropping it. Until then use the path 6.5 lists first anyway: write to imran@mosthofaimran.com and say what the role is.

6.5. Alternatives

PreferencePath
PreferredWrite to imran@mosthofaimran.com and say what the role is.
FineUse the form in 6.2, once it exists.
Also fineDo not request it at all. Sections 3 through 5 will tell you more about how I work.
ImranSection 6, access controlled[Page 8]