Ye Olde RFC
Ye Olde RFC is a tool that transforms technical specifications into medieval-style manuscripts. It uses mock-archaic English and preserves technical details while presenting them in a visually appealing format. The tool requires Python and an Anthropic API key for operation.
- ▪Ye Olde RFC converts Requests for Counsel into scrolls with medieval aesthetics.
- ▪It employs mock-medieval English and maintains technical accuracy in the output.
- ▪Users can generate HTML or PDF versions of their documents using specific commands.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/gabinante/ye-olde-rfc |
| Publication time | Thu, 21 May 2026 04:16:22 +0000 |
| Retrieval time | 2026-05-21T04:35:03.470Z |
| Last seen | 2026-05-21T04:35:03.470Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | None |
| Cluster logic | Not yet clustered, or no peer story found in the clustering window. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Ye Olde RFC Request for Counsel — transform dry technical specs into medieval manuscripts, complete with blackletter fonts, illuminated drop caps, and mock-archaic English prose. Feed it a Request for Counsel, get back a scroll. How it works Claude rewrites your technical document in mock-medieval English with Latin titles, personified services ("Prometheus the Steward of Metrics"), and archaic metaphors — while preserving every technical detail Jinja2 renders the structured output into an HTML template styled with UnifrakturMaguntia blackletter, EB Garamond body text, parchment backgrounds, and illuminated drop caps Quick start # Install uv sync # Generate from a real RFC (needs ANTHROPIC_API_KEY) export ANTHROPIC_API_KEY=sk-ant-...
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.