Core-Lite Admissibility Engine
Status
Canonical source repository: Admissible-Existence/core-lite
Wiki state: watching
Detail status: initial public-safe canonical detail page
Definition
Core-Lite Admissibility Engine is a canonical engine layer for applying admissibility checks, receipts, and transition outcomes in a minimal runtime form.
It connects the formalism graph to executable intake, validation, publication, or transition-gating paths.
Source Boundary
Admissible-Existence defines the formalism or engine boundary. Publisher publishes papers and public exposition. The Admissibility Wiki mirrors, relates, crosswalks, and discovers relationships.
The wiki is not the source authority for this engine.
Scope
Core-Lite Admissibility Engine applies where a repo, organization, or workflow needs a minimal governed path for evaluating transition standing and producing inspectable records.
Purpose
The purpose of Core-Lite Admissibility Engine is to prevent admissibility from remaining only conceptual when a practical execution or publication path needs a deterministic gate, receipt, or validation surface.
Core Constructs
| Construct | Role |
|---|---|
| Intake | Receives proposed artifacts, bundles, or transition requests. |
| Gate | Evaluates whether a transition may proceed, deny, escalate, defer, refuse, or fail closed. |
| Policy reference | Identifies the rule basis for the gate. |
| Evidence packet | Provides data supporting or failing to support standing. |
| Receipt | Records the decision path and enough context for reconstruction. |
| Validator | Checks artifacts, registries, receipts, or state records. |
| Publication path | Makes accepted public-safe state visible when applicable. |
Related Canonical Formalisms
| Related Formalism | Relationship |
|---|---|
| Governance-Centered and Boundary-Centered Admissibility Testing | Supplies admissibility tests used by the engine. |
| Runtime Transition Governance | Applies checks at execution or publication boundary. |
| Transition Table | Classifies engine outcomes and transition posture. |
| Boundary Conditions | Supplies boundary satisfaction checks. |
| State Transition Continuity Model | Supports continuity checks across engine state changes. |
| Decision Continuity | Preserves decision standing across receipts and reruns. |
| Data Continuity | Preserves evidence and data standing across ingestion and publication. |
| Continuity Handoff Formalism | Preserves engine state across handoffs. |
| Triad Governance Model | Supports role-separated governance above engine actions. |
Mathematical Candidates
Status: pending source-confirmed extraction from canonical source or publication artifacts.
Proof Candidates
Status: pending source-confirmed extraction from canonical source or publication artifacts.
Validation Candidates
Status: pending source-confirmed extraction from canonical source or publication artifacts.
Validation candidates should include allow, deny, escalate, stale-state, missing-evidence, failed-publication, and receipt-reconstruction cases when public-safe source artifacts are available.
Publication Artifacts
Status: pending source-confirmed extraction.
Reference Implementations
Status: pending source-confirmed extraction.
External Crosswalk Targets
| External Framework | Relationship |
|---|---|
| GLM | May supply pre-engine declarations of claims, non-claims, scope, and composition. |
| EVIDE | May preserve post-engine evidence for reconstruction and audit. |
These are crosswalk targets only. They do not replace canonical formalism or engine definition.
Open Questions
Which exact Admissible-Existence source file defines Core-Lite Admissibility Engine?
Which engine outcomes are canonical versus explanatory?
Which validators are source-confirmed reference implementations?
Which receipt fields are required for reconstructing engine standing?
Non-Claims
This wiki page does not define, prove, validate, or implement the engine. External framework mappings are crosswalk candidates, not equivalence decisions. A listed relationship does not imply accepted formal equivalence.