research-document
Software Engineering research queue
Software Engineering research queue
The graph-aware portfolio view is
research/frontier/PORTFOLIO-QUEUE.md. Mission files are the durable execution
records; this file is the compact operator view.
| Rank | Question | Decision affected | Dependency | Status |
|---|---|---|---|---|
| 1 | Can the handoff protocol be frozen as a valid confirmatory experiment? | Whether EX-HANDOFF may begin | preflight, ethics, accessibility, statistics, independent review | active; external-dependency |
| 2 | Can rubric, fixtures, safeguards, and accessibility pass preflight? | Whether efficacy research is justified | independent reviewers, accessibility participants, ethics determination | external-dependency |
| 3 | Do completed packages survive independent review? | Accept, revise, or reject four REPs and three decisions | independent reviewer | external-dependency |
| 4 | Which conditions predict lifecycle-adjusted benefit from AI coding assistance? | AI-use policy and pilot design | partner, safeguards, telemetry review, preregistration | blocked |
| 5 | Can whole-ROS value be attributed prospectively? | ROS adoption | first handoff milestone | dependency-blocked |
| 6 | Does the rejected discipline label have measurable coordination value? | Terminology disposition | none | low-value proposed |
Completed in review
- First slice selected: RP-HANDOFF-2026-A8E1 / DF-HANDOFF-2026-5C9B.
- Distinct-discipline claim rejected: RP-BOUNDARY-2026-5A7C / DF-BOUNDARY-2026-3F72.
- Conditional AI-coding evidence map: RP-AICODING-2026-B7E2.
- Handoff outcome model: RP-MEASURES-2026-71B4. Primary outcome is safe continuation under an accessible time policy; harm and lifecycle cost are separate gates.
- Handoff safeguards: MS-SAFEGUARDS-2026-89D1. Design complete, but recruitment is not authorized.
- Artifact baseline: MS-BASELINE-2026-E5A7 / DF-BASELINE-2026-48C0. A competent conventional status note is the control; whole-ROS attribution is separate.