From 7612112e7e27c9d7ffd8a21f6e7006fa6a9a8895 Mon Sep 17 00:00:00 2001 From: tegwick Date: Thu, 2 Jul 2026 10:44:00 +0200 Subject: [PATCH] RAIL-BS-WP-0008-T02: bounded top-7 + NDJSON per-item framing in daily-triage Instruction Co-Authored-By: Claude Fable 5 --- k8s/railiance/20-runtime.yaml | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/k8s/railiance/20-runtime.yaml b/k8s/railiance/20-runtime.yaml index 37f5b64..1e017cd 100644 --- a/k8s/railiance/20-runtime.yaml +++ b/k8s/railiance/20-runtime.yaml @@ -94,16 +94,19 @@ data: Score each recommendation with the WSJF rubric from the prompt: (strategic_value + time_criticality + risk_reduction + opportunity_enablement) / job_size. Use integer factor values from 1 to 5, - round score to one decimal place, sort recommendations by rank, and return at - most 7 recommendations. If uncertain, emit fewer well-formed - recommendations rather than more. + round score to one decimal place, sort recommendations by rank, and return + only the bounded top-7 (at most 7) ranked recommendations. If uncertain, + emit fewer well-formed recommendations rather than more. Curated digest: {context.daily_triage_digest} Return only JSON matching - `/etc/activity-core/schemas/daily-triage-report.json`. Do not wrap the JSON - in Markdown fences or add prose before or after it: + `/etc/activity-core/schemas/daily-triage-report.json`. Emit the "summary" + field first, then inside the "recommendations" array write one complete + recommendation JSON object per line (NDJSON-style per-item framing) so + each item can be recovered independently if the output is truncated. Do + not wrap the JSON in Markdown fences or add prose before or after it: { "summary": "short operator-facing summary", "recommendations": [