18 lines
1.6 KiB
Markdown
18 lines
1.6 KiB
Markdown
|
# InfoTechCanon Observability Model concept boundary review — 2026-09-20
|
||
|
|
|
||
|
|
Authority: INFO-WP-0027-T02, the declaration round that gave this artifact an
|
||
|
|
`owned_concepts` list. Resolutions cite the kernel map concept-owner table where
|
||
|
|
it assigns an owner, and are decided in this review where it does not. No concept
|
||
|
|
is renamed, moved or removed.
|
||
|
|
|
||
|
|
| Concept | Owner | Resolution | Decided by |
|
||
|
|
| --- | --- | --- | --- |
|
||
|
|
| `Alert` | model/observability | Assigned by the kernel map concept-owner table. | kernel map |
|
||
|
|
| `Investigation` | model/security | Security owns Investigation as part of response. The Observability sense is analysis activity over telemetry and imports. | this review |
|
||
|
|
| `Profile` | undecided | Unresolved and deliberately undeclared by Core. Three senses exist: the canon profile artifact (Core prose), the identity Profile owned under accepted CUST-ADR-006, and the Observability runtime performance profile already disambiguated in the identity boundary review. The kernel map assigns Profile to Core, which contradicts the accepted identity ownership. Resolving it needs a decision, not a declaration. | kernel map |
|
||
|
|
| `Summary` | model/information-space | Information Space owns Summary as a derived knowledge artifact. The Observability sense is a metric aggregation and is a distinct qualified concept; disambiguation rather than transfer. | this review |
|
||
|
|
|
||
|
|
Concepts this artifact declares are listed in its frontmatter. An overlap recorded
|
||
|
|
here means another artifact defines the same name; where the owner is another
|
||
|
|
artifact, this one imports the definition rather than restating it.
|