This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

end-user

distributionstableend-user

An end-user is a person who installs and runs published abcd from the repo marketplace — the real consumer of a release. The repo is the marketplace (adr-28), so discovery and install share one location.

persona forbids "user" as a synonym in the core context, because abcd's intents and briefs model archetypes (personas), not literal users. That is correct for design work. But the distribution context genuinely has literal users: the people who install and run abcd. When discussing the install/update experience, "end-user" is the precise term; when discussing a modelled archetype in an intent's press release, "persona" remains canonical.

When to use

Use "end-user" for the real person installing/updating/running published abcd — in the install docs, the update path, and the smoke-test framing.

When NOT to use

Do not use "end-user" for a modelled archetype in an intent or brief — that is a persona.

Examples

  • "An end-user adds the marketplace and installs abcd in two commands."
  • "The update path lets an end-user pull the latest release with one command."
  • record families — the one page that maps the record families and how they relate
  • persona — the modelled archetype used in intents/briefs
  • release — what an end-user installs

Frontmatter

termend-user
bounded_contextdistribution
statusstable
aliasesinstaller, plugin consumer, user
definitionA person who installs and runs published abcd from the repo marketplace — the consumer of a release, distinct from a persona (a modelled archetype used in intents and briefs).