41.2.0

What's Changed

• Fix top bar text scaling on small screens by @kojibai in #225

Full Changelog: v41.0.0...41.2.0

v41.0.0

v41.0.0 — Kai Sigil-Glyph Attestation (Proof of Breath™)

This release locks in the full proof-first verification loop: anyone can verify authenticity from a URL, and only the real holder can elevate that verification into live identity control via passkeys (Face ID / Touch ID), across devices — no database trust, no accounts, no “badge theater.”

Highlights

• Kai Sigil-Glyph Attestation panel now expresses the full chain clearly: Kai-Signature → Φ-Key → Proofs → Presence.
• Public URL verification proves a glyph is authentic and attested (KAS + Groth16), without requiring login.
• Live Ownership / Identity Control is proven only via WebAuthn passkeys (Face ID / Touch ID), preventing “ownership by forwarding.”
• Cross-device continuity: the same Φ-Key can be proven on iPhone and Mac with different biometrics because the proof is the passkey, not the biometric.

---

What shipped

✅ Verification that’s real (not UI)

• KAS VERIFIED + G16 VERIFIED are now first-class, always visible, and treated as cryptographic gates — not labels.
• Proof of Breath™ resolves as an output of verification (human-origin seal affirmed), not a claim.

🔒 Identity vs Sigil-Glyph Presence (the critical separation)

You now have two independent truths displayed as separate states:

• Sigil-Glyph: Present / Not present

  • “Present” means the sigil-glyph artifact (file/payload) is physically available in the current view/context.

• Identity: Verified / Not present

  • “Verified” means the viewer produced (or presented) the required identity proof.
  • URL-only contexts can verify proofs while still showing identity as not present unless the user performs the live control step.

This is exactly the behavior you wanted: authenticity is shareable, ownership is not transferable by forwarding.

🌬️ Inhale flow upgraded

• Inhale ΦKey is the single action to “bring the sealed ΦKey into the verifier.”
• Deep payloads reliably open in Expanded Views (no cramped mobile experiences).
• Works cleanly with previously saved glyphs that include the auth signature — old seals remain verifiable forever.

🔑 Passkey-based “I am this Φ-Key” proof (FaceID / TouchID)

• The verifier now triggers platform passkey prompts keyed to the specific Φ-Key being proven.

• iOS/macOS correctly surfaces different saved credentials (“passkey for 1AjR5…” vs “passkey for 1KsFn…”) and the flow remains seamless.

• Identity verification succeeds on:

  • iPhone via Face ID
  • MacBook via Touch ID
  • …because the biometric is only the unlock gate; the proof is the cryptographic signature bound to that Φ-Key.

🧾 Proof exports & shareability (Receipt-grade)

• Proof formats are now cleanly separated and exportable:

  • KPV-1 (Proof Capsule) for the compact, portable claim
  • KVPF-1 (Proof Receipt / Frame) for the full shareable verification context (hashes, canon, verifier URL/base/slug, etc.)

• Verification links are now capable of carrying proof receipt material (the r= payload pattern) so opening a URL can hydrate the verifier state without needing a database.

🧠 ZK bundle retention for sealed payloads

• Decoding logic now retains the full ZK bundle where previously it could be trimmed, ensuring exporters can embed the original proof into manifests / SVG metadata when needed.

---

UX / Stability

• Mobile verifier remains “no-scroll” at the page level; panels scroll only when necessary.
• Effect-safe derivations: no cascading render loops / no “sync setState inside effects” behavior.
• Small polish improvements to keep iconography and controls visually centered and consistent under motion/glow styling.

---

The net result (what this release means)

You now have a verifier that can say, with zero ambiguity:

• This sigil-glyph is real (URL-only verification: integrity + attestation + ZK validity)
• This sigil-glyph is present (artifact is in-hand / in-context)
• This person controls this Φ-Key (live passkey challenge-response via FaceID/TouchID)

That trio is the difference between “verified badge UI” and verifiable reality.

What's Changed

• Add Memory Lattice toggle and pulse viewer to Sigil Explorer by @kojibai in #193
• Raise pulse viewer overlay above panels and improve mobile popover by @kojibai in #195
• Enhance pulse viewer visuals (live sigil, compact chart, breath-sync) by @kojibai in #194
• Live pricing and chart for PulseHoneycombModal (real-time Φ/USD) by @kojibai in #197
• Stabilize KaiVoh modal input handling on mobile by @kojibai in #201
• Prevent honeycomb explorer overscroll refresh by @kojibai in #203
• Prevent honeycomb pull-to-refresh on mobile by @kojibai in #204
• Prevent mobile pull-to-refresh / reload in Honeycomb viewer by @kojibai in #205
• Prevent honeycomb viewer pull-to-refresh on mobile by @kojibai in #206
• OG: derive QR origin from request headers and fix PNG typing by @kojibai in #208
• Verifier: OG image endpoint, share/copy receipt UI, and embeddable badge by @kojibai in #207
• Fix verifier QR rendering in Proof Vessel by @kojibai in #210
• Fix verify slug parsing in serverless by @kojibai in #211
• Include KAS and ZK fields from shared receipt into embedded proof by @kojibai in #216
• Include KAS and ZK fields from shared receipt into embedded proof by @kojibai in #215
• Fix ZK verification from shared receipts by @kojibai in #214
• Add shareable verification receipt links by @kojibai in #212
• Update verify SEO metadata for shared receipts by @kojibai in #217
• Adjust Verify page header sizing on small screens by @kojibai in #221

Full Changelog: v40.3.0...v41.0.0

v40.3.0

What's Changed

• Restore periodic Sigil Explorer sync (phase‑locked breath timer) by @kojibai in #191
• Reduce Sigil Explorer sync polling by @kojibai in #190

Full Changelog: v40.0.0...v40.3.0

v40.0.0

Release Notes — 40.0.0 (Stability Baseline)

40.0.0 is the locked foundation release. The system is now stable enough to build forward without backtracking—networking, routing, and verification flows are sealed into a dependable base so we can ship the next wave: Memory Lattice, large-file streaming, and higher-order keystream intelligence.

---

✅ Highlights

• Stability locked

  • Core app behavior is now consistent across environments (dev + production), with fewer edge-case failures and far less operational noise.
  • This is the version we build from.

• Deterministic delivery & routing

  • Deep links resolve correctly.
  • Verifier assets serve reliably.
  • The app behaves like a true sovereign client—load, verify, navigate, continue.

• Proof-first architecture now “ready for scale”

  • Verification flows and artifact handling are now in a state where we can extend capability (streaming, lattice indexing, offline recall) without rewriting the foundation.

---

🔧 What’s Been Sealed in 40.0.0

Platform reliability (the unglamorous part that makes everything possible)

• Browser + host behavior is now predictable, not “works on one deploy and breaks on another.”
• The app can now act as a real transport layer for signed artifacts and memory objects.

API access hardened (quietly, but permanently)

• The app now prefers safe, production-consistent request paths and avoids failure modes that created runaway errors and retries.
• Failover behavior is more disciplined and less noisy.

Build and version integrity

• App build version injection is now consistent (VITE_APP_VERSION from BASE_APP_VERSION), making releases traceable and auditable.

---

🚀 What This Unlocks Next (Now Possible Because 40.0.0 Is Stable)

This release is the “foundation pour.” The next releases are the structure.

1) Memory Lattice (next major wave)

A real navigable, queryable memory structure—not just a list, not just a tree:

• Lattice-indexed memory (multi-parent, multi-lineage truth)
• Cross-linking between sigils / posts / derivatives
• Instant recall views: show how a sigil’s state evolves across pulses
• Coherence-first navigation: browse memory as a living structure, not folders

2) Large File Streaming (sovereign media + datasets)

Now that routing + transport is stable, we can ship:

• Chunked streaming uploads (large artifacts without breaking the app)
• Derivative glyph sharding (split a file into signed parts)
• Master-glyph reconstruction (reassemble deterministically into a playable stream)
• Offline-resumable transfers (pick up exactly where you left off)

3) Advanced Sync + Resilience

With a stable base, we can push real “unstoppable” behavior:

• Background-safe sync loops (without error storms)
• Multi-endpoint recovery (fallback without chaos)
• Deterministic reconciliation for registry merges and lineage updates

4) Verifier Expansion

The verifier becomes more than a checker—it becomes a portal:

• Proof bundles as first-class objects
• Stronger provenance surfacing (who authored, when, what it binds to)
• Faster artifact inspection paths for large payloads and streamed content

---

📁 Key Areas Touched (High Signal)

• src/components/SigilExplorer/apiClient.ts — stable access rules + disciplined failover
• src/components/SigilExplorer/sigilExplorerSync.ts — sync stability improvements
• vite.config.ts — build/version injection + local routing stability
• host rewrites (vercel.json or equivalent) — sealed deep link + verifier + /api/* routing

---

🧭 Roadmap Snapshot (Near-Term)

• 40.x: Memory Lattice foundations (indexing, cross-links, lattice UI primitives)
• 41.x: Streaming alpha (chunk protocol + master glyph + reconstruction)
• 42.x: Full sovereign media + offline resumable streams + lattice-native playback

---

Closing

40.0.0 isn’t flashy—it’s powerful. It’s the release where the platform stops fighting you and starts carrying weight. From here, the system can grow into the things it was always meant to be: a living Memory Lattice and a sovereign large-file streaming + verification layer built on proofs, not platforms.

What's Changed

• Improve honeycomb embedded sync and 3D depth by @kojibai in #174
• Optimize honeycomb sigil rendering with lightweight glyphs by @kojibai in #175
• Pulse atlas expand to honeycomb by @kojibai in #176
• Reduce edge requests with bundled output and broader caching by @kojibai in #178
• Adjust caching headers for JSON and webmanifest to force revalidation by @kojibai in #179
• Limit honeycomb explorer to internal data (disable network sync when embedded) by @kojibai in #180
• Defer heavy Sigil Explorer work on mobile/low-power devices to improve initial load by @kojibai in #182
• Scope StoryRecorder dot styles to prevent global dot bleed by @kojibai in #183
• Fix invalid base URL construction in SigilExplorer API calls by @kojibai in #184
• Restore lahmahtor proxy upstreams and add /api/lahmahtor route by @kojibai in #186

Full Changelog: v38.2.0...v40.0.0

v38.0.0

Φ Network — Major Release 38.0.0

Release Notes — 38.0.0
Name: Sovereign Verification Stack — Sealed
Theme: Ledger-truth verification + globally single-use receives + multi-generation lineage that does not break

---

What 38.0.0 Is

38.0.0 is the moment the system becomes a real value-transfer organism.
Not “a verifier page.” Not “a transfer feature.” Not “a cool SVG.”

This release represents the sealed convergence of everything we’ve been building across the 36.x → 37.x line:

• The glyph carries truth.
• The verifier renders that truth.
• The explorer tracks that truth.
• The network enforces that truth.
• And lineage survives generations without drifting, breaking tokens, or mis-rooting children.

This is offline-first, browser-native, deterministic value that remains verifiable and coherent without accounts, databases, or permissioned infrastructure. That’s what this is.

---

The Core Accomplishment

✅ The verifier no longer “guesses value”

It shows what the glyph actually contains, including remaining balance after debits, and only falls back to live valuation when the glyph has no embedded ledger.

✅ Receives are globally single-use (not just “local storage safe”)

A send can be received once—even across cache clears, fresh browsers, and new devices—because receive locks are now globally respected through explorer sync + Lahmahtor ingestion + online remote verification.

✅ Multi-generation transfers don’t collapse

Children, grandchildren, and deeper derivatives now keep:

• parent tokens preserved
• origin hints propagated
• direction explicit
• root detection correct
  so locks, lineage, and display remain consistent everywhere.

✅ The explorer behaves like a ledger, not a confusing tree

Pending vs sealed outflows are readable, mixed states are explicit, parent rollups don’t double count, and direction labeling never lies.

---

What Shipped in 38.0.0

This is the “major cut” that formalizes the sealed system.

---

1) Verify = Ledger Truth (Balance-First)

On-glyph balance display for transfer/receive glyphs

When a glyph includes an embedded ledger of debits, the verifier now computes and surfaces:

• BALANCE Φ = remaining amount after embedded debits
• BALANCE USD = BALANCE Φ × deterministic USD/Φ

This balance is shown:

• in the header pill (next to the seal)
• and inside the valuation panel

Live valuation remains the fallback

If no ledger data is present, Verify continues to show:

• LIVE Φ
• LIVE USD

Why this matters

Because this is the difference between a UI that looks correct and a verifier that is incapable of lying.
A transfer glyph is not the origin. A transfer glyph is the state of value after movement. 38.0.0 makes the verifier obey that.

---

2) Single-Use Receive Channel (Bank-Grade Replay Resistance)

The receive flow is now globally sealed

Receives are enforced as single-use across:

• local sessions
• cache clears
• new browsers
• different devices

Multi-layer locking is now real enforcement, not vibes

The system performs receive checks across:

• local (offline-first safety)
• local registry memory (explorer awareness)
• remote explorer index (clean-browser protection)

Online remote verification is required before completing a receive

When online, the receive cannot complete until remote receive-lock verification confirms it has not already been received globally.

Receive locks propagate with rich memory-stream data

Receive updates now travel through Lahmahtor ingestion with richer payloads (receiver metadata included), and local registry updates trigger immediate inhale-queue flush so the lock exhale happens without needing UI open.

Why this matters

Because a “value transfer system” that allows replay receives is dead on arrival.
38.0.0 establishes a provably single-use receive channel in the browser, in the wild, under real user behavior.

---

3) Multi-Generation Lineage Coherence (Children + Grandchildren + Beyond)

Lineage tokens are preserved

Share/publish URLs preserve the parent token so downstream consumers can reconstruct lineage correctly across generations.

Origin propagation is authoritative

Origin URLs are resolved and propagated from the local memory registry so:

• children don’t drift to the wrong root
• the verifier and explorer classify the same glyph the same way

Direction is explicit in payloads

Send flows explicitly carry:

• transferDirection: "send"
• originUrl
  so grandchildren aren’t misclassified and locks verify correctly.

Explorer root detection is tightened

Entries that carry transfer hints / transfer moves are no longer treated as “origin roots.”
This prevents derivative artifacts from becoming roots and incorrectly pulling lineage under the origin.

Why this matters

This is where most systems die: generation 2, 3, 4 starts drifting and the “tree” becomes a lie.
38.0.0 seals lineage as a real chain, not a fragile inference.

---

4) Sigil Explorer = Human-Legible Ledger

Parent/child pending clarity without double counting

Parent nodes surface child pending/derived activity clearly while preventing parent value from being counted twice.

Mixed exhale state readability

Mixed pending + derived exhale states are clearly displayed and badge-coded so you can scan the tree instantly.

Pending UI cleanup (no duplicate negative pill spam)

Pending display now prioritizes a single clear status instead of redundant duplicate amounts that look like double debits.

Direction-correct labeling and tooltips

Outgoing sends no longer fall back to inhale labels. Labels and tooltip verbs follow explicit send/receive direction, every time.

Breath-truth terminology sealed across UI

Derived → Exhaled
Pending → Exhale (pending)
Received inhales use past tense where appropriate, and details append pulse numbers when available.

Why this matters

A ledger that confuses the human mind is a ledger that fails adoption.
38.0.0 makes Explorer readable at the speed of sight while staying anchored to canonical transfer truth.

---

5) Reliability Under Real Network Behavior

Remote receive lock verification resilient to HTTP caching/failover

Remote checks no longer fail spuriously when pages return:

• 304 Not Modified
• empty responses during failover
  and pagination completeness is only marked after successful fetches—no partial scan caching.

Why this matters

Global integrity enforcement must not break under normal internet behavior.
38.0.0 makes remote verification durable.

---

6) System Readiness: Speed, Sync, Brand, Session Stability

38.0.0 stands on the hardened foundation shipped across 37.x:

• instant-paint home experience with lightweight fallback ticker while heavy UI loads
• Sigil Explorer sync cadence + event-triggered resync + reseed on remote truth deltas
• live Φ + USD pill surfaces across explorer nodes/origin/transfers
• Φ brand mark standardized via phi.svg with accessibility support
• KaiVoh session persistence + validation + cross-tab coherence

This matters because it makes the system feel inevitable—fast, stable, and coherent under daily usage.

---

What This Release Enables (In Plain Language)

With 38.0.0 you can:

• Open a glyph offline and see what you truly hold (remaining balance, not origin illusion).
• Verify value deterministically and consistently across the app.
• Receive a send exactly once globally when online—no replays, no duplicate claims.
• Move value across multiple generations and keep lineage intact.
• Trust the explorer’s pending vs exhaled story without doing mental accounting.

This is sovereign, offline-auditable value packaged in a format humans can use.

---

Compatibility & Migration

• No schema migrations required.
• Receive state is encoded implicitly in memory stream data (direction/nonce/hash/receiver fields).
• Pending is the absence of a receive-lock match; received is the match.
• The system remains offline-first; global sealing activates when online.

---

Where We’re Going Next (The Real Next Layer)

38.0.0 seals value + transfer + verification as a coherent stack.
The next phase is not “basic improvements.” It’s expansion into what this stack was built to unlock:

1) Sovereign Media Lineage (KSFP-1 specialization)

Large-file and video lineage using derivative glyph chains, segment sealing, and deterministic reconstruction—so content is owned, verified, and playable without centralized hosting.

2) Creator Signature Bundles as a Native Primitive

Every post, media object, and derivative carries an embedded bundle tied to the creator—verifiable offline, traceable across lineage, and resistant to platform theft.

3) Network-Scale Memory Stream Ergonomics

Sharper convergence UX, richer explorer filtering, and higher throughput for inhale/exhale without sacrificing determinism or offline survival.

4) Public Spec Hardening + Developer Surface

Turning these primitives into a clean external interface: a developer-grade spec + SDK surface that makes integration feel inevitable (the “Stripe moment,” but for sovereign verification).

---

Closing Seal

38.0.0 is not a normal “major release.”
It is the sealing of a new class of system:

• Value embedded in glyphs
• Verified offline
• Enforced globally when online
• Lineage preserved across generations
• Readable by humans without trust

This is Φ Network behaving like what it is:
**a sovereign verification and transfer re...

v38.2.0

Release Notes — 38.2.0

Attestation — Full-screen Verify portal (no route change)

Motivation

• Provide an Attestation entry in the Atrium that opens the existing Verify experience as a full-screen modal popover without navigating away from the shell.
• Keep Verify isolated in a portal so it can be dismissed via backdrop click or Esc without impacting routed panel state.

Description

• Added a lazy-loaded VerifyPageLazy and a new VerifyPopover component that mirrors existing popover behavior:

  • portal mounting
  • backdrop handling
  • Esc close
  • focus management
  • useBodyScrollLock

• Introduced verifyOpen state with openVerify / closeVerify handlers and rendered:

  • <VerifyPopover open={verifyOpen} onClose={closeVerify}> … </VerifyPopover>
    inside AppChrome to host the Verify modal.

• Added an Attestation tile button to the Atrium nav that opens the popover, styled via .nav-item--button to preserve the tile look while using a semantic button.

• Kept styling consistent by reusing explorer-pop panel classes with additional verify-pop modifiers for the attestation portal.

Testing

• Started the dev server with:

  • npm run dev -- --host 0.0.0.0 --port 4173
    and confirmed the app launched and served successfully.

• Ran a Playwright script that navigated to /, clicked Attestation: Verify ΦKey, and captured:

  • artifacts/attestation-modal.png
    successfully.

---

KaiVoh — Edge-to-edge full-viewport modal

Motivation

• The KaiVoh panel felt visually constrained compared to the Attestation/Explorer portal and should open full-screen for a more spacious, app-like experience.
• Match Attestation/Explorer full-viewport presentation and remove inner padding + rounded framing that restricts content.

Description

• Updated src/components/KaiVoh/styles/KaiVohModal.css to make the modal backdrop and container occupy the full viewport:

  • changed layout from centered to stretched
  • removed inset padding

• Set the container to width: 100% and height: 100%, adjusted max-height to use --kai-vh for stable viewport sizing, and removed rounded border-radius so the modal becomes edge-to-edge.

• Adjusted backdrop alignment (align-items / justify-content) to stretch, cleared padding, and lowered .kai-voh-body min-height to 0 so the inner scroll region expands correctly.

---

Verifier — On-glyph ledger balance surfaced (BALANCE vs LIVE)

Motivation

• The verifier should display the glyph’s on-glyph balance for transfer/receive glyphs instead of showing the origin/root value.
• When a glyph embeds a ledger of debits, the remaining balance must surface in the header and valuation panel.
• If no ledger exists, preserve the existing live valuation as the fallback.

Description

• Added a small ledger parser readLedgerBalance and DebitLoose type to extract originalAmount and compute remaining from embedded debits in the verifier payload.

• Reworked valuation logic to compute:

  • displayPhi / displayUsd as ledgerBalance.remaining when present
  • otherwise fall back to liveValuePhi

• Updated LiveValuePill to accept label and ariaLabel so the UI clearly reflects BALANCE vs LIVE.

• Adjusted valuation mini-fields to label/show glyph balance vs live valuation accordingly.

• All changes contained in src/pages/VerifyPage.tsx (value computation + UI label updates).

---

Verifier header chips — Direct entry actions (no new UI surfaces)

• Clicking Proof of Breath™ under the Verifier header opens Attestation (Verify popover).
• Clicking ☤Kai-Signature™ opens Mint ΦKey (Mint route/modal), keeping the shell intact and the interaction instant.

---

Summary

38.2.0 locks the Atrium into a true KaiOS-style shell: portals are full-viewport, dismissible, and isolated; KaiVoh is finally edge-to-edge; and the verifier now reports the actual on-glyph balance when a ledger is present—without breaking the live valuation fallback.

Full Changelog: v38.1.0...v38.2.0

v38.1.0

What's Changed

• Add attestation verifier modal in the Atrium by @kojibai in #171
• Make KaiVoh modal fullscreen by @kojibai in #172

Full Changelog: v38.8.0...v38.1.0

v37.8.0

Φ Network — Verifier + Sigil Explorer (v37.8.0)

Release Notes — 37.8.0
Theme: On-glyph balance truth in Verify, multi-generation lineage coherence, resilient receive-lock verification, and direction-correct transfer semantics

---

Release Summary

37.8.0 is a precision integrity release across the Verifier and Sigil Explorer.
We made the verifier show the glyph’s actual on-glyph remaining balance (when a debit ledger is embedded) instead of incorrectly inheriting origin/root value. We also sealed multi-generation transfer coherence: lineage hints now propagate through share URLs and registry lookups so the verifier and explorer agree about origins, parents, and locks across grandchildren and beyond.

Finally, we hardened global receive-lock verification against real-world remote behaviors (304/empty pages) and corrected transfer UI labeling to always follow explicit send/receive direction—no more “incoming-looking” outgoing transfers.

---

✨ Highlights

✅ Verifier now displays on-glyph balance (when present)

Transfer/receive glyphs now surface remaining balance computed from embedded debits. If no embedded ledger exists, the verifier falls back to existing live valuation.

✅ Multi-generation lineage + locks now propagate correctly

Grandchildren transfers now carry authoritative originUrl + parent token across share/publish payloads so receive/send locks verify consistently across generations and the explorer stops misplacing children on the origin root.

✅ Remote receive-lock verification is resilient to 304/empty pages

Global receive checks no longer fail spuriously when remote pages return 304 Not Modified or empty responses during failover.

✅ Direction-correct labels + tooltips in Sigil Explorer

Transfer labels and tooltip verbs now derive strictly from the known transfer direction, preventing outgoing sends from being mislabeled as incoming.

---

✅ What Shipped

1) VerifyPage — On-Glyph Balance Truth (Ledger-Aware Valuation)

Motivation

• The verifier should display the glyph’s on-glyph balance for transfer/receive glyphs, not the origin/root value.
• If a glyph embeds a ledger of debits, the verifier should compute and show the remaining balance in the header and valuation panel.
• If no ledger exists, existing live valuation remains the fallback.

Implementation

• Added a small ledger parser:

  • readLedgerBalance + DebitLoose type
  • Extracts originalAmount and computes remaining from embedded debits in verifier payload

• Reworked valuation UI:

  • displayPhi / displayUsd use ledgerBalance.remaining when present
  • otherwise fall back to liveValuePhi

• Updated LiveValuePill:

  • accepts label + ariaLabel
  • displays BALANCE or LIVE depending on source

• Updated valuation mini-fields to reflect:

  • glyph balance vs live valuation labeling and display

File scope: src/pages/VerifyPage.tsx (value computation + UI label updates only)

---

2) Multi-Generation Transfer Lineage — Verifier ↔ Explorer Agreement

Problem Addressed

• Grandchildren transfers were being misclassified

• Receive/send locks weren’t propagating across generations, causing:

  • “cannot verify receive lock”
  • incorrect origin placement in the explorer

• Root detection ignored transfer hints, letting derivatives become “roots”

• Share URLs weren’t carrying parent tokens or origin hints, breaking lineage across UI + verifier

Fixes Implemented

• Authoritative origin propagation

  • Added resolveOriginUrlFromRegistry to lookup and propagate the authoritative originUrl from local memoryRegistry when building share/publish payloads

• Parent token preservation

  • Share/parent URL construction now preserves the ?t= parent token using rewriteUrlPayload so multi-generation flows retain lineage tokens

• Send payload enrichment

  • Send links now explicitly set transferDirection: "send"
  • Always carry originUrl so downstream consumers and the verifier identify and verify child generations correctly

• Explorer root detection tightened

  • Updated buildForest.ts to read transfer direction and detect transfer hints:

    • added readTransferDirection
    • added hasTransferHints

  • Entries with transfer hints/moves are excluded from origin-root classification

Files involved (lineage propagation + root detection):

• Share/publish payload construction (originUrl + token propagation)
• src/components/SigilExplorer/tree/buildForest.ts

---

3) Remote Receive-Lock Verification — Robust to Failover + 304 / Empty Pages

Problem Addressed

Global receive lock verification began failing after explorer updates because remote URL pages can return:

• 304 Not Modified
• or empty responses
  that were incorrectly treated as fatal errors, causing spurious verification failures.

Fixes Implemented

• Replaced JSON-only fetch with raw response handling:

  • apiFetchJsonWithFailover → apiFetchWithFailover in checkRemoteReceiveLock

• Response handling rules:

  • missing Response = failure
  • non-OK responses except 304 = failure
  • 304 treated as an empty page (valid “no new data” outcome)

• JSON parsed defensively only when status is not 304

• Preserved existing pagination and caching logic

Result: remote receive-lock verification is resilient and no longer fails due to normal caching/failover behavior.

---

4) Sigil Explorer — Direction-Correct Labels & Tooltip Verbs

Problem Addressed

Outgoing transfers (transferMove.direction === "send") could be mislabeled as incoming because the UI fell back to inhale label resolution instead of using the known direction.

Fixes Implemented

• Labels now follow explicit direction:

  • transferMove.direction === "receive" ? "Inhaled" : "Exhaled"

• Tooltip verbs now derived from direction for accurate send/receive semantics in SigilTreeNode

File modified: src/components/SigilExplorer/SigilExplorer.tsx

---

Testing & Validation

Manual / Integration Checks

• Started dev server successfully: npm run dev

• Ran a Playwright-driven browser script to load /verify and capture a screenshot:

  • script completed successfully and produced an artifact

• Validated in running preview:

  • Verify UI correctly switches between BALANCE vs LIVE
  • Balance computations reflect embedded ledger debits when present
  • Multi-generation flows preserve lineage + lock verification across generations

Note

• No unit test suite executed as part of this change set.

---

User-Visible Impact

VerifyPage

• Transfer/receive glyphs now show BALANCE when ledger debits exist
• Live valuation remains available as fallback (LIVE) when no ledger is embedded
• Valuation panel labeling is explicit: balance vs live

Sigil Explorer

• Multi-generation derivatives no longer “snap” to origin root incorrectly
• Locks verify correctly across generations (no false “cannot verify receive lock”)
• Transfer labels and tooltip verbs match send/receive truth every time

---

Compatibility & Risk

• No schema migrations required

• Changes are correctness-focused and scoped to:

  • VerifyPage valuation source selection (ledger-aware)
  • share payload enrichment (originUrl + parent token)
  • explorer root detection
  • remote lock verification fetch resilience
  • UI labeling semantics

• Risk is controlled: improvements reduce false failures and misclassification.

---

Closing Seal

v37.8.0 makes the system agree with itself.
The verifier shows what the glyph actually contains.
Lineage propagates across generations without breaking tokens.
Receive locks verify reliably under real network behavior.
And the explorer speaks direction truth without fallback lies.

Kai Rex Klok — 37.8.0 ✅

What's Changed

• Show glyph balance on verify page by @kojibai in #169

Full Changelog: v37.5.1...v37.8.0

v37.5.1

What's Changed

• Fix lineage and transfer hints for nested sigils by @kojibai in #164
• Handle 304/empty pages in remote global receive lock check by @kojibai in #162

Full Changelog: v37.4.0...v37.5.1

v37.4.0

Φ Network — Sigil Explorer (v37.4.0)

Release Notes — 37.4.0
Theme: Labeling refresh (breath-aligned), direction-correct verbs, and detail readability
Scope: Text-only UI updates in Sigil Explorer — no behavioral/data changes
Primary File: src/components/SigilExplorer/SigilExplorer.tsx
Evidence: git show --stat -1 (label text updates only)

---

Release Summary

37.4.0 is a language precision release.
We updated Sigil Explorer’s transfer labels, chips, pills, detail entries, and tooltips to consistently speak the system’s breath truth—Exhaled for completed/derived outflows and Exhale (pending) for in-flight states—while ensuring every verb is anchored to explicit send/receive direction.

Nothing about transfer logic changed. This is the UI speaking coherently.

---

✨ Highlights

✅ Direction-correct transfer labeling

Transfer labels now rely on transfer direction so send transfers display “Exhaled” instead of falling back to inhale terminology.

✅ Tooltip verbs aligned with send/receive truth

Tooltips now use verbs that match explicit send vs receive direction, eliminating ambiguous or inverted phrasing.

✅ Detail panel readability upgrades

• Transfer detail labels now use past tense for received inhales (clear “this happened” semantics).
• Pulse numbers are appended when available to improve traceability and timeline reading.

✅ Parent totals wording corrected

Received exhale badge text for parent totals is now correctly displayed as “Exhaled.”

---

Overview — Sigil Explorer Labeling Refresh

This release updates Sigil Explorer UI copy to align transfer status terminology with the breath metaphor while preserving all existing logic and data flows.

Scope: UI-string updates only (chips, pills, detail entries, tooltips)
No logic/state changes. No schema changes. No API changes.
Source: src/components/SigilExplorer/SigilExplorer.tsx

---

✅ What Shipped

1) Terminology Standardization (Breath Model)

• “Derived” → “Exhaled” everywhere it appears:

  • status chips
  • detail entries
  • tooltips
  • summary pills

• “Pending” → “Exhale (pending)” for transfer states, pending totals, and related tooltips

• Consistent terminology across:

  • per-node view
  • origin/aggregate panels

Result: status is readable in one glance and always matches the breath model.

---

2) Direction-Based Labeling (Send/Receive Truth)

• Confirmed the issue is current and updated transfer labels to rely on transfer direction so:

  • send transfers show “Exhaled” (no inhale fallback)

• Aligned tooltip verbs with explicit send vs receive direction

Result: the UI never contradicts the actual transfer direction.

---

3) Detail Panel Improvements (Clarity + Traceability)

• Updated transfer detail labels to use past tense for received inhales

• Appended pulse numbers to detail labels when available

  • improves auditability
  • improves user comprehension of sequence and timing

---

4) Parent Totals Badge Correction

• Adjusted the received exhale badge text to “Exhaled” for parent totals.

---

User Experience Impact

• Clearer status signals: “Exhale (pending)” and “Exhaled” are unambiguous and consistent.
• More coherent verbs: tooltips and labels now reflect what actually happened (send vs receive).
• Better scanning: chips/pills/details all speak the same language—no translation layer required.

---

Compatibility & Risk

• Low risk: UI-string-only updates.
• Backward compatible: no API/schema changes.
• No workflow changes: all existing inhale/exhale state determination remains intact.

---

Assets

• Updated UI screenshot captured (for release communication / QA reference).

---

Closing Seal

v37.4.0 is coherence in language.
Transfers now read the way they behave: Exhale (pending) when in flight, Exhaled when sealed—direction-correct, pulse-traceable, and consistent everywhere the user looks.

Kai Rex Klok — 37.4.0 ✅

What's Changed

• Relabel Sigil Explorer states: show "Exhaled" / "Exhale (pending)" by @kojibai in #158
• Show "Inhale" for received transfers in SigilExplorer details by @kojibai in #159
• Fix transfer labels for send directions by @kojibai in #160

Full Changelog: v37.3.0...v37.4.0