---
id: evaluation/user-engine/consumer-workplan-brief
title: User Engine Consumer Workplan Brief
status: candidate
consumer: user-engine
evaluation_pack: evaluation/user-engine
---

# User Engine Consumer Workplan Brief

## Purpose

Use this brief as the seed for a user-engine repo workplan. The adoption and
implementation workplan belongs in the user-engine repository, not in
InfoTechCanon.

## Goal

Evaluate user-engine against InfoTechCanon before integration as the
user-management capability.

## Canon Inputs

- `infospace/evaluations/user-engine/evaluation-pack.yaml`
- `infospace/evaluations/user-engine/questions.yaml`
- `infospace/evaluations/user-engine/interface-card-expectations.yaml`
- `infospace/evaluations/user-engine/small-saas-alignment.yaml`
- `infospace/agent/templates/canon-interface-card.template.yaml`
- `infospace/examples/consumer-purpose-portfolio.yaml`

## Workplan Tasks For User Engine

1. Complete a Canon Interface Card for user-engine.
2. Export or describe entity mappings for user, account, actor, subject,
   principal, tenant, team, role, access role, policy, control, evidence, and
   lifecycle work.
3. Export or describe edge mappings for membership, tenant scope,
   authentication, subject evaluation, role assignment, policy governance,
   control implementation, evidence, and task creation.
4. Answer the canon evaluation question set by domain.
5. Evaluate small-saas alignment using Ada Admin, Acme, Globex, tenant
   isolation policy, namespace-per-tenant control, and access review evidence.
6. Record purpose fit, gaps, scope pressure, and requested evolution.

## Expected Outputs

- completed interface card,
- answered question set,
- entity and edge mapping export,
- evidence bundle or explicit evidence gaps,
- small-saas alignment notes,
- list of user-engine changes,
- list of canon evolution requests.

## Non-Goals

- Do not change InfoTechCanon from the user-engine workplan without a canon-side
  evolution request.
- Do not treat this evaluation as integration approval.
- Do not collapse implementation-specific names into canon concepts without a
  mapping and rationale.