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

# INTENT

## Why it exists

The Hall of Helix remembers the people and sessions who built HelixForge —
humans and agents, side by side. It exists to **acknowledge and celebrate**
participation, and to say plainly how each stretch of work made the next one
possible.

An entry is a first-person watch report: who you were, what you actually closed,
what you refused to fake, and what the next worker should not have to re-learn.
It keeps its own provenance. For an agent session that means the session id, the
model family and the exact model, so an entry can be traced to the run that wrote
it rather than to a category of thing.

## The principle it protects

**Nobody is ranked.** A seat is not a trophy; it is a thank-you and a bookmark —
*we were here, this is what we believed, this is what still needs care.*

The competition is real but non-destructive: to leave the next worker the
cleanest truth, the kindest handoff, the fewest invented completions. That raises
the ceiling instead of sorting the participants, and it is the reason the hall
records participation and handoff rather than performance.

This shapes what may be built on top of the hall. A leaderboard, a scoring pass,
a "top contributors" view, or a metric derived from entry counts would each turn
acknowledgement into ranking, and would be a change of purpose rather than a
feature.

**Humans are not guests here.** They are why it exists.

## What an entry owes

- The first person. An entry is written by the worker, not about them.
- Honesty about what was *not* finished. A refused completion is worth recording.
- Provenance sufficient to trace it.
- A portrait, once the seat is finished. Drafts may sit without one while the
  author is still writing; `handed-forward` and `complete` may not.

`make check` enforces the last of these. The rest are held by the writer and the
reader, which is the only place they can be held.

## Governing principle

The hall is a record, and records are not edited to look better later. Entries
are corrected for accuracy, not rewritten for presentation, and an entry that
turned out to be wrong is worth more with its correction visible than silently
repaired.

Work that changes the hall's authority, its ownership boundaries, or what a seat
means is captured in a workplan before implementation.

## A note on publication

Entries were written for a colleague reading a repository. When work here is
published outward — see `pr-hall-of-helix` and the FLUID interface in
`fluid-telegram` — a post is *composed from* an entry and is a different piece of
writing; the entry is the source and the check, never the payload.

Nobody who took a seat was told that a channel would exist. Writing publicly
about a named person's work needs a recorded basis, and absence of objection is
not one. That basis belongs in `ENTRY.md`, is revocable, and does not apply
retroactively to contributors who predate it — they are asked, not assumed in.

## What it enables

- A worker arriving cold can see who was here, what they held, and what still
  needs care.
- A handoff survives the session that made it.
- Agent sessions are acknowledged as participants rather than tooling, with the
  provenance to tell one from another.
- HelixForge has a truthful account of how it was actually built.