Renewal Compass← Back to demo
Sample walkthroughRenewal Compass

Reviewer walkthrough

Use a fresh browser sample or deliberately review a sample reset. Everything is fictional; this app makes no delivery promise, external message or achieved renewal claim.

Primary decision

  1. On Account brief, distinguish existing workspace/support obligation, the need to reduce manual preparation, and requested dashboard/export features. Read O1/O2 observations and A1/A2 assumptions. The review is November 28, 2026; renewal influence and outcome are unknown.
  2. Open Compare packages. Baseline: 14 total days − 6 shared-milestone days = 8 package days. Shared export plus bridge costs 8, bridge-only costs 2, custom costs 14. Custom is blocked by 6. Shared is visibly provisional; exclusions and dependencies appear on every card.
  3. Keep shared selected. Open Prepare conditional brief. Owner defaults to “Product lead (fictional)”; review date November 6, 2026. Conditions require field discovery, capacity approval and bridge owner agreement. Unresolved risk states renewal influence and bridge acceptance are unknown.
  4. Select Preview conditional decision. Inspect the exact package, account-1 evidence, owner, date, scope, conditions, exclusions and capacity. Confirm records a conditional review locally; nothing is sent or promised. With untouched initial draft the record is Review 1.
  5. Refresh, reopen Decision record, and inspect Review 1. Expand its exact reviewed scope and evidence. Export reviewed brief downloads a JSON record containing the entire snapshot and fictional non-promise label.

Package failure and recovery

  1. Review a reset to start fresh. Choose custom dashboard at 14 total days. Recording is blocked because it exceeds the 8-day package budget by 6.
  2. Return to comparison and choose bridge only. It costs 2, leaves 6 and preserves the shared milestone. Review and confirm a new decision. After these two package edits, its identifier is Review 3; identifiers track revisions, not sequential record count.
  3. Select Review withdrawal. Cancel preserves active consideration; confirm marks the original record withdrawn while retaining its exact snapshot.
  4. Select Revise from this record to restore its scope into a draft. Edit conditions, then preview and confirm again. The old withdrawn record remains intact and the new record carries the revised conditions.

Cancellation, conflicts and reset

Preview, then choose Cancel review or Escape. No saved change occurs. A later scope change requires a fresh preview. Unrecorded edits stay in the tab and are discarded by Reload saved sample or refresh.

A second tab can change saved data. If it changes while a decision or reset is being reviewed, confirmation rejects the stale action, including changes with the same revision number. Reload to inspect saved content before reviewing again. Invalid saved data is preserved until explicit reset. Reset replaces only unchanged, readable content that was observed when review opened. If storage is unreadable, work remains in this tab and reset does not overwrite unseen bytes. If writing fails, history remains usable in memory and a refresh-loss notice appears.

Review questions

What need does the package support? Why is the custom dashboard rejected at baseline? Who owns the decision? Which evidence remains an assumption? What conditions must be met before any delivery commitment? Which shared customer outcome would be displaced? These questions are proposed human evaluation prompts, not completed research.