🗂️ AI@CustomCode Data Files (Admin)
This page is for the project administrator: which files the workbench reads and writes, and how they are linked. All files are plain Markdown (.md) or JSON, in UTF-8.
Folders
| Folder | Written by | Read by |
|---|---|---|
| ATC Analysis reports | AI application | Workbench |
| ATC Implementation reports | AI application | Workbench |
| Review output | Workbench | Workbench and AI application (a copy) |
Review output › _config | Workbench (Config page) | Workbench; ATC_Cycles.json also by the AI application (a copy) |
A typical setup is one SharePoint library with the folders 01_Analysis, 02_Implementation and 03_Reviews, synced with OneDrive.
File Names
| File | Pattern | Example |
|---|---|---|
| Analysis report | ATC_Analysis_<CYCLE>.md | ATC_Analysis_CYCLE-01.md |
| Analysis review | ATC_Analysis_<CYCLE>_review_<YYYY-MM-DD_HHmm>.md | ATC_Analysis_CYCLE-01_review_2026-10-22_1610.md |
| Implementation report | ATC_Implementation_<CYCLE>_IT<nn>.md | ATC_Implementation_CYCLE-01_IT02.md |
| Implementation review | ATC_Implementation_<CYCLE>_IT<nn>_review_<YYYY-MM-DD_HHmm>.md | ATC_Implementation_CYCLE-01_IT01_review_2026-10-27_1503.md |
| Cycle closure | ATC_Cycle_<CYCLE>_CLOSED_<YYYY-MM-DD_HHmm>.md | ATC_Cycle_CYCLE-01_CLOSED_2026-11-12_1700.md |
The workbench identifies a report by its header, not by its file name. The names are for people; keep them consistent anyway.
Report Header
Every report starts with a title and a list of - Key: Value lines. The keys the workbench uses:
| Key | Value |
|---|---|
| Report Type | ATC_ANALYSIS, ATC_IMPLEMENTATION or ATC_CYCLE_CLOSURE |
| Cycle | Cycle ID, e.g. CYCLE-01. Links the report to its cycle. |
| Cycle Name / Cycle Scope | Taken from the cycle list; the name in Config › Cycles wins |
| Iteration | Implementation reports only: 1, 2… |
| Document Status | PROPOSAL (analysis), REPORT (implementation) or REVIEW (review file) |
| Review Of, Previous Version, Saved By, Saved On | Added by the workbench in review files. Review files of a report are ordered by Saved On; Previous Version is the file the save was based on. |
| Merged Heads | Added when a save merged parallel review versions: the other review files whose changes were combined |
Each finding is a ## ATC-nnnn | <title> block with a ### Classification list (complexity, priority, module, tags, object, include, line, Total Number of Calls, Number of Findings, SAP notes) followed by the text sections shown on the Analysis and Implementation pages. The workbench appends a ### Review block with the review log when it saves a review file.
Shared Settings (_config)
| File | Maintained in | Content |
|---|---|---|
ATC_Cycles.json | Config › Cycles | Cycle list: ID, name, scope, planned dates, owner, status, comment |
ATC_Tags.json | Config › Tags | Tags with colour and description |
ATC_Modules.json | Config › Modules | SAP module codes and names (created when the list is first changed) |
ATC_Reviewers.json | Config › Reviewer administration | Reviewers, roles and PIN hashes (encoded) |
- Each save keeps the previous version as
<name>_previous.json. - If the file was changed by someone else since you opened it, the workbench warns you before overwriting it.
- The files stay in the Review output folder, so a new version of the HTML file keeps all settings.
Exchange with the AI Application
| Direction | What | How |
|---|---|---|
| AI application → workbench | Analysis and implementation reports | Copied to the report folders |
| Workbench → AI application | Latest review file of each report | Read before the next step (implementation or next iteration) |
| Workbench → AI application | _config/ATC_Cycles.json | Copied to the AI application's project after each change |
| Both | SAP module codes | Same codes in both lists; add new codes on both sides |
To update the workbench, replace ATC_Review_Workbench.html only. Reports, review files and the _config settings are not touched.