Assync Glossary¶
To ensure all agents and human operators interpret the Assync rules with mathematical precision, this glossary centralizes the core terminology used throughout the framework.
Each concept must be defined here exactly once.
Core Terminology¶
Assync¶
The overarching governance framework and protocol that standardizes the initialization, execution, and verification of AI agents working within a repository.
Mission¶
A strictly bounded unit of authorized work assigned to an agent. An agent may not perform repository modifications outside the explicit scope of an active mission.
Governance¶
The set of non-negotiable rules and structural constraints that govern how the repository may be modified. Governance defines authority limits and safety boundaries (e.g., fail-closed design).
Human GO¶
An explicit authorization provided by a human operator required to pass a defined security, architectural, or operational gate. Agents cannot self-authorize a Human GO.
Pre-Flight Check¶
The verifiable 3-tier startup protocol that proves an agent has ingested the necessary context. It consists of the visual boot screen, explicitly cited file paths/revisions, and the active recall self-test.
Evidence¶
Data that can be physically verified by the agent (e.g., git hashes, file existence, test results). Evidence is strictly separated from LLM assumptions and must be classified using the canonical categories defined in .assync/rules.md ยง5: FRESH_EVIDENCE (produced in the current context/uptime), HISTORICAL_EVIDENCE (produced in previous audits or runs), INFERRED, UNVERIFIED, or BLOCKED (defined below).
INFERRED¶
A conclusion derived from available evidence but not directly observed.
UNVERIFIED¶
A claim, state, or assumption that has not yet been validated by sufficient evidence.
BLOCKED¶
A condition where progress cannot continue safely or legitimately because required evidence, authorization, or prerequisites are missing.
Repository Adapter¶
The configuration mapping (usually defined in manifest.yaml) that translates generic Assync requirements into the specific file paths and structures of a target repository. It allows Assync to govern diverse project layouts without renaming files.
Fail-Closed¶
The security principle requiring that an operation must default to a denied or blocked state if authority, context, or evidence is missing, contradictory, or ambiguous.