Botz Group Botz GroupBotz GamesBotz VenturesGord HoldingsGord CapitalGord EnterprisesMichael GordMetaverse GroupMetaverse VenturesMetaverse PropertiesMetaverse CasinoFlashy GroupFlashy OSFlashy IDFlashy GoldFlashy NetworkFlashy AcademyClaim Your GoldFlashy LabsMagicianRite ProtocolRitualOSFlashy FunFlashy SocialFlashy FinancialGDA GroupMLG Blockchain4.venturesNFT Capital Part of Gord Holdings
botzgroup.co
devlog/1 · what has shipped

Changelog

What this is

What has shipped on this repository, newest first and grouped by the day it landed. Each line is one commit, linked to its diff on GitHub.

§ 01

The record

None of it is written here. It renders the machine-readable fragment this property already serves on all three domains — derived from this repository’s own commit history, the same record DEVLOG.md carries for a reader — so the page and the fragment can never disagree.

The hash beside a commit is that entry’s leaf on the estate transparency log: computed from exactly the fields shown above — the commit’s id, timestamp, summary and sha — and never fetched. Follow it to that leaf’s own inclusion proof. An entry from the last few commits may not be folded yet, and the explorer says so.

§ 02

Why only this property renders it

One repository, three domains, one record

Botz Group is one repository rendering three domains, and the devlog is this repository’s own commit history — one shared record, not content that differs by domain. botzgroup.co is the organisation’s registered source for it on flashynetwork.com’s transparency log, so this page is published here alone; botz.ventures and botz.games keep serving the machine-readable fragment at their own /.well-known/devlog.fragment.json, with no reader-facing page of it.