guillermollopis

5 ms·

1.
Show HN: Annexa – Generate EU AI Act technical documentation from your codebase(annexa.eu)
1 points by guillermollopis 6mo ago|0 comments
2.
by guillermollopis 7mo ago
The practical answer is: start with classification. Most developers jump straight to "what documentation do I need?" but the first question is whether your system is even high-risk under Annex III. If it is, you're looking at
3.
by guillermollopis 7mo ago
Interesting approach. One thing worth noting: the compliance challenge isn't just about runtime behavior — it's about documentation that proves you went through the right process. Annex IV requires documenting your training data p
4.
by guillermollopis 7mo ago
The biggest challenge I've seen is the gap between "classification" and "documentation." Most teams can figure out whether they're high-risk (Annex III has 8 clear categories), but then they stare at Annex IV&#
5.
by guillermollopis 7mo ago
The permission control and policy engine angle is interesting, Article 14 (human oversight) explicitly requires the ability for authorized persons to intervene, override, or stop the AI system. Having that built into the agent framework lay
6.
by guillermollopis 7mo ago
This is a useful piece of the puzzle, audit logging and injection detection are real requirements under Article 12 (record-keeping) and Article 15 (cybersecurity/robustness). One thing worth flagging: for high-risk systems under Annex
7.
by guillermollopis 8mo ago
Nice work on the UI, the invoice creation flow looks clean. For anyone reading who's on the other side of this (receiving invoices rather than sending them), the pain point is slightly different: you get PDFs or email invoices and need
8.
by guillermollopis 8mo ago
Nice work on the UI, the invoice creation flow looks clean. For anyone reading who's on the other side of this (receiving invoices rather than sending them), the pain point is slightly different: you get PDFs or email invoices and need
9.
by guillermollopis 8mo ago
Nice work on the UI, the invoice creation flow looks clean. For anyone reading who's on the other side of this (receiving invoices rather than sending them), the pain point is slightly different: you get PDFs or email invoices and need