State before surface
A product should make the current state, the next possible action, and the consequence of that action legible before visual polish carries the story.
Nordic home edition01 02 03 04 05 06 
Start with HAAM
HAAM product edition
haam-
the product namespace
HAAMProducts
Eight products. Each starts with an interaction contract.
The spec comes before the implementation: what a person is trying to resolve, which states the system must expose, where automation has to stop, how failure behaves, and what evidence would prove the interaction is finished. The live builds can work backward from that.
Interaction grammar
What every HAAM product has to keep true.
Behavior before screenshots.
Evidence stays attached
A recommendation, score, classification, or answer should keep the source material close enough that a person can inspect why the system believes it.
Suggestions are not facts
The interface must distinguish sensed, inferred, suggested, confirmed, and executed states instead of letting automation blur them together.
Permission before consequence
The more consequential an action becomes, the clearer the confirmation, preview, scope, and recovery path must be.
Missing stays missing
Unknown, stale, unavailable, and unsupported are designed states. The system should not quietly fill gaps with confidence it does not have.
Failure is part of the loop
Every important flow needs an interruption, refusal, correction, undo, retry, or handoff path that preserves what the person already did.
On haam.co
Projects
Open a case study for the target state model, edge cases, definition of done, and the receipts the current build can already show.
haam-*08 products in the namespace
01
Client Desk
When someone writes, the answer should already be in the work. Approved knowledge, three confirmed actions, then the rest comes to me with the context attached.
Interaction contract
Answer from approved evidence. Ask before acting. Escalate without making the client start over.
02
BI
Cash arriving and leaving, so I can see whether the work is covering the life around it. The public host shows a demo set.
Interaction contract
Every financial conclusion must open back into the rows that made it true.
03
Product Studio
Held still so the material, the light, and the construction can be looked at.
Interaction contract
Manipulate one object directly, then share the exact view rather than a generic product page.
04
Compass
Sleep, energy, time, and what already happened this week decide the session. Then you can see why. The web host uses demo data.
Interaction contract
Turn today’s constraints into a readable fitness suggestion, with the reasons and the stop condition visible.
05
Consistency
A signal can suggest. You still say whether it happened.
Interaction contract
A device may notice a signal. Only the person can say the routine actually happened.
06
Air
Personal Atmotube PM2.5 next to the CAMS city background, hour by hour.
Interaction contract
Compare personal exposure with the city only when metric, place, and hour actually line up.
07
Speaking
Find open calls, rank them against the evidence and talk ideas, prepare the pack, send only with approval.
Interaction contract
Reduce a pile of open calls to a grounded shortlist, then keep sending behind a human decision.
08
Swimmable Cities
The closest managed swim places, the official baseline, nearby pollution, and what the city can still do. Check today’s local notice before you enter the water.
Interaction contract
Show what is officially known about a swim spot, how old it is, and where to verify today.
A job that needs its own address?