{"problem":{"version":1,"last_iteration":0,"domain":"sihlhack","assumptions":[{"id":"A001","statement":"Participants want direct hardware access during hackathon","status":"PENDING","evidence":null,"iteration_updated":null},{"id":"A002","statement":"Sihl-Sim API should mirror real hardware API exactly","status":"PENDING","evidence":null,"iteration_updated":null},{"id":"A003","statement":"Teams prefer self-organizing around specific layers (scheduling, thermal, safety)","status":"PENDING","evidence":null,"iteration_updated":null},{"id":"A004","statement":"Single unified challenge metric works better than multiple separate challenges","status":"PENDING","evidence":null,"iteration_updated":null}],"requirements":[],"open_questions":["What level of hardware abstraction do beginners need?","Should simulation and hardware share the same API?","How do power users differ from casual participants?","What happens when thermal limits are exceeded?","How should Grid-OS handle conflicting job priorities?"],"signals_summary":{"confusion_count":0,"excitement_count":0,"frustration_count":0}},"solution":{"version":1,"direction":"API-first design with progressive disclosure","decisions":[{"id":"D001","statement":"Single unified value metric: V(t) = α×Compute + β×Heat - γ×Energy","rationale":"Simple, objective, measurable. Teams self-optimize.","iteration":0,"status":"TENTATIVE"},{"id":"D002","statement":"Sihl-Sim for development, reference hardware for finals","rationale":"Code once, deploy twice. Simulation enables remote participation.","iteration":0,"status":"TENTATIVE"}],"sketches":[],"design_themes":[]}}