Dizin
Ways of Working
Know what you get before you ask for a quote.
Three defined ways of working. Each states its duration, the outputs delivered, the client's responsibility and the criterion for acceptance.
Compliance Control Prototype
We select one regulatory duty and turn it into a working control with an audit trail. The result is running code, not a report.
For
Organisations with an existing product that want a compliance duty connected to the running system
Client responsibility
Access to the existing system and a named process owner are provided by the client organisation.
Duration
Six weeks
Deliverables
- 01A provision matrix: which rule, in which process, in which data field
- 02A data-flow map and a retention-period table
- 03A working control component and its source code
- 04An audit-trail schema with sample records
- 05A responsibility table and a handover record
Acceptance criterion
Shown through an acceptance test: the chosen duty is enforced and produces a record at run time.
Auditable AI Workflow
We write how a model output was produced, who was responsible, and how a challenge is answered into the system's own record.
For
Organisations using, or preparing to use, AI, who need to be able to show the basis for a decision
Client responsibility
The choice of model or provider is made jointly with the client. Training data is supplied by the client.
Duration
Eight weeks
Deliverables
- 01A model card and data-provenance record
- 02A defined human-review point and its interface
- 03Risk classification and threshold calibration
- 04A decision-record schema: input, version, rationale and human decision
- 05A challenge workflow and response template
Acceptance criterion
For ten randomly selected decisions, the basis for each can be shown end to end.
R&D Project File
We turn a project idea into a file whose R&D character can be defended. We state where the uncertainty lies and how it will be measured.
For
Organisations applying to TÜBİTAK, KOSGEB or European programmes that need a file where the technical and legal sides are built together
Client responsibility
The applicant is the client organisation. Meeting eligibility conditions is the client's responsibility.
Duration
Four weeks
Deliverables
- 01A definition of the R&D uncertainty and its position in the literature
- 02A method design and measurement plan
- 03Work packages, a schedule and a draft budget
- 04An intellectual-property and data-access plan
- 05A draft application form
Acceptance criterion
The file can be defended point by point against the evaluation criteria used by reviewers.
Write to us even if your problem does not fit any of these three.
These formats are defined versions of needs we see often. We also carry out work whose scope we define together. In the first meeting, we put in writing what you will receive and what we will deliver.
Request a meeting