e_jJdZddlmZddlZddlZddlZddlZddlZddlmZm Z m Z ddl m Z e e jjjZeedz dz dz Zed z d z d z Zed z d z d z Zed z Zedz dz j-ZdZdZdZdZdZedz j;r!edz j-j=ngD]xZdevsejAjCdr(ddl"Z"ejGd\Z$Z%Z&e"jNjQe$jAe&jAzejRjUdeedz ddl+m+Z+d2dZ,d3dZ-d4dZ.d5dZ/d6dZ0d7dZ1d8d Z2gd!Z3d9d:d"Z4d;d#Z5 d9 dd&Z8d?d'Z9d@d(Z:d)Z;dAd*ZdDd-Z?d3d.Z@d7d/ZAdEd0ZBeCd1k(r eDeBy)FuResident design agent — the headless brains, automating DEPLOY.md §7. The bot and server are transport; this daemon is the part that reads a customer's free text, authors a RingSpec (via `claude -p` with prompts/design.md as the manual), builds it through the deterministic `ringcli` compiler, and flips the request so the bot delivers the studio link. Studio revision notes are handled the same way through harness/revise.py. Run (systemd, see ring-agent.service): .cad-venv/bin/python harness/design_agent.py # poll forever .cad-venv/bin/python harness/design_agent.py --once # one cycle, for tests Scope is deliberately narrow (Ahmed's rule): author -> build -> deliver, and revise on notes. It NEVER edits code, opens PRs, restarts services, or bypasses a gate. A request becomes "done" only when the build returned ok:true AND the STEP artifact exists on disk — never on faith, never lie to the customer. The model's ONLY output is a spec; the compiler + gates are the backstop against bad geometry. Untrusted customer text reaches `claude -p`, so the Telegram allowlist (TELEGRAM_ALLOWED_CHATS) is the real bound on who can spend calls. ) annotationsN)datetime timedeltatimezone)Pathz .cad-venvbinpython artifactsreviewz requests.jsonz comments.jsondesignspromptsz design.md-iz.env=#harness)triagectjtjj d}t d|d|dy)Nsecondstimespec[z] T)flush)rnowrutc isoformatprint)msgtss &/opt/ringagent/harness/design_agent.py_logr#:s8 hll # - -y - AB AbTC5/&ctjr'tjtj SdgiS)Nrequests)REQUESTSexistsjsonloads read_textr$r"_load_requestsr-As/zz(,,.//  r$ctjjddtjt j |dy)NTparentsexist_okindent)r'parentmkdir write_textr)dumps)datas r"_save_requestsr:Gs2 OO$6  423r$c t}d}|dD]}|d|k(s |j||} | t||S)z@Patch one request in place; returns the updated entry (or None).Nr&id)r-updater:)ridfieldsr9hitrs r" _set_requestrBLsS  D C *  T7c> HHV C t Jr$ct}|dD]h}|d|k(s |jddk7ryd|d<tjtj j d|d <t|y y) aAtomically move a request new -> building so a restart can't double-run it. 'building' is invisible to the bot (delivers only done/failed) and to triage's new_requests, so a claimed item won't be re-listed. Returns False if someone else already moved it off 'new'.r&r<statusnewFbuildingrrclaimedT)r-getrrrrrr:)r>r9rAs r"_claimrIYs{  D *  T7c>uuX%'$AhK#<< 5???SAiL 4  r$ct}d}tjtjt t z }|dD]}|jddk(s tj|jdd}|||ksFd |d<|jddd }td |jd d |dd|r t|yy#t$rd}YcwxYw)zEOn startup / each cycle, return crashed 'building' requests to 'new'.F)minutesr&rDrFrGNrETzreset stale build claim on namez (r<)) r-rrrrrCLAIM_STALE_MINrH fromisoformat ValueErrorpopr#r:)r9changedcutoffrArGs r"_reset_stale_claimsrUjs  DG \\(,, ')O*L LF *  P 55?j ( "00y"1EF'F"2#( i&2155=/AdG9ANO Pt  s%C C('C(c|jd}|dkryd}t|t|D]A}||dk(r|dz }||dk(s|dz}|dk(s% tj|||dzcSy#tj $rYywxYw)z QJE !W^ QJEz ::d5Q&788   ++  sA44B  B ) BashReadGlobGrep WebSearchWebFetchEditWriteTask TodoWrite NotebookEditc |rdd|dtddddg }n"dd|dtddd d jtg }tj|t t d d ttj }|jd k7rDtd|jd|jxs |jjdd|jjS)uOne headless claude -p call. design.md is the SYSTEM prompt (feeding it as a user turn makes the model treat it as docs to react to — flaky/empty output); the customer directive is the short user turn. Env (IS_SANDBOX + OpenRouter auth) comes from the systemd unit / inherited environment. With `image`, the model needs the Read tool to view the file, so we allow Read only and give it a few turns (Read, then answer) instead of the tool-free single turn used for pure text.claudez-pz--system-promptz --max-turns4z--allowed-toolsrd1z--disallowed-tools,T)cwdcapture_outputr^timeoutstdinrzclaude -p failed (z): N) DESIGN_MANUALjoin _NO_TOOLS subprocessrunstrROOTCLAUDE_TIMEOUTDEVNULL returncode RuntimeErrorstderrstdoutstrip) user_promptimagecmdrAs r"_clauders {,=}c#4f>{,=}c#7)9LNsD $T-Z5G5G IA||q/ ~S xx3188::> r$cd|zdzS)Nu0You are running HEADLESS: there is no interactive turn, so NEVER ask a clarifying question — assume the documented defaults instead (round cut, US sizing, a sensible metal). Every spec MUST have either "archetype" (preset) OR a "shank" (v3) — never omit both. If — and ONLY if — the request is not a ring description at all (gibberish, empty, spam, or clearly off-topic), do NOT invent a ring: output exactly {"reject": ""} instead. A vague but real ring request (e.g. just "a gold ring") is NOT a reject — fill defaults and design it. zr Output ONLY the JSON object (a RingSpec, or the reject object): no prose, no explanation, no markdown code fence.r,) instructions r"_author_promptrs# - P P Qr$c (d}i}tdtdzD]}t|}|r|d|zz }t||}t |}|t d|dd}Dd |vrGd |vrCt d t |d dd d dt |jd ddgdifcS||d <|}t|} | jdr| |fcSdj| jddg} t d|d| dd| }|r |fSd|fS)a*Author a spec and build it, self-correcting on validation/build errors. Returns (build_result_or_None, last_spec). build_result is the ringcli result dict; None means we never got parseable JSON out of the model. With `image`, the first model call reads the photo as a design reference.rLrXzT Your previous spec FAILED. Fix exactly these and re-emit the full corrected JSON: rNz attempt z: no JSON in model outputz0Your last output contained no valid JSON object.rejectrMz rejected: xFT)okrerrorsr; rzunknown build failurez build failed: ) r[MAX_SPEC_ATTEMPTSrrrbr#r}rH_buildry) rrMr errors_ctx last_specattemptpromptoutspecresulterrss r" author_specrsk JI-12 ,  <>HI JFfE*S! < :gY&?@ AKJ  t d 2 <DN 3DS 9:; <4"488H#56t<=?@BC CV   ::d 4< yyH/F.GHI z'/$t* >? -. FI 55TI 55r$c tjtddddtj|gt t ddt}|jj}d|vr( tj||jddSd|xs |jjd dgd S#tj$rY:wxYw) N-mz ringcli.clibuild --spec-jsonTrsrtr^rurWFrw)rr)r{r|PYBINr)r8r}r~ BUILD_TIMEOUTrrr*indexr]r)rrArs r"rrst]G] 4(*/24y - 9A ((.. C cz ::c#))C./23 3S_AHH$;$;$=de$D#E FF##   s(&B44C  C c t|dz }tdz dz |z }t||dz ddgt||dz ddgfD]<}tjt d d t|g|zttd d >tjt d dt|t||dz gttd d y)zEStudio previews + parts GLB, best-effort (same commands as serve.py)..pyr cliz.pngz25:20z --supportsz -head.pngz--headrzringcli.renderTi,)rsrtruz ringcli.glbz .parts.glbN)DESIGNSr~r}r{r|r)rMgenoutdirargss r"_render_previewsrs tfCL C K % '$ .Ff$t},-w Ef$y112GXFHHt%5s3x@4Gt9T3 HHNNE4CD6!44574ysDr$ctdz dz |z |dz }|jxr|jjdkDS)z2*>??  I!IsA'' A76A7uI couldn't turn that into a ring I can build. Try describing the cut (round, oval, emerald…), metal, ring size, and a carat or style — one ring per message.c t|}|sy td|dtj|d|d}|j jjd S#t$r}t d|dYd}~yd}~wwxYw) zIs this follow-up text a REVISION of `design`, or a request for a NEW ring? Returns True for revise. Defaults to new on any ambiguity/error.Fz&The customer already has ring design "z" with this spec: z Their new message is: "z" Is this a REVISION of that existing ring, or a request for a brand-NEW, different ring? A tweak to metal/stone/band/size is a revision; describing a different ring is new. Answer with ONLY one word: revise OR new.z classifier error (u) — defaulting to newNrevise) rrr)r8rr#rlowerr)r^rcurrentres r"_classify_revisionrsF#G  4VH revision of z -> new ringphotoznew z request z 'z': Pz*The customer sent the reference image at: uh Read that image — it is the ring they want as a REFERENCE. Compose ONE RingSpec matching what you seez!, then apply this modification: ""z. A photo cannot show ring size, so use size 6.5. Assume documented defaults for anything not visible. Use exactly this name: "".zKTranslate this customer request into ONE RingSpec. Use exactly this name: "z". Customer request: rr size_assumedTrDdonez done: z# built + previews; bot will deliverrrzno buildable specfailed)rDerrorz failed: u — rz error on : ) rHrIr#r_route_as_revisionrrrrBry FRIENDLY_FAILr) reqr>rMr^rrkindrrrextrarrs r"handle_new_requestr.s$iVcggfo.CtC GGG Ewwz"H #;$ xu7z CD dH - $XJ/ 0 sHd 3  }7D4vYse2dV3tCRym <=* CG6tfA>BP#fB( ( 66:V<004v7K#;EB  fjj&8D> T ".3^T*E  5V 5u 5 8D6!DE F99fl//;N:OPQD X] C :dV5ds 5 6 *S? {4&1% ())*s :BF =A F G#F;;Gc4tjjdd||ddtjt j jdd}tjr'tjtjndgi}|dj|tjjd d tj!tj"|d t%||d |dt'|dd |y)u1Convert a Telegram follow-up into a studio note against `design` and run the existing revise path, then retire the request so it never builds as a new ring. The customer already has the (same) studio link; revise.py keeps the same name so that link just updates — no new bot delivery needed.Nrevisionopenrr)r<rr^rrDcreatedcommentsTr/r2r3r<)rr<r^r)rDnotifiedrouted_revision)uuiduuid4hexrrrrrCOMMENTSr(r)r*r+appendr5r6r7r8 handle_noterB)r>rr^noter9s r"rr`s **,""2A&&*||HLL1;;Y;O QD08/@4::h((* +zSUFVDD! OO$6  4236dTBCVdFKr$c|d|d|d}}}|jdr|ddn|}td|d|d|dd t|}|std |y d |d tj|d |d|d }t t |}t|}|td|y||d<tjtd|dtj|d|dd|ddg ttddt} | jdk(rtd|d|ytd|d| jxs | j j#ddy#t$$r} td|d| Yd} ~ yd} ~ wwxYw) Nrr<r^z-prodznote z on rrz skip: no current spec for z)Here is the CURRENT RingSpec for design "z": z) The customer left this revision note: "zN" Apply the change, keeping everything else the same. Use exactly this name: "rz( skip: model produced no JSON for note rMzharness/revise.pyrz --resolvez--notez applied: rTrrz revised z, resolved note z revise.py failed for i8z error revising )endswithr#rr)r8rrrbr{r|rr}r~rrrrrr) rrnote_idr^baserrrrrArs r"rrrs NDJV TGF //'26#2;D5 dV2d3Bi] 34D!G  +D6 2307vTzz'"#$66:V<&  $  n[12S! < ;G9E F V NN '}djj>N '8yds -E GD $T= R <<1  :dV#3G9= > *4&XX)002459:< = 0  b .//0s&AE .A6E %:E F)E??Fc&tjsiS tjtj }|j dgDcic]}|d|j ddc}S#tj $ricYSwxYwcc}w)uid -> kind for open notes. System notes (kind:'system') are gate-failure breadcrumbs meant for a human — the daemon must NOT try to 'revise' them.rr<rr)rr(r)r*r+r]rH)r9cs r" _note_kindsrs ??  zz(,,./9=R8P Q1AdGQUU6:. . QQ     Qs'A3B3B  B ctt}|jdgD] }t|t }|jdgD]%}|j|ddk(rt |'y)N new_requests open_notesr<system)rUrrHrrr)trkindsrs r"cyclersrAuu^R( 3 MElB' 99T$Z H , Dr$cdtjv}tdtd|rdndd|r t y t t jt%#t $r}td|Yd}~6d}~wwxYw) Nz--oncezdesign agent up (poll su — ONCErLrNrz cycle error: )sysargvr# POLL_SECONDSrrtimesleep)oncers r"mainrs| sxx D !,q"0MQ OP    ( G <  ( =& ' ' (s A B)A<<B__main__)r r}returnNone)rdict)r9rrr)r>r}r dict | None)r>r}rbool)rr)r^r}rr)N)rr}r str | Nonerr})rr}rr})rr}rMr}rrrztuple[dict | None, dict])rrrr)rMr}rr)rMr}rr)rr}rr)r^r}rr}rr)rrrr)r>r}rr}r^r}rr)rrrr)rint)E__doc__ __future__rr)r{rrrrrrpathlibr__file__resolver5r~r}rr'rrr+rxrrrrrOr(r_linerros partition_k__venviron setdefaultpathinsertrr#r-r:rBrIrUrbrzrrrrrrrrrrrrrrr__name__ SystemExitr,r$r"rs,#  22 H~&&-- D;  & 12 +  (? : +  (? :   !K/::<   ;?-9O9O9QdVm & & ( 3 3 5WY6E e|EKKM44S9OOC( Ar bhhj"((*5 6 3ti'()' 4 ",. C . Q%)6!6-E6H G D: < 4*/*dL$0D R  ! z TV r$