48 lines
3.9 KiB
Plaintext
48 lines
3.9 KiB
Plaintext
Populate the agent-owned data input for the active linear-stage Characterization report with the maximum evidence-backed accuracy.
|
|
|
|
Before editing:
|
|
1. Read the repository-root AGENTS.md completely.
|
|
2. Read Report/AGENTS.md completely.
|
|
3. Read Report/python_script/Report_Input_Manifest.json completely.
|
|
4. Inspect the current Report/python_script/Agent_Report_Data.json.
|
|
5. Inventory the relevant evidence folders without modifying them:
|
|
ECMC/, Encoder/, Motor/, Measurement_System/, Measurements/, and Media/.
|
|
|
|
Scope and write boundary:
|
|
- Work only on Report/python_script/Agent_Report_Data.json.
|
|
- Treat all folders outside Report/ as read-only evidence.
|
|
- Do not modify FAT_Checklist.xlsx, Report_Input_Manifest.json, source evidence, images, PDFs, ECMC files, or generator code.
|
|
- Do not run Build_Characterization_Report.bat, uv, the report generator, or any PDF build, rendering, inspection, or validation step.
|
|
- Do not operate hardware or execute ECMC commands.
|
|
|
|
Evidence rules:
|
|
- Use only direct, traceable evidence from the source domain permitted for each field in Report_Input_Manifest.json.
|
|
- Preserve exact relative evidence paths in each field_sources entry.
|
|
- Cite the narrowest applicable source file for every nonblank populated field.
|
|
- Use legible, unambiguous Media photographs only where the manifest permits them. Do not infer specifications, calibration, installed configuration, or identity from an indistinct label, a model family, or an image alone.
|
|
- For motor fields: inspect Motor/Motor.xlsx first, if present. Use the explicitly identified motor record. Consult other Motor documents only for fields absent or blank in that workbook. Never use Encoder material to fill Motor fields.
|
|
- For ECMC fields: report direct configured values only. Obtain positioning target positions only from the permitted stopBeforePosition PLC file, and straightness target positions only from the permitted straightness-test PLC file.
|
|
- Do not infer a measured result, test status, acceptance, calibration state, environmental condition, or hardware capability from configuration, documentation, or a successful extraction.
|
|
- Do not convert units or calculate derived values unless the source itself explicitly supplies the reported value and unit. Preserve source units and meaningful precision.
|
|
- Do not use a document merely because its filename/model name appears relevant; confirm the evidence applies to the installed component or the requested field.
|
|
- When sources conflict, do not choose silently. Leave the field blank unless one source is explicitly authoritative for that field; record the conflict in the final response.
|
|
|
|
Data-entry rules:
|
|
- Keep displayed values concise factual values only: no commentary, uncertainty prose, conclusions, test-status claims, or parenthetical qualifications in the values.
|
|
- Leave any unsupported, ambiguous, contradictory, out-of-scope, or unmanifested field blank.
|
|
- Retain valid existing values only when their cited sources remain applicable and traceable.
|
|
- Ensure each populated value has a matching field_sources entry, and each field_sources path is allowed by the manifest.
|
|
- Do not add generator-owned inputs or fields outside the existing approved schema.
|
|
|
|
Verification:
|
|
- Validate the resulting JSON syntax.
|
|
- Validate that every populated field is manifest-authorized and has an allowed, existing evidence path.
|
|
- Recheck numerical values, units, signs, ranges, device identities, and quoted precisions against their cited source before finishing.
|
|
- Do not claim the report is complete, built, issued, accepted, visually reviewed, or hardware-validated.
|
|
|
|
Final response:
|
|
1. State the exact file updated.
|
|
2. List each populated or changed field with its exact evidence path.
|
|
3. List fields deliberately left blank and why.
|
|
4. List conflicts, ambiguous evidence, missing evidence, and any assumptions (ideally none).
|
|
5. State the validation performed on the JSON and manifest/source-path consistency. |