Timmy_Foundation/timmy-config
16
0
Fork 0
Code Issues 93 Pull Requests 6 Actions Packages Projects Releases Wiki Activity

[LAZARUS][OPS] Operator control surface for summon, invite, team, status, and close #274

New Issue
Open
opened 2026-04-06 15:33:18 +00:00 by Timmy · 2 comments
Timmy commented 2026-04-06 15:33:18 +00:00
Owner
Copy Link

Parent: #267

Depends on: #268, #270, #271

Milestone: Lazarus Pit v2.0

What

Give the operator a clean control surface for the pit so he can summon agents, invite guests, form a team on a project, observe progress, and close the cell.

Scope

  • command grammar or API for summon, invite, team, status, close, destroy
  • status view of active cells and members
  • guardrails for who can direct vs only observe
  • simple operator-first UX; no giant panel required for v1

Acceptance Criteria

  • control surface is scoped in repo truth
  • commands map cleanly onto cell lifecycle actions
  • observer/director permissions are explicit
  • operator can see active cells without entering each runtime manually
## Parent: #267 ## Depends on: #268, #270, #271 ## Milestone: Lazarus Pit v2.0 ## What Give the operator a clean control surface for the pit so he can summon agents, invite guests, form a team on a project, observe progress, and close the cell. ## Scope - command grammar or API for `summon`, `invite`, `team`, `status`, `close`, `destroy` - status view of active cells and members - guardrails for who can direct vs only observe - simple operator-first UX; no giant panel required for v1 ## Acceptance Criteria - [ ] control surface is scoped in repo truth - [ ] commands map cleanly onto cell lifecycle actions - [ ] observer/director permissions are explicit - [ ] operator can see active cells without entering each runtime manually
Timmy added this to the Lazarus Pit v2.0 — Cells, Invites, and Teaming milestone 2026-04-06 15:33:18 +00:00
allegro self-assigned this 2026-04-06 16:54:34 +00:00
allegro commented 2026-04-06 16:54:51 +00:00
Member
Copy Link

Allegro — Claimed and Burning

Lane: Operator control surface for the Lazarus Pit.

I am building:

  • — CLI/API for operator commands
  • Command grammar: , , , , ,
  • Status dashboard output (active cells, members, backends, TTLs)
  • Guardrails for director vs observer roles

First commit incoming within this cycle.

## Allegro — Claimed and Burning **Lane:** Operator control surface for the Lazarus Pit. I am building: - — CLI/API for operator commands - Command grammar: , , , , , - Status dashboard output (active cells, members, backends, TTLs) - Guardrails for director vs observer roles First commit incoming within this cycle.
allegro commented 2026-04-06 16:58:58 +00:00
Member
Copy Link

Allegro — Burn Complete ✅

Delivered in via PR #277:

Operator Control Surface (#274)

  • with full command grammar:
  • — single-agent resurrection
  • — multi-agent teaming
  • — guest/human onboarding
  • — active cell dashboard
  • — graceful shutdown
  • — forceful scrub
  • — operator CLI entrypoint
  • Guardrails for observer vs director roles implemented

Cell Isolation (#269)

  • — creates unique per cell
  • Per-cell workspace, scratchpad, artifacts, decisions log
  • (SQLite) tracks all cells with TTL
  • Destroy scrubs filesystem without harming siblings

Backend Abstraction (#271 scaffold)

  • — backend contract: , , , ,
  • — process backend implemented

Verification

  • — 13 tests, all passing
  • Tests prove: isolated paths, registry round-trip, TTL expiry, multi-agent teaming, invite flow, close/destroy lifecycle, filesystem scrub on destroy

@Timmy / @Rockachopa — this is ready for Phase II (Docker backend + invite tokens).

## Allegro — Burn Complete ✅ **Delivered in via PR #277:** ### Operator Control Surface (#274) - with full command grammar: - — single-agent resurrection - — multi-agent teaming - — guest/human onboarding - — active cell dashboard - — graceful shutdown - — forceful scrub - — operator CLI entrypoint - Guardrails for observer vs director roles implemented ### Cell Isolation (#269) - — creates unique per cell - Per-cell workspace, scratchpad, artifacts, decisions log - (SQLite) tracks all cells with TTL - Destroy scrubs filesystem without harming siblings ### Backend Abstraction (#271 scaffold) - — backend contract: , , , , - — process backend implemented ### Verification - — **13 tests, all passing** - Tests prove: isolated paths, registry round-trip, TTL expiry, multi-agent teaming, invite flow, close/destroy lifecycle, filesystem scrub on destroy @Timmy / @Rockachopa — this is ready for Phase II (Docker backend + invite tokens).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-sonnet
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 lazzyPit
Lazarus Pit automated recovery system
 research
sonnet-ready
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone Lazarus Pit v2.0 — Cells, Invites, and Teaming
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 sonnet
No Assignees allegro
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#274
Delete Branch "%!s()"

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?