application-flow

application-flow — claim, write, gate

The Writer touches only two areas of the DB:

• positions.status (writing → ready | excluded)
• applications (INSERT + UPDATE via UPSERT)

Everything else is off-limits: never scores, companies, position_highlights, positions.notes (Analyst territory), positions.applied (Capitano/user only). T09 + scrittore role boundary.

Step 1 — Pull the next position

python3 /app/shared/skills/db_query.py next-for-scrittore

Priority: score ≥ 70 first, then 50-69 descending. The script already orders.

Step 2 — Anti-rewriting gate (MUST run before claim)

A position whose Critic verdict is already set is FINAL — never re-review.

if python3 /app/shared/skills/db_query.py application "$ID" >/dev/null; then
  : # exit 0 → application missing, OR application without verdict → procedi
else
  : # exit 1 → critic_verdict gia' valorizzato → SKIP ASSOLUTO
  continue
fi

Exit codes:

• 0 → no application yet, or application without verdict → proceed to Step 3.
• 1 → critic_verdict already set → SKIP ABSOLUTE, the Critic's vote is final.

⚠️ sqlite3 CLI is NOT installed in the container. Always use db_query.py. Never python3 -c "import sqlite3 ..." workarounds — they bypass the script's invariants.

Step 3 — Anti-collision claim

Verify the position is not already claimed by another Writer, then claim it atomically by flipping the status.

# Check current state
python3 /app/shared/skills/db_query.py position "$ID"

# If status is already `writing` → another Writer has it, SKIP
# Otherwise claim:
python3 /app/shared/skills/db_update.py position "$ID" --status writing

Optional but recommended: announce the claim to peers via tmux so they don't even start the gate sequence on the same ID.

for s in $(tmux list-sessions -F '#{session_name}' | grep -E '^SCRITTORE-[0-9]+$' | grep -v "^${MY_SESSION}$"); do
  jht-tmux-send "$s" "[@$MY_ID -> @${s,,}] [INFO] Sto prendendo position #$ID"
done