~The Internet of Value~WELLBEING IDENTITYMy identity Product evolution · January–October 2026
A dated record of the ideas, experiences and engineering behind Wellbeing Identity.
Identity began as a specification. Word Wallet became its working runtime; the shared Aura connected its views. The open private beta supports Google entry, guided authoring and saving. Value Log now carries that Identity connection into private voice logging, with a table to check and spoken corrections.
January–May 2026
The earliest retained design gathered background, learning, capabilities, values and story around one person. Identity was the continuity between different parts of life.
The January source called Identity a boundary object, not the current Wellbeing Identity protocol. This is the first surviving repository record, not a claim about when the idea was first conceived.
Separate maps made background, learning, skills, values and life story easier to describe. The identity began to have a vocabulary beyond a conventional profile.
Given, Earned, Skill, Moral and Story mappings were formalised in the specification. Historical terms and hierarchy are preserved in their source records; they are not silently rewritten as today’s schema.
Identity became a living state connected to the rest of the system, with eight layers and a clear boundary around disclosure.
The v0.1.7 canonical-layers paper established the protocol, node, facet and signal hierarchy. Validated flows inform Wellbeing Identity; filling in a profile does not calculate a score.
The standalone Explorer explored a more human introduction: an identity world, an eight-layer reveal and a prompt for each layer. It was a prototype for understanding the idea.
A separate mobile-first Explorer repository recorded the vertical slice. Its scenes were exploratory, not a production signup service or a replacement for the later Identity runtime.
June 2026
Word Wallet Web entered as the service behind sign-in, member identity and consent. Human-facing identity profiles also appeared on the Foundation website.
The first Word Wallet service supported invite-gated authentication, custodial did:iov member records, consent and registered-expression research operations. Foundation separately introduced readable public profile pages. The protocol and its runtime remained distinct.
An identity could be formed without making every part public. The person could choose which details to disclose.
Granular consent separated identity formation from publication. Word Wallet also bounded sessions and retention. A later code release or import is not permission to publish someone’s data.
Email sign-in gained clearer return and recovery paths, including when an email opened in another tab. Access to identity was kept separate from creator eligibility.
Successive PKCE fixes preserved the verifier across callbacks and resends, then handled cross-tab completion. A minimal member identity did not become proof of workshop completion or permission to create expressions.
July–August 2026
Optional experimental wellbeing and community readings could accompany an identity, with their own sharing choices.
Pilot W and community-value projections were separately consented and minimized. Pilot W remained experimental; it was not the later issuer-specific Founder WellbeingScore and did not expose raw activity or narrative.
Public and private experiences began using the same eight-ring Aura grammar. Rings became selectable by pointer, touch and keyboard.
Shared packages were published on July 18; the following day established the interactive eight-ring grammar and private owner-projection contract. Shared geometry did not make the renderer an authority over identity values or consent.
Identity gained its own private member home. The public website showed only what the person chose to share, down to a ring and its individual details.
Word Wallet added the Identity home and private-by-default sharing controls. Foundation switched to the minimized owner-approved response. Ring switches became parent boundaries for their facets.
A person could return from Identity sign-in to Value Log or the Checker instead of starting the journey again.
Short-lived, bounded handoffs connected applications while their sessions and private data stayed separate. These handoffs did not turn workshop participation into a universal signup requirement.
Updating or restoring an identity no longer meant resetting what the person shared. Public ring readings also became steadier and easier to inspect.
Signed projection revisions and rollback were separated from owner disclosure settings. The retained production release record documents the rollout; new values did not silently enable public switches.
A starting point and the changes that followed it became separate ideas. The history of how a baseline was formed mattered as much as the latest reading.
Genesis was specified and implemented as a private, issuer-policy-specific projection. Identity layers informed evidence; they were not extra score components or prestige points. Public disclosure remained an independent owner choice.
The public portrait put the Aura first and gave wellbeing, community recognition and historical readings their own places. Access to deeper history became an owner-reviewed request.
The shared renderer source released 0.2.5. Public presentation and disclosure/history-grant work kept movement, recognition, legacy Pilot W and private evidence distinct. A later coordinated rollout records when consumers aligned.
The service behind Identity strengthened how separately consented observations were stored, corrected and deleted. Those records did not automatically become identity facts.
The private V2 observation ledger and Data API lockdown preserved an allowlisted, owner-scoped boundary. The production canary was documented; expression activation and broader canaries remained separate. No public narrative feed was created.
A public explanation connected the identity experience to the wider system and made its role easier to discuss.
The Foundation published a Sign in with Wellbeing Identity article. This was documentation of the concept, not evidence that Google sign-in or the later self-guided builder had shipped.
October 2026
Phone readings opened in a sheet above the map. Desktop selections stayed steady. Complete lists, structured details and sources became readable, and the owner could add videos, certificates, projects, links and milestones.
The existing Identity home gained separate private context drafts, reviewed publication and withdrawal. Source cards stayed outside ring geometry. The verified release aligned renderer 0.2.5 and contracts 0.1.4 across consumers; deployment did not publish an owner’s draft.
We explored a person-led journey: begin with a story, move between layers, review private words and consider sharing later. The first clickable draft tested the sequence; its visual direction was not accepted.
A repository/deployment reconciliation showed that evidence editing and public readings already existed. The new work would be independent admission, Google sign-in and self-authored private identity. A dedicated Google Cloud project was created; Google authentication was not configured or shipped.
The direction became more visual and more precise: explain all eight layers on arrival, use one clear invitation, tell a story after sign-in, then arrive at a full private identity. The visitor journey and the technical process were drawn as separate storyboards.
Original document, preserved unchanged. Design proposals are not shipped features.
The planned routes, full private /me destination and optional sharing path are documented separately from the underlying services. The flows below are preserved as reviewed design documents. This evolution page records the discussion; it does not launch the proposed builder or enable Google sign-in.
Original document, preserved unchanged. Design proposals are not shipped features.
Google sign-in and a signed-in Connect Google option are prepared for existing Identity holders. Email links remain available. Live Google configuration and the real account connection still need to be completed.
The focused native release reuses the existing Supabase member and DID, with separate PKCE and account-bound linking. Value Log returns retain their signed continuation. It adds no authoring tables, changes no sharing choices and does not open new member registration. The guided beta remains unreleased.
Existing Identity holders can now sign in with Google while keeping their email link. The first real Google sign-in opened the original Identity with its existing details and sharing choices. Continue with Wellbeing Identity also returned successfully to the same private Value Log.
The exact production commit was verified before the real Google return. The original DID and all saved sharing controls matched the protected baseline; the Value Log private portrait and eight-ring public profile still loaded. New member registration remains closed. The guided authoring beta and its database changes have not been released.
A separate Google account has now started with Story, saved private records and supporting evidence, left and returned to the same Identity, and downloaded its full saved identity. The journey covers all eight canonical rings and 50 facet paths using the existing Aura. Written guidance is available in every ring; guide videos can be added deliberately. Access remains limited to the release trial while final opening checks finish.
The production trial verified a new ordinary member with no founding status, workshop association, creator credential or public profile. Six repeatable certificate records and correctly linked private evidence survived Google return and export. The original member’s DID, all 73 sharing controls, public projection and Value Log private portrait remain unchanged. New identity material stays private at the API boundary. A separate guide-only editor permission is being prepared; no broad administrator grant is needed.
The private beta is open to anyone signing in with Google. Begin with Story, explore all eight rings, add memories, background, learning, work and supporting evidence, then return to your full private identity at /me. Save at your own pace, export your identity or remove what you added. Each ring has written guidance and provision for one guide video. Your additions remain private; publication follows in a later release.
The beta extends the existing Word Wallet runtime and reuses its accounts, DIDs, evidence editor and shared Aura renderer. A registry covers all 50 canonical facet paths; signed imports stay attributed and read-only, and source-derived readings await their proper sources. Production acceptance verified Google admission, stable repeatable records, private evidence, return and full export. The original identity, sharing controls, public response and Value Log access were preserved. Guide administration has a dedicated narrow permission; it grants no platform administration. An environment-dependent build fixture was isolated and CI now exercises the open-production flags.
Google sign-in now carries your Wellbeing Identity into Value Log. Existing members return to their own records; other Identity members can open a separate private log, record activities, save, return, edit and export. New activities remain unassessed: they do not create a wellbeing score, credits or community membership. Identity details and public sharing stay in Identity.
Value Log reuses the existing Google provider through a short-lived, one-use DID handoff. It keeps its own session and owner-isolated encrypted activities in two shared tables. A fresh encrypted backup and restore-tested transaction preserved every original row across 76 tables, original access settings, triggers and the original DID. Live tests covered the original owner and a separate Google account, saving/editing/return and export preparation. A duplicate callback navigation caught during live testing was reproduced and corrected before acceptance. No scopes, credentials, founding status, calculation authority or public profile settings were granted to newcomers.
Native logging launched inside Value Log on 25 October. The next day, real narration exposed lost time context and too many questions. Today now prepares a read-only table from your voice. Speak again to correct or add something, then Submit Value Log. Missing effects remain unreported; an approved conversation can wait privately in Review. Identity, the existing public profile and the original founder policy are preserved.
The companion Value Log release keeps Sarvam transcription and its hosted GLM-5.3 conversation profile, with schema-constrained output and source-bound whole-table updates. Supported adjoining times remain proposals with visible uncertainty. Capture approval reuses encrypted draft storage, not a fabricated canonical event or score. Two identical-source 14/14 synthetic suites and 440 automated tests passed. Physical-device acceptance remains open. The Field Station policy is deployed but inactive; no invitations or reviewer activation are claimed.
Eight people gathered to log their 24 hours, and logging did not support the session reliably. People gave their time and trusted the product to capture their day. We had not proved the complete journey on real phones. The first recording protections were released on 27 October; the incident remains open until faithful long narration, recovery and each person’s own day work end to end.
Successful Google entry, short synthetic examples and passing builds were insufficient acceptance. Capture, transcription, complete activity readback, explicit approval, saved return and account-specific display require separate checks. The 24-hour DayClock is currently mounted only on the founder Today path and assumes India time; other accounts do not yet receive that view. One-person and two-account real-device acceptance must precede another group-readiness claim. Precise per-device causes remain unverified; participant narratives and private records are not published.
Recording tests exposed missing expected input. Value Log now keeps final audio, gives first and further voice messages the same visible ten-minute allowance, retries temporary uploads and shows a recovery choice when capture is unfinished or substantially returns no words. Normal use stays microphone, table, spoken correction and Submit. Full activity coverage and physical phone acceptance remain open.
The companion Value Log release adds optional capture diagnostics inside the existing encrypted draft and enforces readiness before structuring, its worker and confirmation. Deliberately using captured words is separate from approving activities. Candidate and merged-main checks pass, including 465 tests and isolated database preservation. Generated browser audio and a 600-second simulated-provider upload were checked; no real member log was processed. No migration, model/prompt, Identity, disclosure, founder policy or rollout switch changed.
Current experience · 26 October 2026
Wellbeing Identity has eight canonical rings: Given identity, Earned identity, Rented identity, Moral compass, Story, Skills, Identity state, and Consent and disclosure. The app supports private writing and sourced records. Validated state still requires the appropriate protocol sources; completing a profile does not create an assessed score.
Yes. The private beta is open to Google sign-in. Guided activities cover 50 facet paths, with saving and return. This authoring journey does not assign facilitated-workshop completion, founder status, credentials or skill levels.
No. New writing stays private. Existing published imports and evidence retain their owner sharing controls. General publication of newly authored identities is a later release.
Sign in through Wellbeing Identity to your separate private Value Log. Speak in Today, check the table, speak again to correct or add, then submit. Sarvam prepares the proposal; you approve it. Missing assessment facts can wait in Review without invented effects or scores.
Open work
Awaiting acceptance: the latest microphone journey on real devices, including permission, interrupted recording and accessibility checks. Synthetic tests are not a claim of universal speech accuracy.
Deployed, inactive: the invited Field Station policy. Enrollment, automated review and provisional calculation remain closed pending operator and participant acceptance. Its assumed 700 state is not a general assessment or Genesis qualification.
Content to add: every ring has written guidance and an optional video slot. Guide videos still need their correct links and deliberate publication; no links are invented.
Planned: general publication of newly authored Identity material, exact public preview and withdrawal. Existing public profiles retain their current controls. Read the detailed open-item register for ownership and acceptance evidence.
About this record
The early dates come from retained specification and application commits. They record when work entered source history, not necessarily when it reached production. The January language is historical; it is not presented as today’s protocol definition.
October 22–23 records include design discussions, preserved storyboards and verified releases. The first clickable draft was superseded after review. Proposed flows remain labelled separately from shipped behaviour; release records link to the deployed commit and acceptance evidence.
Illustrations are labelled as diagrams. The prototype capture uses fictional demo content. The original storyboard PDFs are preserved unchanged. No personal identity values, account activity or private participant records are reproduced in this written history.
Current protocol meaning belongs to the IoV Spec. A story or a completed profile does not itself create a validated WellbeingScore. Publishing a code update does not publish anyone’s identity.
