[{"data":1,"prerenderedAt":214},["ShallowReactive",2],{"docs-\u002Fdocs\u002Ffinish":3},{"id":4,"title":5,"body":6,"description":206,"extension":207,"meta":208,"navigation":209,"path":210,"seo":211,"stem":212,"__hash__":213},"docs\u002Fdocs\u002Ffinish.md","Phase C - Finish (The Outlet)",{"type":7,"value":8,"toc":197},"minimark",[9,14,18,21,25,33,36,112,115,119,122,149,158,162,169,172,176,179,194],[10,11,13],"h2",{"id":12},"overview","Overview",[15,16,17],"p",{},"The Forge loop ends when the Tester approves the full suite against the ephemeral environment. At that point, no agent takes any further action automatically. The work is complete - but it has not been delivered. That transition requires you.",[15,19,20],{},"This is the Finish phase: the outlet of the pipeline.",[10,22,24],{"id":23},"the-validation-package","The Validation Package",[15,26,27,28,32],{},"When the Forge loop completes, the DevOps agent assembles a ",[29,30,31],"strong",{},"Validation Package"," and delivers it to you. The package contains everything you need to make a confident delivery decision in under 15 minutes.",[15,34,35],{},"A typical Validation Package includes:",[37,38,39,52],"table",{},[40,41,42],"thead",{},[43,44,45,49],"tr",{},[46,47,48],"th",{},"Section",[46,50,51],{},"Contents",[53,54,55,64,72,80,88,96,104],"tbody",{},[43,56,57,61],{},[58,59,60],"td",{},"Summary",[58,62,63],{},"One-paragraph plain-language description of what was built",[43,65,66,69],{},[58,67,68],{},"Screenshots \u002F screen recordings",[58,70,71],{},"Visual evidence of the feature working in the ephemeral environment",[43,73,74,77],{},[58,75,76],{},"Test report",[58,78,79],{},"Full test suite results with pass\u002Ffail counts and any skipped tests",[43,81,82,85],{},[58,83,84],{},"Diff summary",[58,86,87],{},"Line-count by file, with links to the full diff",[43,89,90,93],{},[58,91,92],{},"Performance notes",[58,94,95],{},"Any latency or bundle-size changes flagged by the Reviewer",[43,97,98,101],{},[58,99,100],{},"Migration plan",[58,102,103],{},"Database migrations that will run on deploy, with rollback instructions",[43,105,106,109],{},[58,107,108],{},"Known limitations",[58,110,111],{},"Anything the Analytic flagged as out of scope for this ticket",[15,113,114],{},"The package is designed to be read, not skimmed past. The expectation is that you will read the summary, look at the screenshots, and check the test report before confirming.",[10,116,118],{"id":117},"the-audit","The audit",[15,120,121],{},"Your job as Gatekeeper is to review the Validation Package and make one of three decisions:",[123,124,125,132,138],"ol",{},[126,127,128,131],"li",{},[29,129,130],{},"Confirm"," - the work meets the acceptance criteria; proceed to delivery.",[126,133,134,137],{},[29,135,136],{},"Reject with notes"," - the work does not meet acceptance criteria; return to Forge with specific feedback.",[126,139,140,143,144,148],{},[29,141,142],{},"Defer"," - the work is acceptable but this is not the right time to deliver; leave the ticket in ",[145,146,147],"code",{},"Validating"," state.",[150,151,152],"blockquote",{},[15,153,154,157],{},[29,155,156],{},"Warning:"," Do not skip the audit. The Validation Package is not bureaucracy - it is the moment the human takes responsibility for the delivery. An agent-confirmed deploy is not a fully-reviewed delivery.",[10,159,161],{"id":160},"the-delivery","The delivery",[15,163,164,165,168],{},"When you confirm, the DevOps agent executes the deployment pipeline: merges the branch, runs migrations against production, promotes the image, and verifies the health check. The ticket transitions to ",[145,166,167],{},"Done"," and Cycle Time is recorded.",[15,170,171],{},"That is delivery. No ceremony. No sprint review. No deployment meeting.",[10,173,175],{"id":174},"after-delivery","After delivery",[15,177,178],{},"The system records:",[180,181,182,185,188,191],"ul",{},[126,183,184],{},"Cycle Time from trigger to confirm",[126,186,187],{},"Interruption count for this ticket",[126,189,190],{},"Test suite coverage delta",[126,192,193],{},"Any performance changes",[15,195,196],{},"Over time, this data builds the probabilistic forecasting model that replaces velocity estimates. It also feeds back into the Analytic agent's instructions - if a particular ticket type is consistently slower than expected, the spec template for that type is updated.",{"title":198,"searchDepth":199,"depth":199,"links":200},"",2,[201,202,203,204,205],{"id":12,"depth":199,"text":13},{"id":23,"depth":199,"text":24},{"id":117,"depth":199,"text":118},{"id":160,"depth":199,"text":161},{"id":174,"depth":199,"text":175},"The Validation Package, the human audit, and the single command that delivers.","md",{},true,"\u002Fdocs\u002Ffinish",{"title":5,"description":206},"docs\u002Ffinish","Wqmv3ONIoegmTS_fjD4zdA2_sO841Y8EJOzMTvuGfxc",1778559261707]