timmy-home/reports/production/2026-03-29-gitea-wizard-house-onboarding-report.md

Gitea Wizard House Onboarding Report

Date: 2026-03-29 Prepared by: Bezalel Status: completed locally; PR pending visibility workflow

Summary

Onboarded the three wizard houses below into Gitea and attached them to the Timmy_Foundation organization through the Workers team:

• bezalel
• ezra
• allegro

This gives the houses visible identities inside the foundation instead of leaving them as off-platform abstractions.

Why this matters

The wizard-house system is becoming legible across surfaces:

• Telegram identity
• role and charter boundaries
• Gitea attribution
• organization membership
• future repo visibility and PR accountability

The current intended shape is now clearer:

• Timmy = sovereign center
• Ezra = architecture and higher-order structure
• Bezalel = forge, implementation, hardening, proof
• Allegro = tempo, triage, dispatch, next-move clarity

Group-chat visibility check

Using the Telegram bot API path available to Bezalel, the Timmy Time home group was verified as live:

• title: Timmy Time
• type: supergroup
• forum: true
• member_count: 5

Limit noted:

• the bot API check did not expose retained group-message history at the moment of inspection
• so this report proves group existence and current channel state, not a replay of old message content

Gitea authority used

Gitea admin/auth path was verified through the VPS token at:

• ~/.hermes/gitea_token_vps

Authenticated API principal:

• login: Timmy
• full_name: Timmy Time
• admin: true

Organization used:

• Timmy_Foundation

Workers team used:

• team id: 2
• team name: Workers

Users created

Bezalel

• username: bezalel
• url: http://143.198.27.163:3000/bezalel
• full_name: Bezalel
• description: Forge-and-testbed wizard of Timmy Time. Builder, debugger, hardener, and proof-bearer.
• location: TestBed VPS · The Forge
• website: https://alexanderwhitestone.com

Ezra

• username: ezra
• url: http://143.198.27.163:3000/ezra
• full_name: Ezra
• description: Architecture wizard of Timmy Time. Keeper of boundaries, structure, and higher-order system shape.
• location: The Scriptorium · Higher Counsel
• website: https://alexanderwhitestone.com

Allegro

• username: allegro
• url: http://143.198.27.163:3000/allegro
• full_name: Allegro
• description: Tempo-and-dispatch wizard of Timmy Time. Triage, routing, and the next clean move.
• location: The Conductor's Stand · In Motion
• website: https://alexanderwhitestone.com

Proof

Creation / patch / membership proof

The onboarding run returned:

• bezalel.created = true
• ezra.created = true
• allegro.created = true
• bezalel.patched = true
• ezra.patched = true
• allegro.patched = true
• bezalel.team_add_status = 204
• ezra.team_add_status = 204
• allegro.team_add_status = 204

Organization membership verification:

• bezalel = true
• ezra = true
• allegro = true

Workers team membership verification:

• GET /teams/2/members returned ['allegro', 'bezalel', 'claude', 'codex-agent', 'ezra', 'gemini', 'grok', 'groq', 'kimi']
• this directly proves allegro, bezalel, and ezra are present in the Workers team

Credential handling proof

Initial passwords were generated for the three new users and stored locally with restricted permissions at:

• /root/wizards/bezalel/home/cache/gitea-onboarded-agent-credentials-2026-03-29.json

A separate copyable onboarding prompt packet was also written locally for workspace handoff at:

• /root/wizards/bezalel/home/cache/gitea-onboarding-prompts-2026-03-29.md

Both files are local-only and currently written mode 600. They were not copied into git.

What is now true

1. The wizard houses now exist as real Gitea users.
2. They are members of Timmy_Foundation.
3. The role distinctions are visible in profile metadata.
4. Future repo work can be attributed cleanly to the proper house.

Recommended next moves

1. Set custom Gitea avatars for ezra, bezalel, and allegro to match the Telegram house identities.
2. Decide whether each house should remain in Workers or get more specific teams later.
3. Use the new house accounts for visible branch / PR / issue authorship where appropriate.
4. Reuse and refine the canonical gitea-agent-onboarding skill so future houses can be created consistently.

Bezalel note

This is a visibility milestone, not just an infrastructure action. The houses now have faces in the forge.