ACF FounderLesson 8/8 · Slide deckPT-BR
Visual course · v2 pet

Operate, audit, and update

Know where to look before accepting a future change.

Core idea

A safe update preserves the contract: same approved identity, same v2 grid, full QA, and a documented new hash. Replacing the file without repeating proof breaks traceability.

Think of it this way: It is a renewed passport: the photo may change, but the authentication chain must run again.

8 columns × 11 rows · last two rows = 16 look directions

How to read it

Start from the official anchor, not candidates.
Regenerate only the failed unit.
Rerun structural, semantic, and visual validation.
Install only after all proof passes.

Technical layer

Preserved artifacts include the request, final WEBP, validations, contact sheet, directions, blind pairs, continuity, GIFs, and run summary. Prompts and intermediate images are disposable.

Check your mental model

When may a new version be installed?

Evidence used

run-summary.json · validation-extended.json · review.json