FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Preparing photo assets for nine AI employees
Fixing lowercase names, WebP format, dimensions, and reference paths in one asset contract
Purpose
Before the corporate site could use profile photos for its AI employees, it needed an asset directory where nine images could be referenced through consistent names, formats, and dimensions.
The work also needed a contract that kept asset preparation separate from screen integration, disclosure, and public display so the presence of an asset alone would not imply that publication was ready.
Implementation
A project guide and nine images were added under portrait asset collection. Each filename followed the same rule: the AI employee's lowercase UI nickname followed by .webp.
mako.webp,yui.webp, andryoma.webpshiori.webp,aya.webp, andmanabu.webpikumi.webp,yasu.webp, andritsu.webp
The project guide defined portrait asset, relative to the repository root, separately from the site-facing /images/ai-employees/<nickname>.webp. This kept the storage location distinct from the public URL interface.
The asset contract required all nine files to be VP8 WebP images at 1536×1024, without same-name PNG files or a PNG fallback. The project guide also separated asset preparation from the gates for screen integration, disclosure, and public display.
Verification compared the expected set of nine filenames with the directory contents and counted missing and extra files. It also checked each image's format and dimensions, the absence of PNG assets, the two path forms in the project guide, and whitespace errors in the diff.
The primary diff was checked line by line to confirm that the behavior described above matched the change at the cutoff.
What was confirmed
Verification results
All nine expected filenames were present, with zero missing and zero extra files.
Every image was a VP8 WebP at 1536×1024. No same-name PNG or PNG fallback was present.
The distinction between the repository-relative path and public URL, the separate gates for asset preparation and display or publication, and the absence of whitespace errors were confirmed.
At the cutoff, the project guide and all nine images were confirmed as reflected in the asset directory. This Activity did not verify screen integration, display of the accompanying disclosure, or production publication.
Basis for completion
The photo-asset preparation scope was considered complete when the project guide and nine images were present in the asset directory and static checks of the filename set, format, dimensions, PNG absence, reference paths, and gates had completed.