info-tech-canon/spec/views_kernel-overview.md

Kernel Overview

First-Generation Kernel

The current InfoTechCanon kernel is composed of:

Kernel:
  InfoTechCanonCore
  InfoTechCanonKernelMap

Models:
  InfoTechCanonInformationSpaceModel
  InfoTechCanonLandscapeModel
  InfoTechCanonOrganizationModel
  InfoTechCanonGovernanceModel
  InfoTechCanonTaskModel
  InfoTechCanonAccessControlModel
  InfoTechCanonSecurityModel
  InfoTechCanonDataModel
  InfoTechCanonDevSecOpsModel
  InfoTechCanonNetworkModel
  InfoTechCanonObservabilityModel

Standards:
  InfoTechCanonTaggingStandard
  InfoTechCanonCaringAccessGovernanceStandard

---

Compact Mental Model

Core
  how the canon works

Information Space
  how canon knowledge is stored, linked, retrieved, and reused

Landscape
  what exists

Organization
  who acts

Governance
  how action is directed, constrained, reviewed, and evidenced

Task
  what work exists and how it progresses

Tagging
  how entities are lightly classified

Access Control
  who/what may do which action on which resource under which conditions

CARING
  how access governance is analyzed orthogonally across lifecycle, planes, scope, exposure, and effective access

Security
  what threatens, weakens, exposes, detects, mitigates, and responds

Data
  what data means, how it is structured, classified, traced, and contracted

DevSecOps
  how source changes become artifacts, releases, deployments, and evidence

Network
  how communication, reachability, addressing, routing, policy, and exposure work

Observability
  how runtime reality becomes signals, evidence, alerts, health, and feedback

---

Primary Kernel Rule

Generic mechanisms belong in Core.
Domain meaning belongs in Models.
Named analytical/design frameworks belong in Standards.
Concrete implementation constraints belong in Profiles.

---

CARING Position

CARING is a specialized access-governance standard. It should live under:

standards/caring/InfoTechCanonCaringAccessGovernanceStandard.md

It should import from:

Core
Organization
Governance
Access Control
Security
Data
DevSecOps
Network
Observability
Task
Tagging

It should not be flattened into Access Control because it owns a distinctive orthogonal descriptor model.