EDM Schema
Implementation Profiles
EDM artifacts are structured at three depth levels. Choose the profile that matches your compliance requirements and use case.
Overview
Implementation Profiles define which EDM fields are required for a valid artifact. Essential is the minimum viable entry point. Extended adds longitudinal depth. Full provides the complete representational manifold.
Choosing a profile: Start with the minimum depth your use case requires. Memory platforms typically start with Essential. Coaching and therapy platforms benefit from Extended or Full. Regulated contexts require Full.
Available Profiles
Essential
24 fields
Minimum viable artifact for session coherence
The lightweight entry point for EDM adoption. Primary emotion, narrative arc, and governance metadata without clinical overhead.
Use cases:
Extended
50 fields
Full narrative and emotional topology
Adds longitudinal depth with full Constellation, key Milky_Way fields, and essential Gravity salience scores. Track emotional patterns over time.
Use cases:
Full
96 fields
Complete representational manifold
All 10 domains fully populated. The affective substrate for platforms building persistent, sovereign emotional memory. Required for regulated contexts.
Use cases:
Profile Comparison
Quick comparison of what each profile includes and supports.
| Feature | Essential | Extended | Full |
|---|---|---|---|
| Field count | 24 | 50 | 96 |
| Core domain | |||
| Constellation (full) | Partial | ||
| Gravity (salience) | Key fields | ||
| Milky_Way (context) | Key fields | ||
| Impulse, System, Crosswalks | |||
| Compliant conformance | |||
| Sealed conformance | |||
| Certified conformance | |||
| VitaPass binding |
Adoption Pathway
Start with the minimum depth your use case requires. Progress as compliance requirements evolve.
Essential
Minimum viable entry. 24 fields for session coherence. Start here for memory integration and agent frameworks.
Extended
Longitudinal context. Add relational dynamics and temporal patterns when users need tracking across sessions.
Full
Complete manifold. Required when enterprise customers need audit, certification, or EU AI Act compliance.
How to select a profile
Profile selection works at three levels. Each level overrides the one below it.
1. Per-request (highest priority)
Override the profile for a specific extraction call.
// Override profile for this call only
const response = await fetch(
'https://deepadata.com/api/v1/extract',
{
method: 'POST',
headers: {
'Authorization': 'Bearer dda_live_...',
'Content-Type': 'application/json',
},
body: JSON.stringify({
content: '...',
profile: 'extended',
}),
}
)2. API key default
Set a default profile for all extractions using a specific key. Applies when no profile is passed in the request.
3. SDK auto-detect (fallback)
If no profile is set at the request or key level, the SDK selects based on content richness. Extended is the recommended default for most use cases.
Recommendation: Set Extended as your API key default and override to Full only for clinical or regulated contexts.
Partner Profiles
Partner profiles are named, versioned field manifests registered against a canonical base profile. They enable vertical-specific field selection — a therapy platform can receive exactly the 24 clinical fields it needs without paying inference cost for all 96 Full profile fields.
A partner profile artifact declares its profile ID in meta.profile using the partner: prefix:
{
"meta": {
"profile": "partner:com.deepadata.therapy.v1",
"version": "0.8.0"
}
}The partner: prefix is the discriminant. A reader encountering a partner: prefixed value knows immediately that registry resolution is required to determine the full field manifest. Canonical field values present in the artifact are fully interpretable without registry access.
Reference Partner Profiles (EDM v0.8.0)
Four reference partner profiles are defined in EDM v0.8.0:
partner:com.deepadata.journaling.v1
Base: Extended. 16 fields.
Focus: identity continuity, arc pattern over time.
partner:com.deepadata.therapy.v1
Base: Full. 24 fields.
Focus: session continuity, clinical depth, recurrence and tethering.
partner:com.deepadata.companion.v1
Base: Extended. 18 fields.
Focus: relational depth, emotional state, identity continuity across sessions.
partner:com.deepadata.wiki.v1
Base: Extended. 17 fields.
Focus: significance classification for PKM and wiki article generation.
All four reference profiles meet the Certification Minimum Bar (10+ affective fields).