Separate the layers
Live legal record, Por Derecho method, foundation governance and technical implementation must remain distinct even when they link to each other.
Partner entry path · document intelligence · workflow architecture
Technical scoping routeBuild the method before touching the live file.
Por Derecho is ready for a technically informed scoping discussion with document-intelligence, BPM, anonymisation, search and responsible-AI implementation partners. The first useful conversation is not a legal merits meeting. It is a systems-design discussion about how a protected record can be ingested, searched, cited, reviewed and governed without delegating human responsibility.
Why this route exists
Give technical partners the right door.
The Sun Park matter is the founding stress test. The partner conversation should focus on a reusable, synthetic-testable method rather than asking a technology provider to evaluate disputed facts.
Start with synthetic material
A pilot can test the architecture without sharing confidential documents, personal data, privileged material or live-case evidence.
Keep humans accountable
AI can retrieve, classify, compare and ask. It must not decide truth, guilt, liability, sanction, closure or professional credibility.
Technical fit map
Capabilities Por Derecho needs.
This is the capability map for an initial AI document-research and implementation discussion.
Document ingestion and preservation
Bulk intake, deduplication, version control, chain-of-custody metadata, file-family handling and evidence-state labelling.
OCR, extraction and classification
Scanned PDFs, signatures, dates, amounts, parties, authorities, proceedings, deadlines and document-type classification.
Semantic research with source references
Natural-language research over the corpus with exact citations, source snippets, uncertainty markers and refusal to answer beyond the record.
Anonymisation and publication controls
Public/private separation, redaction, pseudonymisation, protected training material and no accidental leakage into public pages.
Workflow gates and audit trail
Human review queues, escalation, correction, second review, sign-off, deadline tracking and auditability of AI-assisted steps.
Security and data residency
EU processing, access controls, privilege boundaries, model-use constraints, local embedding options and clear treatment of sensitive records.
Synthetic pilot
Legal memory and evidence integrity.
The first pilot should prove the workflow, not the legal case.
Prepare synthetic corpus
Wholly fictional records with dates, competing versions, missing authority and reversible/adverse outcomes. No anonymised real matter enters the first independent round.
Run document intelligence
OCR, classification, metadata extraction, entity/date/amount/proceeding detection and source normalization.
Research with citations
Ask legal-record questions and require grounded answers, contrary sources, missing evidence and confidence boundaries.
Human gate
A person accepts, corrects, rejects or escalates each output. The system preserves the reason, source and version.
Meeting design
What the first call should decide.
The right first meeting is a technically informed scoping session, not a demo request and not a legal argument.
| Question | Purpose |
|---|---|
| What corpus shape should a synthetic pilot use? | Define file types, languages, metadata and adversarial test conditions before architecture. |
| Which functions belong in search/RAG, BPM workflow and human review? | Prevent a single AI layer from becoming an uncontrolled decision system. |
| How should anonymisation, redaction and public/private boundaries be enforced? | Specify access and publication controls, then test that partner work cannot silently become a public release. |
| What audit trail is required? | Show every prompt, retrieval, source, correction, reviewer and final human gate. |
| What would a paid scoping workshop or limited POC require? | Move from conversation to defined deliverable without claiming partnership or adoption. |
Implementation boundary
AI assists the record. It does not become the authority.
The technical partner’s role would be to help design, implement, test or review controlled document-intelligence workflows. It would not be to endorse the live Sun Park position, decide a professional complaint, provide legal advice or validate Por Derecho as a foundation.