DynamisLab/docs/JFM_WYQ/FIGURE_PLANS/README.md

JFM figure-specification index and production controls

This directory is the Round-4 figure-specification layer for Sections 1–10. It organizes display intent, provenance, readiness and safe omission. It does not make a panel, table, equation, source payload or result publication-ready. No file here authorizes CFD, training, raw-array inspection, computation, rendering or artifact generation.

Section index

• Section 1 — Introduction: no owned empirical display. No plan file required; reason: the frozen introduction owns framing only.
• Section 2 — Problem formulation, control framework and evaluation: SECTION_02_FIGURE_01_CONFIGURATIONS_AND_SENSORS.md; SECTION_02_FIGURE_02_DRL_INFORMATION_ACTION_REWARD.md; SECTION_02_TABLE_01_CONFIGURATION_METHOD.md; SECTION_02_TABLE_02_CASE_METRIC_SEMANTICS.md; SECTION_02_TABLE_03_CFD_QUALIFICATION.md; SECTION_02_EQUATION_SPEC.md.
• Section 3 — Capability progression: SECTION_03_FIGURE_01_STEADY_DISCOVERY_PROFILE.md; SECTION_03_FIGURE_02_WAKE_CLOAKING_AND_RETARGETING.md. Section 3 remains discuss: Fig. 1 composition and representative Vortex offset are author choices.
• Section 4 — Kármán performance: SECTION_04_FIGURE_01_KARMAN_CONDITIONS_AND_LEARNING.md; SECTION_04_FIGURE_02_REFERENCE_FIELD_SIGNAL_ACTION.md.
• Section 5 — Compact Kármán SR law: SECTION_05_KARMAN_SR_CONTROL_LAW.md.
• Section 6 — Kármán mean fields and CCD: SECTION_06_FIGURE_SPEC.md; S6-S2 remains blocked.
• Section 7 — Cross-case extensions: SECTION_07_FIGURE_01_VORTEX_EVENT_RESPONSE.md; SECTION_07_FIGURE_02_ILLUSION_ERASE_EXTENSIONS.md. Role fields exist; quantitative Vortex and Erase products remain blocked; Illusion is bounded PPO capability.
• Section 8 — Steady context and theory boundary: SECTION_08_STEADY_CONTEXT_AND_THEORY.md. Existing outer assets are bounded redraw sources only; no new MFS computation is authorized. Frank's equation/composition choice remains open.
• Section 9 — Qualitative open-loop experiment: SECTION_09_EXPERIMENT.md; author-supply-gated, with strict omission fallback.
• Section 10 — Discussion and conclusions: no display, table or equation by frozen text-only contract. No plan file required.

Every actual plan file in this directory is indexed above. Existing filenames are intentionally unchanged in this pass.

Controlled cross-figure rules

1. Stable reader roles are target/reference → controlled → physical zero/uncontrolled; add constant or SR only when acquired and explicitly bound. A target has no action trajectory.
2. Never pool or visually imply equivalence between configurations. Internal chain labels stay in provenance.
3. Bind case, seed/realization, role and comparator. Use neutral source-case labels where inherited parabolic velocity-reference conversion is unresolved; never guess a reader-facing Reynolds value.
4. Mean, phase, event-relative, steady-profile, native DTW, normalized DTW, standardized rolling DTW and fixed-cycle deletion DTW are non-interchangeable. State whether larger or smaller is better.
5. Record ROI/domain, geometry guard or exact mask, weighting/normalization and retained window/phase/event coordinate. A display crop is not a metric ROI.
6. Record x/y direction, array order/transposition, action/body order and sign, and color/sign semantics.
7. Record exact authority, source artifact, script/evaluator, manifest, role rows/windows and hashes in the production manifest. A partial plot manifest authenticates only the diagnostics it lists; it does not prove completeness, portability or readiness.
8. Share crop, scale, units and mask only within a direct, authority-bound comparison.
9. Captions decode configuration, roles, condition, coordinate and limits; they do not promote morphology to efficacy, signal matching to field matching, qualification to control validation, or association to causality.
10. Omit unresolved panels, scalars or annotations. Never fill a gap with a non-equivalent source, inferred geometry, unsupported conversion or diagnostic screenshot.

Normalized readiness schema

Each plan should use these five independent fields. N/A must include a reason.

• Plan state: specified, discuss, author-supply-gated, or omitted (N/A: reason).
• Evidence state: read, path-confirmed, mapped, not-covered, missing-exact-leaf, or author-supply-gated. read is not independent verification; mapped is not read or locally resolved.
• Metric state: definition-ready, authority-bound, dependency-gated, blocked, or N/A: method-only/no quantitative result.
• Render state: not-started, draft-diagnostic-only, redraw-required, blocked, or N/A: omitted/text-only.
• Disposition: retain, retain-with-gates, supplement, fallback-only, or omit.

Required production record

Before production, record: authority; evidence state; chain/configuration; case/seed/roles/comparator; metric and orientation; ROI/domain/mask/weight/window; display crop; array/action/flow orientation; exact source/script/evaluator/manifest and hashes; render settings/output hash; caption ceiling; fallback. Mark unavailable fields N/A with a reason. Missing required fields prevent a publication-ready claim.

Coverage boundary

read: current Round-4 controls/owning section packets and the two Section-2 repository reports. path-confirmed: exact repository paths named in plans. mapped: authority-described or manifest-linked payloads not opened or independently audited here. not-covered: raw arrays, external payload verification, computation, CFD/training, rendering, figure generation and publication typography. Durable memory was recalled for navigation only; no thread recall or literature search was needed.