@Documentation
Informational metadata, doesn’t affect code generation.
In Program/Screen (top level)
Flat Key : value pairs:
| Key | Description |
|---|---|
Author Name | Name of who wrote the program. |
Author User | User ID of who wrote it. |
App Id | Short application identifier. |
App Name | Visible application name. |
App Description | Long application description. |
Module Id | Short module identifier. |
Module Name | Visible module name. |
Module Description | Long module description. |
Created At | Free-form date/timestamp (e.g. "12/06/2025"), not parsed or validated. |
@Documentation {
Author Name : Programmer Name
Author User : User Code
App Id : Application ID
App Name : Application Name
Module Id : Module ID (if applicable)
Created At : "12/06/2025"
}
In Table (nested inside @Structure)
Here @Documentation has no keys of its own, only sub-sections:
@Author:Name,User,Company.@Application:Id,Name,Description.@Module:Id,Name,Description.@Repository:Official,Type(e.g.git),Branch,Version.@History: container for@Creationand any number of@Changeentries.@Creation:Date,Author,User,Company,Reason.@Change(repeat the block for each entry):Date,Type(by conventionbreaking/feature/fix/security/performance/refactor/config/docs, not enforced by the compiler),Impact(by conventionhigh/medium/low),Version,Reason,Author,User,Company.
@Structure {
Name : "GRIDDEMO"
@Documentation {
@Author {
Name : Programmer
}
@History {
@Creation {
Date : "2025-06-12"
Author : Programmer
Reason : "Initial creation"
}
@Change {
Date : "2026-01-10"
Type : feature
Impact : medium
Reason : "Adds City column"
}
}
}
@Fields { ... }
}