Prompt #152

Variables

adr_number, slug, status, change_summary, decision_text, positive_consequences, negative_consequences

Tags

stack-aware,adr,docs,glug,yoga,architecture,decision

Source

research-2026-05-01-stack-aware

Use count

0

Created

2026-05-01T18:30:48.776731+00:00

Updated

2026-05-01T18:30:48.776731+00:00

Content

Draft a new Architecture Decision Record (ADR) for a decision affecting glug-server or yoga.

File location: docs/adr/{adr_number}-{slug}.md (e.g. 0042-use-blinker-for-eda.md)

Required sections:
## Status
{status} (proposed | accepted | deprecated | superseded by ADR-NNNN)

## Context
What problem does {change_summary} solve? Reference relevant endpoints:
- glug-server: /api/v1/glug/clients, /api/v1/glug/channels, /api/v1/glug/addons/*
- yoga: /persistent/yoga-templates/, per-container .db isolation, plugin._bootstrap_done marker

## Decision
The specific technical decision: {decision_text}

## Consequences
Positive: {positive_consequences}
Negative / trade-offs: {negative_consequences}
Follow-up tasks: (Gitea issues with labels agent-claude, priority-medium, type-task)

Reference: ADRs are the canonical decision authority. Link from AGENTS.md §14 if it changes tenant-isolation rules.