generated from coulomb/repo-seed
Add purpose and demand model extension
This commit is contained in:
@@ -4,17 +4,37 @@
|
||||
|
||||
Schema: `info-tech-canon.retrieval-index.v1`
|
||||
Infospace: `canon`
|
||||
Items: **29**
|
||||
Items: **34**
|
||||
|
||||
## Common Distinctions
|
||||
|
||||
- **Actor vs Subject vs Principal**: Use actor for the acting entity in a context, subject for the entity a policy evaluates, and principal for the authenticated identity bound to access decisions. Sources: `model/organization`, `model/access-control`, `standard/caring`
|
||||
- **Organization Role vs AccessRole vs CARING role**: Organization roles describe responsibility or position; access roles describe permissions; CARING roles classify access-governance needs and analysis. Sources: `model/organization`, `model/access-control`, `standard/caring`
|
||||
- **Policy vs Control vs Evidence**: Policy states intent or rule, control implements or enforces that rule, and evidence records why the claim should be trusted. Sources: `model/governance`, `model/security`, `model/observability`
|
||||
- **Intent vs Scope vs Purpose**: Intent captures why an actor wants something, scope bounds what is included, and purpose captures consumer demand or use case pressure on the repo. Sources: `kernel/itc-core`, `model/governance`, `profile/small-saas`
|
||||
- **Intent vs Scope vs Purpose**: Intent captures why a producer or consumer exists, scope bounds producer ownership and promises, and purpose captures consumer demand anchored in consumer intent. Sources: `kernel/itc-core`, `model/purpose-demand-extension`, `pattern/intent-scope-purposes`, `profile/small-saas`
|
||||
|
||||
## Items
|
||||
|
||||
### Purpose And Consumer Demand Concept Catalog
|
||||
|
||||
- ID: `concept-catalog/purpose-demand`
|
||||
- Kind: `concept-catalog`
|
||||
- Canonical path: `concepts/purpose-demand.yaml`
|
||||
- Source path: `infospace/concepts/purpose-demand.yaml`
|
||||
- Summary: Structured candidate concept catalog: Purpose And Consumer Demand Concept Catalog.
|
||||
- Imports and anchors: `kernel/itc-core`, `model/governance`
|
||||
- Owned concepts: `Purpose And Consumer Demand Concept Catalog`
|
||||
|
||||
### Canon-Side Consumer Purpose Portfolio
|
||||
|
||||
- ID: `example/consumer-purpose-portfolio`
|
||||
- Kind: `example`
|
||||
- Canonical path: `examples/consumer-purpose-portfolio.yaml`
|
||||
- Source path: `infospace/examples/consumer-purpose-portfolio.yaml`
|
||||
- Summary: Canon-side example artifact: Canon-Side Consumer Purpose Portfolio.
|
||||
- Imports and anchors: `profile/small-saas`
|
||||
- Owned concepts: `Canon-Side Consumer Purpose Portfolio`
|
||||
|
||||
### InfoTechCanon Core
|
||||
|
||||
- ID: `kernel/itc-core`
|
||||
@@ -35,6 +55,16 @@ Items: **29**
|
||||
- Imports and anchors: none
|
||||
- Owned concepts: `InfoTechCanon Kernel Map`
|
||||
|
||||
### Purpose Demand Governance Extension Candidates
|
||||
|
||||
- ID: `mapping/purpose-demand-governance-candidates`
|
||||
- Kind: `mapping`
|
||||
- Canonical path: `mappings/purpose-demand-governance-candidates.yaml`
|
||||
- Source path: `infospace/mappings/purpose-demand-governance-candidates.yaml`
|
||||
- Summary: Mapping artifact connecting canon surfaces: Purpose Demand Governance Extension Candidates.
|
||||
- Imports and anchors: `model/task`
|
||||
- Owned concepts: `Purpose Demand Governance Extension Candidates`
|
||||
|
||||
### InfoTechCanon Access Control Model
|
||||
|
||||
- ID: `model/access-control`
|
||||
@@ -125,6 +155,16 @@ Items: **29**
|
||||
- Imports and anchors: `kernel/itc-core`
|
||||
- Owned concepts: `InfoTechCanon Organization Model`
|
||||
|
||||
### InfoTechCanon Purpose And Demand Model Extension
|
||||
|
||||
- ID: `model/purpose-demand-extension`
|
||||
- Kind: `model-extension`
|
||||
- Canonical path: `models/governance/InfoTechCanonPurposeDemandExtension.md`
|
||||
- Source path: `infospace/models/governance/InfoTechCanonPurposeDemandExtension.md`
|
||||
- Summary: Candidate extension to an existing canon model: InfoTechCanon Purpose And Demand Model Extension.
|
||||
- Imports and anchors: `kernel/itc-core`, `model/information-space`, `model/task`
|
||||
- Owned concepts: `ConsumerNeed`, `ConsumerPurpose`, `DemandSignal`, `EvolutionRequest`, `InfoTechCanon Purpose And Demand Model Extension`, `ProducerCapability`, `Purpose`, `PurposeFit`, `ScopePressure`, `UseCase`
|
||||
|
||||
### InfoTechCanon Security Model
|
||||
|
||||
- ID: `model/security`
|
||||
@@ -145,6 +185,16 @@ Items: **29**
|
||||
- Imports and anchors: `kernel/itc-core`
|
||||
- Owned concepts: `InfoTechCanon Task Model`
|
||||
|
||||
### Intent Scope Purposes Pattern
|
||||
|
||||
- ID: `pattern/intent-scope-purposes`
|
||||
- Kind: `pattern`
|
||||
- Canonical path: `patterns/intent-scope-purposes.md`
|
||||
- Source path: `infospace/patterns/intent-scope-purposes.md`
|
||||
- Summary: Reusable canon pattern: Intent Scope Purposes Pattern.
|
||||
- Imports and anchors: `model/governance`, `model/task`
|
||||
- Owned concepts: `Intent Scope Purposes Pattern`, `IntentScopePurposePattern`
|
||||
|
||||
### Small SaaS System Profile
|
||||
|
||||
- ID: `profile/small-saas`
|
||||
|
||||
Reference in New Issue
Block a user