Implementation Profiles
Full Profile
The Full Profile populates all 10 domains completely. It provides the affective substrate for platforms building persistent, sovereign emotional memory — asymmetric longitudinal layered memory across sessions.
Overview
Full Profile is the complete EDM manifold. All 96 fields across 10 domains must be populated — no field may be null unless source content genuinely provides no extraction basis. This depth is required for Certified conformance and regulated contexts.
When to use Full: When your platform operates in regulated contexts, requires third-party certification, or needs complete representational depth for clinical, enterprise, or compliance documentation.
Required Fields
Full Profile requires all 10 domains to be fully populated. The extraction system MUST attempt population of all fields.
| Domain | Required Fields | Notes |
|---|---|---|
| meta | All fields | Full metadata |
| core | All 7 fields | Complete extraction |
| constellation | All 18 fields | Full emotional topology |
| governance | All fields | Complete governance |
| milky_way | All fields | Full context |
| gravity | All fields | Complete salience geometry |
| impulse | All fields | Behavioural vectors |
| telemetry | All fields | Processing metadata |
| system | All fields | System state |
| crosswalks | All fields | External references |
No null without basis: Full Profile fields may only be null when source content genuinely provides no extraction basis. The extraction system MUST attempt population of all fields.
Example Artifact
A Full Profile artifact with all domains populated. This abbreviated example shows the structural completeness required.
{
"meta": {
"id": "art_01HZ3G7K...",
"version": "0.8.0",
"profile": "full",
"created_at": "2026-03-08T10:30:00Z",
"owner_user_id": "user_12345",
"consent_basis": "consent",
"visibility": "private",
"pii_tier": "tier_3",
"source_system": "therapy_platform_v2",
"extraction_context": "clinical_session"
// ... all meta fields populated
},
"core": {
"anchor": "Processing childhood trauma",
"spark": "Mother's visit triggered old patterns",
"wound": "Unresolved abandonment fears",
"fuel": "Desire for authentic relationship",
"bridge": "Previous therapy progress with father",
"echo": "Age 7 separation experience",
"narrative": "Reclaiming agency in family dynamics"
},
"constellation": {
"emotion_primary": "grief",
"emotion_secondary": "anger",
"emotion_subtone": ["relief", "hope"],
"narrative_arc": "integration",
"valence_score": -0.4,
"arousal_score": 0.7,
"dominance_score": 0.5,
"temporal_orientation": "past_to_present",
"social_orientation": "familial",
"certainty_level": "emerging"
// ... all 18 constellation fields populated
},
"governance": {
"jurisdiction": "HIPAA",
"data_controller": "therapy_clinic_001",
"retention_policy": {
"basis": "legal_obligation",
"ttl_days": 2555,
"on_expiry": "archive"
},
"subject_rights": {
"portable": true,
"erasable": false,
"explainable": true
},
"processing_purpose": "clinical_treatment"
// ... all governance fields populated
},
"milky_way": {
"event_type": "therapy_session",
"location_context": "clinical_setting",
"associated_people": ["therapist", "mother_reference"],
"visibility_context": "therapeutic_confidential",
"tone_shift": "distressed_to_grounded",
"temporal_markers": ["childhood", "present_day"],
"environmental_factors": ["safe_space", "therapeutic_alliance"]
// ... all milky_way fields populated
},
"gravity": {
"emotional_weight": 0.89,
"valence": "mixed",
"tether_type": "developmental",
"recurrence_pattern": "triggered",
"strength_score": 0.85,
"decay_rate": 0.1,
"recall_triggers": ["family_contact", "holidays"]
// ... all gravity fields populated
},
"impulse": {
"action_tendency": "approach_avoidance",
"behavioural_vector": "integration_seeking"
// ... all impulse fields populated
},
"telemetry": {
"confidence_score": 0.92,
"model_version": "edm-extract-v2.1",
"processing_time_ms": 145
// ... all telemetry fields populated
},
"system": {
"certification_status": "certified"
// ... all system fields populated
},
"crosswalks": {
"session_id": "sess_clinical_001",
"patient_record_ref": "ehr_12345"
// ... all crosswalks fields populated
}
}Use Cases
Clinical documentation requiring complete representational depth. HIPAA-compliant emotional record keeping.
Article 5(1)(f) documentation. Third-party attestation of emotional AI processing with full audit trail.
Enterprise compliance and procurement requirements. Complete provenance and certification chain.
Memory infrastructure requiring asymmetric longitudinal depth. Complete manifold for sovereign emotional archives.
Conformance Levels
Full Profile artifacts are eligible for all three conformance levels: Compliant, Sealed, and Certified. Full is one of the two Certified-eligible profiles (along with Extended).
| Level | Full Profile | Description |
|---|---|---|
| Compliant | Valid EDM JSON. Schema-validated. | |
| Sealed | DeepaData-issued with registry entry. W3C Data Integrity Proof. | |
| Certified | DeepaData countersignature. Five compliance checks passed. Certificate permalink. |
Certified-eligible: Full Profile includes complete governance fields for full compliance attestation. Request conformance_level: "certified" with your /v1/issue call to receive DeepaData countersignature and certificate permalink.
VitaPass binding: Available at Sealed conformance for all profiles. Full Profile Sealed artifacts are addressable across vendor boundaries via VitaPass.
Longitudinal Subject Registry (Future)
Full Profile + Certified conformance enables entry into the longitudinal subject registry — a planned future capability for trajectory state tracking across certified artifacts.