Taxonomy and evidence

Mechanisms

A confirmed event may carry multiple labels, but remains one consolidated event.

Code Mechanism Minimum confirmation condition Insufficient on its own
T1 Documentary transfer Verified IRTF → IETF continuity supported by history or an explicit statement, checked against content and affiliations WG adoption without a verified IRTF origin
T2 Technical transfer Located passage showing use of an identifiable origin solution; normative dependence must identify the content actually used A normative reference without examining the technical object
T3 Conceptual transfer Explicit attribution and use of a concept, model or requirement from the origin Similar terminology or background citation
T4 Experimental or empirical transfer Identifiable experimental result used in a destination decision or specification Citation of an experiment without demonstrated use
T5 Organizational or process transfer Process record linking a research agenda to creation or change of IETF activity Thematic proximity between an RG and WG
T6 Human-mediated transfer Verified person participation on both sides with a documented role in an already confirmed T1–T5 event Shared authorship alone

T1 can involve a rename, adoption, an IRTF-to-IETF phase transition or publication continuity. Validate each path separately. T6 is auxiliary and cannot confirm an event by itself.

Objects

Code Object
O1 Architecture
O2 Model
O3 Terminology or concept
O4 Requirement
O5 Protocol
O6 Mechanism
O7 Algorithm
O8 Data format or structure
O9 API or interface
O10 Experimental result or measurement
O11 Practice or recommendation
O12 Use case
O13 Threat model or security model
O14 Implementation or prototype
O15 Methodology or tool
O16 Other; requires an explicit description

For T5, an agenda or problem can be coded O16 with a description. New labels require a versioned protocol/manual change. Object and type totals may exceed the number of events because classification is multilabel.

Evidence observations

Keep every EV-* observation individually, with source URL, preserved artifact, SHA-256, version, passage, location, event date, date precision and collection time.

Codes Observation family
EV-CIT-NORM, EV-CIT-INFO, EV-CIT-POSSIBLE Normative, informative or not-yet-classified citation
EV-LINEAGE Documentary continuity
EV-TEXT-USE, EV-TEXT-DERIVATION Located use or derivation
EV-ADOPTION Adoption process
EV-MEETING, EV-SLIDE, EV-MAIL Meeting, slide or mailing-list statement
EV-CHARTER, EV-BOF Charter or BOF evidence
EV-AUTHOR, EV-CHAIR Person participation or role
EV-CODE, EV-IMPLEMENTATION Code or implementation
EV-ISSUE, EV-COMMIT, EV-PR Development activity
EV-OTHER Another described source

For each observation, describe whether the relationship is indirect, explicit or independently corroborated. Copies of the same declaration are not independent corroboration. Preserve contradictions and unresolved limitations.

Legacy E0–E5 descriptors have no universally ordered strength. Do not add, average or select the maximum label to confirm transfer. Apply the mechanism-specific conditions and labeling manual.

Separate discovery from confirmation

CIT/CONT/EVOL/FASE, ORG_* (including ORG_AGENDA_ADOPTION), HUM_SHARED_AUTHOR and HUM_AUTHOR_INTERSECTION describe discovery, not confirmed T labels. See discovery. Source types such as minutes or charters are not transferred objects O1–O16. Shared addresses remain unverified person hints.

An independent author intersection can be discovered without an established contribution or base event. Its pending status is not a T6 finding. Charter publication/approval evidence can support the charter chronology without confirming source-work chronology, adoption or a mediation role.

Use the review workflow to record located evidence, independent decisions and T6 dependencies. O5 means a technical communication protocol; it is not the study plan.