Operations-domain profile for DevSecOps / AIOps / AI4IT operational intelligence.

• What this is
• Repository structure
• Ownership boundaries
• Status
• Documentation
• Validation
• Contributing
• Security
• License

This repository defines the operations-domain specialization for DevSecOps / AIOps / AI4IT operational intelligence, covering:

• AI4IT topic ladder and maturity model
• Ops entity extraction schemas and mapping DSL
• Story grouping, explainability, and feedback loops
• Operational measurement plane
• External seed ontology imports relevant to the operations-domain profile (currently IBM ITOPS)
• Mapping layers from external ontologies into the operations-domain profile
• Evidence-oriented operational graph projections scoped to this profile
• GitHub footprint alignment against workspace topology, ontology scaffolding, website surface taxonomy, operations integration planes, and institutional account hierarchy
• operational exhaust fusion across CI/CD, runtime, policy/evidence, market/execution, and trader-agent lanes

This repository does not own canonical platform storage standards, canonical wire contracts, or the sole canonical platform ontology / broader knowledge semantics.

global-devsecops-intelligence/
├── docs/
│   ├── adr/                    # Architecture decision records
│   ├── architecture/           # Architecture and design notes
│   ├── devops/                 # DevOps process documentation
│   └── vision/                 # Vision and capability statements
├── examples/                   # Example and generated operational profile instances
├── mappings/                   # Ontology mapping ledgers
├── open-ai4it-spec/            # Open AI4IT contracts, schemas, and modules
│   ├── contracts/
│   │   ├── schemas/            # JSON Schema contracts
│   │   └── topics/             # Topic taxonomy
│   ├── docs/glossary/          # Terminology glossary
│   └── modules/openentitymap/  # Mapping DSL schema
├── profiles/                   # Machine-readable domain profiles
├── schemas/                    # Generated-projection schema contracts
├── source_inputs/              # Pinned upstream/manual source extracts for deterministic generators
├── tests/                      # Profile smoke checks and pytest wrappers
├── third_party/
│   └── ibm-itops/              # IBM ITOPS external seed import (metadata + curated excerpt)
├── tools/                      # Local validators and generators
├── CHANGELOG.md
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE
├── MANIFEST.txt
├── Makefile
├── README.md
└── SECURITY.md

Institutional digital-twin semantics may appear here only insofar as they are needed to support the operations-domain profile. Where a concept has both a platform-wide canonical meaning and an operations-domain specialization, the canonical meaning remains upstream and this repository maintains only the specialization, binding, mapping, or projection.

Dependency direction:

platform standards → knowledge / ontology standards → global-devsecops-intelligence → runtime implementations

See docs/architecture/github-footprint-itops-alignment.md and docs/architecture/institutional-account-hierarchy-itops.md for the integration model.

For a guided tour of the documentation tree, see docs/README.md.

Run all local validators:

make validate

The validation target currently covers:

• service-desk metrics examples
• model-fabric release-readiness scorecards
• generated GitHub-footprint projection freshness
• GitHub-footprint ITOPS profile, generated projection, integration planes, institutional account hierarchy, sample, smoke checks, mapping ledger, source inputs, schema, and IBM GLO profile excerpt

Regenerate the GitHub-footprint projection from pinned source inputs:

python3 tools/generate_github_footprint_itops_projection.py --write

Run all pytest wrappers:

make test

Contributions, issue reports, and discussion are welcome. Please read CONTRIBUTING.md before opening a pull request or issue, and follow the Code of Conduct.

To report a security vulnerability, please follow the process described in SECURITY.md. Do not open a public issue for security matters.

This repository is licensed under the MIT License.

Third-party materials vendored under third_party/ carry their own upstream licenses — see the corresponding LICENSE.* files and UPSTREAM.md files for details.