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

2.4 KiB

id, type, title, repo, status, priority, created, updated, depends_on_workplans
id type title repo status priority created updated depends_on_workplans
ITC-WP-0006 workplan Purpose And Demand Model Extension info-tech-canon planned high 2026-05-23 2026-05-23
ITC-WP-0003

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: planned
priority: high
  • 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: planned
priority: high
  • 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: planned
priority: high
  • 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: planned
priority: medium
  • 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.