Emotional Data Model (EDM) v0.8.0

Fuente: Zenodo
Saved in:
Bibliographic Details
Main Author: Harvey, Jason
Format: Recurso digital
Published: Zenodo 2026
Subjects:
Online Access:
Tags: Add Tag
No Tags, Be the first to tag this record!
_version_ 1866901870255013888
author Harvey, Jason
author_facet Harvey, Jason
contents <p class="font-claude-response-body break-words whitespace-normal leading-[1.7]">The Emotional Data Model (EDM) v0.8.0 defines a governed, schema-bound representational architecture for encoding affective context as a stable, machine-interpretable data object. Unlike contemporary AI systems where emotional signals remain transient and architecture-bound, EDM externalises affective context into a structured manifold with explicit field definitions, in-band governance, and strict separation between representation, persistence, and computation layers. Artifacts are preserved within the .ddna envelope — a byte-stable container providing cryptographic integrity via W3C Data Integrity Proofs (eddsa-jcs-2022), sovereignty guarantees, and cross-vendor portability.</p> <p class="font-claude-response-body break-words whitespace-normal leading-[1.7]">v0.8.0 extends v0.7.0 with the Partner Profile system and two arc_type additions. Partner Profiles (Section 3.7.6) introduce a registered, versioned mechanism for vertical field selection: a partner profile declares a named subset of fields from a canonical base profile, enabling token-efficient extraction tailored to a specific deployment context while preserving the Profile Completeness invariant at the base profile level. The base profile determines LLM inference cost; the included_fields manifest determines API response payload. Partner profile IDs are declared in meta.profile using the partner: prefix (e.g., partner:com.deepadata.therapy.v1), enabling unambiguous discrimination without a registry lookup. Four reference partner profiles are defined for the journaling, therapy, companion AI, and significance wiki verticals. Two arc_type values are added — gratitude (moments of thankfulness and appreciation, structurally distinct from the emotion state joy) and authenticity (self-alignment and identity congruence) — bringing the canonical arc_type set to fourteen values. The Certification Minimum Bar is formalised: certification eligibility requires ten or more populated affective fields from the Core, Constellation, Milky_Way, Gravity, and Impulse domains, opening Certified conformance to Extended Profile and qualifying partner profile artifacts. The Essential Profile contains nine affective fields and remains ineligible for Certified conformance by design. No fields were deprecated in v0.8.0. No existing field meanings or enumeration values have been modified or removed.</p> <p class="font-claude-response-body break-words whitespace-normal leading-[1.7]">EDM addresses the representational deficit in current intelligent systems by transforming implicit emotional states into explicit, rights-bearing data objects capable of surviving across model generations, computational paradigms, and regulatory environments.</p>
format Recurso digital
id zenodo_https___doi_org_10_5281_zenodo_19555166
institution Zenodo
language
publishDate 2026
publisher Zenodo
record_format zenodo
spellingShingle Emotional Data Model (EDM) v0.8.0
Harvey, Jason
emotional data model
affective computing
EDM
partner profiles
AI memory
data governance
significance layer
.ddna
affective AI
W3C Data Integrity
eddsa-jcs-2022
VitaPass
representational architecture
<p class="font-claude-response-body break-words whitespace-normal leading-[1.7]">The Emotional Data Model (EDM) v0.8.0 defines a governed, schema-bound representational architecture for encoding affective context as a stable, machine-interpretable data object. Unlike contemporary AI systems where emotional signals remain transient and architecture-bound, EDM externalises affective context into a structured manifold with explicit field definitions, in-band governance, and strict separation between representation, persistence, and computation layers. Artifacts are preserved within the .ddna envelope — a byte-stable container providing cryptographic integrity via W3C Data Integrity Proofs (eddsa-jcs-2022), sovereignty guarantees, and cross-vendor portability.</p> <p class="font-claude-response-body break-words whitespace-normal leading-[1.7]">v0.8.0 extends v0.7.0 with the Partner Profile system and two arc_type additions. Partner Profiles (Section 3.7.6) introduce a registered, versioned mechanism for vertical field selection: a partner profile declares a named subset of fields from a canonical base profile, enabling token-efficient extraction tailored to a specific deployment context while preserving the Profile Completeness invariant at the base profile level. The base profile determines LLM inference cost; the included_fields manifest determines API response payload. Partner profile IDs are declared in meta.profile using the partner: prefix (e.g., partner:com.deepadata.therapy.v1), enabling unambiguous discrimination without a registry lookup. Four reference partner profiles are defined for the journaling, therapy, companion AI, and significance wiki verticals. Two arc_type values are added — gratitude (moments of thankfulness and appreciation, structurally distinct from the emotion state joy) and authenticity (self-alignment and identity congruence) — bringing the canonical arc_type set to fourteen values. The Certification Minimum Bar is formalised: certification eligibility requires ten or more populated affective fields from the Core, Constellation, Milky_Way, Gravity, and Impulse domains, opening Certified conformance to Extended Profile and qualifying partner profile artifacts. The Essential Profile contains nine affective fields and remains ineligible for Certified conformance by design. No fields were deprecated in v0.8.0. No existing field meanings or enumeration values have been modified or removed.</p> <p class="font-claude-response-body break-words whitespace-normal leading-[1.7]">EDM addresses the representational deficit in current intelligent systems by transforming implicit emotional states into explicit, rights-bearing data objects capable of surviving across model generations, computational paradigms, and regulatory environments.</p>
title Emotional Data Model (EDM) v0.8.0
topic emotional data model
affective computing
EDM
partner profiles
AI memory
data governance
significance layer
.ddna
affective AI
W3C Data Integrity
eddsa-jcs-2022
VitaPass
representational architecture
url https://doi.org/10.5281/zenodo.19555166