Dated source reference. Current release status: handoff state. Full original relative paths are in the developer archive.

Rule expansion, native metadata and match assets — active work63

Work70's supported private platform subset is accepted on API70e/API55, native70d/DLL5cf76196 and strict independent module70b.634 Windows API tests/126 schemas pass; all88 native inputs retain470-check original/college fixtures,1,261 registry checks and eight fault processes. Original70liveo/API70c passes natural9–6 and301 schema checks; college70liveq/API70e passes natural6–3 and247 checks after the frozen-overtime decoder fix. Together they record21 applied classification callbacks/nine native3→2 applications, copied C metadata, both selected IFF reads, identical reconciled deliveries to two independent consumers and repeated ACK with zero adapter/host/module faults. Changed FT counts retain original-instruction/headless evidence: original queries one baseline2→2 award; college queries none. Both runs close/restore98 files/DLL50/INI. Final preservation passes at00:25:15UTC, with95 originals in both games, protected binaries/packages/four hosts and zero owned workers/tasks. Custody is released. Arena subsequently reports successful corrected r11 playback and verified restoration/release at00:35:33UTC. Read-only shared status at00:36:12UTC confirms all three projects released/no lock, but free3,213,733,888 bytes is7,491,584 below the3GiB floor; no further GPU run is reserved and fresh storage guards must clear before acquisition. No public/stable promotion. See the current sharing ledger. Earlier checkpoints retain their recorded scope.

October19,22:27UTC work70: coordinated Dell sharing is explicitly authorized and MVP grants OpenHoops the next bounded GPU window once3GiB free is available. Shared custody contract replaces waiting for another safe answer.63livee/f still require deliberate exact-source staging, matching lease/process/disk guards, focused live checks and restoration. At initial handoff they remain unstarted; storage recovery and coordination are not game acceptance. Earlier wait instructions below retain their checkpoint context.

The user authorized all three platform milestones on October19,2026: finish the broader rule configuration/callback work; expose checked custom metadata directly to native modules; support safe per-match asset packages before launch. Presentation rendering, asset creation by the roster team, public release packaging, Mac/Linux game delivery and rare-rule campaigns remain deferred. No new agents are authorized.

Accepted baseline: private API53/HTTPv1, mainABI26/eventABI4/profile4/court3 and rule draft1, final adapter62final2 DLLcd992875.561 API tests/110 schemas,1,018 SDK cases,313 adapter cases plus six fault processes,606 boundary cases and128 captured-handler cases pass. Source62final is immutable. Stable35/restored isolated50,95 originals in both games,98 isolated files and four hosting identities remain protected.

Required outcomes

1. Frozen, validated timing/reset/bonus configuration reaches all relevant original and college consumers. FT/restart state has connected award, continuation/progress and settlement observations before FT-count/classification decisions are advertised. Each supported callback has a defined native transaction and unchanged native fallback; required/optional failure contracts remain.
2. A versioned plain C interface gives native modules copied, typed roster/team/player/arena/uniform metadata, distinct missing/null/false/zero/text, source-row/external-ID association and an expected match/context identity. Bind the exact context before revealing a requested match. Durable API/result context remains the same source of truth.
3. Checked immutable asset-package intake freezes manifest/file identities before startup; the original asset loader reads only the selected per-process overlay. Explicit conflicts/refusals, no in-place overwrite or hot swap, no executable payload/installer, preserved source assets and result provenance. Prove actual native loading on representative files, not just archive intake.
4. Dell-only builds/tests/game checks; exact current sources, meaningful original-instruction/headless checks, focused live acceptance, schemas/client examples/docs and preservation closeout. Recheck MVP before every desktop game launch and generate no shared input.

This is an active implementation ledger. Baseline verification does not claim these new capabilities yet.

Candidate checkpoint — headless63, not live acceptance

SourceAPI54/HTTPv1 retains mainABI26/event4/profile4/court3. Rule C ABI1 layouts remain; private rule transport/interpreter2 adds native-transaction scope/reasons while the reader still accepts1. Platform protocol1 and metadata C ABI1 are independent. No candidate was installed into any game during this work.

Implemented configuration: full/minimum clocks, period/OT whole-minute durations, backcourt selectors0/1, foul threshold5/6; college exposes a distinct rim amount and one-owner one-and-one/double-bonus bundle. FT-count1–3 executes before the original award publisher. Eligible two-/three-point classification executes through original release/foul consumers; generic/pass queries stay native. FT identity survives settlement, ordinals have disposal evidence, and following restart requires a connected native settlement. Required faults suspend after the native boundary; optional fallback is explicit and frozen values remain.

Native metadata supplies copied typed/provenance/entity values, canonical context and epoch/hash guards. Publication/ACK occurs at held phase4 before actual reveal. The broker persists binding first. Assets have bounded immutable ZIP intake, source/hash-bound selection, guarded native root-file reads, sealed independent handles and typed write/read failures. The original files are not replaced; result provenance freezes the observed package/overlay/file identities. See platform contract.

Earlier intermediate evidence includes592 Windows API tests (api63e),353 production/native-instruction checks per original/college fixture and platform63h integration. These stages remain historical evidence; use the final identities and counts below. Retained consumer63b evidence covers63 captured timing/scoring cases; platform63a covers2,954 parser checks/12 C checks. These fixtures contain declared stubs and start no game. Two real preserved stock IFFs pass admission (assets63b); this does not prove native game/render acceptance.

The user explicitly said to keep working headlessly and wait for their Dell-safe notification. MVP was running at the resource check. Headless source-matched checks and fixtures are complete. Remaining: independent native metadata observation in a real match, actual selected IFF reads and focused original/college exact-DLL acceptance, then post-game preservation/restoration. No public package, presentation renderer, rare-event campaign or agent is authorized.

Final headless candidate identity (supersedes earlier WIP builds)

Current full hook: native63i, archiveccb6bd3171d82bf99bb12fc20ce157dae862738e5298057f55adfd82ca34e183, DLL 56e66f24891bfe744e373e68a2798abaa608a92c394d7ecf27a310b2f7983935. Exact106 API/data/test inputs match api63f (595 passes, zero skips,122 schema definitions);16 rule/SDK inputs match rules63i (1,261 registry checks,383 per original/college fixture plus six publication-fault and two missing-actor processes); six platform/protocol/header inputs match platform63j (production export/ACK/hold/read-seal checks,300 concurrent broker status reads, five refusal processes). See source comparison. Native exports resolve undecorated.63 captured timing/scoring consumer cases and prior parser evidence retain their recorded scope.

The final-release correction uses the guarded native registration→detach-to-flight caller. Classification precedes the physical-state change; a held-state sample cannot be used as a gate. Both original and college fixtures now execute that original call sequence and verify a held shooting-foul answer survives its continuous-motion release without a second callback. Application receipts follow native flag/count readback, including the prospective count witness before FT publication. Generic/pass/FT classification queries stay native. Selected asset access now uses an explicit read-access allowlist; the eight forbidden-access cases stop before mutation.

Use pending runs 63livee (original) and 63livef (college), API63f/native63i/rules63i. Their original preflight and college preflight verify the final DLL, independent C module (a9b7d47da6fcbe813a7830ef8b45b763c2760111a3c162fb21e3ff6cbff7e788) and package identities without starting a game or modifying its files. Earlier pending63livea/b/c/d use superseded prototypes and must not be launched. All twenty-four generated PowerShell scripts parse; none was executed/registered. Scripts require an explicit user-safe receipt, then separately check MVP and exact process/source identities. Once the user gives the safe reply, complete these focused native runs, independent C metadata observation, actual selected court/arena opens, natural reconciled immutable results/two consumers/repeated ACK and preservation/restoration. Do not restart the deferred rare-rule campaign.

Missing actor/official-ball identity at an otherwise eligible classification boundary now explicitly degrades an optional policy or suspends a required one; it cannot silently omit a requested rule. Both native fallback cases pass.

Headless preservation passes at2026-10-19T13:37:33Z:95 original save hashes in both games,98 isolated baseline files, original executable/college INI, stable35/restored50 DLLs, published package hashes and all four hosting identities. No owned work63 process/task, game or API listener remains. Free space is6,330,191,872bytes, above the3GiB guard. No game installation/launch, shared desktop input, MVP modification, public package or cloud change occurred. This closes the headless checkpoint, not the pending live milestone.