0crews
0voyages
0queued
← All reports
Demo layout

This report is an illustrative placeholder — the charts and figures are sample data, not a finalised spec. Real data model, metrics, and acceptance criteria for this report still need to be planned and built. Only QA Reports are modelled on real Maestro output.

Acceptance Criteria Completion

15
Criteria
11
Met
2
Partial
2
Outstanding
Overall completion — 73% met
● 11 met● 2 partial● 2 outstanding
PLNORD-0210Plan: slot pressure heuristics3/3
  • ✓Heuristic weighs queue depth + running countMet
  • ✓Cooldown prevents flappingMet
  • ✓Hard ceiling of 5 crews documentedMet
BLDORD-0212Implement slot pressure heuristics3/4
  • ✓Autoscaler reacts to queue depthMet
  • ~Cooldown prevents flapping when a voyage completesPartial
  • ✓Ceiling of 5 crews never exceededMet
  • ✓Behind a feature flagMet
TSTORD-0214Load test: 5-crew saturation4/4
  • ✓Sustains 5 concurrent crews for 30mMet
  • ✓No slot leak after voyage completionMet
  • ✓p99 dispatch latency < 800msMet
  • ✓Burst recovery within 2 cyclesMet
SECORD-0216Threat model: autoscaler API1/4
  • ✓Scale endpoint requires authMet
  • ○Rate limiting on scale endpointOutstanding
  • ○mTLS dispatcher ↔ autoscalerOutstanding
  • ~No secrets in scale-decision logsPartial