Summarize the Release Information (known issues) and System Design/Management manuals, add the system-check and system-management skills practiced on the R1.03 test system, and add the progress tracker, issue register and a CI-Eng-Sample placeholder. CLAUDE.md now requires a version check, asks once per conversation whether to work directly or prepare files only, and treats the manuals as development-only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
CI-Eng-Sample (placeholder)
Status: planned, not built yet. Nothing in this folder can be imported yet.
A small, invented sample project that anyone with this repo can load into a CI Server R1.03 test system. Skills use it for their examples, and every skill task can be practiced and verified against the same known items on any machine.
Planned contents
Built up phase by phase (see knowledge/progress.md):
| Phase | Adds |
|---|---|
| 5 Items and acquisition | Top-level section, sub-sections, template items, internal items (no PLC needed), items with alarm limits |
| 6 Classes and objects | A class and objects created from it |
| 8 Alarms | Alarm settings on sample items |
| 9 History | An item storage group |
| 10 Graphics | A display and symbol |
| 11 Reporting | A report |
Planned files
| File | Purpose |
|---|---|
*.qli |
dssqld data files, one per dataset |
load.cmd |
Imports the data files in dependency order: template items → classes (compiled) → objects → remaining items (IM 36K10J10 §5.6) |
remove.cmd |
Removes the sample project from a system |
Rules
- Test systems only. Loading writes to the CI Server database.
- Invented names only; no real plant or customer data.
- The top-level section name is still to be decided. Item names may not allow
-, so it may differ from the folder name (to be checked in phase 5). - Every file notes the CI Server version it was built and tested on.