ControlLayer
Review field coverage, validation samples, launch blockers, downstream module impact, and API-backed definition commands for tenant-safe custom-field rollout.
Review and persist tenant-scoped field definitions, validation samples, launch blockers, and downstream impact through the settings API boundary.
Tenant context
Primary attention
Evidence owner backup is missing a required projected value
Next review
Before enabling provider-backed custom-field writes
Field definitions
6
tenant-scoped definitions projected from the shared schema catalog
Ready now
3
3 definitions can appear in preview flows without extra mapping
Launch blockers
2
required values or mapping gaps that must stay human-reviewed
Pilot or draft
2
fields that must not be treated as durable tenant configuration yet
Each readiness lane keeps the target entity, launch gate, and review owner visible before durable custom-field settings exist.
Contract operations
Contract
Contract-level fields are close to operational use, but escalation path rules still need a named fallback owner before they become durable settings.
Site context
Site
Site context fields are ready for preview-led coverage and reporting surfaces without adding provider calls or live writes.
Supplier assurance
Supplier evidence
Supplier-assurance fields must stay blocked until upload intake can supply a stable zone reference and backup evidence owner.
Definitions stay typed, tenant-stamped, and linked to downstream consumers without becoming persisted settings edits.
Site risk tier
site_risk_tier
Site
Single select
Required
Example: High-rise residential
Owner: Property operations
Ready for site-detail and coverage preview rows.
Allowed values are mapped to active site profile labels.
Renewal buffer days
renewal_buffer_days
Contract
Number
Optional
Example: 14
Owner: Operations
Ready to appear in renewal-readiness calculations as a preview input.
Numeric validation blocks malformed reminder-buffer values.
Notice escalation path
notice_escalation_path
Contract
Single select
Conditional
Example: Escalate to regional property lead after 5 days
Owner: Operations
Pilot only until fallback owner rules cover unmapped portfolios.
Single-select values are valid, but the fallback owner map is incomplete.
Site occupancy profile
site_occupancy_profile
Site
Multi select
Optional
Example: Residential, mixed-use, overnight access
Owner: Property operations
Ready for preview coverage filters and board-pack grouping.
Multi-select labels normalize into a stable comma-separated projection.
Supplier mobilisation zone
supplier_mobilisation_zone
Supplier evidence
Site reference
Conditional
Example: Awaiting mapped site-cluster reference
Owner: Compliance
Needs mapping before supplier-upload evidence can rely on this zone value.
Upload intake does not yet guarantee a stable site-cluster reference.
Evidence owner backup
evidence_owner_backup
Supplier evidence
User reference
Required
Example: Awaiting backup owner assignment rule
Owner: Compliance
Draft until compliance defines the backup-owner assignment rule.
Required user-reference value is still missing in the supplier evidence projection.
Samples exercise the same shared validator used by projected custom-field values, including wrong-target and missing-required cases.
Valid numeric reminder buffer
Renewal buffer days / Contract
Malformed numeric reminder buffer
Renewal buffer days / Contract
Missing required backup evidence owner
Evidence owner backup / Supplier evidence
Wrong target entity for site risk tier
Site risk tier / Contract
Valid multi-select occupancy profile
Site occupancy profile / Site
Non-valid projections become explicit admin review items instead of silently flowing into compliance or renewal workflows.
Evidence owner backup
Bluefield Cleaning / Supplier evidence
Required projection remains blocked until the backup-owner default rule exists.
Owner: Compliance
Supplier mobilisation zone
Bluefield Cleaning / Supplier evidence
Upload intake still needs a stable site-cluster reference before this becomes reportable.
Owner: Compliance
Create and archive actions call /v1/settings/custom-fields. Archive is metadata-only and preserves existing tenant records.