Context
IssuerCategory is the closed set that states an institution's sector (SPEC-BC-0001 §3, the @tamga-network/trust schema, IIssuerRegistry.sol); the set was closed as "final" in DECISIONS, so extending it requires an ADR. With D10 (tickets) the first event ticket seller (an example ticket seller, operator model) entered the trust listA signed list of a country's root certificates, issuers and registered relying parties. Today trust in Tamga rests on these lists; a shared ledger comes later. and, lacking a fitting category, was given OTHER temporarily. Question (DB-23, 2026-09-26): should only EVENTS be added, or also TRANSPORT and TELECOM, whose labels the wallet already shows on screen?
Project management decision (2026-09-27): the category for ticket issuerThe institution that signs and issues credentials: a university, a professional body, a public institution or a company.s is events.
Decision
- K1 — Only EVENTS is added. Meaning: an institution that issues a ticket or attendance credential granting entry to an event such as a concert, sports match, show or fair (ticket seller, organiser, venue). Transport tickets (TRANSPORT) and operator credentials (TELECOM) are outside this decision; they are added by their own ADR when a real issuer candidate appears.
- K2 — Stable ordinals. The new value is appended to the end of the enum:
{GOVERNMENT, IDENTITY, EDUCATION, HEALTH, FINANCE, LOGISTICS, OTHER, EVENTS}. The contract is not deployed yet (chain stage), but the append-at-end rule applies to every future extension (ABI/storage compatibility). - K3 — Migration. The example ticket seller's trust list entry moves
OTHER→EVENTS(new list version); theevent-ticketverifierThe party that checks a presented credential: signature, issuer in the trust list, status and policy. Also called relying party. policy isallowed_categories: ["EVENTS"]. The wallet label is "Event". - K4 — Schema metadata unchanged.
issuer_categories: ["OTHER"]in theurn:tamga:tkt:EventTicket:1metadata is informative (SPEC-SCHEMA-0001: the binding check is in the trust layer), and the integrity digest of published metadata cannot change (D1,vct#integrity). The correction comes with the next schema version (EventTicket:2).
Rationale / alternatives
- EVENTS + TRANSPORT + TELECOM (rejected): opening categories without issuers grows the set speculatively; the meaning of a category (in transport: card or ticket? in telecom: line ownership?) becomes clear with the first real institution.
- Leaving it in OTHER (rejected): the coarse filter loses its meaning; the ticket verifier would have to accept every institution in the "other" category. The real gate is still
vct+ schema authorisation, but the category is a second line of defence. - Naming: the first proposal was
TICKETING; on project management's suggestion it isEVENTS— the category describes the sector, not the sales channel.
Invariants
| # | Invariant |
|---|---|
| IC1 | IssuerCategory is a closed set; a new value is added only by ADR and appended to the end of the enum (ordinals do not change). |
| IC2 | The category is a coarse filter, not an authorisation: acceptance of an issuer's credential is decided by vct + time-windowed schema authorisation (SPEC-TRUST-0001); the category alone is never a reason to accept. |
| IC3 | A category change is published in a new trust list version and does not retroactively change the authorisation evaluated against the credential's iat (D-BC-3). |
Consequences
- Code: the
@tamga-network/trustschema,IIssuerRegistry.sol, the trust list source (example ticket seller), theapps/verifypolicy, the wallet label/icon mapping (TICKETING→EVENTS). - Documents:
SPEC-BC-0001(enum), SPEC-ID-0002 (comment line), the glossary; DB-23 closed. - Remaining:
issuer_categories: ["EVENTS"]inEventTicket:2(K4).
Status
Accepted — 2026-09-27. DECISIONS: D-CAT-1.
Note (2026-11-04): the example institution name (slug) carrying a real company name was replaced by "example ticket seller"; the decision content is unchanged (project management).