KARDESH · INSTITUTION DISCOVERY SCENARIOS
Before real institutional work begins, the concern, human responsibility, data boundary and stopping conditions must be clear.
The education and media records on this page are not institutional projects. There is no participating institution, appointed team, contract or real data. The two fictional examples simply show which questions would need answers—and which entrusted areas would need protection—before a responsible pilot could be considered.
No institution · No appointed team · No real data · No active pilot
Honest status
Without an institution, authorised people, mutual agreement and a safe field record, we do not describe an active pilot.
An idea brief is not a partnership. A synthetic example is not institutional data. Even a working trial is not proof of success or acceptance. A public record can only help people understand the concern, the boundaries and the responsibilities that would have to be carried later. A real relationship would require authorised parties and the relevant SEDD conditions, recorded separately in a protected area.
The difference between preparation and real fieldwork
A fictional discovery scenario helps people think. An active pilot carries limited and recorded responsibility towards real people.
Fictional discovery scenario
Not yet an institutional relationship
Shows the human, data and safety questions that may surround a general concern.
- Names no institution, team or authorised person
- Uses only synthetic examples and public rules
- Makes no claim of success, partnership or delivery
- Contains no institution-specific data or system
Active and limited pilot
Creates a real relationship of responsibility
Can begin only when the institution, authorised people, scope and safeguards are in place.
- Names the people who decide and have authority to stop
- Records purpose, duration, access and data limits
- Has practical routes for objection, incidents, reversal and closure
- Runs at limited scale and may be refused or stopped
Three entrusted areas in a pilot
Shared professional knowledge may grow; what belongs to a person or institution remains within its own boundary.
This distinction does not prevent shared learning. General, anonymised lessons from an institutional concern may return to the shared field after appropriate review. Personal data, institutional secrets and decision records do not pass to another institution or the public portal.
Architectural direction
People remain at the centre; data, models, representation, limits and shared work form the surrounding layers.
- 01
Shared professional knowledge
Open sources, shared concepts, safety questions, synthetic examples and general guidance that different institutions could develop together.
Explore this layer → - 02
Care across institutions
Keeps track of sources, versions, objections and shared measures without giving one institution authority over another institution’s data or decisions.
Explore this layer → - 03
Amanah belonging to people and the institution
Personal and child data, internal processes, contracts, access, incident and decision records stay within the authorised area and never enter the public portal.
Explore this layer →
Two fictional examples prepared without selecting an institution
How might a responsible start be explored through education and media concerns?
A Discovery label does not mean that an institutional meeting has taken place. Both scenarios use no personal or institutional data; they make visible the questions that a future relationship would have to answer.
2 institutional discovery scenarios
Fictional Discovery Scenario for Learning Content
Shows how source clarity, teacher judgement and child safety might be considered in a school without using real student data.
- No institution, appointed team or authorised person exists. This is a fictional scenario—not a proposal, contract, partnership or active pilot.
- A map of the learning concern, affected children and responsible people
- A small synthetic rehearsal testing source clarity and child safety
Fictional Discovery Scenario for Media Sources and Consent
Shows how source protection, consent, disclosure of synthetic content, correction and human editorial responsibility might be considered without using real personal data.
- No institution, appointed team or authorised person exists. This is a fictional scenario—not a proposal, contract, partnership or active pilot.
- A map of the publication concern, people affected, sources and decision owners
- A small synthetic rehearsal testing consent, synthetic-content disclosure and correction
Public clarity and protected amanah
People should be able to see what is being evaluated without exposing their data or an institution’s internal workings.
What may remain on a public page
The general concern and safety framework
Information people need in order to understand and question the approach, without identifying a person or institution.
- The concern, purpose and limits of the example
- Synthetic examples and open evaluation questions
- Principles for human decision, objection and stopping
- A clear statement when no institution or team exists
What stays inside a protected institutional area
Real people, data and decision records
Entrusted information visible only to authorised people for a clear purpose and limited period.
- The identity of a person, child, staff member or source
- Institutional systems, access and contract information
- Incident, objection, human decision and correction records
- Retention, withdrawal and verifiable deletion records
From an example to a real and limited pilot
Six responsibility gates must be crossed before approaching real people or institutional data.
These are not an automatic approval sequence. If a requirement is missing, the work returns to an earlier step, becomes smaller or closes entirely.
01 1 · Listen to the concern and the people involved
Before translating a request into a ready-made product, listen to staff, experienced professionals and the people who would live with the outcome.
02 2 · Name the responsible people
Identify the institutional representative, professional lead, final decision-maker and the people who will hear objections and stop the system if needed.
03 3 · Separate scope and amanah
Write down the purpose, excluded uses, shared knowledge, private data, access, duration and closure conditions.
04 4 · Complete legal and SEDD conditions
Have competent people review consent, privacy, effects on children and households, harm, retention, objection and deletion.
05 5 · Rehearse with synthetic examples
Test errors, refusal, human approval, incident recording and reversal without using real data.
06 6 · Decide at limited scale
Begin a time-bound, reversible trial only if the conditions are sufficient. Explain whether the result is accepted, corrected, stopped or closed.
What should an institution ask itself?
Before asking for a pilot, consider your readiness to carry responsibility and learn—not only the technology.
Can we describe the concern in the language of the people affected? Is there a named person who will carry the final decision and account for a harmful outcome? Will we use only necessary, permitted data and refuse anything beyond it? Will staff and affected people be heard in a way that can genuinely change the work? Can we accept failure, reversal or closure from the outset? Are there people who can carry maintenance, learning and correction after the pilot?
Current status
Applications for institutional pilots and the submission of real data are not yet open.
For now, you may explore the two fictional scenarios and the approach for institutions, then share only a general introductory message. Do not send private data, staff or child information, institutional documents, contracts, source identities or real datasets. This is not a promise of pilot acceptance, partnership, price, schedule, delivery or success.