A Merge-Readiness Pack (MRP) is the artifact Structured Agentic Software Engineering (SASE) (SASE) proposes as the target deliverable of an agent’s work, introduced in Agentic Software Engineering: Foundational Pillars and a Research Roadmap. Rather than a human reviewer auditing dozens of raw pull requests, the paper argues review should focus on auditing one structured MRP that proves the agent’s work is trustworthy.
Usage
The paper defines five criteria an MRP must provide evidence for: Functional Completeness (proof, e.g. end-to-end test results, that the feature is complete and behaves as specified in realistic scenarios, addressing agents’ tendency to produce superficial or partial fixes that pass only a narrow set of tests); Sound Verification (not just passing test logs, but the agent’s own test plan and the new test cases it generated, proving the verification strategy itself is sound); Exemplary SE Hygiene (static analysis, linting, and complexity-checker reports demonstrating the code is clean, readable, and minimizes technical debt); Clear Rationale and Communication (a human-readable summary, analogous to a PR description, synthesizing an agent’s often verbose reasoning trajectory into an explanation of the approach and trade-offs); and Full Auditability (a “frozen” audit trail — versioned links to the exact BriefingScript/MentorScript, tools, and agent trajectory used — ensuring the result can be reliably reproduced). To manage the resulting density of information, the paper states an MRP must support “progressive disclosure,” letting a reviewer see a high-level summary before drilling into specific evidence like test logs or execution traces. A human responds to an MRP with a Version Controlled Resolution (VCR).
Related Terms
Version Controlled Resolution (VCR), Agentic Guidance Engineering (AGE), Consultation Request Pack (CRP)