fpvetleseter writes the whole blueprint before the code

Nearly 1,800 lines of design documents lay out a Norwegian legal assistant in detail - none of which has been built yet.

draftingsearch

fpvetleseter just committed a stack of design documents describing a three-part legal assistant: one agent for open-ended questions, one that reads an uploaded document and pulls back its most relevant passages, and one that drafts contracts. All three lean on Lovdata - Norway's official public legal database - with cached lookups of statutes feeding into every answer.

The plan goes further than most blueprints dare. It spells out a free tier capped at ten questions a day and three document uploads a month, an unlimited paid tier, usage counters that reset at midnight Oslo time, and the full hosting-and-billing stack underneath. Worth saying plainly: this is documented intent, not working software. None of it runs in the fork yet - it's a statement of where fpvetleseter is headed.

So what If you're tracking who's seriously aiming at the Norwegian legal market, this is fpvetleseter showing their hand before the build.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from fpvetleseter/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
c2e41992 Add desktop project docs fpvetleseter 2026-05-08 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-203.md from inside the repo you want the changes in.

⬇ Download capture-thread-203.md