Skip to main content

🛠️ AI@CustomCode Implementation

The Implementation page shows the ATC Implementation reports of a cycle. The AI application implements the approved analysis in iterations; each iteration has its own report, and each report is signed off here.

Implementation page — iteration 02 with carried-over approvals (demo data)


Cycle, Iteration and Version​

FieldDescription
CycleThe cycles that have implementation reports
IterationIteration 01, Iteration 02 (latest)… Earlier iterations and their reviews stay available.
VersionThe original report of the iteration, or one of its review files

The Finding List​

The list works like the Analysis list: same columns, chips, search, filters, sorting and Export CSV, plus:

Column / filterValues
ImplementationImplemented, Implemented – review needed or Not implemented

The module comes from the analysis review and cannot be changed here. Tags can be added or removed in the detail view.


The Finding Detail​

SectionContent
ClassificationComplexity, review status, priority, object, include, implementation status, Changed In This Iteration, transport, ATC recheck result
Module & tagsModule (from the analysis) and tags
Analysis review (latest)The decisions and comments of the analysis review, for reference
Implementation descriptionWhat was changed and how it was tested
Issues found during implementationProblems met during the change
Proposed solutions / workaroundsHow the issues are handled
Review & sign-offSignatures and the review log

Sign-off Across Iterations​

Signing works as on the Analysis page: choose a decision, comment unless Approved, Validate & sign, then Save review file. This writes ATC_Implementation_<CYCLE>_IT<nn>_review_<date>_<time>.md to the Review output folder.

From iteration 2, findings that were fully approved in the previous iteration and are marked Changed In This Iteration: No keep their signatures. They are shown as Carried over from …, and a green banner tells you how many findings keep their approval. You only review what changed or is still open.


Close the Cycle​

Close cycle is enabled on the latest iteration when every finding is approved with full sign-off. It:

  • writes ATC_Cycle_<CYCLE>_CLOSED_<date>.md to the Review output folder,
  • sets the cycle status to Closed in Config › Cycles,
  • disables signing for the cycle, on both the Analysis and the Implementation pages.

The reports and review files of a closed cycle remain readable.