The Internet of Value
Back to The ~WellbeingIdentity Rendering Architecture

Chapter 6 of 11 · 3 min read

One Identity Traced End to End

Narrative public and replay paths showing exactly what is included, excluded, and never inferred.

The ~WellbeingIdentity Rendering Architecture · v0.2 · edition history ·

Quick Answer

The public route is: identity reference → consent check → minimised public projection → Foundation → shared renderer. The replay route is: canonical slice → completed transition → replay input → owner-authorised replay projection → Value Log Replay. Neither route is a disguised export of a private identity record.

This is the core proof of the architecture. It is best understood as two short walks rather than one abstract flowchart.

Walkthrough one: a public profile

Someone reaches a Foundation profile. Foundation does not start by asking a renderer to retrieve a person. The identity reference is evaluated against the relevant consent purpose. If that purpose is active, a minimised public projection can be made available to Foundation. Foundation renders public-facing labels and consented summaries using the shared portrait. If the permission has expired or been revoked, the public view is no longer available.

01Identity reference

Stable anchor identifies the intended subject.

02Consent check

Purpose and disclosure scope are evaluated.

03Public projection

A minimised, public-purpose view is assembled.

04Foundation portrait

The renderer presents only the supplied public reading.

Figure 3. Public projection lifecycle. Permission precedes rendering; the portrait never upgrades its own input.
May include
  • Public display name
  • Disclosed node labels
  • Consented public summaries
  • Projection metadata
Must exclude
  • Private facets and evidence URLs
  • Activity or audit records
  • W transitions and individual values
  • Performance routes and identity write capability

The critical distinction is practical, not rhetorical: excluded data is not shipped and hidden with CSS. It is absent from the public projection.

Walkthrough two: an owner-authorised replay

Replay begins with a canonical slice and a completed transition. The event’s settlement context is shaped into a replay input. An owner-authorised replay projection then lets Value Log Replay render the relevant reading, timeline controls, and any separate performance route. Selecting a ring for inspection pauses playback but does not alter canonical event data; timeline, scrubber, event-list, swipe, and keyboard navigation restore the intended Identity State focus.

01Canonical slice

Settled context is retained by Value Log.

02Completed transition

A bounded replay input is prepared.

03Replay projection

Owner-authorised reading for replay purpose.

04Value Log Replay

Presentation and inspection, never event mutation.

Figure 4. Replay lifecycle. Replay explains a completed transition; it does not publish it or rewrite it.
May include
  • Slice reference and settlement time
  • Pre-state, movement, and post-state descriptors
  • Node label
  • Separate Performance route where relevant
Must exclude
  • Raw narrative and undisclosed facets
  • Public publication permission
  • Identity write capability
  • Any claim that Pilot W is canonical WellbeingScore

No real identifier, history, private evidence, credential, or individual Pilot W value is required to understand either path. That is the point of the example.

~

End of signal.