QenSAi
Human Front Porch / Task Operations
PUBLIC INTERACTIVE OVERVIEW
OQS · Tasks · Live bot tasks

One queue view.
Two protected task sources.

Task Operations lets an operator see where work came from, what state it is in, how urgently it should be routed, and which evidence belongs to it—without confusing submission with execution.

▣
Public learning boundary. Every row and count shown here is synthetic. This page does not query either task database, stage or promote a request, issue a token, process work, approve a hold, or alter a live queue.
A synthetic task operations diagram showing governance and tenant sources, staged review, promotion, priority routing, lifecycle states, and evidence.
Illustrative public diagram. The two task sources remain structurally separate even when displayed together.

1. Start with the source boundary

The operator view merges records for visibility; it does not merge the databases or their endpoints. Select a source or gate to inspect its responsibility.

1

Governance task

Governance work lives on the Control Plane side and is visibly marked purple in Live bot tasks.

Evidence to look forSource marker, task handle, status, priority, and governance envelope
BoundaryA shared display does not create a shared write path or make the task tenant-visible.

2. Read lifecycle status—not activity theater

A status is a declared operational state. It tells the operator what happened and what kind of attention, if any, is appropriate.

One token per task, ever. A failed tokenized task is not retried in place. The governed retry is a new child request: stage it, review it, run pre-flight, then issue a new token only after promotion.

3. Priority is an ordering signal

The scale runs from 1 (most urgent) to 10 (background). Lower numbers are considered first; priority does not bypass staging, authority, or governance checks.

4. Open a task to inspect its evidence

The row is only an index. The detail surface is where routing, extracted keywords, lineage, and gate results become inspectable.

Synthetic task detail

Reconcile an evidence package

Extracted terms support search and alignment review; they are evidence about the request, not proof that execution succeeded.

reconciliationevidence-chainscope:governanceexpected-outcome
Operator reads

Source → status → priority → evidence

Start with provenance, then current state. Use the task handle to correlate the detail, activity, Flight Recorder events, and any parent/child relationship.

8-char handlelineagegate results
Continue the matched topic

Walk the multi-agent flow, or return to the Porch

The AIAGF walkthrough demonstrates the Workbench, conduct modes, held handoffs, governed decisions, trace evidence, and NTF handoff preparation. The live OQS queue remains operator-gated.