Understand autonomous systems before discussing automation.
A six-part local learning path through autonomous systems, automated actions, pre-execution control, POM-RX, security, and governance, with blockchain as a complementary research domain.
These modules explain concepts and limits. They do not prove a deployment, action blocking, audit, certification, real-world outcome, or level of mastery.
View the learning pathSix tracks
From the action lifecycle to governed decisions.
Each track contains two lessons, a question with contextual feedback, and at least one guided local activity.
- 01 · 01 · Foundations
Autonomous systems
Distinguish automation, an autonomous system, and an agent, then read the full lifecycle of an action.
Open track - 02 · 02 · Decision
Pre-execution control
Turn intent and context into an explicit decision, then stop when a condition is missing.
Open track - 03 · 03 · Structural receipts
POM-RX
Read the three public receipts and their checks without expanding what they demonstrate.
Open track - 04 · 04 · Threats and identity
Security
Protect secrets, identity, and trusted context, then recognise threats specific to agent actions.
Open track - 05 · 05 · Shared ledger
Blockchain
Understand ledgers, consensus, and network boundaries without confusing recording with truth.
Open track - 06 · 06 · Accountability
Governance
Connect policies, roles, and responsibilities, then document decisions, exceptions, incidents, and reviews.
Open track
Trilingual glossary
Stable vocabulary, with its invariants and limitations.
Each term keeps the same identifier in French, English, and Spanish. Its definition bounds how it is used in this Learning Hub.
Autonomous systemautonomous-system
A system that can select or sequence actions within a defined scope.
Invariants
- • Objectives, rules, and context bound the described scope.
- • The term describes a system capability, not a person.
Avoid
- • Independent intent or consciousness.
- • A safety or quality guarantee.
Meaning boundary
The term does not prove that a system is deployed or that its actions are correct.
Software agentsoftware-agent
A software component that acts using available instructions, tools, and context.
Invariants
- • An agent remains a technical component identified by its scope.
- • Its inputs and outputs must be distinguished from external facts.
Avoid
- • A human identity.
- • Unlimited autonomy.
Meaning boundary
The word agent demonstrates neither legal responsibility nor reliable behavior.
Automated actionautomated-action
An action produced by a rule, software, or workflow without manual intervention at every step.
Invariants
- • The rule or workflow that produces it must be described separately.
- • A declared action must remain distinct from an observed action.
Avoid
- • An action that is necessarily authorized.
- • Correct or irreversible execution.
Meaning boundary
The term does not confirm that the action occurred in the outside world.
Declared intentdeclared-intent
A supplied input that describes a proposed or requested action.
Invariants
- • It must be treated as supplied data.
- • It may be compared with a policy or available context.
Avoid
- • Proof of real intent.
- • Actual use of an authorization.
Meaning boundary
It proves neither the real actor, execution, nor outcome of an action.
Evaluated contextevaluated-context
The set of attributes available when a rule or decision is examined.
Invariants
- • The source, freshness, and quality of attributes must be qualified.
- • Context is a bounded view, not the complete world.
Avoid
- • Automatically true external facts.
- • Trusted chronology.
Meaning boundary
Context is valid only for the data and time explicitly stated.
Control policycontrol-policy
A rule or set of rules used to evaluate a described situation.
Invariants
- • A policy must be distinguished from its effective application.
- • Its inputs, outputs, and exceptions must be explicit.
Avoid
- • Proof that the control is applied.
- • A compliance guarantee.
Meaning boundary
The presence of a policy demonstrates neither enforcement nor decision quality.
Authorization decisionauthorization-decision
A model result such as allow, deny, or unresolved for given inputs.
Invariants
- • The decision must name the inputs and rule used.
- • A decision may remain unresolved when evidence is insufficient.
Avoid
- • Actual use of an authorization.
- • Actual blocking of an action.
Meaning boundary
The result does not demonstrate that an execution system respected it.
Pre-execution controlpre-execution-control
A conceptual step where a described action is evaluated before possible execution.
Invariants
- • The control concerns available inputs and a defined rule.
- • The decision and execution must remain separate in evidence.
Avoid
- • An already connected operational control.
- • Proof that an action was prevented.
Meaning boundary
This concept claims neither a deployed mechanism nor a real effect.
Human validation / reviewhuman-review
Explicit involvement of a person to validate, deny, inspect, decide, or escalate a case.
Invariants
- • The review role, timing, and scope must be stated.
- • A review may conclude that more information or a denial is needed.
Avoid
- • Automatic approval.
- • A quality or accountability guarantee.
Meaning boundary
Review is valid only for its scope and documented trace.
Deny when evidence is insufficientfail-closed
A design principle that prefers not to proceed when required conditions are not established.
Invariants
- • Missing conditions must be explicit.
- • An unresolved result remains distinct from success.
Avoid
- • Proof of real deployment.
- • A guarantee against every risk.
Meaning boundary
The principle does not prove that a concrete system actually blocks an action.
Traceabilitytraceability
The ability to link inputs, decisions, or artifacts according to a declared method.
Invariants
- • Links must state their method and scope.
- • A trace must be distinguished from the event it describes.
Avoid
- • Truth of an external fact.
- • Automatically reliable chronology.
Meaning boundary
Traceability depends on the quality and limits of linked data.
Verifiabilityverifiability
The possibility of inspecting a structure or rule with a defined method.
Invariants
- • The method, inputs, and limits must be visible.
- • Checking a structure differs from checking the outside world.
Avoid
- • Implied authenticity or truth.
- • An independent audit.
Meaning boundary
Verifiability is limited to what the method actually checks.
Supplied receiptsupplied-receipt
A record presented to a verifier as input data.
Invariants
- • The receipt must be described as supplied, not independently observed.
- • Its format and links may be inspected.
Avoid
- • Proof that the event occurred.
- • An authenticated source.
Meaning boundary
A supplied receipt proves neither its provenance, real date, nor effect.
Structural checkstructural-check
Inspection of the form, fields, or links of a supplied artifact.
Invariants
- • The check must state the rules it tests.
- • A structural rejection does not qualify the described fact.
Avoid
- • Validation of the real action.
- • A complete security control.
Meaning boundary
The check is limited to the structural properties it implements.
Content provenancecontent-provenance
A reference to the repository, commit, and version that produced a local lesson.
Invariants
- • It identifies local educational content.
- • It remains separate from external authorities cited by the lesson.
Avoid
- • An official external source.
- • Validation that the content is correct.
Meaning boundary
It proves only the versioned origin of local content.
External sourceexternal-source
A public publication or artifact cited to bound an educational statement.
Invariants
- • The source must have a stable identifier, URL, and verification date.
- • Its cited scope and limits must be adjacent.
Avoid
- • An endorsement of SwissTokint.
- • Proof of local implementation.
Meaning boundary
The citation supports only the explicitly bounded wording.
Evidence boundaryevidence-boundary
An explicit limit between what a source demonstrates and what it does not demonstrate.
Invariants
- • Each claim must remain within the identified scope.
- • Forbidden inferences must be visible.
Avoid
- • Absence of limits.
- • Implicit scope expansion.
Meaning boundary
The boundary must be reviewed when the source, version, or context changes.
POM-RX v0.1pom-rx
A public working specification and tested prototype for structural checks of supplied receipts.
Invariants
- • The version, public commit, and limits must be adjacent.
- • Public scope is limited to the schema, Node/TypeScript verifier, and seven-test suite.
Avoid
- • A production product.
- • Proof of truth, security, or execution blocking.
Meaning boundary
POM-RX v0.1 demonstrates neither authenticity, trusted chronology, nor independent observation.
DAGR candidate conceptdagr
An advanced-research candidate concept presented in the Learning Hub.
Invariants
- • Its candidate status must remain visible.
- • No public specification or public implementation is referenced here.
Avoid
- • A published note.
- • An implementation, standard, product, or operational capability.
Meaning boundary
The term claims no operational capability or public maturity.
Secretsecret
A confidential value used to authenticate, sign, or protect access.
Invariants
- • A secret must not be rendered in the client, logs, or examples.
- • Its rotation and scope are operational decisions.
Avoid
- • A simple label or public identifier.
- • A value that may be shared for testing.
Meaning boundary
The presence of a variable name reveals neither its value nor validity.
Identityidentity
Information used to distinguish a subject in a given system.
Invariants
- • The system and level of evidence must be specified.
- • Identity must be separated from attributes and permissions.
Avoid
- • Certain proof of a real person.
- • Automatic authorization.
Meaning boundary
Its meaning is limited to the described identity mechanism.
Least privilegeleast-privilege
A principle of limiting permissions to the identified need.
Invariants
- • The need and permission scope must be explicit.
- • Permissions must be reviewable.
Avoid
- • A guarantee that abuse is impossible.
- • Proof of compliance.
Meaning boundary
The principle does not prove that all real permissions are minimal.
Threat modelthreat-model
A method for describing assets, actors, attack paths, and possible consequences.
Invariants
- • Assumptions and scope must be written down.
- • A threat model must be reviewed when the system changes.
Avoid
- • An exhaustive list of risks.
- • A security guarantee.
Meaning boundary
It informs analysis without demonstrating that risks are eliminated.
Access controlaccess-control
A mechanism or rule that determines requested access to a resource.
Invariants
- • Subject, resource, action, and context must be distinguished.
- • The decision must be separated from observed enforcement.
Avoid
- • Proof that access is actually prevented.
- • Authentication by itself.
Meaning boundary
The term depends on the precise mechanism that is documented.
Zero Trustzero-trust
An approach that avoids treating a location or network as implicitly trusted.
Invariants
- • Access decisions are tied to resources and context.
- • Verification should be considered continuous and bounded.
Avoid
- • A single product.
- • Complete security.
Meaning boundary
The term describes a reference architecture, not demonstrated compliance.
Shared ledgershared-ledger
A set of records replicated or synchronized according to a network’s rules.
Invariants
- • Network rules determine what is verifiable.
- • The ledger must be distinguished from facts it references.
Avoid
- • Automatic truth about the outside world.
- • A necessity for every problem.
Meaning boundary
A ledger proves only the properties made possible by its rules.
Blockchain networkblockchain-network
A network that applies validation, replication, and consensus rules to a ledger.
Invariants
- • The network, its rules, and its participants must be distinguished.
- • A blockchain is a ledger-system type, not the ledger’s content.
Avoid
- • A legal or economic guarantee.
- • A universal solution.
Meaning boundary
Properties depend on the design and rules of the specific network.
Consensusconsensus
A process through which a network applies its rules to accept or order certain records.
Invariants
- • The mechanism and its assumptions must be named.
- • Network consensus is distinct from the truth of an external fact.
Avoid
- • An absolute guarantee against every error.
- • Proof of legality.
Meaning boundary
The term is limited to the rules and threat model of the relevant network.
Smart contractsmart-contract
A program executed according to a platform’s rules, often called a smart contract.
Invariants
- • Code, network, and inputs must be distinguished from a legal contract.
- • Behavior depends on platform rules and state.
Avoid
- • An automatically valid legal contract.
- • A security or outcome guarantee.
Meaning boundary
The term describes a program and does not qualify its legal validity.
Governancegovernance
The organization of roles, rules, decisions, exceptions, and reviews around a system or activity.
Invariants
- • Roles and responsibilities must be explicitly assigned.
- • Exceptions and incidents must have a review path.
Avoid
- • Certification.
- • Proof that decisions are correct.
Meaning boundary
Described governance does not by itself prove effective application.
Exceptionexception
A case that does not follow the ordinary rule and needs explicit handling.
Invariants
- • The exception must state its reason, scope, and review.
- • It must remain traceable and time-bounded when necessary.
Avoid
- • A silent way to bypass a policy.
- • General authorization.
Meaning boundary
An exception does not automatically change the base rule.
Incidentincident
An event or signal that requires a documented assessment, response, or review.
Invariants
- • Scope, known facts, and actions taken must be separated.
- • The response must avoid disclosing sensitive data.
Avoid
- • Complete proof of cause.
- • A guarantee that an incident will not recur.
Meaning boundary
An incident remains bounded to verified information and the documented process.
Automationautomation
Repeatable execution of an operation under a defined rule or workflow.
Invariants
- • The trigger and rule must be identifiable.
- • The outcome remains distinct from intent.
Avoid
- • Autonomous choice without rules.
- • Evidence of intelligence or safety.
Meaning boundary
The term proves neither deployment, authorization, nor a real outcome.
AI agentai-agent
A software agent whose selections or inferences use an AI method.
Invariants
- • It remains a bounded software component.
- • Its permissions remain separate from its capabilities.
Avoid
- • Every AI system.
- • A person or autonomous authority.
Meaning boundary
The term demonstrates neither reliability, legal accountability, nor operational capability.
Actionaction
An operation requested, authorized, triggered, or observed at a given stage.
Invariants
- • Its status must be stated.
- • A declared action and an observed action remain distinct.
Avoid
- • Intent.
- • Automatic evidence of an outcome.
Meaning boundary
The word alone does not confirm that the operation occurred outside the described system.
Intentintent
A representation of a proposed or requested action.
Invariants
- • It is an input to evaluate.
- • Its source and scope must be stated.
Avoid
- • Authorization.
- • An observed action or outcome.
Meaning boundary
Intent proves neither its real author, execution, nor outcome.
Contextcontext
Attributes available around an intent, rule, or decision.
Invariants
- • Source, date, and freshness must be qualified.
- • Context may be incomplete.
Avoid
- • Exhaustive truth.
- • Implicit permission.
Meaning boundary
Context is valid only for the explicitly documented attributes and time.
Policypolicy
A versioned set of rules and responsibilities for decisions within a scope.
Invariants
- • Owner, version, and change authority must be explicit.
- • Policy remains distinct from its application.
Avoid
- • An informal preference.
- • Evidence of enforcement.
Meaning boundary
An obsolete or incomplete policy may produce an incorrect decision.
Rulerule
A declared condition connecting inputs to a decision or output.
Invariants
- • Inputs, logic, version, and output must be identifiable.
- • A rule belongs to a defined scope.
Avoid
- • A complete policy.
- • Evidence that the rule is applied.
Meaning boundary
A described rule demonstrates neither its quality nor effective enforcement.
Preflightpreflight
The first supplied POM-RX phase, with a declared `allow` or `deny` outcome and assertions.
Invariants
- • It precedes the execution acknowledgement.
- • It remains a supplied receipt.
Avoid
- • An executed action.
- • External truth or demonstrated blocking.
Meaning boundary
Preflight alone confirms neither an external fact nor actual use of the decision.
Authorizationauthorization
An explicit decision permitting an action within a defined scope, duration, and context.
Invariants
- • The decision must be attributed and revocable.
- • It precedes the authorized action.
Avoid
- • General permission.
- • Evidence of execution or outcome.
Meaning boundary
Authorization does not confirm that the action was attempted, executed, or successful.
Allowallow
A decision outcome permitting progress within the evaluated scope.
Invariants
- • Scope and conditions must remain attached.
- • The decision may be revoked.
Avoid
- • Universal authorization.
- • Execution or success.
Meaning boundary
`Allow` does not demonstrate that an execution system respected the decision.
Denydeny
A decision outcome that does not permit progress in the evaluated context.
Invariants
- • The reason and inputs must remain traceable.
- • A missing condition may lead to this outcome.
Avoid
- • A general sanction.
- • Evidence of physical blocking.
Meaning boundary
`Deny` does not confirm that an external mechanism actually prevented the action.
Reviewreview
An outcome requiring explicit examination before any new decision.
Invariants
- • The case remains unauthorized until review concludes.
- • The role and outcome must be documented.
Avoid
- • Approval by default.
- • A simple delay.
Meaning boundary
`Review` is neither `allow` nor completed human validation.
Execution acknowledgementexecution-acknowledgement
The second supplied POM-RX phase, with an `accepted`, `rejected`, or `unresolved` outcome linked to preflight.
Invariants
- • The link to preflight must remain checkable.
- • POM-RX does not perform the action.
Avoid
- • Independent observation.
- • Evidence of success or real execution.
Meaning boundary
The supplied acknowledgement confirms neither authenticity, reliable chronology, nor an external fact.
Observationobservation
Information reported or collected about a state after a proposed action.
Invariants
- • Source, time, and method must be qualified.
- • It remains distinct from intent.
Avoid
- • Automatically reliable truth.
- • Completed reconciliation.
Meaning boundary
A non-independent or unverified observation does not prove the external fact described.
Reconciliationreconciliation
A documented comparison between expected and observed states with a bounded outcome.
Invariants
- • Outcomes may remain `matched`, `mismatched`, or `unresolved`.
- • Unknowns must remain visible.
Avoid
- • Automatic correction.
- • Exhaustive evidence of the outside world.
Meaning boundary
Reconciliation does not exceed the sources, data, and methods compared.
Receiptreceipt
A structured supplied record describing a phase, inputs, and an outcome.
Invariants
- • Schema, version, and links must be identifiable.
- • The receipt remains distinct from the event described.
Avoid
- • Automatic evidence of authenticity.
- • Independent observation.
Meaning boundary
A supplied receipt confirms only the properties of its structure that are actually checked.
Evidence / proofproof
An item supporting a precise claim under an identified source and method.
Invariants
- • Claim, source, method, and limitation must remain adjacent.
- • Evidence strength depends on scope.
Avoid
- • Universal truth.
- • Implicit certification.
Meaning boundary
Evidence does not support claims that its method does not check.
Fingerprintfingerprint
A compact value derived from data using a declared method.
Invariants
- • The method and input bytes must be defined.
- • A change may produce a different fingerprint.
Avoid
- • The author identity.
- • Truth or quality of data.
Meaning boundary
A fingerprint enables technical comparison, not content validation.
Hash linkhash-link
A relation in which an object references the computed fingerprint of a preceding object.
Invariants
- • Method, canonical representation, and order must be stated.
- • The match may be checked structurally.
Avoid
- • Reliable chronology.
- • Evidence of authenticity or execution.
Meaning boundary
The link establishes a relation between supplied objects, not the truth of their statements.
External factexternal-fact
A claim about a person, system, or event outside the supplied objects.
Invariants
- • A suitable independent source must be sought.
- • The fact remains distinct from its representation.
Avoid
- • Data that is true because it is recorded.
- • A conclusion drawn from the receipt alone.
Meaning boundary
Receipt or ledger structure alone does not confirm the external fact.
Distributed ledgerdistributed-ledger
A ledger whose participants replicate or synchronize state under common rules.
Invariants
- • Participants, rules, and trust model must be named.
- • The network remains distinct from data and applications.
Avoid
- • A necessarily public blockchain.
- • A solution required for every use case.
Meaning boundary
The ledger proves neither external truth, universal finality, nor use-case suitability.
Finalityfinality
A protocol-defined property qualifying the stability of an observed state or order.
Invariants
- • Network, rules, and time must be stated.
- • Assumptions vary by protocol.
Avoid
- • Universal irreversibility.
- • Legal validity or external truth.
Meaning boundary
Finality applies only within the documented model and observation context.
Anchoringanchoring
Recording a commitment or fingerprint in a ledger system.
Invariants
- • Network, method, and time must be stated.
- • The fingerprint remains distinct from source data.
Avoid
- • Validation of content truth.
- • Evidence of author identity or permission.
Meaning boundary
Anchoring supports a bounded technical relation, not the truth or legality of data.
Waiver / derogationderogation
An explicitly authorized exception to a rule for a defined scope and duration.
Invariants
- • Authority, reason, scope, duration, and review must be traced.
- • It must be able to expire or be revoked.
Avoid
- • An informal bypass.
- • Retroactive relabelling of an incident.
Meaning boundary
A waiver does not automatically change the general policy.
Local progresslocal-progress
State stored in the browser to help resume an educational path.
Invariants
- • Persistence is local and subject to explicit consent.
- • Erasure and storage failures must be visible.
Avoid
- • A user account.
- • Analytics tracking or qualification.
Meaning boundary
Progress is only a local interaction state.
Lesson completedlesson-completion
A state indicating that the planned local interaction for a lesson was completed.
Invariants
- • The completion condition must be explicit.
- • Completion remains distinct from score and mastery.
Avoid
- • Certification.
- • Operational competence.
Meaning boundary
This state proves only that a local interaction was completed.
NO-GOno-go
A controlled decision not to proceed while required conditions are not met.
Invariants
- • Missing conditions and the decision owner must be explicit.
- • A NO-GO must not be converted into implicit success.
Avoid
- • A personal failure.
- • Automatic deferred authorization.
Meaning boundary
The status applies only to the documented scope and time.
Tested prototypeprototype
An artifact exercised within an explicitly stated test scope.
Invariants
- • Tests, version, and limits must be adjacent.
- • A prototype remains distinct from a mature product.
Avoid
- • General availability.
- • Certification or audit.
Meaning boundary
The term does not exceed the documented test scope.
Test scopetest-scope
The precise set of cases, data, and behaviors examined by a test.
Invariants
- • The number of tests and their subject must be stated.
- • A test result must be limited to its environment and inputs.
Avoid
- • Complete product validation.
- • Proof of deployment.
Meaning boundary
A test scope does not cover cases that were not exercised.
No collection
Reason through a synthetic scenario.
The lab remains in the browser. It asks for no secret, account, or real-world data and produces no attestation.