browsy extension field test
browsy · extension plan · field test

The extension, in the room.

A clickable test of the Browsy extension plan: an ephemeral web hash, a page the user allows, and Wizy Magic inside Goddy — first with the broad self, then with MyFamily data when someone else is in the room.

simulated window local only no network sample data
the plan · four moves

The extension is the host. Wizy is the organ.

Browsy does not replace the app. It authenticates the session, pulls only with consent, lets Wizy derive locally, and hands the app a view — never the vault, the root key or the identity hash.

  1. 01 · install

    One key holder

    The extension installs once. The service worker creates and stores the canonical Ed25519 root.

    authy · canonical
  2. 02 · pull

    Click, then read

    You click Browsy on the page you are reading. It reads visible text and form signals, never passwords, hidden inputs or tokens.

    consent · allowlist
  3. 03 · derive

    Local by default

    Wizy mixes the page with the P and L records already in the vault. Deterministic rules first; explanations stay visible.

    wizy · D1
  4. 04 · hand off

    A scoped view

    Authy signs a grant for this session. The app receives the view it asked for, not the vault or the root.

    grant · expiry
AuthyUnlocks, signs grants and keeps the session scoped.
WizyJSON manager, merge and local derivation inside Browsy.
VaultEncrypted P and L records; P normally never leaves.
NetyOnly S publications travel through the social path.
the field test · simulated window

Goddy is open. Browsy is in the toolbar.

The page below is a mock of flove.org/apps/metas/goddy.html. The side panel is the extension. The Magic button belongs to Goddy, but the hints come from Wizy inside Browsy. Rotate the web hash and every trace changes with it.

Goddy · flove
flove.org/apps/metas/goddy.html
Goddygoddess · god · us
your matrix · 3 × 3

How fully do you see each cell?

One cell is marked curious. That is the signal Wizy reads first.

note · sunday

The garden, the call, the hour free

Call grandma on Sunday. Ask about the garden. Keep the hour free — no errands, no screens, just the call.

familycaresunday
session log · local0 events
    Simulated: the app, the page and the extension chrome are one HTML demo. The hash is minted in this tab and expires; it is not a real key. For your own plays, the Browsy index Magic reads flove:appy:plays and flove:myfamily:state. ready
    the hash · two lives

    Ephemeral in the tab. Canonical in the extension.

    The hash in the demo is a web-provisional identity: generated in the tab, good for one session, explicitly not portable. The extension identity is the one that becomes the Nety PeerId. The two are never the same key.

    Web hash · ephemeral

    source: web

    Minted by the page when no extension is present. It can sign local grants for the session, but it has no migration path into the extension.

    • Lives in this tab, rotated in the demo.
    • source:"web" · notPortable:true.
    • Installing the extension starts a new canonical identity.
    • The old web record is kept but hidden — never promoted.

    Extension hash · canonical

    source: extension

    Created and stored by the service worker. One identity, one hash; the same value is the Nety PeerId.

    • CIDv1(sha256(ed25519_pubkey)) → bafk…
    • Unlocks with Authy; signs grants and sessions.
    • The page never receives the vault, the root or this hash from a pull.
    • Recovery is the seed; social quorum comes later.
    01 · openNo extension identity in this tab.
    02 · mintWeb hash appears: bafkrei…
    03 · scopeGoddy Magic uses it for this session.
    04 · rotateClose or rotate; the session scope goes.
    05 · installExtension becomes canonical; web record stays hidden.
    three real tests

    Run the same magic, twice, with different data.

    Each test sets the wizard, the mode and the page state for you. The point is not the sentence — it is what the trace shows: which class was read, which session hash scoped it, and whether anything left the tab.

    test 01~30 s

    Myself · the broad self

    Wizy reads across the user’s own apps, not one screen. The hints connect the matrix to a soul map, a draft and a boundary.

    • Goddy matrix + Souls animal
    • Blogy draft + Trusty boundary
    • No MyFamily person in the mix
    test 02~30 s

    With others · MyFamily

    Marta is an L record with a clear category. Two app links come from the user; the person and the category come from MyFamily.

    • Marta · care × 4 · honesty × 2
    • L record, not the raw P notes
    • Person chip remains local
    test 03~10 s

    Rotate the session

    Rotate the ephemeral hash while Magic is open. Every “Why this?” trace should show the new hash and a fresh TTL.

    • Hash changes in every trace
    • TTL resets to 12:00
    • Extension canonical untouched
    the rules kept

    What this demo refuses to do.

    The interface is playful because the rules are strict. These are the invariants the extension plan keeps, even when the demo makes the flow look easy.

    Browsy pulls; the page does not ask.

    There is no page-to-extension identity or vault API. The user clicks Browsy; the extension reads the public page.

    spec §3.8 →
    P stays in memory.

    Personal records are read locally. A projection is L; a public card is S. Neither is the raw record.

    rationale →
    Derived is local by default.

    Wizy runs D1 deterministic rules first. A remote model would need separate consent and a fresh threat review.

    derivation →
    No silent injection.

    Typed state — idle, pulling, no-access, error — a persistent indicator, a Stop button and a per-site allowlist.

    pull scope →