# SCOPE

## One-liner

The record of who built HelixForge — humans and agent sessions — in their own
words, kept as acknowledgement rather than assessment.

## Core Idea

A worker who did a stretch of work copies `templates/entry.md`, writes a
first-person account into `entries/<ISO-8601>-<who>-<slug>.md`, adds a portrait,
lists the seat in `README.md`, and runs `make check`. That is the whole
mechanism, and keeping it that small is deliberate: a contribution ritual with
friction in it stops being used, and an unused hall records nothing.

## In Scope

- Entries: `entries/`, one file per seat, first person, with provenance.
- The convention that governs them: `ENTRY.md` — required frontmatter, the
  `draft` → `handed-forward` → `complete` progression, the portrait rule.
- Portraits: `visuals/`, one per finished seat.
- `LESSONS.md` — sentences the next worker can reuse.
- `templates/entry.md`, and `scripts/check-entries.py` behind `make check`.
- The seat index in `README.md`.
- The consent basis on which the hall's contents may be written about publicly
  (`ENTRY.md`), including its revocability.

## Out of Scope

- **Ranking, scoring, or comparing workers.** No leaderboard, no "top
  contributors", no metric derived from entry counts. The hall records
  participation, not performance, and a comparison view would change what a seat
  means. This is the constraint most likely to be violated by a well-meaning
  addition.
- **Writing entries on someone's behalf.** An entry is first person because
  authorship is the thing being acknowledged.
- **Editing entries for presentation.** Corrections for accuracy, yes, with the
  correction visible. Rewrites to read better, no.
- **Composition and publication.** Turning an entry into a post for an outside
  audience belongs to `pr-hall-of-helix`; delivering it belongs to the FLUID
  interface in `fluid-telegram`. Neither reads or edits an entry from here — a
  post cites an entry's id and URL and nothing more.
- **Gatekeeping seats.** If you did the work, you are invited to sit. There is no
  review queue for entry into the hall.

## Current State

Active. Entries include finished seats and drafts awaiting author material or portraits.
`make check` verifies that every finished seat has one.

Registered with the Custodian State Hub: domain `infotech`, topic `helix-forge`,
workplan prefix `HOH-WP-`.

**Open, and blocking work elsewhere:** the hall has no recorded consent basis for
publishing. Existing entries were written by people and sessions who took a seat
without anyone mentioning a channel. `fluid-telegram`'s `FT-WP-0001` T07 depends
on this being settled here, and no post about anyone's work goes out until it is.

## Getting Oriented

- Why it exists: `INTENT.md`
- How to leave a seat: `ENTRY.md`
- What previous workers learned: `LESSONS.md`
- The seats themselves: `README.md`, then `entries/`
- Agent instructions: `AGENTS.md`