AI & DIGITAL SKILLS MAGAZINE Learn from beginner to expert
Contact EDITION 2026
ISHRAQA7 — The practical digital learning magazine
ISHRAQA 7 ACADEMY · Security & Future

Emerging technologies: understand, assess and experiment

A fictional cooperative explores technology options for a local service. No real investment or performance result is claimed.

  • LevelBeginner → Intermediate
  • Course programme12 modules
  • Course filesPDF · CSV · TXT · ZIP

Also available in Français العربية

01. Separate trends, evidence and demos

Professional objective : Claim/evidence/limit matrix.

Fictional case study

A fictional cooperative explores technology options for a local service. No real investment or performance result is claimed.

Method to understand

This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.

Guided demonstration

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Assess four fictional announcements for maturity, independent evidence and deployment constraints.
  3. Check the result against this criterion: A controlled demo is not industrial proof.
  4. Archive output, date and limitations; request human approval for sensitive choices.

Independent practice

Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Assess four fictional announcements for maturity, independent evidence and deployment constraints.

Reference answer and verification

Claim/evidence/limit matrix. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.

Limits and safety

A controlled demo is not industrial proof.

Expected output : Claim/evidence/limit matrix.

Next chapter: reuse this output as the starting point for the next activity.

02. Generative AI and its limits

Professional objective : Reliability checklist for six claims.

Fictional case study

A fictional cooperative explores technology options for a local service. No real investment or performance result is claimed.

Method to understand

This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.

Guided demonstration

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Compare two fictional AI answers to a business request; log unverified statements.
  3. Check the result against this criterion: Fluent output may contain invented facts.
  4. Archive output, date and limitations; request human approval for sensitive choices.

Independent practice

Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Compare two fictional AI answers to a business request; log unverified statements.

Reference answer and verification

Reliability checklist for six claims. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.

Limits and safety

Fluent output may contain invented facts.

Expected output : Reliability checklist for six claims.

Next chapter: reuse this output as the starting point for the next activity.

03. AI agents and human oversight

Professional objective : Diagram with input, tool, approval and stop.

Fictional case study

A fictional cooperative explores technology options for a local service. No real investment or performance result is claimed.

Method to understand

This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.

Guided demonstration

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Diagram a fictional agent that sorts requests without sending or performing external actions.
  3. Check the result against this criterion: Require human authorization before any real-world action.
  4. Archive output, date and limitations; request human approval for sensitive choices.

Independent practice

Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Diagram a fictional agent that sorts requests without sending or performing external actions.

Reference answer and verification

Diagram with input, tool, approval and stop. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.

Limits and safety

Require human authorization before any real-world action.

Expected output : Diagram with input, tool, approval and stop.

Next chapter: reuse this output as the starting point for the next activity.

04. IoT devices and sensors

Professional objective : Sensor sheet and failure analysis.

Fictional case study

A fictional cooperative explores technology options for a local service. No real investment or performance result is claimed.

Method to understand

This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.

Guided demonstration

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Design a fictional temperature sensor use case with threshold, battery and privacy needs.
  3. Check the result against this criterion: Do not connect physical devices without permission.
  4. Archive output, date and limitations; request human approval for sensitive choices.

Independent practice

Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Design a fictional temperature sensor use case with threshold, battery and privacy needs.

Reference answer and verification

Sensor sheet and failure analysis. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.

Limits and safety

Do not connect physical devices without permission.

Expected output : Sensor sheet and failure analysis.

Next chapter: reuse this output as the starting point for the next activity.

05. Edge computing and local processing

Professional objective : Latency/privacy/maintenance comparison.

Fictional case study

A fictional cooperative explores technology options for a local service. No real investment or performance result is claimed.

Method to understand

This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.

Guided demonstration

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Compare local processing and a remote service for a fictional sensor decision.
  3. Check the result against this criterion: Performance figures are hypotheses requiring measurement.
  4. Archive output, date and limitations; request human approval for sensitive choices.

Independent practice

Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Compare local processing and a remote service for a fictional sensor decision.

Reference answer and verification

Latency/privacy/maintenance comparison. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.

Limits and safety

Performance figures are hypotheses requiring measurement.

Expected output : Latency/privacy/maintenance comparison.

Next chapter: reuse this output as the starting point for the next activity.

06. Blockchain: uses and limits

Professional objective : Decision tree with costs and trade-offs.

Fictional case study

A fictional cooperative explores technology options for a local service. No real investment or performance result is claimed.

Method to understand

This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.

Guided demonstration

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Evaluate a fictional provenance ledger and choose between a database and immutable log.
  3. Check the result against this criterion: Blockchain does not remove the need for trust governance.
  4. Archive output, date and limitations; request human approval for sensitive choices.

Independent practice

Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Evaluate a fictional provenance ledger and choose between a database and immutable log.

Reference answer and verification

Decision tree with costs and trade-offs. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.

Limits and safety

Blockchain does not remove the need for trust governance.

Expected output : Decision tree with costs and trade-offs.

Next chapter: reuse this output as the starting point for the next activity.

07. AR and immersive experiences

Professional objective : Six-scene storyboard and non-immersive alternative.

Fictional case study

A fictional cooperative explores technology options for a local service. No real investment or performance result is claimed.

Method to understand

This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.

Guided demonstration

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Draft an accessible augmented-visit storyboard without claiming a headset was tested.
  3. Check the result against this criterion: Consider accessibility, comfort and consent.
  4. Archive output, date and limitations; request human approval for sensitive choices.

Independent practice

Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Draft an accessible augmented-visit storyboard without claiming a headset was tested.

Reference answer and verification

Six-scene storyboard and non-immersive alternative. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.

Limits and safety

Consider accessibility, comfort and consent.

Expected output : Six-scene storyboard and non-immersive alternative.

Next chapter: reuse this output as the starting point for the next activity.

08. Robotics and responsible automation

Professional objective : Safety diagram and responsibility matrix.

Fictional case study

A fictional cooperative explores technology options for a local service. No real investment or performance result is claimed.

Method to understand

This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.

Guided demonstration

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Diagram a fictional sorting flow with sensor, decision, emergency stop and operator.
  3. Check the result against this criterion: Real safety functions require specialist engineering and validation.
  4. Archive output, date and limitations; request human approval for sensitive choices.

Independent practice

Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Diagram a fictional sorting flow with sensor, decision, emergency stop and operator.

Reference answer and verification

Safety diagram and responsibility matrix. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.

Limits and safety

Real safety functions require specialist engineering and validation.

Expected output : Safety diagram and responsibility matrix.

Next chapter: reuse this output as the starting point for the next activity.

09. Quantum computing: promise and limits

Professional objective : Assessment without quantum-speedup claims.

Fictional case study

A fictional cooperative explores technology options for a local service. No real investment or performance result is claimed.

Method to understand

This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.

Guided demonstration

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Classify three fictional problems by theoretical fit, maturity and classical alternatives.
  3. Check the result against this criterion: Do not claim speedups without reproducible benchmarks.
  4. Archive output, date and limitations; request human approval for sensitive choices.

Independent practice

Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Classify three fictional problems by theoretical fit, maturity and classical alternatives.

Reference answer and verification

Assessment without quantum-speedup claims. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.

Limits and safety

Do not claim speedups without reproducible benchmarks.

Expected output : Assessment without quantum-speedup claims.

Next chapter: reuse this output as the starting point for the next activity.

10. Post-quantum cryptography

Professional objective : Cryptographic inventory and migration plan.

Fictional case study

A fictional cooperative explores technology options for a local service. No real investment or performance result is claimed.

Method to understand

This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.

Guided demonstration

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Inventory fictional cryptographic dependencies and plan monitoring for FIPS 203/204/205.
  3. Check the result against this criterion: Do not invent or deploy a home-grown cryptographic scheme.
  4. Archive output, date and limitations; request human approval for sensitive choices.

Independent practice

Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Inventory fictional cryptographic dependencies and plan monitoring for FIPS 203/204/205.

Reference answer and verification

Cryptographic inventory and migration plan. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.

Limits and safety

Do not invent or deploy a home-grown cryptographic scheme.

Expected output : Cryptographic inventory and migration plan.

Next chapter: reuse this output as the starting point for the next activity.

11. Ethics, impacts and environmental footprint

Professional objective : Trade-off matrix with metric limitations.

Fictional case study

A fictional cooperative explores technology options for a local service. No real investment or performance result is claimed.

Method to understand

This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.

Guided demonstration

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Compare three hypothetical options for risk, resources, accessibility and public benefit.
  3. Check the result against this criterion: No environmental statistics without defined scope and source.
  4. Archive output, date and limitations; request human approval for sensitive choices.

Independent practice

Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Compare three hypothetical options for risk, resources, accessibility and public benefit.

Reference answer and verification

Trade-off matrix with metric limitations. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.

Limits and safety

No environmental statistics without defined scope and source.

Expected output : Trade-off matrix with metric limitations.

Next chapter: reuse this output as the starting point for the next activity.

12. Final project: technology review board

Professional objective : Decision dossier, risk table and pilot protocol.

Fictional case study

A fictional cooperative explores technology options for a local service. No real investment or performance result is claimed.

Method to understand

This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.

Guided demonstration

  1. Prepare the case: read the scenario, identify the output, record assumptions.
  2. Perform the chapter task: Compare three candidate technologies, recommend a reversible pilot and define stop criteria.
  3. Check the result against this criterion: Separate sourced facts, hypotheses and untested results.
  4. Archive output, date and limitations; request human approval for sensitive choices.

Independent practice

Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Compare three candidate technologies, recommend a reversible pilot and define stop criteria.

Reference answer and verification

Decision dossier, risk table and pilot protocol. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.

Limits and safety

Separate sourced facts, hypotheses and untested results.

Expected output : Decision dossier, risk table and pilot protocol.

Next chapter: reuse this output as the starting point for the next activity.

Check your knowledge

1. Separate trends, evidence and demos
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
2. Generative AI and its limits
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
3. AI agents and human oversight
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
4. IoT devices and sensors
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
5. Edge computing and local processing
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
6. Blockchain: uses and limits
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
7. AR and immersive experiences
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
8. Robotics and responsible automation
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
9. Quantum computing: promise and limits
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
10. Post-quantum cryptography
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
11. Ethics, impacts and environmental footprint
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?
12. Final project: technology review board
1. Which output demonstrates completion of this chapter?
2. Which action applies the chapter method?
3. Which check is required before approval?

Course files

Choose a language, then the format you need.

العربية

FileFormatSizeDownload
الدليل التعليمي PDF 45 KB Download — الدليل التعليمي (PDF)
دفتر التمارين PDF 39 KB Download — دفتر التمارين (PDF)
دليل التصحيح PDF 39 KB Download — دليل التصحيح (PDF)
المشروع النهائي PDF 22 KB Download — المشروع النهائي (PDF)
قائمة التحقق CSV 2 KB Download — قائمة التحقق (CSV)
بيانات افتراضية CSV 1 KB Download — بيانات افتراضية (CSV)
مراجع رسمية TXT 1 KB Download — مراجع رسمية (TXT)
حقيبة تدريب دون اتصال ZIP 2 KB Download — حقيبة تدريب دون اتصال (ZIP)

Français

FileFormatSizeDownload
Manuel pédagogique PDF 30 KB Download — Manuel pédagogique (PDF)
Cahier d’exercices PDF 25 KB Download — Cahier d’exercices (PDF)
Corrigés des exercices PDF 26 KB Download — Corrigés des exercices (PDF)
Projet final PDF 12 KB Download — Projet final (PDF)
Grille de contrôle CSV 2 KB Download — Grille de contrôle (CSV)
Données fictives CSV 1 KB Download — Données fictives (CSV)
Références officielles TXT 1 KB Download — Références officielles (TXT)
Kit pratique hors ligne ZIP 2 KB Download — Kit pratique hors ligne (ZIP)

English

FileFormatSizeDownload
Course manual PDF 28 KB Download — Course manual (PDF)
Practical workbook PDF 24 KB Download — Practical workbook (PDF)
Answer guide PDF 25 KB Download — Answer guide (PDF)
Final project PDF 12 KB Download — Final project (PDF)
Quality checklist CSV 1 KB Download — Quality checklist (CSV)
Fictional data CSV 1 KB Download — Fictional data (CSV)
Official references TXT 1 KB Download — Official references (TXT)
Offline practice kit ZIP 2 KB Download — Offline practice kit (ZIP)