Resources — Methodological cards
The 17 canonical ACF® cards (ACF-00 to ACF-16) — the operational backbone of the standard. Each card is served as bilingual Markdown with a structured frontmatter (code, title, dimension, related principles, related articles, related cards, keywords).
acf.advisor so an agent picks for you.What this contains
Seventeen resources, one per card, URI acf://fiche/ACF-XX. The content is served as Markdown (text/markdown). Both locales ship for all seventeen cards in V1.0 — the client picks via Accept-Language.
See also — READ tool acf.fiche.lookup for enriched access (keyword resolution, related cards, example).
Exhaustive list ×17
acf://fiche/ACF-00MarkdownFR + ENACF-00 — Introduction to ACF®
Standard overview, founding principles, autonomy levels, dimensions and the DDAO role on a single page.
acf://fiche/ACF-01MarkdownFR + ENACF-01 — Autonomy Mapping
Methodology for placing an existing or planned agent on the N0–N3 scale and documenting the rationale.
acf://fiche/ACF-02MarkdownFR + ENACF-02 — Criticality Matrix
How to score an agent on a (dimension × business impact) matrix to calibrate controls proportionally.
acf://fiche/ACF-03MarkdownFR + ENACF-03 — Agentic Constitution
Template for a written constitution that bounds an agent — purposes, forbidden domains, escalation triggers.
acf://fiche/ACF-04MarkdownFR + ENACF-04 — Agent Card
Standard documentation card for an agent in production: identity, model, mandate, DDAO, criticality, controls.
acf://fiche/ACF-05MarkdownFR + ENACF-05 — Decision Register
Time-stamped, hash-chained record of every agentic decision — the operational expression of P2.
acf://fiche/ACF-06MarkdownFR + ENACF-06 — Ecosystem Constitution
Cross-agent rules of the road when several agents share data, tools or a mandate scope.
acf://fiche/ACF-07MarkdownFR + ENACF-07 — Kill Switch & human takeover
How to design, document and test a kill switch — the direct AI Act Article 14 operationalisation.
acf://fiche/ACF-08MarkdownFR + ENACF-08 — Agentic Observability
End-to-end observability requirements: traces, metrics, drift signals, replayable inputs.
acf://fiche/ACF-09MarkdownFR + ENACF-09 — Escalation Thresholds
Numeric and qualitative thresholds that force escalation to a human — calibrated by criticality.
acf://fiche/ACF-10MarkdownFR + ENACF-10 — Agent Lifecycle
Phased lifecycle (design, pre-flight, go-live, run, decommission) with controls per phase.
acf://fiche/ACF-11MarkdownFR + ENACF-11 — Risk Assessment
Agentic-specific risk assessment template — feeds the DPIA, the AI Act Art. 9 risk system and the ISO 42001 clause 6.
acf://fiche/ACF-12MarkdownFR + ENACF-12 — Agent Mandate
Written mandate that defines an agent’s perimeter, thresholds, DDAO and review cadence — mandatory above N1.
acf://fiche/ACF-13MarkdownFR + ENACF-13 — Retention Policy
Retention rules for decision logs, inputs, outputs and rationale, aligned with legal retention periods.
acf://fiche/ACF-14MarkdownFR + ENACF-14 — Human-takeover Drill
Drill protocol for kill switch tests — frequency by criticality, scoring grid, post-drill remediation.
acf://fiche/ACF-15MarkdownFR + ENACF-15 — Controls Calibration
Annual recalibration of controls against P4 — verifies controls still match real autonomy and risk.
acf://fiche/ACF-16MarkdownFR + ENACF-16 — Doctrine Update
Process for updating the doctrine — versioning, hash refresh, archive URL bump, downstream notification.
Frontmatter structure
Each card starts with a YAML block giving the code, the slug, the title in the served locale, the canonical English title, the associated maturity dimension, and the cross-references (principles, regulator articles, related cards).
---
code: "ACF-07"
slug: "kill-switch"
title: "Kill Switch & reprise humaine"
title_en: "Kill Switch & human takeover"
order: 7
maturity_dimension: "D3"
related_principles: ["P3"]
related_articles: ["ai-act/14", "iso-42001/8"]
related_fiches: ["ACF-09", "ACF-14"]
keywords: ["kill switch", "reprise humaine", "AI Act 14"]
version: "1.0"
pdf_url: "/toolkit/ACF-07_kill-switch.pdf"
---
# Kill Switch & reprise humaine
…Fetching a card
A resources/read call against the card URI. The actually-served locale is exposed in a served_locale header prepended to the response — that is how a client detects a fallback if a locale does not exist for a given card (which does not happen in V1.0 but is provisioned for future locales es, de, pt, etc.).
// Read ACF-12 — Agent Mandate, in French
const { contents } = await client.readResource({
uri: "acf://fiche/ACF-12",
});
console.log(contents[0].mimeType); // "text/markdown"
console.log(contents[0].text);
// ---
// served_locale: fr
// is_fallback: false
// ---
// ---
// code: "ACF-12"
// title: "Mandat d'Agent"
// ...
// ---
// # Mandat d'Agent
// ...
// Force English locale via env var (the client picks)
const transport = new StdioClientTransport({
command: "npx",
args: ["-y", "acf-mcp@latest"],
env: { ACF_MCP_LOCALE: "en" },
});