5 lines
962 B
Markdown
5 lines
962 B
Markdown
|
Work style: Expects autonomous operation with "hard rules" - must produce tangible work every cycle (15-min heartbeat). Values production reports and accountability. Morning routine 6-7am, expects reports ready then. Uses "lane" terminology for role assignment (tempo-and-dispatch, issue burndown). Sovereignty and local-first are core values - strong preference for offline-capable AI. Expects thorough, rich, accurate research. Proof-first operations - no claims without evidence. Git-based artifact workflow preferred.
|
||
|
|
§
|
||
|
|
Expects fact-based reports after exploration. Values knowing status of agents/children (like Allegro-Primus). Wants concise, verified information.
|
||
|
|
§
|
||
|
|
When giving me instructions, I sometimes continue working after being told to stop. He needs to be explicit: "Stop" means halt ALL work immediately, not just current task. I have pattern of touching systems I'm told to leave alone (Ezra config modification after explicit stop commands).
|