ARCHITECTURE REVIEW

Keep the proposal and the version your team reviewed.

Use one link while an architecture or roadmap proposal changes. Keep a fixed version for the decision record and the next AI task.

ILLUSTRATIVE SAMPLE · THE REVIEW GAP

Review an illustrative roadmap proposal that keeps changing.

This sample is a single uploaded HTML file. It shows the workflow shape; it is not a customer artifact or a production approval.

Without a review artifact: A deck left in a repository, attached to a message, or reduced to screenshots does not provide one stable place for an active review and an exact record of the approved state.
With the versioned workflow: This illustrative sample keeps the latest URL for review and the fixed version URL for the exact HTML a person reviewed. A later agent can retrieve that authorized source.

UPLOADED HTML SAMPLEOpen full sample

PUBLISHING SEQUENCE

led publish ./architecture-v2.html --slide <SLIDE_KEY> --workspace <WORKSPACE_KEY> --visibility workspace --json

01
Generate one complete HTML file
Ask the agent for one complete architecture or roadmap HTML file. Remote references may remain runtime dependencies and are not copied into storage.
02
Publish the first review privately
Start with private visibility. The first private draft is visible only to its current private owner.
03
Update the same Slide for team review
When the proposal is ready for team review, make sure each reviewer is an active member of the owning Workspace, then publish the next version with --visibility workspace. Changing visibility applies to the whole Slide, including earlier fixed versions.
04
Record the fixed version
Attach the version-specific URL to the architecture decision or handoff that must not move.