[{"data":1,"prerenderedAt":167},["ShallowReactive",2],{"docs-\u002Fdocs\u002Ffeed":3},{"id":4,"title":5,"body":6,"description":159,"extension":160,"meta":161,"navigation":162,"path":163,"seo":164,"stem":165,"__hash__":166},"docs\u002Fdocs\u002Ffeed.md","Phase A - Feed (The Inlet)",{"type":7,"value":8,"toc":150},"minimark",[9,14,18,26,30,33,49,57,61,64,78,89,111,114,118,125,128,136,140,143],[10,11,13],"h2",{"id":12},"overview","Overview",[15,16,17],"p",{},"The Feed phase is the inlet of the pipeline. It transforms a raw, loosely-specified human requirement into a precise, self-contained ticket that is ready to be triggered whenever you choose. Nothing in the Forge phase begins until you say so.",[15,19,20,21,25],{},"The key insight: ",[22,23,24],"strong",{},"staging a ticket costs almost nothing",". Triggering a ticket has a real cost - agent time, compute, your attention for the Validation Package. The Feed phase protects you from triggering work that is not yet well understood.",[10,27,29],{"id":28},"step-1-submit-the-requirement","Step 1 - Submit the requirement",[15,31,32],{},"You (the Orchestrator) drop a raw requirement into the Inlet. The format is deliberately unconstrained. It can be:",[34,35,36,40,43,46],"ul",{},[37,38,39],"li",{},"A one-line user story: \"As a user, I want to reset my password by email.\"",[37,41,42],{},"A paragraph of context: \"Our analytics dashboard is missing a week-over-week comparison view. Users keep asking about it in support tickets.\"",[37,44,45],{},"A link to a Figma mockup with a note: \"Build this.\"",[37,47,48],{},"A voice memo transcript.",[15,50,51,52,56],{},"The AI PM receives it and creates a draft ticket in the ",[53,54,55],"code",{},"Inbox"," state. No work starts at this point.",[10,58,60],{"id":59},"step-2-pm-refines-the-ticket","Step 2 - PM refines the ticket",[15,62,63],{},"The AI PM takes the raw requirement and frames it into a well-formed ticket:",[34,65,66,69,72,75],{},[37,67,68],{},"Title and user story",[37,70,71],{},"Acceptance criteria",[37,73,74],{},"Priority",[37,76,77],{},"Dependencies on other staged or in-flight tickets",[15,79,80,81,84,85,88],{},"For ",[22,82,83],{},"straightforward tickets"," the PM can do this alone. For ",[22,86,87],{},"larger or cross-cutting work"," the PM pulls in the Analytic to co-author a richer task description: which areas of the product the change touches, which existing use cases it interacts with, what the expected user-visible behaviour looks like end-to-end.",[90,91,92],"blockquote",{},[15,93,94,97,98,102,103,106,107,110],{},[22,95,96],{},"Important:"," the goal of Feed is ",[99,100,101],"em",{},"not"," to produce a full technical specification. API contracts, data models, component lists, sequence diagrams - those belong in the Forge phase, after you trigger the ticket. Feed produces only what the agents need to confidently start: a clear description of ",[99,104,105],{},"what"," is wanted and ",[99,108,109],{},"why",".",[15,112,113],{},"If either agent encounters genuine ambiguity that cannot be resolved by inferring user intent, they surface a specific, minimal question to the Subject Matter Expert - never vague (\"Can you tell us more?\") and always with concrete options (\"Should deleted records be permanently purged after 30 days, or retained indefinitely?\").",[10,115,117],{"id":116},"step-3-ticket-moves-to-staged","Step 3 - Ticket moves to Staged",[15,119,120,121,124],{},"Once the PM is satisfied that the ticket has clear acceptance criteria and an unambiguous task description, the ticket transitions to the ",[53,122,123],{},"Staged"," state.",[15,126,127],{},"A staged ticket is a promise: if you trigger this ticket right now, the agents have everything they need to start the Forge phase without coming back to you for clarification of intent.",[90,129,130],{},[15,131,132,135],{},[22,133,134],{},"Note:"," Staged does not mean prioritised. You may have dozens of staged tickets. The Orchestrator decides which ones to trigger and when, based on current business priority.",[10,137,139],{"id":138},"step-4-you-trigger-the-ticket","Step 4 - You trigger the ticket",[15,141,142],{},"When you are ready - when you know you will have 10-15 minutes later in the day to review a Validation Package - you trigger the staged ticket.",[15,144,145,146,149],{},"The ticket transitions to ",[53,147,148],{},"In Progress"," and the Forge phase begins.",{"title":151,"searchDepth":152,"depth":152,"links":153},"",2,[154,155,156,157,158],{"id":12,"depth":152,"text":13},{"id":28,"depth":152,"text":29},{"id":59,"depth":152,"text":60},{"id":116,"depth":152,"text":117},{"id":138,"depth":152,"text":139},"How a raw requirement enters the system and becomes a staged, ready-to-trigger ticket.","md",{},true,"\u002Fdocs\u002Ffeed",{"title":5,"description":159},"docs\u002Ffeed","9jEtU-HVcCbSMDEy0sAH4g8FEOFoh8kuUni_KzhXHHU",1778559261706]