Skip to content

Administration Value Objects

Why This Exists

This document defines immutable or value-based concepts used by the Administration Domain.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Value objects make administration settings, scopes, priorities, statuses, and references consistent across platform operations.

Value Object Catalogue

Value object Purpose Validation rules
ConfigurationKey Identifies a configuration setting. Must be unique within scope.
ConfigurationScope Defines setting scope. Allowed values include platform, environment, tenant, domain, integration.
ConfigurationVersion Identifies configuration version. Must increase on change.
FeatureFlagKey Identifies feature flag. Must be stable and unique.
RolloutState Defines feature rollout state. Allowed values: off, internal, beta, partial, general, emergency_off.
SupportPriority Classifies support urgency. Allowed values: low, normal, high, urgent, critical.
SupportStatus Tracks support case state. Allowed values: open, triaged, in_progress, waiting, resolved, closed.
AdminActionResult Captures action outcome. Allowed values: succeeded, failed, denied, pending_review.
PolicyConfigStatus Tracks policy configuration state. Allowed values: draft, review, active, deprecated, archived.
AuditReviewStatus Tracks audit review lifecycle. Allowed values: opened, reviewing, finding_recorded, resolved, closed.
GovernanceDecisionType Classifies governance decision. Examples: approval, exception, override, rejection, escalation.
IntegrationType Classifies integration configuration. Examples: payment_provider, email, sms, whatsapp, identity_provider, calendar.
SourceReference References source domain evidence or record. Must include source domain and record identifier.
TenantReference References tenant context. Must use OrganizationId without duplicating profile facts.
EffectiveDateRange Defines when configuration applies. End date must be after start date where present.

Validation Principles

  • Administrative configuration values must have scope.
  • Admin actions must record actor and result.
  • Source references must not become source facts.
  • Sensitive configuration must not expose secrets in plaintext.