docs(01): create verified fidelity baseline plans
This commit is contained in:
1 parent
36f24e4474
commit
cf64b8ce18
21 files changed
+1473
-32
No files matched your search
@@ -419,13 +419,16 @@ No dependency modernization or runtime architecture migration is proposed.
|
||||
|
||||
These are execution hypotheses, not locked compatibility claims. Do not gate independent implementation on a vague preference question; resolve through the prescribed preflight/native acceptance checkpoint before claiming success.
|
||||
|
||||
## Open Questions
|
||||
## Open Questions — RESOLVED planning dispositions
|
||||
|
||||
1. **Actual DxWnd version/config and original launch behavior:** no successful Windows reference run is supplied by context. Prepare profile collection and preflight; retain limitations rather than inventing settings.
|
||||
2. **Windows capture/audio/browser availability:** user's PC is available, but tools/devices are unprobed. Include dependency checklist and one short test inside the combined session.
|
||||
3. **Original input precision:** minimum procedural input plus manual observed markers is honest but not exact original sampling. Label the method/uncertainty; add instrumentation only if a concrete comparison requires it.
|
||||
4. **Timing/image/audio tolerances:** no universal numeric parity threshold is established. Capture raw values and uncertainty first; later system owners justify thresholds from original evidence.
|
||||
5. **Historical applicability:** current reports contain historical package/runtime revisions and superseded defect narratives. Bind ledger claims by actual content and source report scope, not date or prose order.
|
||||
Each policy below is resolved for planning. Actual future capture/native outcomes remain
|
||||
execution acceptance dependencies; RESOLVED does not claim a successful Windows run.
|
||||
|
||||
1. **RESOLVED — Actual DxWnd version/config and original launch behavior:** collect the user's actual executable/version/profile hashes and settings through plan 01-05 preflight, then record launch, visibility and audibility during plan 01-07's combined session. No guessed profile or compatibility guarantee is required to implement the collector. Failed/missing original execution keeps EVID-02 open.
|
||||
2. **RESOLVED — Windows capture/audio/browser availability:** use a local dependency checklist and short recording/decode/audio preflight in the prepared combined session (plans 01-05/01-07). Record observed versions/devices and blockers; do not automatically download tools or silently substitute black/silent media. Unavailable dependencies remain explicit pending capture acceptance.
|
||||
3. **RESOLVED — Original input precision:** use procedural inputs plus manually observed event markers, each labeled with method and uncertainty (plans 01-01/01-05/01-07). Port observations remain separately instrumented. No claim of exact original input sampling or deterministic original replay is made. Further instrumentation requires a concrete comparison need and the existing original-binary evidence rules.
|
||||
4. **RESOLVED — Timing/image/audio tolerances:** preserve actual-speed raw captures, elapsed values and drift without a blanket numeric parity threshold (plans 01-02/01-07). Record discrepancies/uncertainty; later system owners derive any acceptance tolerances from authoritative evidence. Tool acceptance tests validate timing/audio controls, not unestablished whole-game parity.
|
||||
5. **RESOLVED — Historical applicability:** bind claims to content/source/platform/scenario identity, preserve explicit supersession and reject ambiguous conflicting current evidence (plans 01-01/01-03/01-07). Report date/order alone never promotes historical packages to current proof. Missing underlying artifacts remain missing/historical rather than receiving fabricated identity.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
Reference in new issue
Block a user