Decisions and risks
| Product choice | Rationale | Alternative and cost | Unresolved risk |
|---|---|---|---|
| Provisional shared export + bridge | Meets the workflow need while retaining the shared milestone | Custom dashboard costs 14 package days and is blocked at baseline; bridge-only retains manual work | Field fit and bridge acceptance remain unknown |
| Separate obligations / needs / requests | Prevent a feature request from becoming an implied agreement | Flat request queue obscures what is already owed | Real contract interpretation is outside scope |
| Explicit capacity rather than retention score | Arithmetic can be independently checked | Revenue score would imply unsupported causality | Scenario capacity is invented and needs real approval |
| Snapshot exact reviewed scope | Decisions must remain auditable after revisions | Mutable option references would silently rewrite history | The browser is not a shared approval system |
| Deliberate withdraw and restore | Preserve history and require another review of revisions | Destructive edits lose provenance | Reset intentionally removes local history after review |
| Preserve invalid and unseen bytes | The user must review content before destructive replacement | Automatic recovery could erase unseen decisions | Memory work may be lost on refresh when persistence fails |
| Download exact review as JSON | Self-contained data includes scope and evidence for inspection | A summary alone omits material conditions | Export is a fictional review record, not an agreement or import format |
All records and capacity figures are invented. There is no real retained revenue, employer result, account endorsement, outreach, legal/compliance determination or personal commercial claim. The fixture is a transparent demonstration, not human research. Mo owns Product / Program Management direction; AI assists implementation and verification.
The history is finite. At its 98-event bound, the app requires an explicit reviewed reset to begin again; export valuable records first. Only schema 1 and account-1 fixture references are compatible. Unknown or tampered records remain preserved rather than being guessed into a new format.