generated from coulomb/repo-seed
RAIL-BS-WP-0008-T02: bounded top-7 + NDJSON per-item framing in daily-triage Instruction
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -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": [
|
||||
|
||||
Reference in New Issue
Block a user