Event Kind Registry¶
This document is the working registry for OpenETR event kinds.
Its purpose is to provide one canonical place to track:
- event kind numbers
- event kind names
- current status
- intended purpose
- related specifications
- implementation notes
This registry is a draft and may change as the OpenETR model evolves.
Status Values¶
Suggested status values:
workingfor active experimental assignmentsdraftfor proposed but not yet adopted assignmentsreservedfor intentionally held future assignmentsdeprecatedfor assignments that should no longer be used
Registry¶
| Kind | Name | Status | Purpose | Notes |
|---|---|---|---|---|
1415 |
Anchor Event | working | Initial signed event establishing an anchored control state for an object | Regular event used as the starting point for a candidate control graph |
1416 |
Evidence Event family | working | Signed evidence of actions after an Anchor Event | Regular event family subtyped by the action tag |
1418 |
Witness Record | draft | Signed observation receipt for an exact signed anchor or evidence event | Optional; provisional OpenETR assignment, not a Nostr reservation; schema and signature binding checks required |
Current Interpretation¶
1418 Witness Record (Draft)¶
The Witness Record Specification, draft 0.1 defines the experimental Spurline-compatible receipt profiles and separate verification/trust assessment. Witness Records do not themselves change Core Record Ruleset 1.0 results. This local registry entry does not claim global allocation or approval by the Nostr standards community.
1415 Anchor Event¶
The Anchor Event is the initial event by which an object enters an OpenETR control graph.
Current intended role:
- establish the initial anchored control state
- bind the object identifier into the scheme
- serve as the starting point for later control analysis
An Anchor Event is the wire-level starting point for a candidate control graph. When valid under the applicable OpenETR rules, it establishes initial consequential state and brings the identified Digital Artifact into the Digital Original model. The registry does not decide which candidate graph is authoritative, whether it is recognized, or what external effect follows.
A single object digest may have more than one Anchor Event. The registry does not require global uniqueness of kind 1415 events per object digest; verifiers must evaluate candidate anchors under the relevant recognition profile.
1416 Evidence Event Family¶
The proposed action=inspection extension reuses kind 1416; no new event
kind is assigned. Its report-encryption and profile-scoped key_ref conventions
are draft-only. Private key-store and disclosure kinds remain unassigned. See
Inspection Evidence.
The 1416 event family expresses signed evidence of actions after an Anchor
Event. Defined rules determine whether an event changes control, contributes to
other Consequential State, or has no state consequence.
Current intended role:
- represent transfer initiation after anchoring
- represent transfer acceptance
- represent termination
- represent attestations
- represent Publisher Notices
- represent encumbrances
- represent discharges
- represent redemption or presentation events
- support later exclusive-controller determination
- separate later control movement from initial anchoring
Current working action subtypes:
action=initiateaction=acceptaction=terminateaction=attestaction=noticeaction=encumberaction=dischargeaction=redeem
This means 1416 is presently used as a shared Evidence Event family rather
than as a single-action kind.
That choice remains working and provisional.
Related Specifications¶
- CANONICAL_ETR_TRANSACTION_SPEC.md
- REGULAR_EVENT_KIND_MIGRATION_DESIGN_NOTE.md
- OPENETR_NOSTR_WIRE_FORMAT_SPEC.md
- OPENETR_CORE_RECORD_RULESET_1_0.md
- CONTROL_EVENT_MINIMUM_SHAPES.md
- DIGITAL_ORIGINALITY_CONTROL_AND_STANDING_DESIGN_NOTE.md
- TITLE_TRANSFER_AUTHORITY_REPLACEABLE_EVENT_SPEC.md
Notes¶
- This registry does not yet define all future OpenETR event kinds.
- Separate event kinds for attestation, encumbrance, discharge, redemption, substitution, cancellation, and revocation remain open design areas, but the current working model represents several of these as
1416actions. - New graph events use regular event kinds
1415and1416; the event id is the durable graph node. - The
otag is the object-wide query anchor, theetag links to a prior event, and the namedactiontag identifies the semantic action. - Termination is currently modeled as
action=terminatewithin1416, but may later be revisited as a separate kind if implementation experience suggests that is clearer. - Event kind assignment alone does not determine legal or operational effect; effect depends on the wider OpenETR recognition and domain-policy context.