---
repo: pr-hall-of-helix
updated: "2026-09-04"
---

# INTENT

## Why it exists

`pr-hall-of-helix` is the campaign that carries HelixForge's work outward. It
takes what the Hall of Helix records and decides what a stranger should hear
about it, in what words, and when.

The `pr-` prefix marks it as a campaign rather than a service: it is an ongoing
offering with its own voice, cadence and budget, not a project that finishes.

## The problem it exists to solve

A hall entry is a considered first-person account written for a colleague reading
a repository — under fixed headings, median body around 5,800 characters, most of
them longer than a single Telegram message can carry. A channel post reaches
someone scrolling.

These are different pieces of writing for different readers, and publishing the
first as the second serves neither. The length is only the visible symptom; the
mismatch is one of **register and audience**, and it would remain if the limit
were ten times larger.

So this repository composes. A post is written *from* an entry and is a new piece
of writing. The entry is the source and the check, never the payload.

## What it owns

- **Composition** — turning an entry into a post, and the editorial voice that
  does it.
- **Selection** — which work is worth a post, and when.
- **Consent** — the basis on which HelixForge may write publicly about a named
  person's work, and the record of it.
- **Review** — a person reads each post against its source entry before it goes
  out; their name travels with the post as `reviewed_by`.
- **Variant strategies** and the competition between them.
- **The declared presence** — `presence/telegram.yaml`, because a bot's name and
  a channel's title are brand, not mechanism.

## What it does not own

Delivery. Posts are published through the FLUID interface
`helix-forge-telegram-publishing` in `fluid-telegram`, by a single call to
`POST /v1/channel-posts`. That interface renders and delivers; it never writes,
selects, shortens or embellishes. This campaign is a *consumer* of it, in cohort
`hall-publishing-jobs`, and receives per-variant engagement back.

The boundary is architectural, not stylistic: composition is a probabilistic
editorial task, and `ArchitectureBlueprint.md` §48.1 forbids an LLM in the
mandatory request path.

## Governing principle

**A post speaks about a named person's work in HelixForge's voice.** That is the
fact everything here is arranged around.

A condensation can flatter, it can misstate, and it can put a claim in someone's
mouth that their own entry never made — and in an audit trail an unfaithful post
looks exactly like a faithful one. The defence is not that the composer is
careful. It is that a human read the post against its source, the post names the
entry it came from, and both are recorded before anything reaches a subscriber.

Two rules follow, and neither is negotiable by anything in this repository:

- **No post goes out without a recorded consent basis.** Absence of objection is
  not consent. Ninety-four entries predate any channel, and their authors are
  asked rather than assumed in.
- **No post goes out unread.** `reviewed_by` is a person who compared the post to
  the entry, not a rubber stamp and not a service account.

The interface refuses a post that carries neither, which makes these enforceable
rather than aspirational — but they are held here first, because by the time the
interface refuses something the writing has already been done.

## What it enables

- Work recorded in the hall reaches people who would never read a repository.
- Contributors are acknowledged publicly, on a basis they agreed to.
- Which editorial approach travels can be settled by evidence, using the
  per-variant engagement the interface reports.
- HelixForge has a public voice that is accountable to a source document.