info-tech-canon/workplans/ITC-WP-0007-user-engine-evaluation-readiness.md

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

id	type	title	repo	status	priority	created	updated	depends_on_workplans
ITC-WP-0007	workplan	User Engine Evaluation Readiness	info-tech-canon	planned	high	2026-05-23	2026-05-23	ITC-WP-0004 ITC-WP-0005 ITC-WP-0006

ITC-WP-0007 - User Engine Evaluation Readiness

Goal

Prepare canon-side evaluation material for assessing user-engine against InfoTechCanon before integrating it as the user-management capability.

Intent

The first use of the service will be evaluation, not direct enforcement. The canon should help determine whether user-engine cleanly represents users, actors, subjects, principals, organization roles, access roles, purposes, governance expectations, and integration boundaries.

Tasks

T01 - Evaluation question set

id: ITC-WP-0007-T01
status: planned
priority: high

• Create a canon-side question set for user-management capability evaluation.
• Cover Organization, Access Control, Governance, Data, Security, Task, and PURPOSES concepts.

T02 - Expected artifact profile

id: ITC-WP-0007-T02
status: planned
priority: high

• Define expected Canon Interface Card fields for user-engine.
• Define expected entity and edge types user-engine should expose or map.
• Define evidence needed before integration.

T03 - Small SaaS alignment

id: ITC-WP-0007-T03
status: planned
priority: medium

• Use the small SaaS profile as the concrete evaluation lens.
• Identify where user-engine should satisfy profile requirements.

T04 - Consumer workplan brief

id: ITC-WP-0007-T04
status: planned
priority: medium

• Produce a brief that can be copied into a user-engine workplan.
• Do not create or maintain the user-engine adoption workplan here.

Non-Goals

• Do not refactor user-engine in this repo.
• Do not decide user-engine implementation details here.

Acceptance

• InfoTechCanon can evaluate user-engine before integration work begins.
• The evaluation pack is machine-readable enough for CLI/API use.
• A consumer workplan brief exists for user-engine.