Timmy_Foundation/timmy-home
16
0
Fork 0
Code Issues 176 Pull Requests Actions Packages Projects Releases Wiki Activity

[DOCS] Ezra and Bezalel wizard houses canon, deployment, and launch report #51

Merged
Rockachopa merged 8 commits from alexander/wizard-houses-ezra-bezalel into main 2026-03-30 02:06:41 +00:00
Conversation 5 Commits 8 Files Changed 8 +1073
Timmy commented 2026-03-29 17:33:25 +00:00
Owner
Copy Link

This PR triages the wizard-house work into Gitea.

Included:

  • canon sheet and architecture document for Timmy / Alexander / Ezra / Bezalel
  • Ezra and Bezalel house charters
  • deployment shape for the two VPS houses
  • Telegram bot cutover plan + wiring script
  • production launch report with exact proof and honest blockers

Important truth:

  • Ezra and Bezalel houses were launched on the two VPS hosts
  • Hermes health endpoints answered for both houses
  • Telegram acceptance is still blocked on BotFather bot creation through Alexander's real Telegram user session
  • the launch report is the evaluation artifact for review

Primary review artifact:

  • reports/production/2026-03-29-wizard-houses-launch-report.md
This PR triages the wizard-house work into Gitea. Included: - canon sheet and architecture document for Timmy / Alexander / Ezra / Bezalel - Ezra and Bezalel house charters - deployment shape for the two VPS houses - Telegram bot cutover plan + wiring script - production launch report with exact proof and honest blockers Important truth: - Ezra and Bezalel houses were launched on the two VPS hosts - Hermes health endpoints answered for both houses - Telegram acceptance is still blocked on BotFather bot creation through Alexander's real Telegram user session - the launch report is the evaluation artifact for review Primary review artifact: - `reports/production/2026-03-29-wizard-houses-launch-report.md`
Timmy added 3 commits 2026-03-29 17:33:27 +00:00
docs: define and launch Ezra and Bezalel houses 2d48b38b1e
docs: add wizard telegram bot cutover plan 85cde7b623
docs: add wizard houses launch report 3b395d0bb3
Rockachopa was assigned by Timmy 2026-03-29 17:33:27 +00:00
claude added 1 commit 2026-03-29 18:32:54 +00:00
docs: update wizard launch report with telegram proof 7f5de12de2
Timmy commented 2026-03-29 18:33:24 +00:00
Author
Owner
Copy Link

Update:

Telegram cutover progressed materially after the initial PR.

Now proven in the launch report:

  • @EzraTimeBot and @BezazelTimeBot exist
  • both are in the Timmy Time group
  • token wiring completed into the wizard houses
  • bot discussion messages posted successfully into the group

Latest report commit:

  • 7f5de12 — docs: update wizard launch report with telegram proof

Remaining exact acceptance gap:

  • Alexander needs to post one message in the group so the conversation becomes a true four-party discussion.
Update: Telegram cutover progressed materially after the initial PR. Now proven in the launch report: - `@EzraTimeBot` and `@BezazelTimeBot` exist - both are in the `Timmy Time` group - token wiring completed into the wizard houses - bot discussion messages posted successfully into the group Latest report commit: - `7f5de12` — `docs: update wizard launch report with telegram proof` Remaining exact acceptance gap: - Alexander needs to post one message in the group so the conversation becomes a true four-party discussion.
claude added 1 commit 2026-03-29 18:53:24 +00:00
docs: record bezalel codex wake proof d87f1d1605
Timmy commented 2026-03-29 18:53:52 +00:00
Author
Owner
Copy Link

Update: Bezalel is now awake on the intended Codex-backed Hermes lane.

New proof landed in the launch report:

  • copied working openai-codex auth store into Bezalel's Hermes home
  • switched Bezalel to provider: openai-codex, model: gpt-5.4
  • direct runtime-provider proof showed a non-empty Codex access token
  • direct remote chat proof returned:
    BEZALEL_CODEX_AWAKE
    session_id: 20260329_185219_1c4787

Latest branch commit:

  • d87f1d1 — docs: record bezalel codex wake proof

Ezra remains infra-alive but Anthropic-blocked for now.

Update: Bezalel is now awake on the intended Codex-backed Hermes lane. New proof landed in the launch report: - copied working `openai-codex` auth store into Bezalel's Hermes home - switched Bezalel to `provider: openai-codex`, `model: gpt-5.4` - direct runtime-provider proof showed a non-empty Codex access token - direct remote chat proof returned: `BEZALEL_CODEX_AWAKE` `session_id: 20260329_185219_1c4787` Latest branch commit: - `d87f1d1` — `docs: record bezalel codex wake proof` Ezra remains infra-alive but Anthropic-blocked for now.
claude added 1 commit 2026-03-29 19:06:13 +00:00
docs: record ezra auth and four-party telegram proof 66e038509e
Timmy commented 2026-03-29 19:06:39 +00:00
Author
Owner
Copy Link

Final progress update for this cycle:

  • Bezalel is awake on a Codex-backed Hermes lane
  • Ezra auth is now fixed: valid Anthropic model calls return HTTP 429 rate-limit/quota responses instead of missing-credential errors
  • the four-party Telegram discussion proof is now complete

Four-party proof in group Timmy Time:

  • Alexander messages: 255, 259, 263
  • Timmy reply: 266
  • Ezra reply: 267
  • Bezalel reply: 268

Latest proof commit:

  • 66e0385 — docs: record ezra auth and four-party telegram proof

Canonical report:

  • reports/production/2026-03-29-wizard-houses-launch-report.md
Final progress update for this cycle: - Bezalel is awake on a Codex-backed Hermes lane - Ezra auth is now fixed: valid Anthropic model calls return HTTP 429 rate-limit/quota responses instead of missing-credential errors - the four-party Telegram discussion proof is now complete Four-party proof in group `Timmy Time`: - Alexander messages: `255`, `259`, `263` - Timmy reply: `266` - Ezra reply: `267` - Bezalel reply: `268` Latest proof commit: - `66e0385` — `docs: record ezra auth and four-party telegram proof` Canonical report: - `reports/production/2026-03-29-wizard-houses-launch-report.md`
claude added 1 commit 2026-03-29 19:13:51 +00:00
docs: note nostr cutover future work f0de93554d
Timmy commented 2026-03-29 19:14:12 +00:00
Author
Owner
Copy Link

Future work recorded:

  • follow-on issue opened for private Nostr client cutover with distinct per-agent identities
  • report updated to reference this as the next sovereign messaging step

New issue:

  • #54 — [NOSTR] Cut wizard houses from Telegram to private Nostr client with per-agent identities

Latest branch commit:

  • f0de935 — docs: note nostr cutover future work
Future work recorded: - follow-on issue opened for private Nostr client cutover with distinct per-agent identities - report updated to reference this as the next sovereign messaging step New issue: - #54 — [NOSTR] Cut wizard houses from Telegram to private Nostr client with per-agent identities Latest branch commit: - `f0de935` — `docs: note nostr cutover future work`
claude added 1 commit 2026-03-29 19:23:16 +00:00
docs: record timmy openclaw telegram path 85f0a34e39
Timmy commented 2026-03-29 19:23:37 +00:00
Author
Owner
Copy Link

Telegram path update:

  • Timmy now wears OpenClaw on the local Telegram path
  • OpenClaw probe shows the Timmy bot configured/running with TimmysNexus_bot
  • Alexander's Telegram user was paired/approved in OpenClaw
  • DM is now the streamlined path
  • group replies are still intentionally blocked by current OpenClaw group policy (not-allowed), so DM is the clean channel until we relax group policy on purpose

Latest proof commit:

  • 85f0a34 — docs: record timmy openclaw telegram path
Telegram path update: - Timmy now wears OpenClaw on the local Telegram path - OpenClaw probe shows the Timmy bot configured/running with `TimmysNexus_bot` - Alexander's Telegram user was paired/approved in OpenClaw - DM is now the streamlined path - group replies are still intentionally blocked by current OpenClaw group policy (`not-allowed`), so DM is the clean channel until we relax group policy on purpose Latest proof commit: - `85f0a34` — `docs: record timmy openclaw telegram path`
Rockachopa merged commit 6f9fe7f31b into main 2026-03-30 02:06:41 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
alembic
The Alchemical Vessel - Kimi-powered transformation
 architecture
Auto-created architecture label
 assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 auth-needed
auth-needed
 bizzalo
bizzalo
 blocker
blocker
 claw
Claw Code runtime (Rust)
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 deadline-7am
deadline-7am
 epic
Parent tracking issue
 golden_bilbo
Bilbo at peak performance - max churn, fast responses
 harness-engineering
Auto-created harness-engineering label
 intel
Competitive intelligence
 kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 morning-report
morning-report
 runtime
Runtime abstraction layer
 saiyah
Auto-created saiyah label
 study
Learning from external source code
 substratum
The dissolution engine - runtime layer
 substratum:invoke
Trigger Substratum execution
 urgent
urgent
 velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity
No Assignees Rockachopa
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-home#51
Delete Branch "alexander/wizard-houses-ezra-bezalel"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?