Conditional horizon
Executable opportunities only. Every later item is recomputed after the current result.
TodayQueue control
Decision controller ready.
Live
Pending radar
Wake contracts grouped by runtime state.
Decision-changing facts
Shown only when a bounded outcome can remove a gate or change the selected action.
Queue summaryActionable counts, evidence health, and execution phasesSecondary
Operational risk against effort
Diagnostic source labels only. This chart cannot select an action.
Module distribution
Explicit modules first, bounded keyword classification second.
Execution phases
Local attempt state only. Source status remains unchanged.
Latest source delta
Field changes applied in this browser.
Causal control ledger
The selected action is traceable from source observation through gate, branch, and invalidation rule.
0
Closure requires current proof.
Exact terminal source status, current revision, validation, and attestation must agree.
Operational workspace
Action Board
Drag cards to change local planning lanes. The imported source bucket and status remain preserved for comparison and audit.
Source control
Sync Center
Import current statuses from CSV or JSON, link a local file for repeat refreshes, paste raw exports, or stage a read-only REST connector. Every import is previewed, hashed, diffed, validated, and reversible.
Upload a snapshot
Accepts CSV, TSV, JSON, and text exports. Automatic column detection is followed by a mapping and diff review.
Link a local source file
Use the browser File System Access API to refresh the same export later without choosing it again.
Paste an export
Paste CSV, TSV, or JSON from a ticket export. The parser detects the format and starts the same guarded import workflow.
Read-only connector studio
Prepare a generic REST or Zendesk JSON pull. Secrets remain session-only and are not included in exports.
Drop a current ticket export hereCSV, TSV, JSON, or TXT. Nothing is applied until the preview passes and you confirm.
1. Map source columns
Auto-detected mapping
2. Preview the merge
The preview compares incoming fields to the current source record and respects timestamp conflicts.
| Result | Ticket | Customer | Changed fields | Incoming updated |
|---|
Connector profile
Generic read-only adapters. Browser CORS and your endpoint policy still apply.
Security boundary: headers are held only in memory for the current tab. They are never saved to IndexedDB, localStorage, workspace exports, or connector profiles.
Linked source and import history
A local file handle can be retained with browser permission. Each applied import creates a recovery snapshot.
No local file linked.
Use Link local file to retain a refreshable source handle when the browser supports it.
Use Link local file to retain a refreshable source handle when the browser supports it.
CD-AI verification layer
Ticket Intelligence
Classification, identifier extraction, data quality, risk reasons, closure gates, and escalation readiness are visible and inspectable. Derived values are labeled as derived and never replace source facts.
Module classification coverage
Explicit module values remain authoritative. Auto-classification uses the project routing keywords and exposes its matched terms.
Identifier extraction coverage
GUIDs, CRM URLs, domains, email addresses, Jira keys, account keys, and error codes found in imported text fields.
Validation queue
Fail-closed checks surface missing identifiers, unsupported closure states, source conflicts, stale updates, and untriaged imports.
Canonical ticket registry
Queue Explorer
Use plain text or field queries such as bucket:pending, owner:name, module:dns, workflow:doing, changed:true, priority:1, or -status:solved.
25 ticketsNo filters
| P | Ticket | Customer | Module | Source status | Effective lane | Owner | SLA | Risk | Workflow | Updated | Quality |
|---|
Agent CouncilDecision auditConstraints select. Review domains expose exceptions.
Governing decision
The executable action, strongest alternative, branches, and invalidation boundary.
Exceptions first
Hard blockers and action-changing reviews remain expanded. Passing checks are inspectable.
Portfolio horizon
Conditional receipts in current order.
Evidence Vault
Build a verifiable evidence chain without uploading customer files.
Files are hashed locally. Only metadata and the fingerprint are retained. File contents are not stored or sent anywhere.
Ingest local evidence
Link files to a ticket, calculate SHA-256, enforce a size boundary, and preserve metadata without retaining file contents.
Drop files here
SHA-256 and metadata are calculated in this browser.
Add source reference
Use for a record URL, log query, KB article, screenshot location, or other evidence reference.
Evidence registry
Every entry shows ticket linkage, fingerprint, source time, privacy flags, and retention status.
Relationship Graph
See the queue as a connected operational system.
Tickets are linked to customers, modules, owners, patterns, dependencies, and technical identifiers. The graph is derived from current source data and local planning state.
Most connected entities
High-degree entities often reveal shared infrastructure, ownership concentration, or recurring failure paths.
Graph focus
Select a node to inspect its first-degree relationships.
Temporal Twin
Model time, aging, capacity, and the next risk horizon.
The temporal model uses supplied timestamps when present and labels low-confidence estimates explicitly. It never fabricates customer timestamps or SLA deadlines.
Execution horizon
Risk-weighted work sequence bounded by available minutes and supplied effort ranges.
Time evidence coverage
Source timestamps determine whether age and breach calculations are exact, partial, or unavailable.
Temporal registry
Current source anchors, age, due horizon, confidence, effort, and next action.
| Ticket | Customer | Anchor | Age | Due horizon | Confidence | Risk | Effort | Next action |
|---|
Pattern Observatory
Detect repetition before it becomes noise.
Deterministic clustering across modules, customers, exact errors, failure language, and action paths. Signals are operational prompts, not confirmed incidents or root causes.
Portfolio intelligence
No confirmed multi-customer incident
The engine looks for repeated evidence while preserving the difference between a pattern signal and a verified incident.
Issue clusters
Clusters must meet the active policy thresholds before they are promoted to a signal.
Exact error fingerprints
Repeated exact error text is preserved without rewriting.
Module co-occurrence matrix
Shows tickets where primary and secondary module language overlap.
Pattern watchlist
Signals that cross customer, module, or exact error boundaries.
Forecast Lab
Plan the queue as a constrained system.
Seeded simulation converts ticket effort ranges into repeatable completion bands. Risk, ownership, focus factor, and dependencies shape the recommended sequence.
Recommended execution sequence
Ordered by expected risk reduction per minute, dependency readiness, and current workflow state.
Completion distribution
P50, P80, and P95 are computed from the same deterministic seed.
Interpretation: This is a planning model based on supplied effort ranges, not a promise of completion time.
Dependency graph
Local planning dependencies only. Adding a dependency does not modify Zendesk or another system.
Support Packet Studio
Generate complete Zendesk-ready packets.
The studio enforces the CD-AI A through G contract, character limits, unverified root-cause language, evidence gates, and minimum-data asks.
Policy and Replay
Make every decision inspectable and reversible.
Versioned policy controls scoring and pattern thresholds. Checkpoints support undo and redo. Integrity checks hash critical state, detect drift, and preserve audit evidence.
Risk policy
Weights alter ordering and forecasts, not source facts.
Pattern thresholds
Minimum evidence needed to promote a repeated signal.
Encrypted recovery package
AES-GCM encrypted workspace export with PBKDF2 key derivation. Passwords are never stored.
Integrity watchdog
State consistency, source hash, dependency cycles, duplicate IDs, and audit continuity.
Audit replay
Move through local events without changing the underlying workspace.
Policy impact preview
Shows how pending policy edits would reorder the first ten active tickets.
Hosted Readiness
Prepared for static hosting, PWA install, and a future API gateway.
This build remains read-only against external systems. The package includes deployment profiles, cache controls, a local bridge, API contracts, schemas, and a stable adapter boundary.
Reference architecture
Browser, adapter, gateway, source, and audit boundaries remain separable.
Queue Nexus PWARead-only UI, local workspace, offline shell, simulations
Adapter boundaryNormalization, schema validation, ETag and cursor handling
API gatewayOAuth, RBAC, rate limits, secret isolation, observability
Zendesk and telemetryTickets, events, logs, metrics, file evidence
Audit storeImmutable evidence, approvals, idempotency, rollback
Live connection contract
Minimum controls before any write capability is considered.
Adapter SDK
Current runtime extension points for read-only integrations.
Polling leadership
One browser tab can hold the polling lease to prevent duplicate source reads.
Queue time series
Local snapshots captured from imports and app opens.
Reversible local operations
Audit and Recovery
Every local status change, planning move, import, rollback, export, and integrity check is recorded. Source snapshots can be restored without touching Zendesk.
Recovery snapshots
The newest snapshot is listed first. Restore creates a safety snapshot before replacement.
Audit timeline
Local browser events only. No production action is implied.
Runtime and storage
Build metadata, source hash, browser storage mode, and extension hooks.
Extension API: window.QueueNexus.registerAdapter(name, adapter), window.QueueNexus.startImport(rows, options), window.QueueNexus.exportState(), and window.QueueNexus.getRecords().
Workspace settings
Settings affect this local browser only.