Shrvan Benke — PO terms conflict checker and restaurant corrective-plan app

[01shrvan]

Shrvan Benke — both assigned builds for the SuperDocs Round 2 engineer task.

use-cases/01shrvan/po-terms-conflict-checker (S3)

Compares a buyer's purchase order against a supplier's acknowledgement clause area by clause area, quotes both sides on every contested point, states which document is likely to govern given the recorded sequence of events, and drafts the objection or confirmation letter that preserves the buyer's position.

Matching is by substance rather than heading — the bundled pile-b shares none of pile-a's headings ("Liability Ceiling", "Forum for Disputes") and still resolves every area. Silence is reported as a finding distinct from a conflict, with its own band in the interface and its own section in the memo, because a reader who skims a conflicts list and doesn't find warranty there will conclude warranty is agreed. It isn't — nobody said anything.

The "which document governs" analysis is not a model call. The sequence of events is explicit input, the doctrine lives in rules/last-shot-england.json, and the output names the facts it relied on and carries a disclaimer. Adding one objection event before performance flips the conclusion; dating it after delivery does not. 43 tests.

use-cases/01shrvan/restaurant-corrective-plan (S2)

Takes cited health-inspection violations and drafts a corrective plan with a fix and a named owner per violation code, formatted for resubmission to the health department.

The centrepiece is a coverage verifier that refuses a plan where actions or owners are copied between codes, where a code was cited but not answered, or where the plan invents a code nobody cited. Hand-written fixtures include a blended single paragraph and individually-coded boilerplate; both are rejected. 21 tests.

Notes

• Every test runs without an API key. Both builds have an offline path so a stranger can clone and run them.
• Both use the SuperDocs async approval flow (/v1/chat/async with approval_mode: "ask_every_time"), not the synchronous /v1/chat shown in the quickstart — that endpoint applies edits immediately and returns no change_id, so approval is impossible on it. Reported as a bug.
• /api/export renders locally and produces HTML only. Asking either build for docx returns 501 naming where DOCX is available, rather than handing back HTML bytes under a .docx name.
• All sample data is synthetic and describes fictional companies.
• Limitations are stated in each README rather than omitted.