Portable Social Value Graph: What GlobaX Has Demonstrated in Production

What PSVG is

The Portable Social Value Graph (PSVG) is GlobaX's answer to a simple problem: when a post leaves a platform, it usually loses its history. Who made it, what it was, and where it came from all disappear the moment it crosses the boundary.

PSVG gives each shared social object a portable, verifiable reference to its own origin. The reference travels. The private identity behind it does not.

What was demonstrated in production

One genuine production social object completed the full path end to end on the live system: signed share → external transit → verified return → attribution → owner journey. The run used a real authenticated account and a separate unauthenticated browser session. No test harness, no staging environment, no synthetic data.

What actually travels in the public share link

What GlobaX verifies on return

When a visitor arrives through the shared link, the production system resolves the opaque reference back to the originating social object, reconstructs the canonical signed payload and verifies the signature on its own servers. The visit is recorded as a privacy-preserving hashed return event, repeat visits from the same visitor are deduplicated per day, and an attribution edge is written into the value graph linking the return to the original content.

The mechanism fails closed: if verification does not succeed, nothing is attributed.

Create → Prove → Share → Leave → Return → Verify → Attribute → Journey

1. 1

   Create. A person posts something real on GlobaX.

2. 2

   Prove. The action is recorded as a verifiable platform record.

3. 3

   Share. The share issues a sealed, server-signed share envelope.

4. 4

   Leave. The public link travels outside GlobaX carrying one opaque reference.

5. 5

   Return. Someone opens that link and comes back through it.

6. 6

   Verify. GlobaX rebuilds the signed payload and checks it on its own servers.

7. 7

   Attribute. The return is linked back to the original social object.

8. 8

   Journey. The owner can see the resulting journey of that object.

Why the privacy-minimal design matters

What VALIDATED WITH OBSERVATIONS means

It means the corridor completed on real production infrastructure, and the things that were not fully proved are stated rather than hidden. It is not a claim that PSVG is validated in every possible scenario.

One defect was also found and fixed during validation: an early run exposed a timestamp canonicalisation mismatch that caused verification to fail closed. The correction was implemented, the previously failing record then verified naturally, and a completely fresh end-to-end run passed. The failure and its fix are part of the evidence trail.

Current limitations

• Anonymous self-return is bounded, not fully prevented. Public share links must stay open to unauthenticated visitors, so the system deliberately cannot prove whether an anonymous returner is the original sharer. The residual is bounded to at most one non-payable return record per visitor per day per link.
• The external session was independent in identity, not in network. The unauthenticated visitor used a fully separate browser session but shared the same egress network as the authenticated account. This is recorded as a limitation.
• Correctness, not scale. The run proved that the path works, not how fast it works or how far it scales.

What this milestone does not claim

• No blockchain, OpenTimestamps or third-party ledger was used.
• No third-party platform integration participated in this validation.
• No performance, latency or scale benchmarks were measured — this was a correctness run, not a load test.
• No payouts, earnings or real-money settlement were involved. The demonstrated path is non-payable.
• No claim that anonymous self-return is fully prevented.
• No claim of independent public-key cryptographic verification by outside parties.
• No claim that later phases are live.

P0–P3 closed / P4–P8 held