Skip to main content

🗂️ 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​

FolderWritten byRead by
ATC Analysis reportsAI applicationWorkbench
ATC Implementation reportsAI applicationWorkbench
Review outputWorkbenchWorkbench and AI application (a copy)
Review output › _configWorkbench (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​

FilePatternExample
Analysis reportATC_Analysis_<CYCLE>.mdATC_Analysis_CYCLE-01.md
Analysis reviewATC_Analysis_<CYCLE>_review_<YYYY-MM-DD_HHmm>.mdATC_Analysis_CYCLE-01_review_2026-10-22_1610.md
Implementation reportATC_Implementation_<CYCLE>_IT<nn>.mdATC_Implementation_CYCLE-01_IT02.md
Implementation reviewATC_Implementation_<CYCLE>_IT<nn>_review_<YYYY-MM-DD_HHmm>.mdATC_Implementation_CYCLE-01_IT01_review_2026-10-27_1503.md
Cycle closureATC_Cycle_<CYCLE>_CLOSED_<YYYY-MM-DD_HHmm>.mdATC_Cycle_CYCLE-01_CLOSED_2026-11-12_1700.md
Header, not file name

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:

KeyValue
Report TypeATC_ANALYSIS, ATC_IMPLEMENTATION or ATC_CYCLE_CLOSURE
CycleCycle ID, e.g. CYCLE-01. Links the report to its cycle.
Cycle Name / Cycle ScopeTaken from the cycle list; the name in Config › Cycles wins
IterationImplementation reports only: 1, 2…
Document StatusPROPOSAL (analysis), REPORT (implementation) or REVIEW (review file)
Review Of, Previous Version, Saved By, Saved OnAdded 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 HeadsAdded 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)​

FileMaintained inContent
ATC_Cycles.jsonConfig › CyclesCycle list: ID, name, scope, planned dates, owner, status, comment
ATC_Tags.jsonConfig › TagsTags with colour and description
ATC_Modules.jsonConfig › ModulesSAP module codes and names (created when the list is first changed)
ATC_Reviewers.jsonConfig › Reviewer administrationReviewers, 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​

DirectionWhatHow
AI application → workbenchAnalysis and implementation reportsCopied to the report folders
Workbench → AI applicationLatest review file of each reportRead before the next step (implementation or next iteration)
Workbench → AI application_config/ATC_Cycles.jsonCopied to the AI application's project after each change
BothSAP module codesSame codes in both lists; add new codes on both sides
Deploying a new version

To update the workbench, replace ATC_Review_Workbench.html only. Reports, review files and the _config settings are not touched.