coulomb/info-tech-canon
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
main
info-tech-canon/spec/views_refactoring-checklist.md

2.7 KiB
Raw Permalink Blame History

Refactoring Checklist

Goal

Move repeated generic mechanisms out of individual seed standards and into InfoTechCanonCore, while keeping domain-specific meaning in each model or standard.

1. Core Mechanisms to Centralize

  • Mapping types
  • Mapping record structure
  • Assimilation process
  • Assimilation workspace structure
  • Profile format
  • Pattern format
  • Validation rule format
  • Conformance levels
  • Lifecycle statuses
  • Artifact statuses
  • Concept statuses
  • Agent brief format
  • Canon Interface Card format
  • Repository layout conventions
  • Machine-readable schema conventions

2. Per-Standard Refactor Checklist

For every model or standard:

  • Declare import of InfoTechCanonCore
  • Declare canonical owner namespace
  • Declare owned concepts
  • Declare imported concepts
  • Remove duplicated generic mapping type definitions
  • Remove duplicated generic assimilation process definitions
  • Keep domain-specific mapping targets
  • Keep domain-specific assimilation candidates
  • Keep domain-specific profiles
  • Keep domain-specific validation rules
  • Keep domain-specific anti-patterns
  • Add or update agent-brief.md
  • Add concept extraction candidates
  • Add profile extraction candidates
  • Add mapping extraction candidates

3. CARING Refactor Checklist

  • Place CARING under standards/caring/
  • Use file name InfoTechCanonCaringAccessGovernanceStandard.md
  • Add namespace itc-caring
  • Add Canon metadata preface
  • Declare imports from Core, Organization, Governance, Access Control, Security, Data, DevSecOps, Network, Observability, Task, and Tagging
  • Declare CARING-owned concepts
  • Preserve CARING canonical role taxonomy
  • Preserve CARING access descriptor model
  • Preserve declared/effective access distinction
  • Preserve derived and induced capability analysis
  • Add CARING benchmark directory
  • Create CARING access descriptor schema
  • Create CARING mapping-to-kernel document
  • Create CARING agent brief

4. First Schemas to Create

  • concept.schema.yaml
  • standard.schema.yaml
  • mapping.schema.yaml
  • profile.schema.yaml
  • assimilation.schema.yaml
  • interface-card.schema.yaml
  • agent-brief.schema.yaml
  • caring-access-descriptor.schema.yaml

5. First Generated Views

  • views/by-standard.md
  • views/by-concept.md
  • views/by-profile.md
  • views/by-mapping-target.md
  • views/dependency-graph.md
  • views/kernel-overview.md

6. First Assimilation Workspaces

  • CARING
  • Kubernetes RBAC
  • ServiceNow CSDM
  • OpenTelemetry
  • DCAT / PROV-O
  • SLSA / in-toto
Reference in New Issue View Git Blame Copy Permalink