# Modular Runtime Phase 5 — Matched Complex Shadow 02

Date: 2026-08-01

Status: accepted matched comparison; modular wins

Live test time: 710.057 seconds

## Sealed comparison

Both runtimes received clones of one content-addressed Care Dashboard fixture and the same four-outcome contract:

1. implement the exact five-field person summary;
2. implement stable overdue-first care priority;
3. accept their combined dashboard behavior;
4. implement a dependent caregiver handoff from both accepted modules.

The two core source files were independent and eligible to run concurrently. The handoff owned one third file and could start only after the combined core milestone was accepted. Both runtimes received the same four final commands and the same unattended model-call and wall-clock ceilings.

Canary SHA-256: `0f415b32a357fbcdf4a8aca99ac64519cbc8f79d30dd3e6c8697abb8f3a82189`.

The complex threshold was frozen before execution: modular had to accept the exact contract and materially improve at least one of elapsed time, model-call count, or recovery while preserving correctness. Material elapsed improvement was defined as a ratio no greater than `0.80`.

## Result

| Measure | Legacy Core | Modular builder |
|---|---:|---:|
| Contract outcome | `needs_review` | `accepted` |
| Elapsed time | 467.083 s | 242.608 s |
| Model calls | 4 Luna | 3 Luna + 1 Sol |
| Attempts | 4 | 3 |
| Retries | 0 | 0 |
| Orphaned processes | 0 | 0 |
| Integration promotions | 0 | 2 |
| Final checks passed | 0/4 on authority | 4/4 |

Comparator verdict: `modular_wins`.

The modular runtime completed in `0.5194108970×` legacy elapsed time, 224.475 seconds faster, with the same total model-call count and no retry or orphan regression.

## Modular execution proved

1. Two Luna/xhigh implementation workers started in isolated worktrees against one accepted base and disjoint one-file ownership.
2. The existing graph runner accepted both exact candidates without either worker holding integration authority.
3. The controller formed one compatible epoch, created one deterministic union commit, ran the person, priority, and system checks, and advanced authority once.
4. The core milestone checkpointed and compacted without losing dependency truth.
5. One Sol/high renewal promoted only the remaining coarse `care-handoff` milestone into horizon revision two.
6. One Luna/xhigh handoff worker consumed the accepted current integration head.
7. Trusted direct integration promoted that candidate, and all four sealed final commands passed from the clean authoritative repository.
8. Every worker process family finished and reaped; no human checkpoint occurred.

Legacy Core also respected implementation dependencies: two implementation workers ran concurrently, followed by the dependent handoff worker. Its fourth model call was a Luna-owned integration stage. The worker proved the exact merges and all four tests in a writable verification clone, but it could not create `.git/ORIG_HEAD.lock` in the authoritative workspace. Legacy therefore returned `needs_review`, made zero authority promotions, and correctly did not claim success.

## Revision 01 retained

The first complex attempt is preserved as rejected harness evidence rather than erased. Its two modular core workers, deterministic union, first checkpoint, compaction, and Sol renewal succeeded, but the test helper authored the handoff packet with one combined acceptance sentence while the production packet contract requires two to six concrete checks. The runtime rejected it before launching a third Luna worker.

Revision 01 `run-summary.json` SHA-256: `40359b8d1630d3f9c221921a9c6fdeaf1ea41b53a1ca5a650a3e5007d09a5759`.

Before revision 02, the helper was repaired to use two independent checks and a deterministic preflight was added for every complex packet. That preflight now runs before any model call. The complete deterministic suite and TypeScript passed before revision 02 began.

## Durable evidence

Accepted evidence directory: [`evidence/MODULAR_RUNTIME_PHASE5_COMPLEX_SHADOW_02`](./evidence/MODULAR_RUNTIME_PHASE5_COMPLEX_SHADOW_02/)

`run-summary.json` SHA-256: `d77acdc328ee97cc659afe29573b4fd5107ac565c2b90dbbd1d62d82330e90d0`.

Content-addressed comparison SHA-256: `7c25a2620aae635cfb7f515a8a7450eeda69797ea006a2f9abcfa152a8f1287b`.

Independent evidence review reparsed the canary and both run envelopes and reproduced the exact stored comparison. A separate aggregate reviewer then combined this immutable complex verdict with the accepted direct verdict and derived `evidence_supports_switch` from production comparator code.

## Boundary

This is strong comparative evidence, not an automatic mutation of production authority. Legacy Core remains intact and authoritative until an explicit transition is authorized and the migration procedure is exercised recoverably.