KARDESH · FOR INSTITUTIONS
Begin with the concern your institution carries—then decide together which people, knowledge and tools are actually needed.
KARDESH does not begin by selling a ready-made technology package. It brings professionals, staff, people with lived field knowledge and the institution’s real need around the same table. Shared professional knowledge can grow across institutions, while private information about the institution, its staff and the people it serves remains within its entrusted boundary.
Current status: preparation framework · no active service application
People and professional knowledge before technology
An institution does not always need new software. Sometimes it first needs to name the concern, the human decision-maker and what must be protected.
A tool may produce a fast answer, but it cannot decide whether that answer is fitting, recognise everyone it may harm or carry responsibility for the outcome. KARDESH therefore considers technology alongside professional knowledge, staff experience, human judgement and the limits set by SEDD. Any resulting solution remains a human-made representation: it must be tested, open to objection and capable of being corrected or stopped.
What question is your institution bringing?
Answer six questions together before naming the solution.
This is not a sales form. It is a first framework for seeing what the institution genuinely needs—and where it may not yet be ready for outside support.
Which human or professional concern are you trying to address?
Describe the concern through the people, service and professional responsibility involved—not only through efficiency, cost or automation.
Who makes the decision today, and who carries accountability for it?
Make the authority of staff, experienced professionals, managers, boards and machines visible. Do not leave final human responsibility unclear.
Which knowledge lives in experience, and which knowledge is recorded?
Do not treat documents as the only source. Listen to experienced practitioners, staff, the people served, local language and exceptions found in the field.
What can be shared, and what must remain within the institution?
Separate shared professional knowledge from personal data, institutional secrets, contracts and private working processes at the outset.
Who can object when something goes wrong, and how can the work be reversed?
Do not place a system into people’s lives until correction, stopping, recording and remedy are practical possibilities.
Who will carry maintenance and learning after the work ends?
Move beyond a one-off delivery. Develop the institution’s own people, follow change and keep knowledge current.
From purchasing a tool to learning together
A ready-made product may give an institution a tool. A living professional relationship helps people use and adapt that tool in the right place.
Technology purchase alone
Looks for the answer inside the product
- May narrow the concern to whatever the product can already do
- May reduce experienced professionals to people who approve a decision afterwards
- May separate data from the institution and create dependence on an outside system
- May leave maintenance, objection and learning weak after delivery
Shared work through KARDESH
Begins by understanding the concern and the amanah
- Listens to staff, experienced professionals and the people the institution serves
- Separates shared knowledge from the institution’s private entrusted area
- Begins with a small, safe, human-approved and reversible step
- Develops the institution’s own people, maintenance and capacity for correction
Three areas of shared work
Shared professional knowledge, common safeguards and institution-specific amanah do not belong in the same place.
This distinction does not isolate an institution. It allows shared knowledge to grow while protecting private information, people and the institution’s own decision-making space.
Architectural direction
People remain at the centre; data, models, representation, limits and shared work form the surrounding layers.
- 01
Shared professional knowledge
Concepts, open sources, shared questions, learning principles, safety measures and guidance that different institutions can develop together.
Explore this layer → - 02
Care across languages and institutions
A relationship that keeps visible where a source came from, which version is being used, who objected and how shared knowledge was corrected.
Explore this layer → - 03
Institution-specific amanah
Personal and institutional data, private processes, contracts, access, internal tools and decision records do not pass into the public portal or another institution.
Explore this layer →
A responsible way to begin
If an active service is established, institutional work should move through small and reversible steps.
The sequence below is not an application or delivery process available today. It is a preparation model showing the responsibilities that a real institutional relationship would need to carry.
01 1 · Listen to the concern
Understand the concern in context with the institution’s representative, staff, experienced professionals and the people affected.
02 2 · Separate the amanah and its limits
Identify shared knowledge, private data, authority, law, possible effects on children or households and anything that must remain outside the work.
03 3 · Form one manageable working question
Instead of promising transformation, choose a limited, time-bound and measurable scope with a named human owner and a practical way to stop.
04 4 · Try it with synthetic examples
Test the rules, likely errors and required human approval through fictional cases before using any real institutional data.
05 5 · Decide together
If professional, SEDD, institutional or human conditions are not sufficient, do not proceed. Record the reason, revise the work or close it.
Eight work areas in preparation
Working frameworks for concerns institutions commonly face
These cards are not service packages available for purchase today. Each is a preparation record showing how an institutional concern could be approached with human and professional responsibility. A Planned label does not promise an active team, application, price, schedule or delivery.
8 institutional services
Concept and Source Map
The same concept is used differently across teams, while the origin of a source and its relationship with professional experience remain unclear.
- Preparation record · scope and duration not set
- Concepts used in shared and differing ways
- Connections between sources and claims
Human-Approved Institutional Workflow
As automation adds speed, it becomes unclear who started a task, who approved it, who may object and who can reverse a wrongful action.
- Preparation record · process scope and duration not set
- Tasks and responsible people
- Required approval and stopping points
Institutional Concern and Responsibility Map
The institution is adopting new tools, but the human and professional concern being addressed, who makes the decision and who carries accountability for the outcome are not yet clear.
- Preparation record · no duration promised
- Map of the concern and people affected
- Decision and responsibility chain
Maintenance, Updating and Correction
Knowledge, rules and tools remain as they were first established; field changes, new risks and staff objections do not reach later versions.
- Preparation record · continuing-care model not set
- What changed and why
- People and processes affected
Professional EDEB and Institutional Learning
As staff learn new tools, human decision, source clarity, privacy, EDEB in representation and responsibility for correcting errors are often treated as separate from learning.
- Preparation record · programme length not set
- Questions of professional amanah and EDEB
- Cases close to real working life
Responsible Data Arrangement
The institution uses data, but its source, permission, purpose, underrepresented groups and deletion point are not visible in one record.
- Preparation record · data scope and duration not set
- Meaning and source of the data
- Purpose, permission and access limits
SEDD: Harm, Privacy and Human Oversight
Harm, privacy, effects on children and households, the right to object and final human responsibility remain on separate lists, so people do not know who can stop the work in practice.
- Preparation record · risk and duration not set
- People and entrusted areas to be protected
- Actions that must not be taken
Sourced, Human-Governed Institutional Assistant
Machine assistants used by the institution do not clearly show what they do not know, which sources they rely on or which decisions must remain human.
- Preparation record · risk and scope not set
- Tasks the assistant may and may not support
- Visible links to sources
Responsibilities the institution cannot hand away
KARDESH does not take over the institution’s decisions, duties towards staff or accountability for outcomes.
If real work begins, the institution is not merely a client. It remains responsible for the concern, the data, its staff and the consequences of the work.
Define the real need and the people affected by it Name an authorised institutional representative and the final human decision-maker Use only necessary and permitted data, with a clear purpose and retention period Include staff and protect a practical right to object and withdraw Bring errors, harm and unexpected outcomes into review without concealment Carry responsibility for maintenance, learning, updates and stopping the system when needed
What are we not promising?
A model, piece of software or advisory output cannot make an institution fair, safe or competent by itself.
KARDESH does not replace professional competence, human judgement, legal responsibility, fiqh review or institutional leadership. Every framework, learning programme, data arrangement and tool is a fallible human-made representation. It should not enter real use until its sources, limits, responsible people, path for objection and record of correction are visible.
Preparation and introduction
Which professional concern, human responsibility or use of technology would your institution like to reconsider?
Institutional applications, proposals and contracts are not yet open. For now, you may share only a general introductory message about the concern. Do not send private data, staff information, contracts, institutional secrets or real datasets. This is not a promise of an active service, accepted pilot, price, schedule, delivery or partnership.