Storage status
-
JSON / Mongo artifacts
-
-
SQL operational evidence
-
-
Interruption dossiers
-
-
Total artifacts
0
Components
0
Artifact types
0
Business contexts
0
Insight
Defined, read-only query output over Workspace data.
Datasets
0
Dataset versions
0
Queries
0
Results
0
Reference / Master Data
Workspace VC reference data used to enrich Forms and Views.VC Definitions
Released Workspace View and Row View definitions.Attribute Definitions
Released Composer metadata used to generate Commands, Entities, Forms, and Views.Artifact Inventory
Technical artifact lookup. Use the validation sections above first.Component Technical Data
Component/release internals are hidden from the main artifact list.Artifact Detail
No artifact selected.{}
Operational Control Data
BQ capacity is SQL-backed control data. Interruption dossiers are NoSQL/JSON VC-style artifacts.
Control Center Operations
Attention, notifications, outcomes, and active operational context.
Needs attention
0
Blocked sequences
0
Waiting BQ tasks
0
Recent notifications
0
Attention Queue
Notifications
Recent Outcomes
Release / Access Context
BQ Supervision Dashboard
Lane health, sequence blocking, worker settings, and task attention.
Lanes
0
Sequences
0
Blocked
0
Task attention
0
Lane Health
Lane / Sequencer State
Task Attention
Worker And Capacity Control
Capacity overrides
0
Interruption dossiers
0
Open dossiers
0
Selected messages
0
Procedure traces
0
Action traces
0
BQ task traces
0
Recovery decisions
0
Interruption Dossier
No dossier selected.Notification API Records
Persisted Control Center notification records. UI delivery is active; email and SMS are modeled as planned channels.| Type | Severity | User | Company | Read | Delivery | Source | Message | Created UTC | Action |
|---|
BQ Capacity Overrides
Component-scoped SQL records; defaults still come from released manifest metadata.| Component | Lane | Runtime Max | Lane Limit | Weight | Status | Reason | Requested By |
|---|
Procedure Trace SQL Evidence
Procedure-level operational state, timing, command correlation, and return code.| Component | Procedure | Status | Command | Company | User | Started UTC | Completed UTC | Return |
|---|
Action Trace SQL Evidence
Action attempt state, current step, return text, and JSON error-context reference.| Action | Status | Attempt | Step | Started UTC | Completed UTC | Return | Error JSON Ref |
|---|
BQ Task Trace SQL Evidence
Queue state, sequencing key, worker claim, lease expiry, and dossier link.| BQ Task | Lane | Sequence | Status | Queue Meaning | Priority | Worker | Claimed UTC | Lease Expires | Dossier | Operator |
|---|
Operator Recovery Decisions
Manual decisions applied to blocked BQ tasks and their interruption dossiers.| Decision | Status | BQ Task Trace | Dossier | Operator | Reason | Result | Decided UTC |
|---|
Interruption Dossiers
NoSQL dossier VC data. Select a dossier to show occurrences and conversation.| Status | Priority | Component | Company | Command | Procedure | Action Step | Assigned Operator | Summary |
|---|
Dossier Occurrences
Repeated failures remain separate occurrences under the same dossier.| No | Status | Error Code | Action | Step | Procedure | BQ Task | Error Message |
|---|
Dossier Conversation
NoSQL dossier messages. Later these updates should come through Control Center Forms.| Author | Type | Company | Visibility | Message | Created UTC |
|---|