Requires structured context. This model assumes that context fragments have passed quarantine and structural validation. 2. Requires deterministic validators. Admissibility checks must not depend on p

The gap

Consensus across the literature

Supporting evidence — 3 representative gaps

• AIKernel Phase-1 Paper 01: ROM Format and Knowledge Snapshot Model (2026) · doi

  This model has several limitations. First, ROM‑level equivalence is not full semantic equivalence. It is equivalence under a declared canonical‑ ization contract. Natural‑language meaning remains broader than any deterministic canonical form. Second, canonicalization intentionally discards non‑semantic representation entropy. Prompt behaviors that depend on microscopic whitespace or formatting perturbations are not preserved. This is intentional: AIKernel treats such behaviors as unstable prompt manipulation rather than governable architecture. Third, the security model depends on correct implementation of canonicalization, hashing, signature val‑ idation, relation resolution, and trust‑store management. Bugs in those components can undermine the governance boundary. Fourth, bounded topology may reject knowledge graphs that are useful but too large or too dynamic. This trade‑off is deliberate. AIKernel prioritizes deterministic governance over unbounded context expansion. 11. Relationship to Other Phase‑1 Papers Paper 01 provides the knowledge substrate for the rest of Phase‑1. • Paper 02 governs the storage and transport layer that persists and retrieves ROM documents. • Paper 03 uses trusted knowledge snapshots as preconditions for admissibility decisions. • Paper 04 uses stable root goals and governed context as inputs to trajectory monitoring. • Papers 05 and 06 rely on ROM‑derived contracts during execution and delegation. 7 • Paper 07 validates the model through AIKernel.NET implementation. • Paper 08 integrates the Phase‑1 architecture as a unified AIOS governance model.

  Keywords: model equivalence aikernel governance knowledge phase semantic canonical deterministic canonicalization prompt behaviors architecture implementation context
• AIKernel Phase-1 Paper 02: VFS Architecture and Semantic Storage Model (2026) · doi

  This architecture has several limitations. 1. No independent distributed‑consistency guarantee. VFS defines semantic storage boundaries. It does not, by itself, solve distributed transactions, object‑store consistency, or network partition be‑ havior. 2. Capability granularity and access‑control boundary. The initial VFS model intentionally exposes coarse‑grained capabilities such as read, write, delete, navigate, and query. Fine‑grained authorization, such as allowing writes only under a specific directory or only under a given user attribute, belongs to higher‑level policy evaluation. In this sense, ABAC and XACML‑style policy systems are treated as PDP/PEP‑layer mechanisms, while VFS provides truthful session capabilities and semantic storage facts consumed by those policies. 3. Provider honesty requirement. The model assumes providers honestly expose their capabili‑ ties. Provider identity contracts, signed manifests, testing, and attestation are needed for stronger assurance. 4. Semantic path design. The model depends on disciplined path and namespace design. Poorly de‑ signed namespaces can still produce confusing governance boundaries. 11. Relationship to Other Phase‑1 Papers This paper defines the physical and semantic storage boundary for AIKernel’s knowledge and data layer. 6 • Paper 01: ROM Format and Knowledge Snapshot Model defines the governed knowledge units stored and retrieved through VFS. • Paper 03: Pre‑Inference Admissibility Governance evaluates whether proposed storage operations are admissible before execution. • Paper 04: Trajectory Governance Model assumes storage operations are already bounded by VFS and governance policies. • Paper 05 / Paper 07: Execution and Implementation use VFS abstractions for execution state persis‑ tence, conversation snapshots, and replay archives.

  Keywords: storage model semantic governance defines knowledge execution distributed consistency boundaries boundary grained capabilities policy layer
• AIKernel Phase-1 Paper 03: Pre-Inference Admissibility Governance (2026) · doi

  1. Requires structured context. This model assumes that context fragments have passed quarantine and structural validation. 2. Requires deterministic validators. Admissibility checks must not depend on probabilistic LLM calls. They must be implemented as deterministic code, policy rules, schemas, or versioned heuristics. 3. Task extraction is not omniscient. Task profiles are governance evidence, not ground truth. If a profile cannot be derived deterministically, the extractor must return Unknown and the pipeline must fail closed. 4. Does not govern trajectories. This paper determines whether inference may begin. Runtime convergence, semantic drift, tool- candidate risk, and post-generation control belong to Trajectory Governance. 5. Does not implement full policy algebra. ABAC or XACML-style policy evaluation may inform the PDP layer, but this paper defines the admission boundary and evidence model, not a complete enterprise authorization language. 13. Relationship to Other Phase-1 Papers • Paper 01 provides governed ROM knowledge and snapshot identity used as trusted context input. • Paper 02 provides storage capability facts and semantic storage boundaries used by capability admission. • Paper 04 monitors semantic trajectories after a request has been admitted. • Paper 05 and later papers consume admission decisions as part of the AIKernel execution pipeline.

  Keywords: must context policy semantic admission requires model deterministic task governance evidence pipeline trajectories papers provides