Declare concepts and review boundaries for the silent artifacts (T02)
Twelve of the thirteen artifacts that declared nothing now declare what they define, together with the map-assigned concepts the Organization Model was missing and the Landscape seed concepts the extractor cannot see because they are listed rather than defined in prose. The ownership index grows from 164 entries to 750, undeclared prose definitions fall from 637 to 57, and there are no ownership conflicts. The 57 that remain are overlaps this round assigned to another owner: imports, each recorded in a boundary review. The kernel map declares nothing, deliberately, because it assigns concepts to owners rather than defining them. It is now the only silent artifact and the suite asserts that, so an artifact added without declarations fails. itc-org:Authority is declared, with Actor, Ownership, Membership, Role, Responsibility and Accountability, which SecurityCanon and the identity model already treat as organization-owned. The regression test that previously asserted the blind spot now asserts that the kernel map's assignment and the declaration agree. Profile is deliberately left undeclared. The kernel map assigns it to Core, the identity model owns it under accepted CUST-ADR-006, and Observability defines a runtime performance profile. Three senses need a decision, not a declaration, so it is recorded as open rather than forced. Eleven boundary reviews are added beside the artifacts they describe, in the shape the identity model has used since INFO-WP-0021. The largest finding is that Core and the Information Space model restate eight provenance concepts in nearly identical words; Core owns them and Information Space imports. Label, Drift, Summary and Attribute are resolved by disambiguation rather than transfer. make check passes with 50 tests, clean validation, no stale generated assets. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 3588@bnt-lap001 Assistant-Session: 24b80f66-e5a7-4e61-99fe-2d422e6d17da
This commit is contained in:
parent
164993d4e2
commit
f7b17b83f2
46 changed files with 5665 additions and 39 deletions
|
|
@ -1,3 +1,53 @@
|
|||
---
|
||||
owned_concepts:
|
||||
- AccessCertification
|
||||
- AccessControlEntity
|
||||
- AccessFinding
|
||||
- AccessRemediation
|
||||
- AccessReview
|
||||
- AccessRole
|
||||
- AccessSession
|
||||
- AgentAccess
|
||||
- AuthenticatedSubject
|
||||
- AuthenticationStrengthReference
|
||||
- AuthorizationDecision
|
||||
- AuthorizationRequest
|
||||
- BreakGlassAccess
|
||||
- Condition
|
||||
- CredentialReference
|
||||
- DecisionReason
|
||||
- DelegatedAccess
|
||||
- Denial
|
||||
- Entitlement
|
||||
- EvaluationContext
|
||||
- ExcessAccess
|
||||
- Grant
|
||||
- IdentityReference
|
||||
- JustInTimeAccess
|
||||
- Operation
|
||||
- OrphanedAccess
|
||||
- Permission
|
||||
- PolicyAdministrationPoint
|
||||
- PolicyBinding
|
||||
- PolicyDecisionPoint
|
||||
- PolicyEnforcementPoint
|
||||
- PolicyInformationPoint
|
||||
- PolicyRetrievalPoint
|
||||
- Principal
|
||||
- Privilege
|
||||
- ProtectedResource
|
||||
- RelationshipTuple
|
||||
- Resource
|
||||
- ResourceAction
|
||||
- ResourceScope
|
||||
- RoleBinding
|
||||
- ServiceAccountAccess
|
||||
- StaleAccess
|
||||
- Subject
|
||||
- TemporaryAccess
|
||||
- TokenReference
|
||||
---
|
||||
|
||||
# InfoTechCanon Access Control Model
|
||||
|
||||
**Short Name:** `ITC-ACCESS`
|
||||
|
|
|
|||
16
infospace/models/access-control/boundary-review.md
Normal file
16
infospace/models/access-control/boundary-review.md
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
# InfoTechCanon Access Control 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 |
|
||||
| --- | --- | --- | --- |
|
||||
| `Action` | model/task | Assigned by the kernel map concept-owner table. | kernel map |
|
||||
| `Attribute` | model/data | Data owns Attribute. Access Control uses it for attribute-based decisions and imports; its AttributeValueType catalog already depends on the data definition. | this review |
|
||||
| `Subject` | model/access-control | ITC-ACCESS owns Subject as the access-control view of an actor. CARING analyses subjects and imports; SecurityCanon imports it under SECURITY-DEC-2026-003 and uses AuthorityContext for its own dimension. | 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.
|
||||
|
|
@ -1,3 +1,58 @@
|
|||
---
|
||||
owned_concepts:
|
||||
- Attribute
|
||||
- AttributeValueType
|
||||
- BreakingChange
|
||||
- BusinessTerm
|
||||
- CodeList
|
||||
- CompatibilityRule
|
||||
- Constraint
|
||||
- ConsumerExpectation
|
||||
- DataAccessPattern
|
||||
- DataAvailability
|
||||
- DataCategory
|
||||
- DataClassification
|
||||
- DataContract
|
||||
- DataDefinition
|
||||
- DataDistribution
|
||||
- DataDomain
|
||||
- DataElement
|
||||
- DataElementConcept
|
||||
- DataEntity
|
||||
- DataFlow
|
||||
- DataFreshness
|
||||
- DataLineage
|
||||
- DataObject
|
||||
- DataProduct
|
||||
- DataQualityCheck
|
||||
- DataQualityDimension
|
||||
- DataQualityIssue
|
||||
- DataQualityResult
|
||||
- DataQualityRule
|
||||
- DataResidency
|
||||
- DataService
|
||||
- DataStoreReference
|
||||
- DataSubjectCategory
|
||||
- DataType
|
||||
- DataUsageConstraint
|
||||
- Dataset
|
||||
- DatasetSeries
|
||||
- Derivation
|
||||
- Field
|
||||
- FitnessForUse
|
||||
- GlossaryTerm
|
||||
- MasterDataReference
|
||||
- ProcessingPurpose
|
||||
- ProducerExpectation
|
||||
- Record
|
||||
- ReferenceData
|
||||
- Representation
|
||||
- RetentionRuleReference
|
||||
- SchemaEvolutionPolicy
|
||||
- Sensitivity
|
||||
- Transformation
|
||||
---
|
||||
|
||||
# InfoTechCanon Data Model
|
||||
|
||||
**Short Name:** `ITC-DATA`
|
||||
|
|
|
|||
15
infospace/models/data/boundary-review.md
Normal file
15
infospace/models/data/boundary-review.md
Normal file
|
|
@ -0,0 +1,15 @@
|
|||
# InfoTechCanon Data 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 |
|
||||
| --- | --- | --- | --- |
|
||||
| `Attribute` | model/data | Data owns Attribute. Access Control uses it for attribute-based decisions and imports; its AttributeValueType catalog already depends on the data definition. | this review |
|
||||
| `ProvenanceRecord` | kernel/itc-core | Assigned by the kernel map concept-owner table. | kernel map |
|
||||
|
||||
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.
|
||||
|
|
@ -1,3 +1,69 @@
|
|||
---
|
||||
owned_concepts:
|
||||
- AgentExecutionEvidence
|
||||
- AgentGeneratedPatch
|
||||
- AgentReview
|
||||
- Artifact
|
||||
- ArtifactDigest
|
||||
- ArtifactVersion
|
||||
- Attestation
|
||||
- Branch
|
||||
- ChangeFailure
|
||||
- CodeReview
|
||||
- CodingAgentChange
|
||||
- Commit
|
||||
- ContainerImage
|
||||
- DeliveryMetric
|
||||
- DeploymentExecution
|
||||
- DeploymentHealthSignal
|
||||
- DeploymentManifest
|
||||
- DeploymentPlan
|
||||
- DeploymentRecord
|
||||
- DeploymentVerification
|
||||
- DevSecOpsEntity
|
||||
- EnvironmentPromotion
|
||||
- FeedbackLoop
|
||||
- GateDecision
|
||||
- HumanSupervisionReference
|
||||
- IaCModule
|
||||
- Package
|
||||
- Pipeline
|
||||
- PipelineDefinition
|
||||
- PipelineIdentity
|
||||
- PipelineJob
|
||||
- PipelineResult
|
||||
- PipelineRun
|
||||
- PipelineStage
|
||||
- PipelineStep
|
||||
- PolicyGate
|
||||
- Promotion
|
||||
- Provenance
|
||||
- PullRequest
|
||||
- QualityGate
|
||||
- RecoveryAction
|
||||
- Release
|
||||
- ReleaseApprovalReference
|
||||
- ReleaseCandidate
|
||||
- ReleaseNote
|
||||
- ReleaseVersion
|
||||
- Repository
|
||||
- Rollback
|
||||
- RolloutStrategy
|
||||
- Runner
|
||||
- ScanResult
|
||||
- ScanRun
|
||||
- Signature
|
||||
- Software Bill of Materials
|
||||
- SourceChange
|
||||
- SourceTag
|
||||
- SupplyChainEvidence
|
||||
- TestResult
|
||||
- TestRun
|
||||
- TransparencyLogEntry
|
||||
- VEXReference
|
||||
- VerificationEvidence
|
||||
---
|
||||
|
||||
# InfoTechCanon DevSecOps Model
|
||||
|
||||
**Short Name:** `ITC-DEVSECOPS`
|
||||
|
|
|
|||
14
infospace/models/devsecops/boundary-review.md
Normal file
14
infospace/models/devsecops/boundary-review.md
Normal file
|
|
@ -0,0 +1,14 @@
|
|||
# InfoTechCanon DevSecOps 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 |
|
||||
| --- | --- | --- | --- |
|
||||
| `Attestation` | model/devsecops | Assigned by the kernel map concept-owner table. | kernel map |
|
||||
|
||||
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.
|
||||
|
|
@ -1,3 +1,50 @@
|
|||
---
|
||||
owned_concepts:
|
||||
- Approval
|
||||
- Assertion
|
||||
- Assessment
|
||||
- AssuranceCase
|
||||
- AssuranceConclusion
|
||||
- Audit
|
||||
- CompensatingControl
|
||||
- ComplianceRequirement
|
||||
- Control
|
||||
- ControlActivity
|
||||
- ControlImplementation
|
||||
- ControlObjective
|
||||
- ControlResult
|
||||
- ControlTest
|
||||
- Decision
|
||||
- DecisionRight
|
||||
- Escalation
|
||||
- EvidenceBasis
|
||||
- Exception
|
||||
- Finding
|
||||
- GovernanceCycle
|
||||
- GovernanceEntity
|
||||
- GovernanceForum
|
||||
- GovernanceProcess
|
||||
- GovernanceScope
|
||||
- GovernanceSystem
|
||||
- Guideline
|
||||
- Impact
|
||||
- Likelihood
|
||||
- Nonconformity
|
||||
- Obligation
|
||||
- Policy
|
||||
- Principle
|
||||
- RegulatoryReference
|
||||
- Remediation
|
||||
- Requirement
|
||||
- Review
|
||||
- Risk
|
||||
- RiskAcceptance
|
||||
- RiskSource
|
||||
- RiskTreatment
|
||||
- Rule
|
||||
- Waiver
|
||||
---
|
||||
|
||||
# InfoTechCanon Governance Model
|
||||
|
||||
**Short Name:** `ITC-GOV`
|
||||
|
|
|
|||
15
infospace/models/governance/boundary-review.md
Normal file
15
infospace/models/governance/boundary-review.md
Normal file
|
|
@ -0,0 +1,15 @@
|
|||
# InfoTechCanon Governance 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 |
|
||||
| --- | --- | --- | --- |
|
||||
| `Attestation` | model/devsecops | Assigned by the kernel map concept-owner table. | kernel map |
|
||||
| `Standard` | kernel/itc-core | Assigned by the kernel map concept-owner table. | kernel map |
|
||||
|
||||
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.
|
||||
|
|
@ -1,3 +1,66 @@
|
|||
---
|
||||
owned_concepts:
|
||||
- Anchor
|
||||
- AssimilationReport
|
||||
- Backlink
|
||||
- Block
|
||||
- BrokenLink
|
||||
- Chunk
|
||||
- Citation
|
||||
- Collection
|
||||
- ConceptIndex
|
||||
- ConceptPage
|
||||
- ConflictingDefinition
|
||||
- Corpus
|
||||
- CrossReference
|
||||
- DependencyReference
|
||||
- Document
|
||||
- DuplicateContent
|
||||
- EmbeddingRecord
|
||||
- Excerpt
|
||||
- FrontMatter
|
||||
- Generation
|
||||
- GraphView
|
||||
- Heading
|
||||
- Index
|
||||
- InformationSpace
|
||||
- Infospace
|
||||
- KnowledgeArtifact
|
||||
- KnowledgeBase
|
||||
- Link
|
||||
- LowRetrievalQuality
|
||||
- MapView
|
||||
- MappingDocument
|
||||
- MappingReference
|
||||
- MarkdownDocument
|
||||
- MetadataRecord
|
||||
- MissingMetadata
|
||||
- NavigationView
|
||||
- OrphanArtifact
|
||||
- PatternDocument
|
||||
- ProfileDocument
|
||||
- RelationshipIndex
|
||||
- RepositorySpace
|
||||
- RetrievalContext
|
||||
- RetrievalEvaluation
|
||||
- RetrievalQuery
|
||||
- RetrievalResult
|
||||
- RetrievalUnit
|
||||
- ReviewRecord
|
||||
- Revision
|
||||
- SearchIndex
|
||||
- Section
|
||||
- Shard
|
||||
- SourceReference
|
||||
- StaleContent
|
||||
- StandardDocument
|
||||
- Status
|
||||
- Summary
|
||||
- TopicIndex
|
||||
- UsePath
|
||||
- VectorIndex
|
||||
---
|
||||
|
||||
# InfoTechCanon Information Space Model
|
||||
|
||||
**Short Name:** `ITC-INFOSPACE`
|
||||
|
|
|
|||
27
infospace/models/information-space/boundary-review.md
Normal file
27
infospace/models/information-space/boundary-review.md
Normal file
|
|
@ -0,0 +1,27 @@
|
|||
# InfoTechCanon Information Space 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 |
|
||||
| --- | --- | --- | --- |
|
||||
| `Activity` | kernel/itc-core | Core and Information Space state this definition in nearly the same words. Core owns the provenance mechanism; Information Space imports it. | this review |
|
||||
| `AgentBrief` | kernel/itc-core | Assigned by the kernel map concept-owner table. | kernel map |
|
||||
| `AgentReference` | kernel/itc-core | Same definition restated. Core owns it as part of the provenance family the kernel map assigns to Core; Information Space imports. | this review |
|
||||
| `Alias` | kernel/itc-core | Core defines the general alternative identifier or label; Information Space restates it and imports. | this review |
|
||||
| `DecisionRecord` | kernel/itc-core | Core owns the record type; the Information Space enumeration of context, options, rationale and consequences is guidance on the same concept, not a second definition. | this review |
|
||||
| `ExternalReference` | kernel/itc-core | Core owns the outward pointer; Information Space scopes it to sources outside the information space and imports. | this review |
|
||||
| `Influence` | kernel/itc-core | Identical definitions. Core owns it with the provenance family; Information Space imports. | this review |
|
||||
| `Label` | kernel/itc-core | Three uses, one owner. Core owns Label as a human-readable name. The Tagging sense, a display-oriented representation of a Tag, is a qualified use of the same word and keeps its section; Information Space imports. No rename. | this review |
|
||||
| `Link` | model/information-space | Assigned by the kernel map concept-owner table. | kernel map |
|
||||
| `Namespace` | kernel/itc-core | Core owns the naming scope; Information Space adds the collision-prevention purpose and imports. Identity Realm and Tagging namespaces specialize it rather than redefining it. | this review |
|
||||
| `ProvenanceRecord` | kernel/itc-core | Assigned by the kernel map concept-owner table. | kernel map |
|
||||
| `Source` | kernel/itc-core | Identical definitions. Core owns it; Information Space imports. | this review |
|
||||
| `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 |
|
||||
| `VersionRecord` | kernel/itc-core | Assigned by the kernel map concept-owner table. | kernel map |
|
||||
|
||||
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.
|
||||
|
|
@ -1,3 +1,19 @@
|
|||
---
|
||||
owned_concepts:
|
||||
- BusinessService
|
||||
- ApplicationService
|
||||
- TechnicalService
|
||||
- RuntimeResource
|
||||
- Environment
|
||||
- Workload
|
||||
- LandscapeClaim
|
||||
- LandscapeEntity
|
||||
- LandscapeEvidence
|
||||
- LandscapeRelationship
|
||||
- LandscapeSource
|
||||
- LandscapeState
|
||||
---
|
||||
|
||||
# InfoTechCanon Landscape Model
|
||||
|
||||
**Short Name:** `ITC-LAND`
|
||||
|
|
|
|||
|
|
@ -1,3 +1,82 @@
|
|||
---
|
||||
owned_concepts:
|
||||
- ACL
|
||||
- AddressFamily
|
||||
- AllowedFlow
|
||||
- AppliedNetworkState
|
||||
- AssessedNetworkState
|
||||
- AttackSurfaceReference
|
||||
- Circuit
|
||||
- ConnectivityService
|
||||
- DNSRecord
|
||||
- DNSZone
|
||||
- DeclaredNetworkState
|
||||
- DeniedFlow
|
||||
- EgressEndpoint
|
||||
- Endpoint
|
||||
- Firewall
|
||||
- FirewallRule
|
||||
- Gateway
|
||||
- HistoricalNetworkState
|
||||
- Hostname
|
||||
- IPAddress
|
||||
- IPAllocation
|
||||
- IngressEndpoint
|
||||
- IntendedNetworkState
|
||||
- Interface
|
||||
- KubernetesNetworkPolicy
|
||||
- LoadBalancer
|
||||
- ManagementEndpoint
|
||||
- Microsegment
|
||||
- NAT
|
||||
- NetworkACL
|
||||
- NetworkConfiguration
|
||||
- NetworkDevice
|
||||
- NetworkDomain
|
||||
- NetworkEntity
|
||||
- NetworkFabric
|
||||
- NetworkFlow
|
||||
- NetworkIntent
|
||||
- NetworkNode
|
||||
- NetworkPolicy
|
||||
- NetworkRegion
|
||||
- NetworkSegment
|
||||
- NetworkSite
|
||||
- NetworkTenant
|
||||
- NetworkZone
|
||||
- NextHop
|
||||
- ObservedFlow
|
||||
- ObservedNetworkState
|
||||
- OverlayNetwork
|
||||
- Path
|
||||
- Peering
|
||||
- Port
|
||||
- Prefix
|
||||
- PrivateEndpoint
|
||||
- Proxy
|
||||
- PublicEndpoint
|
||||
- ReachabilityClaim
|
||||
- ReachabilityTest
|
||||
- ReconciliationResult
|
||||
- Route
|
||||
- RouteTable
|
||||
- Router
|
||||
- SecurityGroup
|
||||
- SecurityZone
|
||||
- ServiceEndpoint
|
||||
- ServiceMeshPolicy
|
||||
- ServiceName
|
||||
- Subnet
|
||||
- Switch
|
||||
- TerminationPoint
|
||||
- TrafficPolicy
|
||||
- TrustZoneReference
|
||||
- UnderlayNetwork
|
||||
- VLAN
|
||||
- VRF
|
||||
- WorkloadEndpoint
|
||||
---
|
||||
|
||||
# InfoTechCanon Network Model
|
||||
|
||||
**Short Name:** `ITC-NET`
|
||||
|
|
|
|||
16
infospace/models/network/boundary-review.md
Normal file
16
infospace/models/network/boundary-review.md
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
# InfoTechCanon Network 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 |
|
||||
| --- | --- | --- | --- |
|
||||
| `Drift` | kernel/itc-core | Core owns Drift as divergence of artifact usage from definition. The Network sense, divergence between intended, declared, applied and observed state, is configuration drift and is a distinct qualified concept. Disambiguation rather than transfer. | this review |
|
||||
| `Exposure` | model/security | Security owns Exposure; it is one of the model purpose entities alongside threat, weakness and vulnerability. Network describes reachability that produces exposure and imports. | this review |
|
||||
| `Link` | model/information-space | Assigned by the kernel map concept-owner table. | kernel map |
|
||||
|
||||
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.
|
||||
|
|
@ -1,3 +1,71 @@
|
|||
---
|
||||
owned_concepts:
|
||||
- Alert
|
||||
- AlertCorrelation
|
||||
- AlertRoute
|
||||
- AlertRule
|
||||
- AlertSuppression
|
||||
- Annotation
|
||||
- AvailabilityWindow
|
||||
- Baggage
|
||||
- BurnRate
|
||||
- Correlation
|
||||
- Counter
|
||||
- Dashboard
|
||||
- ErrorBudget
|
||||
- EscalationReference
|
||||
- Event
|
||||
- EventConsumer
|
||||
- EventCorrelationKey
|
||||
- EventEnvelope
|
||||
- EventSource
|
||||
- EventType
|
||||
- Exemplar
|
||||
- Gauge
|
||||
- HealthState
|
||||
- Histogram
|
||||
- Log
|
||||
- LogContext
|
||||
- LogLevel
|
||||
- LogRecord
|
||||
- LogStream
|
||||
- Metric
|
||||
- MetricInstrument
|
||||
- MetricPoint
|
||||
- Notification
|
||||
- ObservabilityEntity
|
||||
- ObservabilityEvidence
|
||||
- ObservedIncident
|
||||
- ObservedResource
|
||||
- OperationalView
|
||||
- PerformanceProfile
|
||||
- PostIncidentObservation
|
||||
- ProfilingSample
|
||||
- Query
|
||||
- QueryResult
|
||||
- ResourceAttribute
|
||||
- ResourceProfile
|
||||
- RootCauseHypothesis
|
||||
- Runbook
|
||||
- SLAReference
|
||||
- Service Level Indicator
|
||||
- Service Level Objective
|
||||
- Signal
|
||||
- SignalSource
|
||||
- Snapshot
|
||||
- Span
|
||||
- SpanEvent
|
||||
- SpanLink
|
||||
- Telemetry
|
||||
- TelemetryPipeline
|
||||
- TelemetrySource
|
||||
- TimeSeries
|
||||
- Timeline
|
||||
- Trace
|
||||
- TraceContext
|
||||
- TraceSample
|
||||
---
|
||||
|
||||
# InfoTechCanon Observability Model
|
||||
|
||||
**Short Name:** `ITC-OBS`
|
||||
|
|
|
|||
17
infospace/models/observability/boundary-review.md
Normal file
17
infospace/models/observability/boundary-review.md
Normal file
|
|
@ -0,0 +1,17 @@
|
|||
# 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.
|
||||
|
|
@ -7,6 +7,20 @@ version: RC1-seed
|
|||
# Incremental machine-readable ownership for the social extension; existing
|
||||
# organization concepts retain their definitions and ownership declarations below.
|
||||
owned_concepts:
|
||||
- Accountability
|
||||
- Actor
|
||||
- Agent
|
||||
- Authority
|
||||
- Membership
|
||||
- Organization
|
||||
- OrganizationalUnit
|
||||
- Ownership
|
||||
- Person
|
||||
- Position
|
||||
- Responsibility
|
||||
- Role
|
||||
- Stewardship
|
||||
- Team
|
||||
- Community
|
||||
- Household
|
||||
social_collectives_extension:
|
||||
|
|
|
|||
|
|
@ -1,3 +1,58 @@
|
|||
---
|
||||
owned_concepts:
|
||||
- AttackImpact
|
||||
- AttackPath
|
||||
- AttackPattern
|
||||
- AttackPrecondition
|
||||
- AttackStep
|
||||
- AttackTechnique
|
||||
- BlastRadius
|
||||
- ChokePoint
|
||||
- CompensatingMeasure
|
||||
- Containment
|
||||
- DataSecurityFinding
|
||||
- Detection
|
||||
- DetectionCoverage
|
||||
- DetectionRule
|
||||
- Eradication
|
||||
- Exploit
|
||||
- ExploitLikelihood
|
||||
- Exploitability
|
||||
- Exposure
|
||||
- ExposureFinding
|
||||
- HardeningMeasure
|
||||
- IdentityFinding
|
||||
- Investigation
|
||||
- LessonLearned
|
||||
- Misconfiguration
|
||||
- MisconfigurationFinding
|
||||
- Mitigation
|
||||
- PenTestFinding
|
||||
- ProtectedAssetReference
|
||||
- Recovery
|
||||
- SecurityAssessment
|
||||
- SecurityBoundary
|
||||
- SecurityDomain
|
||||
- SecurityEntity
|
||||
- SecurityEvidence
|
||||
- SecurityFinding
|
||||
- SecurityIncident
|
||||
- SecurityMeasure
|
||||
- SecurityPosture
|
||||
- SecurityPostureScore
|
||||
- SecurityReview
|
||||
- SecuritySignal
|
||||
- Severity
|
||||
- SupplyChainFinding
|
||||
- Tactic
|
||||
- Threat
|
||||
- ThreatActor
|
||||
- ThreatEvent
|
||||
- Vulnerability
|
||||
- VulnerabilityFinding
|
||||
- Weakness
|
||||
---
|
||||
|
||||
# InfoTechCanon Security Model
|
||||
|
||||
**Short Name:** `ITC-SEC`
|
||||
|
|
|
|||
16
infospace/models/security/boundary-review.md
Normal file
16
infospace/models/security/boundary-review.md
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
# InfoTechCanon Security 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 |
|
||||
| `Exposure` | model/security | Security owns Exposure; it is one of the model purpose entities alongside threat, weakness and vulnerability. Network describes reachability that produces exposure and imports. | this review |
|
||||
| `Investigation` | model/security | Security owns Investigation as part of response. The Observability sense is analysis activity over telemetry and imports. | 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.
|
||||
|
|
@ -1,3 +1,59 @@
|
|||
---
|
||||
owned_concepts:
|
||||
- AcceptanceCriteria
|
||||
- Action
|
||||
- Actionability
|
||||
- ApprovalTask
|
||||
- AssignmentReference
|
||||
- Backlog
|
||||
- Blocker
|
||||
- Bug
|
||||
- ChangeTask
|
||||
- Commitment
|
||||
- CompletionEvidence
|
||||
- Complexity
|
||||
- Deadline
|
||||
- DecisionTask
|
||||
- DefinitionOfDone
|
||||
- DefinitionOfReady
|
||||
- Deliverable
|
||||
- Dependency
|
||||
- DueDate
|
||||
- EffortEstimate
|
||||
- Epic
|
||||
- Experiment
|
||||
- Exploration
|
||||
- Feature
|
||||
- Importance
|
||||
- IncidentTask
|
||||
- Issue
|
||||
- Milestone
|
||||
- Move
|
||||
- NextAction
|
||||
- Option
|
||||
- Outcome
|
||||
- Priority
|
||||
- ProblemTask
|
||||
- Reachability
|
||||
- Readiness
|
||||
- RemediationTask
|
||||
- Request
|
||||
- ReviewTask
|
||||
- Step
|
||||
- Story
|
||||
- Task
|
||||
- TaskEntity
|
||||
- Transition
|
||||
- Urgency
|
||||
- Value
|
||||
- WIPLimit
|
||||
- WaitingFor
|
||||
- WorkItem
|
||||
- WorkPackage
|
||||
- Workflow
|
||||
- WorkflowState
|
||||
---
|
||||
|
||||
# InfoTechCanon Task Model
|
||||
|
||||
**Short Name:** `ITC-TASK`
|
||||
|
|
|
|||
15
infospace/models/task/boundary-review.md
Normal file
15
infospace/models/task/boundary-review.md
Normal file
|
|
@ -0,0 +1,15 @@
|
|||
# InfoTechCanon Task 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 |
|
||||
| --- | --- | --- | --- |
|
||||
| `Action` | model/task | Assigned by the kernel map concept-owner table. | kernel map |
|
||||
| `Dependency` | model/task | Assigned by the kernel map concept-owner table. | kernel map |
|
||||
|
||||
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.
|
||||
Loading…
Add table
Add a link
Reference in a new issue