coulomb/info-tech-canon
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add purpose and demand model extension

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-23 04:59:16 +02:00
parent cf8ff12608
commit 82424cc6f4
39 changed files with 1597 additions and 86 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
infospace/agent/briefs/concept-catalog-purpose-demand.md Normal file
View File

@@ -0,0 +1,31 @@
---
id: agent-brief/concept-catalog-purpose-demand
artifact_id: concept-catalog/purpose-demand
source_path: concepts/purpose-demand.yaml
source_kind: concept-catalog
generated: true
---
<!-- GENERATED by info_tech_canon; do not edit by hand. -->
# Agent Brief: Purpose And Consumer Demand Concept Catalog
- Artifact ID: `concept-catalog/purpose-demand`
- Kind: `concept-catalog`
- Canonical path: `concepts/purpose-demand.yaml`
- Full source: `concepts/purpose-demand.yaml`
- Summary: Structured candidate concept catalog: Purpose And Consumer Demand Concept Catalog.
## Retrieval Hints
Imports and anchors:
- `kernel/itc-core`
- `model/governance`
## Owned Concepts
- `Purpose And Consumer Demand Concept Catalog`
## Related Distinctions
No common distinction is anchored directly on this artifact.

30
infospace/agent/briefs/example-consumer-purpose-portfolio.md Normal file
View File

@@ -0,0 +1,30 @@
---
id: agent-brief/example-consumer-purpose-portfolio
artifact_id: example/consumer-purpose-portfolio
source_path: examples/consumer-purpose-portfolio.yaml
source_kind: example
generated: true
---
<!-- GENERATED by info_tech_canon; do not edit by hand. -->
# Agent Brief: Canon-Side Consumer Purpose Portfolio
- Artifact ID: `example/consumer-purpose-portfolio`
- Kind: `example`
- Canonical path: `examples/consumer-purpose-portfolio.yaml`
- Full source: `examples/consumer-purpose-portfolio.yaml`
- Summary: Canon-side example artifact: Canon-Side Consumer Purpose Portfolio.
## Retrieval Hints
Imports and anchors:
- `profile/small-saas`
## Owned Concepts
- `Canon-Side Consumer Purpose Portfolio`
## Related Distinctions
No common distinction is anchored directly on this artifact.

2
infospace/agent/briefs/kernel-itc-core.md
View File

@@ -26,4 +26,4 @@ No imports or anchors recorded.
## Related Distinctions
- **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.
- **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.

30
infospace/agent/briefs/mapping-purpose-demand-governance-candidates.md Normal file
View File

@@ -0,0 +1,30 @@
---
id: agent-brief/mapping-purpose-demand-governance-candidates
artifact_id: mapping/purpose-demand-governance-candidates
source_path: mappings/purpose-demand-governance-candidates.yaml
source_kind: mapping
generated: true
---
<!-- GENERATED by info_tech_canon; do not edit by hand. -->
# Agent Brief: Purpose Demand Governance Extension Candidates
- Artifact ID: `mapping/purpose-demand-governance-candidates`
- Kind: `mapping`
- Canonical path: `mappings/purpose-demand-governance-candidates.yaml`
- Full source: `mappings/purpose-demand-governance-candidates.yaml`
- Summary: Mapping artifact connecting canon surfaces: Purpose Demand Governance Extension Candidates.
## Retrieval Hints
Imports and anchors:
- `model/task`
## Owned Concepts
- `Purpose Demand Governance Extension Candidates`
## Related Distinctions
No common distinction is anchored directly on this artifact.

1
infospace/agent/briefs/model-governance.md
View File

@@ -28,4 +28,3 @@ Imports and anchors:
## Related Distinctions
- **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.
- **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.

41
infospace/agent/briefs/model-purpose-demand-extension.md Normal file
View File

@@ -0,0 +1,41 @@
---
id: agent-brief/model-purpose-demand-extension
artifact_id: model/purpose-demand-extension
source_path: models/governance/InfoTechCanonPurposeDemandExtension.md
source_kind: model-extension
generated: true
---
<!-- GENERATED by info_tech_canon; do not edit by hand. -->
# Agent Brief: InfoTechCanon Purpose And Demand Model Extension
- Artifact ID: `model/purpose-demand-extension`
- Kind: `model-extension`
- Canonical path: `models/governance/InfoTechCanonPurposeDemandExtension.md`
- Full source: `models/governance/InfoTechCanonPurposeDemandExtension.md`
- Summary: Candidate extension to an existing canon model: InfoTechCanon Purpose And Demand Model Extension.
## Retrieval Hints
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`
## Related Distinctions
- **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.

32
infospace/agent/briefs/pattern-intent-scope-purposes.md Normal file
View File

@@ -0,0 +1,32 @@
---
id: agent-brief/pattern-intent-scope-purposes
artifact_id: pattern/intent-scope-purposes
source_path: patterns/intent-scope-purposes.md
source_kind: pattern
generated: true
---
<!-- GENERATED by info_tech_canon; do not edit by hand. -->
# Agent Brief: Intent Scope Purposes Pattern
- Artifact ID: `pattern/intent-scope-purposes`
- Kind: `pattern`
- Canonical path: `patterns/intent-scope-purposes.md`
- Full source: `patterns/intent-scope-purposes.md`
- Summary: Reusable canon pattern: Intent Scope Purposes Pattern.
## Retrieval Hints
Imports and anchors:
- `model/governance`
- `model/task`
## Owned Concepts
- `Intent Scope Purposes Pattern`
- `IntentScopePurposePattern`
## Related Distinctions
- **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.

2
infospace/agent/briefs/profile-small-saas.md
View File

@@ -39,4 +39,4 @@ Imports and anchors:
## Related Distinctions
- **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.
- **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.

3
infospace/agent/consumer-briefs/railiance-fabric.md
View File

@@ -16,6 +16,9 @@ Use the canon to make captured entities and edges cleaner for conformance and vi
- `agent/retrieval-index.md`
- `agent/templates/canon-interface-card.template.yaml`
- `models/governance/InfoTechCanonPurposeDemandExtension.md`
- `patterns/intent-scope-purposes.md`
- `examples/consumer-purpose-portfolio.yaml`
- `profiles/small-saas/profile.yaml`
- `views/by-concept.md`

3
infospace/agent/consumer-briefs/repo-scoping.md
View File

@@ -16,6 +16,9 @@ Compare repo-scoping concepts with canon INTENT, SCOPE, PURPOSES, and interface-
- `agent/retrieval-index.md`
- `agent/templates/canon-interface-card.template.yaml`
- `models/governance/InfoTechCanonPurposeDemandExtension.md`
- `patterns/intent-scope-purposes.md`
- `examples/consumer-purpose-portfolio.yaml`
- `profiles/small-saas/profile.yaml`
- `views/by-concept.md`

3
infospace/agent/consumer-briefs/user-engine.md
View File

@@ -16,6 +16,9 @@ Evaluate user-management concepts, roles, access traces, profile claims, and gov
- `agent/retrieval-index.md`
- `agent/templates/canon-interface-card.template.yaml`
- `models/governance/InfoTechCanonPurposeDemandExtension.md`
- `patterns/intent-scope-purposes.md`
- `examples/consumer-purpose-portfolio.yaml`
- `profiles/small-saas/profile.yaml`
- `views/by-concept.md`

6
infospace/agent/global-agent-brief.md
View File

@@ -5,8 +5,8 @@
This brief summarizes the current canon service surface for agents.
- Infospace slug: `canon`
- Artifact count: 29
- Retrieval index items: 29
- Artifact count: 34
- Retrieval index items: 34
- Primary confidence command: `make validate`
- Refresh generated indexes and views with: `make index`
- Refresh agent briefs and interface templates with: `make agent-briefs`
@@ -32,7 +32,7 @@ This brief summarizes the current canon service surface for agents.
- **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.
- **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.
- **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.
- **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.
- **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.
## Consumption Notes

170
infospace/agent/retrieval-index.json
View File

@@ -34,16 +34,72 @@
"id": "intent-scope-purpose",
"source_artifacts": [
"kernel/itc-core",
"model/governance",
"model/purpose-demand-extension",
"pattern/intent-scope-purposes",
"profile/small-saas"
],
"summary": "Intent captures why an actor wants something, scope bounds what is included, and purpose captures consumer demand or use case pressure on the repo.",
"summary": "Intent captures why a producer or consumer exists, scope bounds producer ownership and promises, and purpose captures consumer demand anchored in consumer intent.",
"title": "Intent vs Scope vs Purpose"
}
],
"infospace": "canon",
"item_count": 29,
"item_count": 34,
"items": [
{
"canonical_path": "concepts/purpose-demand.yaml",
"id": "concept-catalog/purpose-demand",
"imports": [
"kernel/itc-core",
"model/governance"
],
"kind": "concept-catalog",
"owned_concepts": [
"Purpose And Consumer Demand Concept Catalog"
],
"relationships": [
{
"target": "kernel/itc-core",
"type": "conforms_to"
},
{
"target": "model/governance",
"type": "uses"
}
],
"source_path": "infospace/concepts/purpose-demand.yaml",
"summary": "Structured candidate concept catalog: Purpose And Consumer Demand Concept Catalog.",
"title": "Purpose And Consumer Demand Concept Catalog",
"warnings": []
},
{
"canonical_path": "examples/consumer-purpose-portfolio.yaml",
"id": "example/consumer-purpose-portfolio",
"imports": [
"profile/small-saas"
],
"kind": "example",
"owned_concepts": [
"Canon-Side Consumer Purpose Portfolio"
],
"relationships": [
{
"target": "model/purpose-demand-extension",
"type": "illustrates"
},
{
"target": "pattern/intent-scope-purposes",
"type": "illustrates"
},
{
"target": "profile/small-saas",
"type": "uses"
}
],
"source_path": "infospace/examples/consumer-purpose-portfolio.yaml",
"summary": "Canon-side example artifact: Canon-Side Consumer Purpose Portfolio.",
"title": "Canon-Side Consumer Purpose Portfolio",
"warnings": []
},
{
"canonical_path": "kernel/InfoTechCanonCore.md",
"id": "kernel/itc-core",
@@ -129,6 +185,35 @@
"title": "InfoTechCanon Kernel Map",
"warnings": []
},
{
"canonical_path": "mappings/purpose-demand-governance-candidates.yaml",
"id": "mapping/purpose-demand-governance-candidates",
"imports": [
"model/task"
],
"kind": "mapping",
"owned_concepts": [
"Purpose Demand Governance Extension Candidates"
],
"relationships": [
{
"target": "model/purpose-demand-extension",
"type": "maps"
},
{
"target": "model/governance",
"type": "maps"
},
{
"target": "model/task",
"type": "uses"
}
],
"source_path": "infospace/mappings/purpose-demand-governance-candidates.yaml",
"summary": "Mapping artifact connecting canon surfaces: Purpose Demand Governance Extension Candidates.",
"title": "Purpose Demand Governance Extension Candidates",
"warnings": []
},
{
"canonical_path": "models/access-control/InfoTechCanonAccessControlModel.md",
"id": "model/access-control",
@@ -348,6 +433,54 @@
"title": "InfoTechCanon Organization Model",
"warnings": []
},
{
"canonical_path": "models/governance/InfoTechCanonPurposeDemandExtension.md",
"id": "model/purpose-demand-extension",
"imports": [
"kernel/itc-core",
"model/information-space",
"model/task"
],
"kind": "model-extension",
"owned_concepts": [
"ConsumerNeed",
"ConsumerPurpose",
"DemandSignal",
"EvolutionRequest",
"InfoTechCanon Purpose And Demand Model Extension",
"ProducerCapability",
"Purpose",
"PurposeFit",
"ScopePressure",
"UseCase"
],
"relationships": [
{
"target": "kernel/itc-core",
"type": "conforms_to"
},
{
"target": "model/governance",
"type": "extends"
},
{
"target": "model/information-space",
"type": "uses"
},
{
"target": "model/task",
"type": "uses"
},
{
"target": "concept-catalog/purpose-demand",
"type": "introduces"
}
],
"source_path": "infospace/models/governance/InfoTechCanonPurposeDemandExtension.md",
"summary": "Candidate extension to an existing canon model: InfoTechCanon Purpose And Demand Model Extension.",
"title": "InfoTechCanon Purpose And Demand Model Extension",
"warnings": []
},
{
"canonical_path": "models/security/InfoTechCanonSecurityModel.md",
"id": "model/security",
@@ -395,6 +528,37 @@
"title": "InfoTechCanon Task Model",
"warnings": []
},
{
"canonical_path": "patterns/intent-scope-purposes.md",
"id": "pattern/intent-scope-purposes",
"imports": [
"model/governance",
"model/task"
],
"kind": "pattern",
"owned_concepts": [
"Intent Scope Purposes Pattern",
"IntentScopePurposePattern"
],
"relationships": [
{
"target": "model/purpose-demand-extension",
"type": "implements"
},
{
"target": "model/governance",
"type": "uses"
},
{
"target": "model/task",
"type": "uses"
}
],
"source_path": "infospace/patterns/intent-scope-purposes.md",
"summary": "Reusable canon pattern: Intent Scope Purposes Pattern.",
"title": "Intent Scope Purposes Pattern",
"warnings": []
},
{
"canonical_path": "profiles/small-saas/profile.yaml",
"id": "profile/small-saas",

54
infospace/agent/retrieval-index.md
View File

@@ -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`

119
infospace/agent/retrieval-index.yaml
View File

@@ -1,7 +1,43 @@
schema: info-tech-canon.retrieval-index.v1
infospace: canon
item_count: 29
item_count: 34
items:
- id: concept-catalog/purpose-demand
kind: concept-catalog
title: Purpose And Consumer Demand 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.'
owned_concepts:
- Purpose And Consumer Demand Concept Catalog
imports:
- kernel/itc-core
- model/governance
relationships:
- type: conforms_to
target: kernel/itc-core
- type: uses
target: model/governance
warnings: []
- id: example/consumer-purpose-portfolio
kind: example
title: Canon-Side Consumer Purpose Portfolio
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.'
owned_concepts:
- Canon-Side Consumer Purpose Portfolio
imports:
- profile/small-saas
relationships:
- type: illustrates
target: model/purpose-demand-extension
- type: illustrates
target: pattern/intent-scope-purposes
- type: uses
target: profile/small-saas
warnings: []
- id: kernel/itc-core
kind: kernel
title: InfoTechCanon Core
@@ -54,6 +90,25 @@ items:
- type: maps
target: standard/caring
warnings: []
- id: mapping/purpose-demand-governance-candidates
kind: mapping
title: Purpose Demand Governance Extension Candidates
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.'
owned_concepts:
- Purpose Demand Governance Extension Candidates
imports:
- model/task
relationships:
- type: maps
target: model/purpose-demand-extension
- type: maps
target: model/governance
- type: uses
target: model/task
warnings: []
- id: model/access-control
kind: model
title: InfoTechCanon Access Control Model
@@ -207,6 +262,40 @@ items:
- type: conforms_to
target: kernel/itc-core
warnings: []
- id: model/purpose-demand-extension
kind: model-extension
title: InfoTechCanon Purpose And Demand 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.'
owned_concepts:
- ConsumerNeed
- ConsumerPurpose
- DemandSignal
- EvolutionRequest
- InfoTechCanon Purpose And Demand Model Extension
- ProducerCapability
- Purpose
- PurposeFit
- ScopePressure
- UseCase
imports:
- kernel/itc-core
- model/information-space
- model/task
relationships:
- type: conforms_to
target: kernel/itc-core
- type: extends
target: model/governance
- type: uses
target: model/information-space
- type: uses
target: model/task
- type: introduces
target: concept-catalog/purpose-demand
warnings: []
- id: model/security
kind: model
title: InfoTechCanon Security Model
@@ -240,6 +329,26 @@ items:
- type: conforms_to
target: kernel/itc-core
warnings: []
- id: pattern/intent-scope-purposes
kind: pattern
title: Intent Scope Purposes Pattern
canonical_path: patterns/intent-scope-purposes.md
source_path: infospace/patterns/intent-scope-purposes.md
summary: 'Reusable canon pattern: Intent Scope Purposes Pattern.'
owned_concepts:
- Intent Scope Purposes Pattern
- IntentScopePurposePattern
imports:
- model/governance
- model/task
relationships:
- type: implements
target: model/purpose-demand-extension
- type: uses
target: model/governance
- type: uses
target: model/task
warnings: []
- id: profile/small-saas
kind: profile
title: Small SaaS System Profile
@@ -665,9 +774,11 @@ common_distinctions:
- model/observability
- id: intent-scope-purpose
title: Intent vs Scope vs Purpose
summary: Intent captures why an actor wants something, scope bounds what is included,
and purpose captures consumer demand or use case pressure on the repo.
summary: Intent captures why a producer or consumer exists, scope bounds producer
ownership and promises, and purpose captures consumer demand anchored in consumer
intent.
source_artifacts:
- kernel/itc-core
- model/governance
- model/purpose-demand-extension
- pattern/intent-scope-purposes
- profile/small-saas

11
infospace/agent/templates/canon-interface-card.template.yaml
View File

@@ -7,7 +7,11 @@ consumer:
owner: ''
intent: ''
scope: ''
purposes: []
purposes:
- id: ''
use_case: ''
consumer_need: ''
demand_signals: []
canon_surfaces:
implemented_profiles: []
consumed_artifacts: []
@@ -19,6 +23,11 @@ validation_expectations:
commands: []
evidence_required: []
known_gaps: []
purpose_fit:
state: ''
matched_capabilities: []
scope_pressure: ''
recommended_disposition: ''
consumer_needs:
current: []
requested_extensions: []

9
infospace/agent/templates/consumer-brief.template.md
View File

@@ -13,6 +13,8 @@ generated: true
- Intent:
- Scope:
- Purposes:
- Use cases:
- Demand signals:
## Canon Surfaces
@@ -26,3 +28,10 @@ generated: true
- Commands:
- Evidence:
- Known gaps:
## Purpose Fit
- State:
- Matched producer capabilities:
- Scope pressure:
- Requested evolution: