generated from coulomb/repo-seed
Add user-engine evaluation readiness pack
This commit is contained in:
65
infospace/evaluations/user-engine/evaluation-pack.yaml
Normal file
65
infospace/evaluations/user-engine/evaluation-pack.yaml
Normal file
@@ -0,0 +1,65 @@
|
||||
id: evaluation/user-engine
|
||||
title: User Engine Canon Evaluation Pack
|
||||
status: candidate
|
||||
consumer: user-engine
|
||||
purpose: Evaluate user-engine against InfoTechCanon before integration as the user-management capability.
|
||||
created_by_workplan: ITC-WP-0007
|
||||
evaluation_mode: pre-integration
|
||||
canon_anchors:
|
||||
- model/organization
|
||||
- model/access-control
|
||||
- model/governance
|
||||
- model/data
|
||||
- model/security
|
||||
- model/task
|
||||
- model/purpose-demand-extension
|
||||
- profile/small-saas
|
||||
- standard/caring
|
||||
pack_components:
|
||||
questions: evaluations/user-engine/questions.yaml
|
||||
interface_card_expectations: evaluations/user-engine/interface-card-expectations.yaml
|
||||
small_saas_alignment: evaluations/user-engine/small-saas-alignment.yaml
|
||||
consumer_workplan_brief: evaluations/user-engine/consumer-workplan-brief.md
|
||||
evaluation_surfaces:
|
||||
- user identity and account lifecycle
|
||||
- actor, subject, and principal distinctions
|
||||
- organization roles and access roles
|
||||
- tenant, team, and membership boundaries
|
||||
- permission and entitlement traces
|
||||
- policy, control, evidence, and access review traces
|
||||
- data handled by user management
|
||||
- security controls around credentials, sessions, and privileged access
|
||||
- tasks created by onboarding, review, remediation, and deprovisioning
|
||||
- consumer purpose, demand signal, purpose fit, and scope pressure
|
||||
readiness_gates:
|
||||
- id: gate/user-management-core
|
||||
title: Core user-management concepts are mapped.
|
||||
required: true
|
||||
expects:
|
||||
- User, Account, Actor, Subject, Principal, Team, Tenant, Role, AccessRole, Policy, Control, Evidence.
|
||||
- id: gate/access-trace
|
||||
title: Access grants are traceable to scope, policy, control, and evidence.
|
||||
required: true
|
||||
expects:
|
||||
- Each privileged grant identifies role, subject or principal, resource scope, tenant boundary, governing policy, and evidence.
|
||||
- id: gate/governance-evidence
|
||||
title: Governance evidence exists before integration.
|
||||
required: true
|
||||
expects:
|
||||
- Access review, exception, approval, and remediation records are available or explicitly marked as gaps.
|
||||
- id: gate/purpose-fit
|
||||
title: Consumer purpose and producer fit are explicit.
|
||||
required: true
|
||||
expects:
|
||||
- user-engine declares intent, scope, purposes, demand signals, current fit, and requested evolution.
|
||||
output_expectations:
|
||||
- completed Canon Interface Card for user-engine
|
||||
- answered evaluation question set
|
||||
- entity and edge mapping export
|
||||
- small-saas alignment notes
|
||||
- evidence bundle or explicit evidence gaps
|
||||
- consumer-side workplan created in the user-engine repo
|
||||
non_goals:
|
||||
- Refactor user-engine in this repo.
|
||||
- Decide user-engine implementation details in this repo.
|
||||
- Treat evaluation success as automatic integration approval.
|
||||
Reference in New Issue
Block a user