Frank14f/DynamisLab
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor(workflow): update JFM research workflow and remove obsolete figures

Browse Source 
Revise the JFM research workflow documentation to clarify project structure, decision-making processes, and tool routing. Remove outdated figures and images that are no longer relevant to the current manuscript. Ensure that the workflow aligns with the latest research objectives and safety protocols.
This commit is contained in:
Frank14f
2026-08-11 21:25:33 +08:00
parent 0ade812864
commit 1a8b994a03
101 changed files with 5757 additions and 23827 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.cursor/rules/jfm-research-workflow.mdc
+19 -22
View File
@@ -1,30 +1,27 @@
---
description: DynamisLab JFM research, decision, and drafting workflow
description: General JFM startup, authority, memory, literature, and safety routing
alwaysApply: true
---
# JFM Research and Manuscript Workflow
# JFM Research Start and Tool Routing
## Round-aware operating mode
- Identify the active round and output before work. R1 indexes evidence; R2 designs the manuscript; R3 builds section dossiers; R4 settles author-facing arguments, ownership, displays and section freezes; R5 drafts prose only from frozen R4 packets and authorities.
- Keep evidence states distinct: `mapped` is not `read`; `read` is not independently verified or artifact-audited. Use a compact ledger (`read`, `mapped`, `not-covered`, `external-inaccessible`) proportional to the round; do not let governance overwhelm argument/design.
- In R4/5 prioritize the section question, bounded answer, paragraph jobs, display logic, ownership, interfaces, author choices and manuscript value. Do not recreate R1 inventories or rediscover the project.
## Start from the assigned unit
- Name the project, active round, exact unit, deliverable, output, and exclusions. R1 indexes evidence; R2 designs; R3 builds dossiers; R4 freezes arguments/displays; R5 writes admitted section prose and controls from frozen R4 packets.
- Read fresh supplied context once. Follow the coordinator packet's exact reads, ownership, limits, questions, and acceptance checks; do not rediscover the project or recreate R1 coverage.
## Continuation and context
- When prior decisions matter, continuation agents begin with targeted Nowledge `memory_search`; use thread recall for exact prior discussion. Then verify every operative decision against current repository authorities. Memory aids discovery/history and never overrides authorities, manifests, code/configuration or immutable artifacts.
- Before launching section agents, the coordinator creates a minimum context packet containing: exact controlling reads; accepted author feedback; available material/artifact inventory with readiness; requested output decision; exclusions; target length/section share; paragraph jobs; concrete display layout; ownership; and exact questions. Agents stay within that packet and perform only targeted authority checks.
- Cadence after the initial architecture: present two detailed section packets together; receive author feedback; launch two tightly scoped continuation agents in parallel; then perform a coordinator second audit before either section is frozen or handed to R5.
## Recall, then verify
- Use 2–3 narrow Nowledge `memory_search` queries containing `DynamisLab JFM` plus round, section/unit, and decision/claim/term. Use `thread_search` and scoped `thread_fetch_messages` only when exact prior wording or conversation history is needed.
- Memory navigates decisions; `mem_fs` may locate source/original text only when actually stored, with source state retained. It is not a general full-text corpus.
- R1–R4 indexes, dossiers, plans, controls, and figure plans route architecture, ownership, ceilings, and fallbacks; they do not establish a new internal fact or verify/promote an artifact.
- Bind internal facts/numbers to current package authority, manifest, code/configuration, or immutable artifact. If unbound, omit, use the frozen fallback, mark an authorized placeholder, or report the gate. Current authority overrides memory and summaries.
- Search before `memory_add`; update rather than duplicate. Save only durable decisions, procedures, or lessons.
## Tool routing and execution safety
- Nowledge: decisions, preferences and discussion history. Undermind: external literature only, after `get_orientation` and `list_workspaces`; literature cannot establish internal results. Repository read/search tools: internal evidence, authorities, code, manifests and artifacts.
- For read-only derivations or scripts, discover the designated conda environment from current repository authority or environment listings and record it; never guess an environment. Do not run CFD, training, artifact generation or expensive analysis unless explicitly authorized.
## Literature and tool routing
- For Undermind: run `get_orientation`, list/select the DynamisLab workspace, inspect existing folders/files/searches, search the library first, and broaden only if needed. Confirm identity, DOI, and availability with `get_paper_info`.
- Keep each `read_pdfs` request bounded and self-contained: identify the papers/pages or question, request only necessary passages, and preserve `full-PDF`, `full-report`, `mapped`, `snippet`, or `inaccessible` state. Mapped/snippet evidence cannot support detailed wording or structural claims.
- Literature supports external propositions and rhetorical/structural diagnosis only; it never verifies internal results, numbers, artifacts, priority, readiness, or claim ceilings.
- Before any authorized read-only script, discover and use the repository-designated environment and documented entry point; do not guess an environment or install/change dependencies.
## Evidence and claim boundaries
- Trace claims to current authorities and preserve solver, geometry/configuration, Reynolds convention, case/seed/role, comparator, metric/estimand, ROI/window and artifact. Keep internal Legacy and modern V5 chains separate; use physical configuration names in manuscript prose.
- Use case-specific periodic, transient and steady metrics. Distinguish sourced fact, bounded observation, interpretation, historical/negative result and open question; report gaps and conflicts without inventing citations or numbers.
- Image work inventories existing data/scripts before proposing panels; inventory is not panel readiness. Label existing derivations, independent checks and new conjectures separately.
## Fixed scientific cautions
- Bound positive SR to Kármán/cloaking. Illusion SR is historical/negative; CCD is descriptive/noncausal and uses `action-correlated correction-field modes`; OID is claim-free; steady results are contextual; experiment is qualitative/provenance-gated.
- Kan99b K2 retains the authority's exact overall `partial pass`. Its opposite mean-lift sign is explained by the CFD coordinate/force-direction convention, not unresolved physics or suspected wrong rotation; do not call the sign unresolved.
- Never promote claims across chains, alter evidence packages/archive/history, or inflate solver qualification into controller or mechanism validation.
## Safety and closeout
- Do not run CFD, training, artifact generation, or expensive/new analysis without explicit authorization. Never fill an evidence gate by inference.
- Close out whether Working Memory, durable memory, thread recall, `mem_fs`, scripts, and literature were used, distinguishing `read`, `mapped`, and independently verified/audited evidence.