hiveiq-src/hiveops-guide
4
0
Fork 0
Code Issues 9 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

feat(guide): dev audience tier + GUIDE_SERVED_AUDIENCES env cap (prod = customer,internal)

Browse Source 
4-tier ladder customer<internal<dev<bcos. Re-tagged Architect/Testing/Claude +
platform/technical from internal->dev; Processes stays bcos. Backend visible()
enforces a per-instance served-audiences cap at the API. bcos.dev/DLX serve all;
production sets GUIDE_SERVED_AUDIENCES=customer,internal so dev/bcos never leave
dev. Verified: capped instance returns only Customer+Internal, 404s dev/bcos.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Johannes
2026-07-01 17:11:00 -04:00
parent e02aab4d3b
commit 930a4b968e
231 changed files with 262 additions and 233 deletions
Download Patch File Download Diff File Expand all files Collapse all files
backend/src/main/resources/content/aria/precursor-alerts/architect.md
+1 -1
View File
@@ -3,7 +3,7 @@ module: aria.precursor-alerts
title: Precursor Alerts
tab: Architect
order: 30
audience: internal
audience: dev
---
How the **Precursor Alerts** feature is built. Everything lives in **hiveops-aria** (port 8095, DB `hiveiq_aria`). ARIA owns detection end-to-end — it does not read another service's tables to build alerts. See [platform.service-ownership].