Slice C: Deal Sheet + Wednesday Risk View - #5
Open
sheharyaralidev wants to merge 1 commit into
Open
Conversation
Settlement starts on Wednesday, not at 2am. Two new surfaces that surface
deal-capture ambiguities before they become 2am settlement fights.
- lib/dealParser.ts deterministic parser + ambiguity catalog
(LLM-swappable; same interface)
- lib/clarifications.ts JSON-file persistence for resolutions
- lib/riskQueries.ts aggregate parse for the Wednesday view
- app/shows/[id]/deal-sheet per-show deal sheet with flag cards
+ structured-vs-prose comparison
- app/wednesday risk view across all shows; surfaces the
brief's status/sign-off mismatch breadcrumb
- components/deal-sheet/flag-card.tsx
interactive flag card: resolve/acknowledge/
dismiss + draft clarification email
- Show detail page new Deal Sheet entry-point button
- Sidebar nav new Wednesday top-level link
- MEMO.md 1.5-page PRD: why this slice, what I built,
what I cut, validation plan, ship-next list
- README.md case-study overview at the top
sheharyaralidev
force-pushed
the
slice-c-deal-sheet-wednesday-view
branch
from
May 15, 2026 15:06
aca6e4f to
dbb9784
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Settlement starts on Wednesday, not at 2am. Most disputes are caused by ambiguities already present in the deal email the day it was signed — the venue and the agent just don't notice them until the room is empty and the tour bus is loading out. I built two surfaces:
/shows/[id]/deal-sheet) — parsesdeal_notes_freetextagainst the structured fields and a catalog of dispute-causing patterns. Each ambiguity becomes a flag with severity, evidence quote, suggested action, and a pre-drafted clarification email. Each can be resolved, acknowledged, or dismissed — and the trail of those decisions becomes the audit record that's missing today./wednesday) — every show with open flags, sorted by severity. Marcus's exact ask: "I wish she could see, before a show even happens, whether the deal is going to be a clean one or a messy one."Hero demo path:
/wednesday→ see the Coastal Spell dispute surfaced as a sign-off mismatch (status:disputed, sign-off: "Looks good") + 8 high-severity flags across the corpus.show_coastal_spell_dispute→ 🔴 "Marketing recoup — inside or outside the expense cap?" flag, with evidence quoted from the prose, suggested action, and a draft email Mariana can copy-paste in 30 seconds.show_0000(a clean flat deal) → 🟢 "Deal is settle-ready."