info-tech-canon/workplans/ITC-WP-0006-purpose-and-demand-model.md

id, type, title, domain, repo, status, priority, created, updated, depends_on_workplans, state_hub_workstream_id

id	type	title	domain	repo	status	priority	created	updated	depends_on_workplans	state_hub_workstream_id
ITC-WP-0006	workplan	Purpose And Demand Model Extension	canon	info-tech-canon	proposed	high	2026-05-23	2026-05-23	ITC-WP-0003	71fba9d5-f34f-427b-9da1-01990ab04e4d

ITC-WP-0006 - Purpose And Demand Model Extension

Goal

Explore and formalize the missing PURPOSES concept family and how it relates to INTENT, SCOPE, governance, repository evolution, and consumer demand.

Intent

A repository should be able to learn what it is used for. Consumers express their demand as purposes or use cases anchored in their intent. The producing repo can then adapt its scope, interfaces, profiles, and evolution priorities based on those declared purposes.

Working distinction:

INTENT
  Why the producer exists and what it is trying to become.

SCOPE
  What the producer currently includes, excludes, owns, and promises.

PURPOSES
  What consumers use, need, want, or value from the producer, anchored in
  the consumers' own intent.

Tasks

T01 - Concept proposal

id: ITC-WP-0006-T01
status: todo
priority: high
state_hub_task_id: "654ce87f-2967-4998-8528-3ec6db31ff1c"

• Define candidate concepts:
  • Purpose
  • ConsumerPurpose
  • UseCase
  • DemandSignal
  • ConsumerNeed
  • ProducerCapability
  • PurposeFit
  • ScopePressure
  • EvolutionRequest
• Identify likely owners across Core, Governance, Task, and Information Space.

T02 - INTENT/SCOPE/PURPOSES pattern

id: ITC-WP-0006-T02
status: todo
priority: high
state_hub_task_id: "9fb752da-3daa-4f7b-96d4-3887673e68c2"

• Create a pattern explaining how producer intent, current scope, and consumer purposes interact.
• Show how purposes can generate tasks, governance decisions, profile changes, and interface changes.

T03 - Governance extension candidates

id: ITC-WP-0006-T03
status: todo
priority: high
state_hub_task_id: "f2ec2951-fe90-48c6-acf2-35e0b7183513"

• Determine which purpose concepts belong in the Governance Model.
• Add decision and evidence expectations for accepting, rejecting, or deferring consumer purposes.
• Connect purpose pressure to roadmap and change control concepts.

T04 - Examples

id: ITC-WP-0006-T04
status: todo
priority: medium
state_hub_task_id: "5cfd80ee-3b04-4389-862b-d7913e953076"

• Add examples for user-engine, railiance-fabric, and repo-scoping as consumers of InfoTechCanon.
• Express each as canon-side examples, not as consumer repo adoption tasks.

Acceptance

• PURPOSES is defined enough to use in the first consumer evaluations.
• The relation between INTENT, SCOPE, and PURPOSES is explicit.
• Governance model extension candidates are documented for review.