[{"data":1,"prerenderedAt":135},["ShallowReactive",2],{"product-\u002Fwork\u002Fsweeai":3},{"id":4,"title":5,"bench":6,"body":7,"brand":5,"claim":117,"description":118,"extension":119,"handoff":120,"listed":121,"meta":122,"movement":123,"navigation":121,"order":124,"path":125,"receipt":126,"receiptLabel":126,"receiptStatus":127,"retired":126,"seo":128,"state":129,"stem":130,"substrate":131,"__hash__":134},"products\u002Fproducts\u002Fsweeai.md","SweeAI","agent",{"type":8,"value":9,"toc":110},"minimark",[10,40,47,54,59,75,78,82,85,89,100],[11,12,13,14,18,19,22,23,27,28,31,32,35,36,39],"p",{},"SweeAI is the product; the company is ",[15,16,17],"strong",{},"Swee",". Underneath the product sits ",[15,20,21],{},"SweeOS",", the orchestration layer —\nthe glue and the scheduling, the part that runs agents. SweeOS ",[24,25,26],"em",{},"hosts"," a harness, and the\ndefault resident one is ",[15,29,30],{},"SweeHarness","; it ",[24,33,34],{},"calls"," ",[15,37,38],{},"SweeTrust"," for enforcement.",[11,41,42,43,46],{},"That second arrow only points one way, and it is the whole reason the hierarchy is worth\nwriting down rather than just drawing. Orchestration may ask the trust kernel whether an\naction is permitted. It may not reconfigure the answer. The tempting simplification — the\nOS is the OS, so it owns everything — is right about the glue and wrong about the cage,\nbecause ",[15,44,45],{},"a guard the guarded thing controls is not a guard."," SweeTrust never depends on\nSweeOS, and SweeOS may not widen its own authority.",[11,48,49,50,53],{},"Listing this card at all is a deliberate choice, and it is the honest one: ",[15,51,52],{},"the\norchestration layer is not built."," There is no execution engine, and that omission is a\ndecision rather than a gap — an ADR concluded it should be bought. The supervision client is\ndesigned through the skeleton plane and no further. The adoption flow, which is the actual\nthesis, has not been started.",[55,56,58],"h2",{"id":57},"what-is-real","What is real",[11,60,61,62,66,67,70,71,74],{},"The monorepo, and the discipline inside it. One package, ",[63,64,65],"code",{},"sweetrust@0.3.0",", carrying\nthree primitives with ",[15,68,69],{},"177 passing tests"," between them, arrived at by a pass that found\neleven fail-open defects in code that already looked finished. Two of those eleven were\n",[15,72,73],{},"the same defect shape in different primitives"," — an empty fold returning the strongest\npossible claim instead of the weakest. That is a blind spot with a signature, and it is now something to grep for.",[11,76,77],{},"That is harness engineering rather than product engineering, which is why it belongs on this\nsite at all.",[55,79,81],{"id":80},"the-handoff","The handoff",[11,83,84],{},"A fleet of agents produces a supervision problem long before it produces a scaling problem.\nTen concurrent runs generate more status than a person can read, and the useful surface is\nnot a dashboard — it is a queue of things that genuinely need a human, ranked, arriving\nsomewhere a person already looks. Designing that queue is the thesis. It is unbuilt, and\nthis page says so.",[55,86,88],{"id":87},"state-designed-nothing-public","State — designed, nothing public",[11,90,91,92,95,96,99],{},"The card says ",[15,93,94],{},"designed"," rather than built, and the distinction is the point. Real code\nexists in the monorepo and it is described above; the ",[24,97,98],{},"orchestration layer this card is\nnamed for"," does not. Claiming \"built\" would have let one true fact — the packages are real —\nstand in as the answer to a different question, which is the exact move the rest of this site\nexists to refuse.",[11,101,102,105,106,109],{},[63,103,104],{},"sweeai\u002Fmonorepo"," is private and ",[63,107,108],{},"@sweetrust\u002F*"," is unpublished, so a visitor can verify none\nof it. Hence no receipt.",{"title":111,"searchDepth":112,"depth":112,"links":113},"",2,[114,115,116],{"id":57,"depth":112,"text":58},{"id":80,"depth":112,"text":81},{"id":87,"depth":112,"text":88},"The supervision layer for a fleet of agents.","SweeAI is the product; the company is Swee. Underneath the product sits SweeOS, the orchestration layer —\nthe glue and the scheduling, the part that runs agents. SweeOS hosts a harness, and the\ndefault resident one is SweeHarness; it calls SweeTrust for enforcement.","md","Supervising a fleet. Of N runs happening right now, which one needs you — and can you tell from a phone?",true,{},"orchestration",5,"\u002Fproducts\u002Fsweeai",null,"none-yet",{"title":5,"description":118},"specced","products\u002Fsweeai",[132,133],"TypeScript","Sui","kk9J6dsb5IG6sa9IKHnlKVexp5W5IOdrgCFx1ULxIZo",1790479752332]