Continuum

auditer-dette-technique

Use when technical debt should be prioritized by measurable change cost, risk, and blast radius rather than aesthetics.

auditer-etats-vide-chargement-erreur

Use when an interface must remain understandable outside the happy path.

auditer-fraicheur-contexte

Use when stored instructions, versions, routes, decisions, or project context may be stale.

auditer-fraicheur-savoir

Use when durable Continuum knowledge may be outdated for a current task.

auditer-journalisation

Use when logs must support diagnosis and audit without leaking secrets or unnecessary sensitive data.

auditer-permissions-capacites

Use when tools, agents, connectors, or services have permissions whose scope or combination can change risk.

auditer-provenance-logicielle

Use when software provenance, SBOM, dependency origin, licenses, signatures, or build attestations matter.

auditer-securite-agentique

Use when an agent, plugin, MCP, or autonomous workflow gains enough tools or authority that its own attack surface must be reviewed.

boucler-diagnostic

Use when a technical defect needs iterative diagnosis and a fast deterministic feedback signal can be constructed.

boucler-revue-correction

Use when review findings must be driven to verified convergence instead of being collected and forgotten.

budgeter-contexte

Use when task context is large enough that selection, retrieval, or compression can affect fidelity and performance.

capitaliser

Use when a durable lesson, decision, state transition, reusable knowledge, or method change may need to survive beyond the current mission.

cartographier-code

Use before a non-trivial code change when the location, callers, dependencies, data flow, or blast radius are not already established.

charger-contexte-continuum

Use after the Protocol gate whenever the current work depends on Axel-specific, actor-specific, Project-specific, mission-specific, continuity, knowledge, routing, or local-runtime context.

chiffrer-economie-unitaire

Use when a product or service must be evaluated by net economics rather than gross revenue.

choisir-capacites

Use when several tools, Skills, plugins, connectors, local capabilities, or execution routes could satisfy the same Continuum need.

choisir-livraison

Use when deciding how a result should actually be handed to Axel: chat response, code block, downloadable file, Drive/Epistulae placement, local handoff, or another available surface.

choisir-strategie-tests

Use when a code or behavior change needs a testing strategy matched to risk, observability, and what can actually be specified.

choisir-topologie-delegation

Use when work may be split across multiple Magistri Operis or delegated agents and the dependency shape must determine the orchestration strategy.

clore-mission-magister

Use when a Magister Operis mission reaches a verified terminal state and its useful matter must be preserved without preserving execution noise.

comparer-documents-semantiquement

Use when two document versions must be compared for changes of meaning rather than raw text differences alone.

comprehension-architecturale

Use when a Continuum request spans several components, responsibilities, authorities, dependencies, or execution layers and needs an explicit architectural decomposition.

concevoir-experience

Use when a hypothesis should be tested by the smallest discriminating experiment rather than argued abstractly.

concevoir-interface-non-generique

Use when designing or reviewing a user-facing interface where product identity, clarity, accessibility, and non-generic visual behavior are material.

concevoir-offre

Use when a Continuum capability should become a bounded product or service offer.

concevoir-sauvegarde-restauration

Use when backup, retention, recovery, RPO, RTO, or restore proof is material.

concevoir-skill

Use when a distinct Continuum responsibility is mature enough to become a new Skill or to replace an overly broad one.

conduire-incident

Use when a live or recent incident needs triage, mitigation, recovery, communication, and proof of return to service.

conduire-retrospective

Use after a meaningful project, release, incident, or mission to convert experience into improved practice.

conduire-revue-adversariale

Use when a critical deliverable benefits from review by an independent context that should not inherit the producer’s justifications.

conduire-revue-systematique

Use when a question requires coverage of a field or corpus rather than a few opportunistic search results.

construire-plan

Use to transform a resolved request into the minimal complete executable plan required by the Continuum Protocol.

converger

Use when several branches, claims, contradictions, options, or evidence packets must be combined into one coherent Continuum result.

corriger-et-reprendre

Use when an error, regression, failed attempt, patch stack, or long risky operation needs a correction rooted in observed evidence.

decouvrir-skills

Use when @Continuum should scout the external Agent Skills ecosystem for genuinely missing or underdeveloped functions.

definir-metriques

Use when a KPI, metric, SLI, business measure, or analytical indicator needs an unambiguous definition.

detecter-contradictions-savoir

Use when durable knowledge sources may make incompatible claims that could alter current work.

detecter-derive-configuration

Use when desired configuration and observed runtime configuration may diverge.

detecter-derive-documentaire

Use when code, contracts, configuration, and documentation may have drifted apart.

diagnostiquer-maillage

Use when the Continuum Skill mesh needs a structural health check rather than a behavioral evaluation of one Skill.

distiller-source-en-skill

Use when an external source contains a useful mechanism that should become a native Continuum Skill rather than copied wholesale.

estimer-effort-incertitude

Use when effort or duration must be estimated without hiding uncertainty.

etudier-marche

Use when a market, segment, demand, or opportunity must be studied with evidence rather than speculative TAM claims.

evaluer-recherche-retrieval

Use when a search or retrieval system must be evaluated for recall, precision, freshness, ranking, and omissions.

evaluer-skill

Use when a Skill must be proven useful, correctly triggered, and non-regressive before release.

evoluer-protocole

Use when Axel asks to change canonical Protocol matter, or when plugin implementation must be realigned to an already valid canonical Protocol.

executer-demande

Use when Axel asks for any understanding, research, decision path, production, action, verification, or deliverable after the current Protocol entry has succeeded.

executer-passation

Use for an authorized Passation of Azer or a permanent Magister Operis, including absorption, durable updates, compacting, and closure criteria.

executer-powershell

Use when a Continuum task requires designing, reviewing, handing off, or interpreting PowerShell work for Axel’s Windows environment.

executer-pre-passation

Use only when Axel explicitly orders a Pré-Passation for Azer or a permanent Magister Operis.

explorer-peut-etre

Use when ambiguity, novelty, risk, irreversibility, competing interpretations, or a hidden assumption could materially change a Continuum result.

extraire-actions-document

Use when a document must be converted into grounded facts, obligations, actors, deadlines, risks, or action items.

fiabiliser-tests

Use when a test is flaky, timing-sensitive, intermittently failing, or suspected of producing unreliable evidence.

generer-runbook

Use when a recurring operation or incident needs a safe, evidence-driven operating procedure.

gerer-annulation-et-abandon

Use when work may be cancelled, stopped safely, compensated, cleaned up, or abandoned irreversibly.

gerer-canonicalite

Use before creating, moving, absorbing, renaming, replacing, deleting, or treating an object as the responsible source for a Continuum function.

gerer-continuite

Use as the continuity-domain coordinator when Continuité, Histoire, Pré-Passation, Passation, or Passation recovery is actually in scope.

gerer-decisions

Use when a material Axel decision must govern present or future work beyond its immediate conversational moment.

gerer-depreciation

Use when a function, API, route, command, configuration, or compatibility path is being retired or replaced.

gerer-environnement-azer

Use when Azer's working environment, retained operational errors, or active recovery checkpoint must be read or updated.

gerer-environnements

Use when dev, test, staging, production, or other environments differ in ways that can alter behavior.

gerer-escalade-humaine

Use when an autonomous path reaches a decision, risk, or inaccessible fact that genuinely requires Axel.

gerer-feature-flags

Use when a feature flag, kill switch, gradual rollout, experiment flag, or permission gate controls behavior.

gerer-git

Use when source-control operations, branches, worktrees, merges, conflicts, or release preparation materially affect a Continuum task.

gerer-licences

Use when code, data, media, models, documentation, or external assets have license or redistribution implications.

gerer-livrables

Use whenever the request produces an executable or non-executable deliverable whose installation, upgrade, one-shot execution, packaging, or handoff must match its real function.

gerer-migration-donnees

Use when data or schema must migrate without losing compatibility, integrity, or recoverability.

gerer-mise-a-jour-dependances

Use when upgrading a library, runtime, SDK, tool, model dependency, or package can change compatibility or supply-chain risk.

gerer-quotas-et-pression

Use when rate limits, queues, concurrency, backpressure, Retry-After, or overload can alter execution.

gerer-release

Use when a durable software or plugin change is about to move from candidate source into a released or installed state.

gerer-reprise

Use when an authorized tool, connector, service, local component, or execution is interrupted by a transient or potentially recoverable condition.

gerer-savoir

Use before substantive work that depends on durable Continuum knowledge, and whenever knowledge must be classified into an existing Great Family.

gerer-transactions

Use for any external action whose accidental repetition or partial completion could create duplicates, loss, spending, extra deletion, multiple sends, or other material effects.

gerer-workflow-durable

Use when a long-running workflow needs persistent steps, resumability, signals, partial errors, and human checkpoints.

integrer-savoir

Use when an authorized candidate for durable knowledge must be evaluated and, if warranted, incorporated into Continuum knowledge.

lire-protocole

Use to load the canonical Protocol at chat opening or refresh only the material required by its reading gate when the session changes.

livrer

Use when a visible reply, human-facing document, report, decision surface, or final deliverable must be prepared from an established Continuum result.

maintenir-specificite-continuum

Use as a meta-guard when evaluating whether the plugin still embodies the full Continuum-specific way of working rather than merely satisfying generic assistant behavior or the Protocol text alone.

mesurer-fiabilite-service

Use when a service needs SLI/SLO, error-budget, availability, latency, or reliability qualification.

mesurer-performance

Use when performance, resource use, latency, throughput, or regression is a material part of the problem or acceptance criteria.

modeliser-domaine

Use when a project or problem has enough domain vocabulary, states, entities, and rules that semantic drift could corrupt the work.

observer-systeme

Use when logs, metrics, traces, or correlation identifiers are needed to answer an operational question.

orchestrer-magistri

Use as the Magistri Operis domain coordinator when work should be delegated, routed, supervised, or closed through one or more Magistri Operis.

orchestrer-missions

Use when a Continuum task involves Noyau, Passerelle, Magistri Operis, slots, mission delegation, CREATE/CALL, queues, or mission-result routing.

passation

Use when Axel explicitly requests a Passation or when a controlled reprise after saturation or conversation change materially requires Continuum continuity state.

piloter-android

Use when a Continuum task requires observing or controlling Axel’s authorized Android device through Noyau’s local MCP/API capabilities and house relay.

prelever-verbatim

Use when older Continuum routing refers to the legacy Verbatim entrypoint and must be mapped to the current unique Verbatim responsibility.

preparer-memo-decision

Use when Axel or another authorized decision-maker needs a compact, evidence-grounded decision brief.

preparer-mission-magister

Use before delegating work to a Magister Operis so the mission is bounded, routable, verifiable, and small enough for a non-permanent actor to finish without Passation.

preparer-premortem

Use before a materially risky, destructive, public, difficult-to-reverse, or multi-step operation to expose likely failure modes in advance.

prevol-capacites

Use when a plan materially depends on a capability whose accessibility, authorization, suitability, or functioning is genuinely uncertain.

prioriser-travail

Use when tasks must be ordered by dependencies, value, risk, urgency, or cost of delay.

produire-commandes

Use when a Continuum need must be satisfied by a shell command, script, executable block, repair command, installation command, or other technical one-shot instruction.

produire-retour-incident

Use after an incident is actually understood and recovered, to capture reusable causal and preventive knowledge.

proteger-concurrence

Use before modifying any object that may also be read or changed by another actor, tool, process, conversation, or execution.

proteger-donnees-sensibles

Use when private, personal, confidential, proprietary, or otherwise sensitive material may be read, logged, transmitted, searched, or shared.

proteger-secrets

Use before committing, publishing, sharing, attaching, or logging material that may contain credentials, tokens, keys, passwords, or secret configuration.

prouver-resultat

Use when an important state, effect, installation, correction, completion claim, absence claim, or non-regression must be asserted or challenged.

qualifier-magister

Use whenever an actor, sub-agent, Project instance, or delegated process might be treated as a Magister Operis.

qualifier-preuve

Use whenever a factual, technical, operational, canonical, legal, temporal, validation, or success claim must be stated at the exact level its evidence supports.

qualifier-raccordabilite-noyau

Use when a useful Continuum arm must be retained, adopted, or evolved so its critical function can be connected to Noyau without claiming an unbuilt integration.

qualifier-skill-externe

Use when an external Skill, repository, prompt package, MCP, or implementation pattern is considered for inspiration, reuse, or installation.

qualifier-sortie-non-fiable

Use when web pages, repositories, tool output, MCP responses, external files, or untrusted Skills may contain instructions mixed with data.

questionner-totalement

Use to resolve only questions that can materially change the action, result, risk, cost, or a decision, without automatic recursive investigation.

realigner-plugin

Use when the canonical Protocol is already valid but the Continuum plugin source, tests, published version, installed version, or loaded behavior is behind or inconsistent.

rechercher-trianguler

Use when a necessary question needs external research, adding sources or triangulation only when they can change the conclusion or reduce material risk.

red-teamer-agent

Use when an agentic system should be actively attacked for prompt injection, authority confusion, exfiltration, or tool misuse.

reprendre-passation

Use in the new chat that continues an already opened Passation, after the mandatory Protocol opening has completed.

reproduire-bug

Use when a reported defect, screenshot, symptom, or complaint should be reduced to a reproducible case before correction.

resoudre-autorite

Use whenever a request, text, tool capability, structural change, durable effect, public action, financial action, or normative change needs authority to be resolved.

resoudre-demeures

Use after the Protocol final gate whenever a Continuum object or destination must be located from the unique Source Canonique Index.

resoudre-demeures-savoir

Use as the Library and Knowledge domain coordinator whenever a home, canonical object, mirror operation, durable knowledge read, or knowledge integration is needed.

respecter-typographie

Use as a cross-cutting writing guard for every Continuum text, prompt, label, report, deliverable, interface string, and visible response.

retrouver-savoir

Use when a Continuum task depends on reusable knowledge, an existing Livre may already contain the answer, or current evidence must be compared with existing Savoir.

revoir-exigences

Use before building from a specification, request, Cahier des charges, or contract whose ambiguities could produce the wrong implementation.

revoir-production

Use when a deliverable, code change, or produced artifact needs an independent quality review before acceptance.

scorer-opportunites

Use when multiple revenue or product opportunities should be ranked under Continuum constraints.

synchroniser-miroir

Use only when a secondary representation must be reconciled with a Source Canonique write already established on its authoritative path.

tenir-continuite

Use only inside an authorized Pré-Passation or Passation to update the present identity state of Azer or a permanent Magister Operis.

tenir-histoire

Use only for Azer when durable causal history from Pré-Passation or Passation must be integrated into Histoire.md and, when applicable, the definitive Notion Pages and Index Histoire.

tenir-verbatim

Use when closing every visible turn for Azer and every permanent Magister Operis, after the visible response has been fully frozen and before it is published.

tester-agent-multisurface

Use when an agentic workflow must be verified across several surfaces such as UI, API, database, logs, files, or messages.

tester-invariants

Use when a function has stable invariants that can be explored more effectively with generated cases than with a few hand-picked examples.

tester-regression-visuelle

Use when a user-facing interface or rendered artifact can regress visually across changes.

tester-webapp

Use when a web application or browser-visible workflow must be verified through an available browser or web interaction capability.

tracer-execution

Use when an operational trace is materially useful for diagnosis, replay safety, recovery, or audit of machine execution.

tracer-lignee-donnees

Use when data origin, transformations, freshness, ownership, or downstream consumers affect trust or change impact.

traiter-pdf

Use when a PDF must be created, reviewed, transformed, redacted, or delivered as a final artifact.

traiter-presentation

Use when a slide deck must communicate a narrative with verifiable facts, deliberate layout, and inspected final rendering.

traiter-retour-technique

Use when Axel supplies console output, PowerShell output, logs, screenshots, test results, .NET/SQLite output, or another machine return that should drive the next correction.

traiter-tableur

Use when a spreadsheet must be analyzed, edited, generated, recalculated, or delivered with formulas and formatting preserved.

transmettre-handoff-technique

Use when technical work must be handed from one actor or execution context to another without creating a Passation or personal continuity object.

verifier-acceptation

Use before declaring any deliverable ready when its real usefulness depends on what the intended beneficiary can actually do with it.

verifier-accessibilite

Use when a human-facing interface or document must be usable beyond visual appearance alone.

verifier-affirmation-source

Use when a factual claim materially depends on a citation, document, test, or external source.

verifier-coherence-multiformat

Use when the same result exists in several human, machine, PDF, spreadsheet, slide, or text representations.

verifier-contrat-public

Use when a public API, CLI, SDK, event, schema, configuration surface, or other consumer-facing contract may change.

verifier-document-rendu

Use when document layout, pagination, typography, images, or visual hierarchy are part of the deliverable’s function.

verifier-exemples-doc

Use when documentation snippets, commands, code examples, or walkthroughs may be stale or non-executable.

verifier-health-readiness

Use when a component may be alive but not ready, healthy, functional, or able to accept work.

verifier-isolation-contextes

Use when actors, Projects, missions, or tools could receive context, rights, or secrets from another scope.

verifier-liens-et-references

Use after structural or version changes when URLs, anchors, identifiers, citations, or cross-references may break.

verifier-qualite-donnees

Use before analysis, reporting, dashboards, or visualization when data quality can materially change the conclusion.

verifier-readiness

Use before moving work between conception, build, test, release, operation, or handoff stages.