Agent work can disappear into terminal scrollback.
Operators need bounded mission state, current lane status, and review checkpoints instead of reconstructing progress after the fact.
Boundary Visibility starts from local runtime state, not from this static public website.
Risky actions need context before they move forward.
Approvals, file and tool timelines, validation results, and prompt lifecycle markers should remain attached to the mission story.
Boundary Website copy cannot authorize tools, bypass prompts, or execute commands.
Parallel agents create drift when lanes are not visible.
Planner, builder, review, and subagent handoffs need one operating picture so work does not split into hidden fragments.
Boundary Coordination visibility is not a remote execution or hosted control claim.
Prompts, paths, credentials, and replay data need clear boundaries.
Teams need to know which surfaces are local, which handoffs are optional, and which public demos are synthetic examples.
Boundary External demo and docs links are separate destinations with explicit link semantics.