Evidence Event Minimum Shapes¶
The filename is retained for link compatibility. Evidence Event is the canonical term; earlier drafts called this the control-event family.
This note defines minimum event shapes for OpenETR Evidence Events within the current Nostr event family.
It is intended to extend the current OpenETR working model in which:
kind 1415represents the Anchor Eventkind 1416represents the Evidence Event family
The Anchor Event forms a one-record candidate Evidence Graph. Validation of that Evidence Graph under an applicable policy may establish initial consequential state and bring the identified Digital Artifact into the OpenETR Digital Original model. The event does not by itself determine that the candidate is uniquely authoritative, recognized, or entitled to legal, institutional, contractual, or community effect.
The goal is to define a minimal, internally consistent event shape for the current working 1416 action family:
INITIATEACCEPTTERMINATEATTESTNOTICEENCUMBERDISCHARGEREDEEM
These definitions are intentionally minimal. They are not intended to settle the full legal, operational, or attestation semantics of the events. They define only the minimum Nostr event structure required to express them in the current OpenETR model.
Shared Evidence-Event Pattern¶
Each of the events in this note is a kind 1416 event.
They follow the same general pattern:
oidentifies the Digital Artifactelinks the event to the current control chainactionidentifies the event type
An Evidence Event records a signed action concerning the Digital Artifact. It does not necessarily change control or Consequential State. Defined rules determine what consequence follows. Unless explicitly stated otherwise, the events in this note do not change the Current Controller.
The reference implementation centralizes these actions and labels in openetr/control.py.
Implementation Mapping¶
The current CLI maps these action shapes as follows:
| CLI command | Event kind | action |
Participant tag |
|---|---|---|---|
openetr transfer initiate |
1416 |
initiate |
p = transferee |
openetr transfer accept |
1416 |
accept |
optional p = counterparty |
openetr terminate-etr |
1416 |
terminate |
none |
openetr attest |
1416 |
attest |
optional p = subject |
| not yet exposed by the reference CLI | 1416 |
notice |
none |
openetr encumber |
1416 |
encumber |
p = beneficiary |
openetr discharge |
1416 |
discharge |
optional p = releasing party |
openetr redeem |
1416 |
redeem |
p = obligor |
openetr query consumes the same event family to derive lifecycle state, current controller, control chains, and encumbrance state. openetr query-etr remains available as a compatibility alias.
INITIATE¶
Purpose¶
INITIATE records a transfer initiation from the current controller toward a transferee.
The event identifies the intended transferee but does not, by itself, settle every recognition question outside the wire layer.
Minimum Shape¶
kind = 1416- required tags:
["o", "<object_hex>"]["e", "<prior_control_event_id_or_anchor_event_id>"]["action", "initiate"]["p", "<transferee_pubkey_hex>"]
Control Effect¶
- candidate transfer of Current Controller to the transferee
- recognized effect depends on the implementation's control-chain and recognition rules
ACCEPT¶
Purpose¶
ACCEPT records acceptance of a transfer or control transition by the receiving party.
Minimum Shape¶
kind = 1416- required tags:
["o", "<object_hex>"]["e", "<initiate_event_id_or_prior_control_event_id>"]["action", "accept"]
Optional Tags¶
["p", "<transferor_or_related_counterparty_pubkey_hex>"]
Control Effect¶
- no independent controller change at the protocol layer
- may be required by policy or implementation logic before a transfer is treated as complete
TERMINATE¶
Purpose¶
TERMINATE records termination of the active OpenETR lifecycle concerning the Digital Artifact.
Minimum Shape¶
kind = 1416- required tags:
["o", "<object_hex>"]["e", "<prior_control_event_id_or_anchor_event_id>"]["action", "terminate"]
Control Effect¶
- terminates the active lifecycle if recognized as effective
- later evidence events should not be treated as effective after recognized termination
ATTEST¶
Purpose¶
ATTEST records an authenticated assertion relating to the Digital Artifact.
The attestation should reference the specific prior event being attested.
That means the e tag should point to the concrete Anchor Event or evidence event whose declaration, occurrence, or effect is being attested, rather than merely to the latest event in the chain in general.
Examples may include:
- custody
- inspection
- quality
- quantity
- certification
An attestation does not change the Current Controller.
Minimum Shape¶
kind = 1416- required tags:
["o", "<object_hex>"]["e", "<specific_event_id_being_attested>"]["action", "attest"]
Optional Tags¶
["type", "<attestation_type>"]["p", "<subject_pubkey_hex>"]["ref", "<external_reference>"]
Control Effect¶
- no change to Current Controller
NOTICE¶
Purpose¶
NOTICE records the Anchor Publisher's signed position concerning the
Digital Artifact.
A qualifying notice is evidence of what the Anchor Publisher states. It does not erase the Anchor Event or independently establish validity, recognition, or effect.
Minimum Shape¶
kind = 1416- required tags:
["o", "<object_hex>"]["e", "<anchor_event_id_or_prior_notice_event_id>"]["action", "notice"]["notice_type", "<publisher_position>"]
Optional Tags¶
["severity", "<information_warning_or_critical>"]["effective_at", "<publisher_declared_time>"]["reason_code", "<structured_reason>"]["ref", "<external_reference>"]["successor", "<successor_artifact_digest>"]
State Effect¶
- derives Publisher Position under OpenETR Core Record Ruleset 1.0
- does not change
anchor_state - does not change the Current Controller
The notice vocabulary, signer requirements, chain rules, and conflict handling are defined in OPENETR_CORE_RECORD_RULESET_1_0.md.
ENCUMBER¶
Purpose¶
ENCUMBER records an authenticated declaration of an encumbrance affecting the Digital Artifact.
Examples may include:
- pledge
- security right
- lien
- restriction
OpenETR records the declaration but does not determine legal validity, perfection, priority, or legal effect.
Minimum Shape¶
kind = 1416- required tags:
["o", "<object_hex>"]["e", "<prior_control_event_id_or_anchor_event_id>"]["action", "encumber"]["p", "<beneficiary_or_secured_party_pubkey_hex>"]
Optional Tags¶
["type", "<encumbrance_type>"]["ref", "<external_reference>"]
Control Effect¶
- no change to Current Controller at the protocol layer
DISCHARGE¶
Purpose¶
DISCHARGE records the authenticated release or satisfaction of a previously declared encumbrance.
This event should identify the encumbrance event being discharged.
Minimum Shape¶
kind = 1416- required tags:
["o", "<object_hex>"]["e", "<prior_control_event_id_or_anchor_event_id>"]["action", "discharge"]["enc", "<encumbrance_event_id_hex>"]
Optional Tags¶
["p", "<beneficiary_or_releasing_party_pubkey_hex>"]["ref", "<external_reference>"]
Control Effect¶
- no change to Current Controller
REDEEM¶
Purpose¶
REDEEM records that the Current Controller has presented the Digital Artifact to the Obligor and requested performance.
REDEEM does not itself terminate the Digital Artifact's OpenETR lifecycle.
Minimum Shape¶
kind = 1416- required tags:
["o", "<object_hex>"]["e", "<prior_control_event_id_or_anchor_event_id>"]["action", "redeem"]["p", "<obligor_pubkey_hex>"]
Optional Tags¶
["ref", "<presentation_or_claim_reference>"]
Control Effect¶
- conceptually moves the Digital Artifact's derived state into a redemption-pending state
- does not itself terminate the object
- does not by itself change the Current Controller unless a later policy layer says otherwise
Graph Reconstruction Convention¶
The minimum convention in this note is:
ofinds all candidate Evidence Graph events for the Digital Artifactelinks each non-anchor graph event to the exact prior event idactionidentifies how the event should be interpreted- action-specific tags such as
p,enc,type,notice_type, andrefprovide signed structured event data
Summary¶
The minimum required tags for each event are:
INITIATEo,e,action,pACCEPTo,e,actionTERMINATEo,e,actionATTESTo,e,actionNOTICEo,e,action,notice_typeENCUMBERo,e,action,pDISCHARGEo,e,action,encREDEEMo,e,action,p
These definitions provide a minimum event grammar for extending the OpenETR regular Evidence Event family.