generated from coulomb/repo-seed
68 lines
3.7 KiB
YAML
68 lines
3.7 KiB
YAML
id: example/consumer-purpose-portfolio
|
|
title: Canon-Side Consumer Purpose Portfolio
|
|
status: candidate
|
|
model: model/purpose-demand-extension
|
|
pattern: pattern/intent-scope-purposes
|
|
consumers:
|
|
- id: user-engine
|
|
title: User Engine Evaluation
|
|
consumer_intent: Evaluate user-management capabilities against the canon before integrating user management as a producer capability.
|
|
consumer_scope: User identity, account lifecycle, roles, access decisions, tenancy boundaries, and governance evidence.
|
|
purposes:
|
|
- id: user-engine/user-management-evaluation
|
|
use_case: Compare user-engine entities and access behavior with InfoTechCanon models and small-saas profile expectations.
|
|
consumer_need: Clear distinctions among Actor, Subject, Principal, Organization Role, AccessRole, policy, control, and evidence.
|
|
demand_signals:
|
|
- Needs conformance questions before integration starts.
|
|
- Needs source-linked concepts for user, role, tenant, access, and evidence records.
|
|
producer_capabilities_used:
|
|
- profile/small-saas
|
|
- model/organization
|
|
- model/access-control
|
|
- model/governance
|
|
- standard/caring
|
|
purpose_fit: fits_with_profile
|
|
scope_pressure: Add evaluation pack and conformance questions after PURPOSES vocabulary is accepted.
|
|
evolution_requests:
|
|
- Create canon-side user-management evaluation pack.
|
|
- id: railiance-fabric
|
|
title: Railiance Fabric Refactoring Support
|
|
consumer_intent: Refactor captured entities and edges so the fabric conforms to and informs the canon.
|
|
consumer_scope: Entity capture, edge semantics, provenance, visualization utility, and governance of extracted relationships.
|
|
purposes:
|
|
- id: railiance-fabric/entity-edge-cleanliness
|
|
use_case: Use canon concepts to classify fabric nodes and edges for cleaner visualization and better practical meaning.
|
|
consumer_need: Stable concept ownership, relationship semantics, and examples for entity and edge capture.
|
|
demand_signals:
|
|
- Needs cleaner capture of entities and edges for visualization.
|
|
- Needs relationship types that can be traced to canon models.
|
|
producer_capabilities_used:
|
|
- model/information-space
|
|
- model/governance
|
|
- model/task
|
|
- standard/tagging
|
|
purpose_fit: partial_fit
|
|
scope_pressure: Add mapping examples and relationship expectations for visualization-oriented captures.
|
|
evolution_requests:
|
|
- Create fabric entity and edge capture criteria.
|
|
- id: repo-scoping
|
|
title: Repo Scoping Comparison
|
|
consumer_intent: Compare repo-scoping concepts with the canon and identify extensions that maximize scoping utility.
|
|
consumer_scope: Repository intent, scope, domain, consumer demand, governance, and interface-card semantics.
|
|
purposes:
|
|
- id: repo-scoping/intent-scope-purposes-alignment
|
|
use_case: Use INTENT, SCOPE, and PURPOSES to improve repo scoping and feed canon extension candidates back to InfoTechCanon.
|
|
consumer_need: Explicit fit between repo intent, current scope, consumer purposes, and governance decisions.
|
|
demand_signals:
|
|
- Needs canon vocabulary for PURPOSES as consumer demand.
|
|
- Needs interface card fields that repo-scoping can produce or consume.
|
|
producer_capabilities_used:
|
|
- kernel/itc-core
|
|
- model/purpose-demand-extension
|
|
- pattern/intent-scope-purposes
|
|
- agent/templates/canon-interface-card.template.yaml
|
|
purpose_fit: gap
|
|
scope_pressure: Extend interface cards and governance vocabulary around PURPOSES.
|
|
evolution_requests:
|
|
- Compare repo-scoping with canon purpose and demand model.
|