hey Contra, first post here.

I'm Nouman. I build AI agents and automations, and for the last while I've been deep in the boring side of AI that nobody posts about: compliance.

most teams I talk to are shipping AI features fast and have no idea if they'd pass an EU AI Act check. usually they wouldn't, and usually it's fixable in a few weeks, not months.

so that's what I work on. agents and automations that actually run in production, plus the logging, risk checks and evidence trail that keep them legal.

I'll be sharing what I learn here, mostly practical stuff. if you're building with AI and have a question about either side, ask away.

what's everyone here building right now?

The evidence trail you mentioned is the hard engineering part. What do you retain for each agent tool call so someone can reconstruct the run without storing sensitive payloads?

I (and lovable AI) built a small, simple and fast site for a small hidden hostel in the Lima Center

Why? A lot of nice places often have poor discovery and visibility, especially in historical districts and areas with strict regulations.

So we bypassed that limitation using technology and the internet, we built a landing page that communicates the hostel's vital info, how to reach it and the passcodes/door numbers. This info is often spread across multiple channels and travelers don't have the time nor interest in checking Instagram or Titkok videos just to get to their accommodation.

Here's AI's perspective, which I consider my collaborator, breaking down the rest of the details

AI perspective — how we solved Hostal Pasaje Central

Guests arrive at Pasaje Central 214 and see nothing that says "hostal". A grand hotel with brass and glass. A loud restaurant with terrace tables. A staircase with no sign. So they call. Twenty calls a day, fifteen minutes each, and the owner walks the stairs between the third floor and the street until the afternoon is gone.

The fix is not another app. Nobody downloads an app at 11 p.m. with one bar of signal and two suitcases. The fix is one web link.

What we shipped:

· A Visual Arrival Pass — a single page that opens in under a second on a weak connection. No install, no login, nothing to update. · A 10-second walk, filmed street to door. Hurried guests watch it; careful ones scroll the photo cards. Same route either way. · Landmark directions only: the big hotel that isn't us, the restaurant whose building actually holds us, the small green door with the HOSPEDAJE plaque. No meters — a tired traveller can't read "30 m", but can read "the green door next to the restaurant". · The door code and the reception number in large type, tap to copy. · One button that matters: "I'm still lost". It opens WhatsApp with the message already written, so a stranded guest never has to type while anxious. · Bilingual by default. ES/EN on the pass, and the staff panel switches too.

Behind the desk, at /staff: passcode in, guest name and dates in, and out comes a pass link plus a message ready to send — WhatsApp for the guest, a paste-ready template for Booking.com. The radar shows who's due, who's walking, who's in. That's the whole system, and it's honest about being manual: a PMS hook, not a PMS. Nothing pretends the booking arrived by itself.

The number we judge ourselves by: 20 calls a day down to 2, and the 2 that remain are the ones that matter. Guests will always call — the point is that directions stopped being the reason.

And none of it needs a $100+/month property-management system. Those are priced for chains, not for a hostal on the third floor.

Built with Lovable for the #lovablechallenge (Built for Small Business), "Fix the follow-through" angle. The hostal is fictional; the problem isn't — it's every small property in a historic centre with no signage and a busy ground floor.

Live: https://hotel-arrival-pass.lovable.app · Desk: /staff, passcode: hospedaje-214 (irrelevant since it's a fictional business)