MandateArc
I built MandateArc so a data owner and a buyer can describe what they need before anyone uploads business records.
Owners and buyers arrive with different questions
An owner knows its systems and permissions; a buyer knows the task it wants data to support. MandateArc gives each a guide and a brief builder, then makes missing information visible before a handoff.
The form produces a decision state
Astro renders the public guides from structured industry and use-case data. TypeScript and browser scripts run the qualification, mandate and checklist tools locally.
The builders apply deterministic rules, invalidate prepared output after an answer changes and let STOP override completion. They accept business metadata and prepare a brief without uploading source records or submitting a message automatically.
A visitor can try the whole qualification path
The public owner and buyer desks lead into their respective tools. A demonstration uses fictional metadata, prepares a brief and edits an answer to show why the previous output is no longer current. The local repository builds with pnpm verify, which also checks HTML, links and content structure.
The next action should follow the missing fact
Method & limits: this is a published software prototype. Customer demand, active mandates, rights clearance and completed licensing transactions require independent validation.
I’d ask the next relevant question before adding an upload button. A form earns its place when it improves the decision the visitor can make.