A session's life: how Iris is steered

A session's life: how Iris is steered A workflow diagram generated by Archify. 01 / Iris session 02 / Hooks + guards 03 / Memory + Brain Start Work + verify Close + carry forward Luke opens · terminal or phone · Iris session › Start Luke opens terminal or phone Grounding · identity · health · Iris session › Start Grounding identity · health Work · skills · agents · MCPs · Iris session › Work + verify Work skills · agents · MCPs Bench + verify · Codex · read-back · Iris session › Work + verify Bench + verify Codex · read-back Session end · lessons · handoff · Iris session › Close + carry forward Session end lessons · handoff Guard hooks · deny before run · Hooks + guards › Work + verify Guard hooks deny before run Stop hooks · save each turn · Hooks + guards › Work + verify Stop hooks save each turn Start pack · compiled weekly · Memory + Brain › Start Start pack compiled weekly Consolidate · 6-hourly · nightly · Memory + Brain › Work + verify Consolidate 6-hourly · nightly Memory stores · graph · vectors · wiki · Memory + Brain › Close + carry forward Memory stores graph · vectors · wiki Journal · predictions · notes · Memory + Brain › Close + carry forward Journal predictions · notes writes facts starts read transcripts Sunday compile every call every turn Legend Agent logic Policy Tool action Context / trace External system

Re-chosen each session

  • • No memory between sessions; grounding rebuilds Iris
  • • Pack, journal and handoff are written for the next one

Guarded, then benched

  • • Hooks check tool calls before they run
  • • Codex reviews consequential work before it ships

Every turn is kept

  • • Stop hooks save each turn to the transcript store
  • • The Brain turns terminal transcripts into facts every 6h