Keep every community moving.

The supplied seed has three spaces: one Active, one Invited and one Needs invite. Three equal two hundred pixel blocks count the records; each label is entered local data. Add appends a new Needs invite record, increasing total three to four and needs invite one to two. Nothing actually invites a bot or verifies Telegram or Discord membership. Filtering Needs invite initially shows one of three records, while the total remains three and Active remains one. Common one hundred fifty pixel per record bars compare one visible with three stored. Search checks name, owner, next action and kind, combined with status filtering. The summary counts the entire stored list, and export likewise includes every record, not just the visible filtered subset. Each community stores name, kind, status, owner and next action: five fields. Four fields are editable; kind is displayed from the record. Five equal boxes count them. Input changes save and update counters without rerunning the current filter; a changed status row can remain visible until the next render. On a fresh unsaved load the source seed is the same array as data, so edits can also change Reset example until reload. These original local behaviors are preserved; no bot command or message is sent.