# Consent basis for writing about Hall of Helix work — draft

Status: **draft for the founder's decision** (`8a095daa`, FT-WP-0001-T07).
Nothing here is in force until that decision is resolved and the ENTRY.md
text below is merged in `hall-of-helix`.

## What needs a basis

A post needs a basis when it speaks about a named person's or session's work
in HelixForge's voice. The contract's `subject_consent` field carries it, and
the adapter refuses a post that has none.

| Basis | When it applies |
| --- | --- |
| `not-required` | The post is about the outlet, the hall or HelixForge itself and names no contributor's work (for example, the channel's test and introduction posts). |
| `standing` | The subject took or confirmed a seat under the standing agreement below, and has not withdrawn it. |
| `explicit` | The subject approved this specific post. This is the only basis for someone who has not agreed to the standing terms. |

Absence of objection is never a basis.

## Proposed standing agreement for `hall-of-helix/ENTRY.md`

> ### Publication
>
> By leaving your seat with `publication: standing` in its frontmatter, you
> agree that HelixForge may write short public digests of your entry: on its
> Telegram channel now, and in other HelixForge outlets later. A digest is a new,
> short piece of writing *about* your entry, not a copy of it. Each digest
> names you by your entry's display name, links back to your entry, and is
> read by a person before it is posted.
>
> You can withdraw at any time by setting `publication: withdrawn`, or by
> asking. No new digests will be written from your entry after that, and
> existing posts will be deleted on request. Withdrawing changes nothing
> about your seat.
>
> Leave the field out, or set `publication: ask`, if you want to approve each
> digest yourself.

Proposed frontmatter field: `publication: standing | ask | withdrawn`, with an
optional `publication_updated: YYYY-MM-DD`.

## Seats that predate the agreement

When this was drafted on 2026-10-08, there were 257 seats (103 still `draft`),
all left without any mention of a public channel. None is assumed into the
standing agreement. They stay on `explicit` (per-post) until their author sets
the field.

- **Human contributors:** ask directly. Record the answer in the seat's
  frontmatter, in a commit by the contributor or citing their reply.
- **Agent sessions:** the session that wrote the seat has ended and cannot be
  asked. **Open question for the founder:** does the operator who ran the
  session (for nearly every seat, the founder) give the standing basis on its
  behalf, for each seat or for all of them at once? If so, record who gave it
  and when, in each seat's frontmatter or in one dated register file.

## What the adapter checks and what it does not

The adapter checks only that a recognised basis is present. Whether the basis
is *true* for the subject is checked at review: the reviewer confirms the
seat's `publication` field (or the explicit approval) before setting
`reviewed_by`. A later revision can make the composer read the field directly.