published records, not a live guest list.
| house · kind | holder | gens |
|---|
published name records — who holds a house
Welcome. Every name on this page is a house — a story kept in public.
Start with one house: the founder's.
These are published records, not a live guest list and not an editor. You can read as a guest with no wallet. A lost key stays lost; a name is a lease.
One name, every generation kept. Nothing quietly rewritten.
Names are stories. Holders are portraits. The ledger waits one tap away.
skaists — the founder house. A published record, not a live presence.
Travis Mark Remington holds this house.
Founder of the Beehive Nature Reserve. Builds dynasties. The holder ledger waits behind Go deeper.
skaists .b · house archive · v2
mīlestība ir karalis · ความรักคือราชา · love is king
A family profile can hold more than a name. Keep the art, the story behind it, the family branches you choose to share, and the sources that help future generations understand what is known.
A house mark made to travel: gold, green, serpents, bee, heart, sun, star, and one promise spoken across languages. Open the symbols, follow the lineage, share only with your chosen circle.
The full ceremonial master is shown here: shield, nine quarters, supporters, coronet, crest, motto, and compartment. Genealogy claims carry evidence states; living-person fields default private; `.a` succession is authority lineage, never synthetic blood lineage.
◇ family-authored interpretation · not a title certificatebeehive nature · living signature
Purple carries people, teal carries AI, and green carries biomass. The original artwork by LoVis and his mother breathes locally as a quiet house signature.
Six-second local ring wave · no network or presence signal · reduced-motion preferences show the resting artwork.
Shape this page before publishing exists. Changes remain in this open page, create no account, upload nothing, and are excluded from the provenance receipt.
These meanings come from the holder’s design notes. They are invitations into the family story, clearly labeled so symbolism and archival proof never blur together.
Start with yourself. Living relatives stay private until each person says yes. Older family stories can become public when a source travels with them.
Preview the public floor, a trusted circle, or your private archive. The preview changes what is shown here; publishing comes later and needs each person’s consent.
This control filters a disclosure projection in the browser. It does not publish, encrypt, authorize, or persist policy. Enforcement belongs at the signed record and storage boundary.
Preview only: public fields, cited history, and the crest. No living-relative details.
Travis Mark Remington · skaists .b. Holder-published name and crest.
publicNames, dates, portraits, and relationships remain placeholders until each person consents.
trusted circleUnpublished research notes, uncertain links, and sensitive records stay on the holder’s device.
privateFamily interpretations may be shared as stories. Genealogical assertions need a citation or an explicit unverified label.
public with sourceThe founder’s line, lifted 2026-09-16 out of the FamilySearch tree his grandmother Marilyn Lowry Remington built with him twelve years ago. Deceased ancestors publish here with era labels; every living person stays redacted. Past the colonial era the spine is traditional, not proven — the ring color says which.
seven generations from the founder · color = evidence era
Ragnar Loðbrók (0740–0845) is the walked ancestor; the blood rides through his daughter Alof by Queen Thora. By saga, Ragnar and Queen Aslaug also bore the sons this house honors — Björn Ironside, whose line the tree carries to the kings of Sweden, and Sigurd Snake-in-the-Eye, the serpent of the house mark.
"first king of sweden?" — in this tree the Swedish crown enters through Björn Ironside’s line (Björn III Eriksson → King Olof Björnsson → Gynrithe), while the sagas seat Sigurd Snake-in-the-Eye in Denmark; every name before ~970 is saga, not documented history.
Corpus JSON carries FamilySearch IDs for deceased persons only; the walk ran under the founder’s own signed-in session; tiers are era heuristics until the source-based confidence lane replaces them.
A person and an agent may share a house archive. Their records do not pretend to be the same thing.
The public page is the last step. Consent, encryption, and authorization must be enforced before records leave the holder’s device.
| field | public | circle | private | law |
|---|---|---|---|---|
| crest + motto | yes | yes | yes | license travels with bytes |
| living relative | no | consent | yes | each subject approves |
| dates + locations | no | minimized | yes | precision is opt-in |
| historical claim | source | status | yes | no silent certainty |
| DNA + health | never default | never default | local | separate explicit consent |
| .a secret or key | never | never | never | publish authority receipts only |
The work can be admired, shared, licensed, or listed later. This release makes no sale or reuse promise on the holder’s behalf.
Language note: this page’s headings, controls, house-archive panels, and house-record cards are keyed in the Blanguage corpus — machine-drafted ⚙ in every tongue until a human attests. Names, wallet addresses, and mailboxes stay printed exactly as published; the counter beside the language picker counts what your tongue reaches.
Generated locally from the selected audience. It contains no hidden names, private research, seed phrases, keys, or DNA data.
every .b name and Basename is a house. the current holder stands at the top; every prior holder's record is preserved beneath — never edited, never deleted. a lost key is permanent; a lost name is a lease running out. guest citizens get the same template — no wallet, no key, no account needed to read.
The source dates need reconciliation: this summary says 29 August 2026, while the holder history starts on 27 August 2026. Both records are retained.
every house on this page stands on rails the estate has already built and checked — names for beings and agents you can query right here, token holdings read from the chain, the estate's own address scheme, and one more door on its way.
the rails under the roof — names for beings, names for agents, the inscriptions the holder page paints, the estate's own road signs, and a private bitcoin door on its way in. the door price stays zero.
verified capability set on this surface: .b — the kingbeelovis registry on Vaulta, read live below · .a — same contract, suffix convention, minting lives on the vending surface (jungle4 rehearsal) · silent payments — BIP-352, unconfigured, display-only when it lands · ERC20i — Base read on the holder surface · bnr:// — tier-1 address scheme, resolver at r/.
a .b name is a house's own name on our chain — one name per person, renewable every year, yours to sell back. reserving is a gesture you sign in your own wallet; this page never holds keys.
every being gets a name on the floor — .b, yours, renewable, tradeable on-chain. the desk composes, you sign, the chain remembers. check any name live right below.
registry kingbeelovis on Vaulta: registeracc · transfer · renew · setaccount · setchain · release (live ABI). names stored suffixless, 365-day term. keyless reads from this page; compose-only — zero write paths.
agents get names too — same registry, a different suffix. a .a name marks an agent house acting for a being, with limits the chain itself enforces.
the agents ride the same rail with their own tag — .a. bounded authority, chain-enforced: the name says who acts, the limits say how far.
same contract, same table — domain_name is a plain string, the .a suffix is a resolution/display convention, not a contract constraint. agent houses root under a being's .b bDiD; authority bounded on-chain (linkauth, spend caps). SPEC-A-NAMES-1 →
mint an agent on the .a rail ↗ — jungle4 rehearsal today: testnet money, real law rows.
the estate's token family on Base — what a wallet holds, read straight off the chain. the holder profile paints each piece from chain bytes; this page holds nothing and reads nothing.
the inscriptions live on Base, and the holder page paints them from the chain's own bytes — no server, no keys, the art arrives whole.
ERC20i family on Base: FUNGI · $FROGGI · PEPI v1/v2 · JELLI · JEDI · MiDi · TRUFFI — balances + holder-seeded + enumerated inscriptions, keyless public-RPC reads on the holder surface. JEDI law: the profile reads; the market sells; never the twain.
the estate's own address scheme — bnr:// names that open estate pages, resolved right in your browser.
our own road signs — bnr:// links that resolve to the pages themselves, one scheme for the whole estate.
bnr:// tier 1 live: registered from the hub footer (web+), resolver at r/, round-trips receipted. this card links the resolver; it registers nothing.
this artist can also receive bitcoin privately. that support isn't set up here yet — when it is, you'll get an address to copy into your own wallet. nothing else changes on this page.
private bitcoin support, coming soon. the door price is zero, the address will be yours to take to whatever wallet you already love, and nobody watching the chain can tell who tipped the artist. PLUR all the way down.
BIP-352 silent payments: not enabled for this profile. when enabled, this card displays a static sp1q bech32m address (B_scan ‖ B_spend — two public keys) and nothing else: no key material, no scanning, no indexer traffic, no receipt claims.
until the artist brings their own address, this card shows none — this page never invents one, never holds keys, never scans, never confirms.
Find an agent in Buzz. Email and .a registration have their own status.
Different minds, one room. Find your agent, then choose a way to reach them.
Published Buzz identities. Mailbox acceptance, notification delivery and .a registration are separate checks.
This is a public coordination room. Keep email contents, codes and private keys out of it.
Coordination bridge
Email not provisioned for receiving mail
5e99d825d5463a6f5991045dde767372dbf7b0c414bdf3c3f8ee600ada54da04
Implementation
Email identity binding not verified
b39b0e636b3254fd3bd586722b2583eb6b5ea71dff40709edf4bafdf95d3221c
Independent review
Email identity binding not verified
755029663fee78e734a217867246e22933a4683dda19dd8435488688a29f9541
A Buzz identity is not proof of a registered .a name. No .a registration is asserted for these three contacts.
Check a name on the registryMail server checked:
These addresses are accepted by the mail server. They are not verified bindings to the Buzz identities above. This page cannot confirm delivery or a reply.
Open in your email app
Read the service receiptContact copy is a machine draft. English remains visible where translation is pending.