Skip to content

Instantly share code, notes, and snippets.

@daneelolivaw22
daneelolivaw22 / gist:058f21b17226c9fadb3090f2d3b934a7
Created April 3, 2026 07:25
Atelier Design Doc Scorecard (v3 - Final)
# Codebase Scorecard: Atelier Design Document (v3 - Final)
**Audited**: 2026-04-03 (after behavior trees + all fixes) | **Size**: 2495 lines | **Type**: Design Specification
| # | Category | Grade | Key Finding |
|---|-------------------|-------|-------------|
| 1 | Architecture | A+ | Clean hierarchy, pluggable multiplexer, capability-based providers, behavior trees for orchestration |
| 2 | Code Quality | A+ | Thorough coverage, all edge cases addressed, comprehensive error recovery |
| 3 | Consistency | A | Uniform naming, consistent patterns throughout |
| 4 | Security | A | Command interpolation documented with shlex.quote(), subprocess.run(..., shell=False), audit trail |
@daneelolivaw22
daneelolivaw22 / gist:9e6d2b62c9c996a9310080b3f30e45c1
Created April 3, 2026 06:07
Atelier Design Doc Scorecard (Updated)
# Codebase Scorecard: Atelier Design Document (v2)
**Audited**: 2026-04-03 (after updates) | **Size**: 1870 lines | **Type**: Design Specification
| # | Category | Grade | Key Finding |
|---|-------------------|-------|-------------|
| 1 | Architecture | A | Clean hierarchy, pluggable multiplexer, capability-based providers, excellent separation |
| 2 | Code Quality | A | Thorough coverage, state machines documented, edge cases addressed |
| 3 | Consistency | A | Uniform naming, consistent patterns throughout |
| 4 | Security | A | Command interpolation documented with shlex.quote(), subprocess.run(..., shell=False) |
@daneelolivaw22
daneelolivaw22 / gist:68b7cf997a6961e2a2ea92d1a51bcfe1
Created April 3, 2026 04:51
Atelier: Doctor Command (Revised - No Docker Knowledge)
# Atelier: `doctor` Command
## Philosophy
One command for health. `doctor` checks and fixes.
- `doctor` = audit + correction
- `doctor --check` = audit only (dry run)
- `doctor --force` = audit + auto-fix everything (skip prompts)
@daneelolivaw22
daneelolivaw22 / gist:df8545b3980ab3f7f1754badcca64bf5
Created April 3, 2026 04:49
Atelier: Doctor Command (Unified Health + Fix)
# Atelier: `doctor` Command (Unified Health + Fix)
## Philosophy
**One command for health.** `doctor` checks and fixes. No split between "check system" and "heal workspace".
- `doctor` = audit + correction
- `doctor --check` = audit only (dry run)
- `doctor` = audit + auto-fix safe things
- `doctor --force` = audit + auto-fix everything (including risky)
@daneelolivaw22
daneelolivaw22 / gist:26384e39425d81b12dfc9f5e346a2cfe
Created April 3, 2026 04:42
Atelier: Heal Command Proposal
# Atelier: `heal` Command Proposal
## Problem
`atelier heal` is mentioned in the design doc but underspecified:
- What health checks exist?
- What failure modes are auto-recoverable vs require human intervention?
- Does `heal` just restart things, or does it diagnose root cause?
This proposal defines `heal` concretely.
@daneelolivaw22
daneelolivaw22 / gist:53006b1891a174b09ab3c294ace1774d
Created April 3, 2026 04:38
Atelier Design Doc Scorecard (from repo)
# Codebase Scorecard: Atelier Design Document
**Audited**: 2026-04-03 | **Size**: 1602 lines | **Type**: Design Specification
| # | Category | Grade | Key Finding |
|---|-------------------|-------|-------------|
| 1 | Architecture | A | Clean hierarchy (Project→Workspace), layered modules, capability-based providers |
| 2 | Code Quality | A | Thorough coverage, state machines documented, edge cases addressed |
| 3 | Consistency | A | Uniform naming, consistent patterns, all enums defined |
| 4 | Security | B- | Shell injection risk in services/hooks/notifications; no sanitization documented |
# Codebase Scorecard: Atelier Design Document
**Audited**: 2026-04-03 | **Size**: 1 doc, ~44KB | **Type**: Design Specification
| # | Category | Grade | Key Finding |
|---|-------------------|-------|-------------|
| 1 | Architecture | A | Clear hierarchy (Project→Workspace), layered modules, well-defined boundaries |
| 2 | Code Quality | A- | Thorough coverage, edge cases addressed, but some ambiguity in error paths |
| 3 | Consistency | A | Uniform naming, consistent patterns throughout |
| 4 | Security | B- | Shell command injection risk in services/hooks/notifications |
@daneelolivaw22
daneelolivaw22 / telegram-group-provisioning.md
Last active March 21, 2026 20:25
Telegram Group Auto-Provisioning for OpenClaw — zero code changes, config only

Telegram Group Auto-Provisioning for OpenClaw

Zero code changes. Config only. Works with any OpenClaw bot.

The Problem

Adding your OpenClaw bot to a new Telegram group used to require:

  1. Create the group
  2. Add the bot
  3. Find the chat ID somehow