Designed and implemented the OficIA UX v2 product shell, connected the existing audited queue and review workflows, clarified field-level evidence states, and recorded desktop and mobile acceptance.
Local document intelligence / human review
OficIA
A local document-intelligence workbench that turns sensitive PDFs into source-backed proposals for human approval.
What I owned
- Period
- July 2026
- Role
- Product shell, workflow integration, and browser acceptance
- Team
- Joaquín Fernández Cedeira on the core pipeline; Franco Ferreira on OficIA UX v2 and the real-data product interface
- Users
- People reviewing sensitive operational documents before an accountable decision is recorded
- Status
- Live auth-gated system; local Document AI with universal human review
Let local inference remove repetitive extraction work while keeping the source, corrections, and final operational decision visibly owned by a person.
Authored implementation commits and QA records in the canonical repository, a live health endpoint and auth boundary, and an earlier public LLM Local PDF baseline. All portfolio documents and values are synthetic.
- Deployment
- Local-first inference
- Workflow
- Every document reviewed
- Evidence
- Field-level anchors
- Record
- Versioned human decision
Documents become review-ready work
OficIA turns an incoming PDF into a prioritized review item, not an autonomous action. The inbox separates operational documents from controlled tests and makes ownership, source quality, and missing evidence visible before a reviewer opens the file.
Review without leaving the source
The workbench keeps extracted instructions, the original document, and the decision panel in one context. Reviewers can navigate the source, correct proposed values, and choose the next action without rebuilding the document in another tool.
Every value earns its place
Each critical field carries a source snippet, page location, and visible validation state. Missing or conflicting support stays attached to the field, so reviewers can open the exact fragment that justifies or challenges a proposal.
A human decision becomes the record
Approval is not the end of the interface. Corrections, versions, reviewer identity, evidence state, and the final action become an auditable record before anything is published to the next system.