- Bilingual French and Arabic interface
- Versioned workflow runs and tamper-detection fields
- Deterministic expected-versus-observed findings
- Human verification and golden-set methodology
- Publicity-period, penalty-cap, and payment-delay controls
Public procurement · Pilot solution
Procurement controls, computed rather than sampled.
Tasaab’s Avokaat proof-of-value applies the deterministic compliance boundary to procurement: source documents become reviewable facts, facts become controls, and findings remain linked to evidence and controller decisions.
The control problem
One procurement decision is scattered across many records.
Plans, notices, specifications, bids, commission records, evaluation sheets, awards, and declarations arrive in different formats and languages. Sampling a few documents can miss a contradiction that only appears across the full dossier.
The proposed workflow builds one evidence graph, runs explicit controls over every dossier in scope, and routes uncertainty to a controller instead of hiding it in model prose.
End-to-end workflow
From procurement plan to final report.
Deterministic findings and semantic signals travel through the same human-controlled audit record.
- 01
Plan and dossier intake
Join procurement-plan records to tender notices, specifications, pricing schedules, and contractual documents.
- 02
Source-anchored facts
Extract dates, amounts, guarantees, criteria, parties, and document spans with confidence and human verification.
- 03
Deterministic controls
Compare observed facts to transcribed legal thresholds and internal consistency rules—without asking a model to adjudicate.
- 04
Semantic signals
Surface potentially directed specifications, discriminatory criteria, and probity concerns for controller review, not automatic accusation.
- 05
Award reconciliation
Compare evaluation records, scoring, recommended award, publication, and final outcome across the dossier.
- 06
Controller deliverables
Carry accepted findings and amendment history into editable findings sheets, notes, reports, and transmittal documents.
Example implemented control
Each finding carries the rule and the arithmetic.
DELAI_SUFFISANCE_AODETERMINISTIC
- Legal reference
- Décret n° 2-22-431 · Art. 23
- Expected
- Minimum publicity period: 21 days
- Observed
- Dates extracted from the source notice
- Decision
- Code compares the dates; the controller validates the source
Delivery truth
What exists, what needs acceptance, and what remains pilot work.
The public demonstration illustrates the intended workflow with labelled simulated data. It is not presented as a completed CDC/CRC audit.
- VM and Kubernetes reference deployment profiles
- Self-hosted model and embedding routes
- Zero-egress, recovery, and backup-restore drills
- Signed Ed25519 acceptance-evidence bundles
- Production PMP ingestion and reconciliation
- Directed-specification and discriminatory-criteria validation
- Award-versus-evaluation reconciliation
- Probity and conflict-of-interest protocols
- Official CDC/CRC report templates and portfolio-scale processing
Target deliverables
Controller decisions flow into the formal record.
Orientation noteProvisional reportFinal reportFindings summary sheetTransmittal letter
Official CDC/CRC templates must be supplied and accepted during the pilot. Current generated examples are demonstrative scaffolds.
Evaluate before you licence
Define a controller-labelled procurement pilot.
Start with authorized PMP records, tender dossiers, official output templates, and agreed acceptance criteria. Measure field accuracy, alert precision and recall, traceability, review time, and sovereign deployment evidence.