Terms defined in the Gemara Lexicon — including assessment, assessment requirement, catalog, control, evaluation, enforcement, guidance, objective, policy, and risk — are used throughout this project with their canonical Gemara definitions. Terms related to governance maturity — including evidence, audit, and policy enforcement — align with the Automated Governance Maturity Model.

This glossary covers terms specific to ComplyTime.

Domain Terms#

TermDefinition
Authority documentA source standard, regulation, or organizational policy that defines compliance requirements (e.g., NIST 800-53, CIS Benchmarks, PCI-DSS).
Effective policyThe resolved output of policy composition — all imports flattened, inheritance applied, overrides resolved. The concrete set of requirements an organization is assessed against.
EvidenceRaw proof that a requirement is met or not — configuration scan output, API responses, attestation documents, logs. The underlying data that supports a finding. See Evidence problem doc.
Requirement fidelityThe degree to which a machine-evaluable requirement faithfully represents the intent of its source authority document. See Requirement Fidelity problem doc.
Trust chainThe end-to-end provenance linking an authority document to a requirement to a check to evidence to a finding. See architecture.

Implementation Terms#

TermDefinition
ComplyPackUniform OCI distribution envelope for packaged evaluation logic. Content is opaque to the runtime; only the evaluator understands it. See ComplyPack Phase 0 plan and complypack repo.
ComplyPack IDReverse-domain identifier (e.g., io.complytime.opa.cis-k8s) that uniquely identifies a ComplyPack.
Evaluator IDIdentifier (e.g., opa) that routes a ComplyPack to the correct provider.
#EvaluationLogMerged assessment output produced from one or more #AssessmentLog entries. The universal output contract of a scan.
#AssessmentLogOutput of a single evaluator’s assessment. Contains results for the controls/requirements it assessed.
GemaraSchema framework for compliance content. CUE-based. See gemara.openssf.org.
Native providerA gRPC binary that handles data collection and evaluation. Runs with host privileges. See complytime-providers.
OCI layoutOn-disk representation of OCI artifacts (per the OCI Image Layout Specification). Used for caching and transport.
ProviderAn execution unit that performs data collection and/or evaluation. Discovered by filesystem convention. See ADR-0004.
Two-stream modelArchitectural separation between compliance content (what must be true) and assessment logic (how to verify it). Independent lifecycles, independent authorship. See ADR-0005.