1. Build information
The build’s identity, which version this manual documents, which commit it was produced from, and when. The values arrive from the build itself rather than being typed here, so a published page can always answer "what am I looking at?" without anyone reading a pipeline log.
After this chapter the values are ordinary AsciiDoc attributes, so any later text can say 0.9.0-develop.901
or {built} and get the real thing.
| Property | Value |
|---|---|
|
2026-10-22 06:50 UTC |
|
a8324e14f52fe74e2371aa8ebce8f2aa3aacd979 |
|
NETSetup |
|
0.9.0-develop.901 |
1.1. Why this file exists
cmd/BuildInfo is a command macro, the same mechanism cmd/API
== Build information
include::cmd/BuildInfo.adoc[leveloffset=+1]it tells osisa-statiq to run the command BuildInfo and substitute its output for this content.
1.2. What it produces
A settings document setting one attribute per fact, and a table that references those attributes rather than repeating them, so the table and the attributes cannot disagree, and a reader can see which name to write.
| Attribute | Where it comes from |
|---|---|
|
The build, as |
|
The build, as |
|
The build, as |
|
The command’s own clock, in UTC. Nobody passes "now" on a command line, and a manual that cannot say when it was produced is the gap this closes. |
Passing no tokens at all is not an error, the manual can still say when it was built, but it warns, because a published page that cannot name its own version is usually an accident.