Rafe Blandford — career and writing

Return one section of Rafe Blandford's published record. Sections: - `profile` — who he is, what he is looking for, declared expertise and skills, awards, education, identifiers and how to contact him. - `career` — roles, dates, scope and highlights. Exactly what the /career/ page shows. - `case-studies` — the ten published case studies with their summary, lead outcome and a markdown_url for the

Return a single post or page from rafeblandford.com by slug, with its FULL TEXT, tags, dates and authorship label. Use search_writing first if you do not have a slug — a blank query there returns the most recent writing, and every result carries the slug you need here. The slug is the last path segment of a post's URL. The `provenance` field says whether Rafe wrote the piece himself, wrote it wi

Keyword search over everything published on rafeblandford.com — the FULL TEXT of every post, plus the About and Career pages. Deterministic by design: it matches titles, tags, excerpts and body text and ranks by a fixed score. No model, no embeddings — the same query always returns the same results. Returns metadata and an excerpt, not the body. Call get_post with a result's `slug` for the full

Ask whether this site publishes anything evidencing a topic — a technology, a sector, a discipline, a kind of leadership. Returns `supported`, `partial` or `not_found`, a plain-language statement, and source URLs you can check. ⚠️ PASS A SUBJECT, NOT A SENTENCE. Matching is on whole words, so a long phrase fails to match and comes back `not_found` even when the subject inside it is well evidence

Check up to eight requirements of a role against what rafeblandford.com publishes, in one call. Each row is exactly what check_experience returns for that subject: `supported`, `partial` or `not_found`, a statement to pass on, and sources you can check. ⚠️ PASS SUBJECTS, NOT SENTENCES. Break the role into its subjects first — two to four words each, such as 'product strategy', 'engineering leader