Architecture
One model and shared rules.
Small modules separate semantic work from rendering, editing, IO and optional services.
| Modules | Responsibility |
|---|---|
| types | Core, scene and browser API contracts. |
| model, language | Qualified identities, indentation parsing, typed records and source patches. |
| profiles, defaults | Codex, profile rules and file > CSS > standard resolution. |
| execution | Fingerprints, budgets, cancellation and optional worker execution. |
| runtime | Immutable revisions, data providers, commands, lifecycle protection and history. |
| presentation, viewer | Profile scenes, tables, safe Markdown, navigation, inspection and capture. |
| designer | Editing controls using the shared viewer and command service. |
| verifier, standalone | Staged verification and local browser application shells. |
Versioned identity and updates
Definitions carry stable identity separate from the displayed label. Files retain their identity when included in a main workarea. Commands and data revisions check their base state so a stale operation cannot quietly overwrite newer work.
Boundary with Weaver
The DDN foundation is a standalone single-user client system. Commercial coordination, multi-user collaboration, meetings, media and server paging are Weaver responsibilities. None is required to open or edit a local DDN diagram.
Scope and qualification
The complete edition implements the adopted bounded profiles. Full standards execution and external certification are not implied. Browser, accessibility, performance and release qualification remain separate from the presence of a profile in the registry.