0001. Project name: affirmatrix
================================

Status
------

Accepted, 2026-07-24.

Context
-------

The tool was designed and prototyped under the working name ``seg`` in the
research workspace. As an independent OSS project it needs a real name.

Decision
--------

The project is named **affirmatrix** — Latin agent noun, *she who affirms* —
built on *affirmation*, the project's distinctive mechanism (a content-bound
human judgement no surveyed tool possesses). ``affirmare`` = *ad + firmare*,
"to make firm" — the same root as *firmware*: affirmatrix is the sibling of
firmhold. **"Safety evidence graph" (SEG) remains the artifact term**:
affirmatrix manages safety evidence graphs. Name verified free on PyPI, npm,
and GitHub at decision time.

The full naming path — rejected candidates and the collision sweep — is
recorded in the research workspace this project grew out of, not here.

Consequences
------------

- Code, imports, and CLI entry points use ``affirmatrix``; ``seg`` survives
  only as the artifact term and in identifier prefixes (``SEG-SYS-nnn``,
  ``SEG-SREQ-nnn``, the ``seg:`` vocabulary namespace).
- The "daily affirmations" wellness echo in web search is an accepted,
  fading risk.