Hugin is most useful when it slows a reader down just enough to see what is known, what is missing, and what should not be turned into a claim.
Today was about that posture. The scanner, the News reader, the security baseline, and the values layer all moved in the same direction: more evidence, less performance.
Scans should land without hiding limits
Reddit often lets a public thread load while blocking some hosted account metadata. Hugin should not turn that into a vague failure. If the thread, comments, reply graph, public archive, and source coverage are available, the report should land.
The limit still matters. Missing author metadata belongs in the report as a coverage note, not as a hidden assumption and not as a reason to abandon the request.
News should feel like a source room
The News page now gives the story more of the screen. The image and article card carry the main view; categories, counts, refresh state, receipts, and site navigation move into a side rail.
That is closer to the right shape. A reader should be able to sit with one story, open the source links, inspect the mix of article rows and official records, and see whether the feed is live, cached, partial, or waiting on a public source.
The point is not to create urgency. It is to make the receipt trail easier to hold.
The morals layer is part of the interface
Hugin now carries a visible values layer through /morals, scan reports, and
News cards. The compass is simple: evidence, dignity, repair, and common good.
This is not there to scold the reader. It is there to constrain the product. Public evidence can help people avoid harm, but it can also be misused as fuel for pile-ons. The interface should keep that risk visible.
For scans, the values lens means separating observation from interpretation, showing blocked or missing data, and refusing to flatten people into a verdict. For News, it means asking who is helped, harmed, or left out; which official or primary source would make the story fairer; and what remains unknown.
Security belongs in the same promise
Security work is part of the reader contract too. The public site now keeps a tighter browser posture around content security, permissions, browsing-context isolation, DNS prefetching, and legacy cross-domain policy surfaces.
Most of that should stay quiet. A reader does not need a ceremony around headers. They should simply get a site that is harder to misuse and less likely to drift into weaker defaults.
The shape of today's work
In plain terms: scans should finish with honest limits, News should make source receipts easier to inspect, and the values layer should keep Hugin from treating public evidence as a license to target people.
That is the better direction for the product. Not more spectacle. More useful context, more restraint, and clearer public receipts.