Cogniform · Engineering note
Cogniform exports one revision through four observations
CF082 renders the canonical room and updated table into a diagnostic bundle. The four image files share a revision and camera, while retaining distinct frame and observation identities.
Source: https://louijiecompo.com/updates/cogniform-canonical-graphics/
Create room, table, light and camera → update table → revision 2 → observe.
- Frame 4
- Appearance
- color.png
- Frame 5
- Distance
- depth.png
- Frame 6
- Surface direction
- normals.png
- Frame 7
- Object identity
- identity.png
Four sequential requests share the final revision and camera. They are not simultaneous captures. The new bundle remains local; this diagram does not depict its rendered pixels.
PR #82 merged on 30 September. The render-scenario command first completes the fixed canonical flow: create four entities, update the table, query revision two, verify the accepted-event chain and replay to the same logical hash. It then requests color, depth, normals and identity observations.
The public validation record describes frames 4 through 7 with separate observation identities but the same final revision and camera. These are sequential requests. The earlier render-example cube derives all four files from one reference frame, so its images must not be relabeled as the new scene.
The destination must be new; a failed write can leave a partial directory. Diagnostic PNGs do not expose exact numeric depth or normal payloads, accept caller-authored scenes, or establish cross-adapter screenshot baselines. The bundle remains local and its manifest needs review before sharing. This page shows the documented sequence as a diagram, with no new GPU run or new scene capture claimed.
Explore the topic
Follow the evidence
Read source evidence ↗ (opens in a new tab)
Related reading
Follow writing and engineering notes
Add this feed to your RSS reader to follow new articles and engineering notes. No signup or tracking on this site.
Follow via RSS