Back to The ~WellbeingIdentity Rendering Architecture

Chapter 3 of 11 · 2 min read

Ownership and System Responsibility

A precise responsibility map for the Spec, Word Wallet Web, Value Log, Foundation, renderer, and Explorer.

The ~WellbeingIdentity Rendering Architecture · v0.2 · edition history · Moses Sam Paul Johnraj

Quick Answer

The Spec owns vocabulary, node semantics, and the DID registry; Word Wallet Web governs verified owner binding and consent; Value Log owns canonical slices and Pilot W transitions; Foundation publishes public projections; the renderer owns interaction geometry; and Explorer owns its guided teaching scene.

Shared presentation is safe only when responsibility remains unambiguous. A useful architecture does not say that every system “owns the identity.” It assigns narrow work to each system and makes the hand-offs visible.

Semantic sourceSpec

Vocabulary, node semantics, DID registry.

Identity and permissionWord Wallet Web

DID-to-owner binding and consent.

Private event meaningValue Log

Canonical slices and Pilot W transitions.

Public publicationFoundation

Public projection and public narrative.

InteractionRenderer package

Ring geometry, focus, preview, selection.

TeachingExplorer

Native person-form, facets, and guided scene.

Figure 2. Responsibility is deliberately distributed. No public surface or shared component becomes an undisclosed substitute for identity authority.

A narrower claim about custody

This paper uses “private identity document” only where an owner and storage boundary have been established by the relevant system. It does not use the phrase as a catch-all for every value associated with an identity. The verified, narrower responsibilities matter more: owner binding and consent precede disclosure; Value Log retains its own canonical slices and transition records; Foundation receives publication material; and the renderer receives already-authorised display data.

Why the split is useful

This structure gives product teams freedom without confusing their authority. Foundation can improve public legibility without acquiring private evidence. Value Log can improve replay without changing identity semantics. Explorer can teach through an expressive native scene without being constrained by a production profile component. The renderer can become accessible and deterministic without becoming a policy engine.

That is not fragmentation for its own sake. It is a way to make each boundary testable.