Niflheim Lab / Weiß · 001
Next up — fully designed, not yet downloadable
Hand it the job. Not the instructions.
Most assistants answer a question and stop. Weiß is being built to take the whole errand — work out the steps, use your tools, keep at it for hours if that's what it takes — and never touch anything important without asking you first.
It's the later of the two because it's the bigger one. Its sibling, Weiß CODE, does the same thing for your code — and you can download that one today, for free.
Runtime layers
- The goalwhat you actually asked for
- The planyour goal, broken into steps you can read
- The memorywhat it keeps, and for how long
- The ruleswhat needs your yes, and what never runs
- The toolsthe apps and services it is allowed to touch
- The recordevery decision, written down as it happens
A look ahead · not built yet
Here's what we're aiming at.
A quiet app on your desk where you hand over a job and watch it get done. This is a drawing, not a screenshot — we're showing it early because it's easier to argue with a picture than with a finished product.
Goal · session b7f1c2a4 · opened 41 minutes ago
Prepare the Q3 vendor security review
Fourteen questionnaires read and the control gaps extracted. The portal step is holding, because signing in takes credentials out of the vault.
- ✓ Collect the vendor questionnaires14 read · 2 missing
- ✓ Extract the control gaps31 entities added
- ◐ Pull last quarter's findingsinside the context budget
- ! Sign in to the vendor portalwaiting for you
- · Draft the review summaryblocked by the portal step
! Approval required
Sign in to the vendor portal and download the Q3 attestation pack
Credentials leave the vault and enter a third-party site. network.external · outside the allowlist
One job, the steps it turned into, and the single step that stopped. The amber card is it asking permission before doing something that reaches outside. What it has spent sits in the bottom bar, in plain sight, because that number should never be a surprise.
A clever answer is the easy half.
The hard half starts after the answer: keeping track, picking the right tool, stopping before it breaks something, and being able to say what it did and why. Smarter AI doesn't fix any of that. Someone has to build the part around it.
- 01
Knowing what matters
Bringing up the right context, not everything it has.
- 02
Picking the right tool
And knowing exactly what that tool may touch.
- 03
Not losing the thread
Work that survives a restart, or a colleague picking it up.
- 04
Remembering well
Some things for a minute, some for a year — told apart.
- 05
Making a plan
Steps you can read, correct, or throw away.
- 06
Stopping in time
A checkpoint in front of anything that leaves a mark.
- 07
Working while you sleep
Jobs that outlast the conversation that started them.
- 08
Showing the bill
What it cost, how long it took, what it actually did.
What happens after you ask
One request, six things it has to get right.
Step 01 · Ask
You say what you want.
Not a command, an outcome. It opens a job for it and starts keeping notes from the first second — notes that are still there tomorrow.
Step 02 · Gather
It picks up what it needs.
Some things it remembers for a minute, some for months. It pulls forward only what this job actually calls for, instead of drowning the question in everything it knows.
Step 03 · Plan
You see the steps first.
The goal is broken into steps written for a person. Read them, fix the one that's wrong, come back tomorrow and carry on. A plan nobody can read is a plan nobody can check.
Step 04 · Check
Nothing risky slips through.
Before anything happens, it decides: fine, do it somewhere safe, ask first, or refuse. Spending limits sit on that same line, so there is no quiet surprise at the end of the month.
Step 05 · Do
It gets on with it.
The core stays small and quick. Heavier helpers wake up only when a job needs them and shut down the moment it's done, so it isn't sitting there eating your machine.
Step 06 · Show
The record is the truth.
Not a summary it wrote about itself — the actual sequence of what happened. Later, away from the work, it looks back over old jobs and turns the ones that went well into shortcuts.
Light on your machine
Small at the centre. Everything else optional.
One small thing runs all the time: the part that keeps track, makes plans and enforces your rules. Everything heavier — a browser, a scraper, whatever a job happens to need — wakes up for that job and shuts down after. No fan noise, no background hog.
That's also why it isn't married to any one AI company. The AI, the tools and the storage all plug in from outside, so replacing one is a setting, not a migration.
- Your AI
- Your tools
- Your files
- Your calendar
- Weißkeeps track · makes plans
holds the line · writes it down - Your inbox
- Your scripts
- Your reminders
- Your records
Nothing off the record
You can always ask what it did.
Your yes, your spending limit and the written record all sit on the same line as anything that leaves a mark. What you read afterwards isn't the assistant's own version of events — it's the list of things that actually happened, in order.
Below: how a job will read. A sketch, not a recording.
weiss · what happened
- 12:41:08Job opened · notes started
- 12:41:09Looked things up · recent work + saved know-how
- 12:41:10Plan written · 4 steps
- 12:41:11Wants to write a file · outside its usual patch
- 12:41:11Rule checked · only inside this project
- 12:41:12Allowed · limited to one folder
- 12:41:13Helper started · stops on its own when idle
- 12:41:17Result saved · file + what changed
- 12:41:18Step done · still inside budget
Different jobs. Same rules, every time.
Digging things up
Read around a question and keep the sources.
The boring repeat
The same chore, every week, without you.
Touching real systems
Only ever behind your yes.
The long haul
Jobs measured in hours, not replies.
Several at once
A few helpers working under one budget.
What's next
Where the work really is.
Weiß is fully written up and not yet built. You'll find the thinking, not a download. No percentages below, either — a progress bar on work nobody has started is just a nice-looking lie.
FirstWritten up
The basics, done properly
Talk to it, give it goals, let it use tools and remember things — all under rules you set.
ThenNext
Deeper
It checks its own work, browses the web, replays old jobs, and connects to more of what you use.
LaterLater
Wider
Teams, a proper app on your desk, and shortcuts learned from work it has already done.
Rules we hold ourselves to
- 01One thing to install, one thing to run.
- 02Stay light until heavy is proven.
- 03Plans a person can read.
- 04Nothing happens quietly.
- 05Remember in layers, not one heap.
- 06Learn on its own time, not yours.
- 07Never married to one AI.
- 08Yours on your machine, first.
Don't wait for it
Weiß CODE already does all of this for your code, and it's free. Take that one for a spin tonight — then come tell us what the bigger one should get right.