Modules and subscriptions
Screen 1.4 — record purchased module entitlements, terms and quotas with commercial evidence; the module catalog explained.
PEEK Entitlement Administrator · PEEK Platform Administrator
/peek/customers/tenant-a/1-4Subscriptions record what the customer bought — module code, term, quotas and commercial evidence. Three states are always kept apart: purchased entitlement (here), agency enablement (agency app) and operational availability (runtime).
Module catalog (v1.1)
| Module | ID | Base capability | Requires |
|---|---|---|---|
| Shared Core | core | Acquisition identity and record registry; documents, evidence and basic human tasks; external-work intake and controlled handoffs; permissions | — |
| Market Research | market_research | Human-led research workspace, approved source queries, research package and provenance | Core |
| Acquisition Planning | acquisition_planning | Plan workspace and human review, Core intake of external research, planning package and handoff | Core |
| Contract Execution & Closeout | contract_execution_closeout | Execution and closeout records, Core intake of external plans, human tasks and review | Core |
| Sigma Companion | sigma_companion | Authorized assistance over permitted Core records, approved provider routing | Core |
| Studio | studio | Advanced composition with approved components, agency page design and within-bound publication (standard pages stay in Core) | Core |
| Agentic Operations | agentic_operations | Governed execution of approved actions, action manifests, human gates, execution history | Core |
| Enterprise Integrations | enterprise_integrations | Additional contracted enterprise connectors and governed integration operations | Core |
- 1
Choose a capability
Select a catalog capability (must exist in the published capability manifest).
- 2
Set term and quotas
Start must precede end; quotas are explicit (null never means unlimited).
- 3
Attach evidence
Attach the commercial evidence for the change.
- 4
Stage
Stage entitlement change creates a versioned change that goes through 1.11 continuity review before it commits.
1.4 · Modules & Subscriptions
Record purchased product capabilities and effective dates. Open it at /peek/customers/tenant-a/1-4 (any tenant ID you can access works in place of tenant-a). The primary action is Stage entitlement change, which requires entitlement.manage.
How 1.4 works
1. Select catalog capability, term and quotas
2. Attach commercial evidence
3. Stage a versioned change for 1.11
Screen 1.4 contract
- Fields shown
- Module code, term, quota, dependency, evidence, status
- Primary action
- Stage entitlement change
- Required capability
entitlement.manage- Validation
- Start precedes end; quotas are explicit; capability IDs exist; base module independence is preserved.
- Successful outcome
- Reviewed commercial binding changes without enabling agency use or granting users data.
- Screen states
- Loading; empty; ready; restricted; stale; error; review pending
- Audit event
admin.screen.1.4.action(acceptance testAT-UI-1.4)- Requirements
- R02, R06, R25, R28, R30, R31, R33, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-1.4
Related guides
Module capabilities and dependencies
Screen 1.10 — publish the capability manifest: Core requirements, optional peers, per-feature prerequisites and manual alternatives.
Module change and continuity review
Screen 1.11 — simulate a planned module change and review impact on jobs, handoffs, navigation and retained records before committing.
Activation readiness and completion
Screens 1.5 and 1.5A — evaluate readiness blockers for the purchased configuration, activate the tenant and read the activation receipt.