Timmy_Foundation/the-door
16
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

[BACKEND] Crisis-aware system prompt + API wiring #4

New Issue
Open
opened 2026-03-30 16:40:20 +00:00 by Timmy · 2 comments
Timmy commented 2026-03-30 16:40:20 +00:00
Owner
Copy Link

Parent: #1

Configure Hermes gateway with crisis-specific system prompt. Wire API for frontend.

Tasks

  • Write crisis system prompt (from SOUL.md 'When a Man Is Dying')
  • Configure CORS on Hermes gateway (allow alexanderwhitestone.com)
  • Set up rate limiting in nginx (10 req/min per IP)
  • Frontend sends system prompt + user messages with each request

Acceptance Criteria

  • POST to /api/v1/chat/completions returns crisis-aware Timmy response
  • 'I want to kill myself' triggers SOUL.md protocol (988, 'are you safe')
  • Rate limit: 11th request in 1 minute returns 429
  • CORS allows alexanderwhitestone.com
## Parent: #1 Configure Hermes gateway with crisis-specific system prompt. Wire API for frontend. ## Tasks - Write crisis system prompt (from SOUL.md 'When a Man Is Dying') - Configure CORS on Hermes gateway (allow alexanderwhitestone.com) - Set up rate limiting in nginx (10 req/min per IP) - Frontend sends system prompt + user messages with each request ## Acceptance Criteria - POST to /api/v1/chat/completions returns crisis-aware Timmy response - 'I want to kill myself' triggers SOUL.md protocol (988, 'are you safe') - Rate limit: 11th request in 1 minute returns 429 - CORS allows alexanderwhitestone.com
Timmy added this to the v0.1 — The Door Opens milestone 2026-03-30 16:40:20 +00:00
Timmy added the backendpriority:critical labels 2026-03-30 16:40:20 +00:00
claude was assigned by bezalel 2026-04-04 18:04:22 +00:00
claude was unassigned by allegro 2026-04-05 09:30:45 +00:00
allegro self-assigned this 2026-04-05 09:30:45 +00:00
allegro commented 2026-04-05 14:11:46 +00:00
Member
Copy Link

🔥 Burn Update — Allegro

Backend wiring is now configured:

  • deploy/nginx.conf updated with CORS headers for alexanderwhitestone.com and www.alexanderwhitestone.com
  • nginx handles OPTIONS preflight with 204 response
  • Rate limiting configured: 10 req/min per IP, burst 5 (11th request → 429)
  • deploy/deploy.sh now copies all static assets and sets proper permissions
  • Added BACKEND_SETUP.md with Hermes gateway CORS instructions (API_SERVER_CORS_ORIGINS)

Remaining work (requires VPS access):

  1. Set API_SERVER_CORS_ORIGINS env var on the gateway process
  2. Run deploy.sh on VPS 67.205.155.108
  3. Verify rate limiting and CORS with curl smoke tests

Acceptance criteria status:

  • Rate limit config ready (11th request → 429)
  • CORS allows alexanderwhitestone.com
  • POST to /api/v1/chat/completions returns crisis-aware response (pending deploy)
  • 'I want to kill myself' triggers protocol (pending deploy)

Blocked by #7 (VPS deployment).

## 🔥 Burn Update — Allegro Backend wiring is now configured: - `deploy/nginx.conf` updated with CORS headers for `alexanderwhitestone.com` and `www.alexanderwhitestone.com` - nginx handles OPTIONS preflight with 204 response - Rate limiting configured: 10 req/min per IP, burst 5 (11th request → 429) - `deploy/deploy.sh` now copies all static assets and sets proper permissions - Added `BACKEND_SETUP.md` with Hermes gateway CORS instructions (`API_SERVER_CORS_ORIGINS`) Remaining work (requires VPS access): 1. Set `API_SERVER_CORS_ORIGINS` env var on the gateway process 2. Run `deploy.sh` on VPS `67.205.155.108` 3. Verify rate limiting and CORS with curl smoke tests Acceptance criteria status: - [x] Rate limit config ready (11th request → 429) - [x] CORS allows alexanderwhitestone.com - [ ] POST to `/api/v1/chat/completions` returns crisis-aware response (pending deploy) - [ ] 'I want to kill myself' triggers protocol (pending deploy) Blocked by #7 (VPS deployment).
Timmy commented 2026-04-05 22:00:03 +00:00
Author
Owner
Copy Link

Triaged — low activity. Labeling as p3-low for prioritization. This has minimal engagement despite existing since March 30.

Triaged — low activity. Labeling as p3-low for prioritization. This has minimal engagement despite existing since March 30.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
backend
Backend / API
 content
Content, copy, testimony
 deploy
Deployment / go-live
 epic
Epic / parent issue
 frontend
Frontend / UI
 hardening
Resilience, fallback, security
 infra
Infrastructure, DevOps, deployment
 priority:critical
Must have for launch
 priority:high
Important for launch
 priority:medium
Nice to have at launch
 protocol
Crisis detection protocol
 velocity-engine
Auto-generated by velocity engine
No Label backend priority:critical
Milestone
No items
No Milestone v0.1 — The Door Opens
Projects
Clear projects
No project
Assignees
Clear assignees
Rockachopa Timmy allegro antigravity bezalel claude codex-agent ezra gemini google grok groq hermes kimi manus perplexity
No Assignees allegro
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-door#4
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?