omnius 1.0.674 → 1.0.676

package/docs/.vitepress/config.mts

@@ -54,6 +54,7 @@ export default defineConfig({
         items: [
           { text: "Bring Your Own Inference", link: "/guides/bring-your-own-inference" },
           { text: "Tools And Web Search", link: "/guides/tools-and-web-search" },
+          { text: "Evidence-Bound Adjudication", link: "/ADJUDICATION" },
           { text: "Categorized OSINT Research", link: "/guides/osint-research" },
           { text: "Agent Integration", link: "/guides/agent-integration" },
           { text: "TUI Workflows", link: "/guides/tui-workflows" },

package/docs/ADJUDICATION.md

@@ -0,0 +1,270 @@
+# Evidence-bound adjudication
+
+`adjudicate` resolves a genuine decision impasse. It does not replace normal
+engineering judgment. It creates a small, tools-free decision environment. It
+then runs independent constituent assessments and a final judge.
+
+The tool separates three things:
+
+1. Evidence is part of the caller-supplied admissible record.
+2. Arguments are claims about that evidence. Arguments are not evidence.
+3. Constituent findings are analysis. Agreement between constituents does not
+   create a new fact.
+
+The host validates all identifiers, citations, panel results, and the verdict.
+The tool holds the case when it cannot validate the required quorum or final
+contract. It does not guess a result.
+
+## Availability
+
+`adjudicate` is an agent-bound tool in the top-level interactive TUI. Start
+`omnius` and ask the active agent to adjudicate an exact impasse with an
+admissible evidence record. The tool is intentionally unavailable to child
+agents. This prevents nested panels, recursive terminal projections, and
+unbounded inference fan-out.
+
+The daemon direct-tool registry does not currently expose this tool. Do not
+infer `GET /v1/tools/adjudicate` or
+`POST /v1/tools/adjudicate/call` from the tool name. Use
+`omnius show tool.adjudicate` for its static discovery contract.
+
+## When to use it
+
+Use `adjudicate` when all of these conditions are true:
+
+- The active task has one exact, unresolved decision.
+- Two or more outcomes remain materially plausible.
+- The decision affects the next action.
+- The available evidence conflicts or supports different risk tradeoffs.
+- A fresh, impartial context can assess the decision more reliably than the
+  main loop's large working context.
+
+Do not use it for an ordinary implementation choice, a factual lookup, or a
+way to avoid gathering missing evidence.
+
+## Minimum call
+
+```json
+{
+  "question": "Should the failed release be rolled back or repaired in place?",
+  "allowedOutcomes": ["rollback", "repair_in_place"],
+  "evidence": [
+    {
+      "id": "E1",
+      "kind": "test_result",
+      "source": "integration run 2026-08-31T18:00:00Z",
+      "content": "The post-deploy integration suite failed 14 of 80 tests."
+    },
+    {
+      "id": "E2",
+      "kind": "artifact",
+      "source": "release receipt sha256:abc",
+      "content": "The prior artifact matches the last known-good receipt."
+    }
+  ]
+}
+```
+
+The case framer derives three distinct constituent assignments by default. Set
+`panelSize` from 2 through 6 to change that count.
+
+## Detailed call
+
+```json
+{
+  "caseId": "release-impasse-2026-08-31",
+  "question": "Should the failed release be rolled back or repaired in place?",
+  "context": "The release is paused. No mutation is authorized during this decision.",
+  "allowedOutcomes": ["rollback", "repair_in_place"],
+  "burdenOfProof": "clear_and_convincing",
+  "decisionRules": [
+    "Prefer verified recovery evidence.",
+    "Do not infer a successful recovery from panel agreement."
+  ],
+  "evidence": [
+    {
+      "id": "E1",
+      "kind": "test_result",
+      "source": "integration run 2026-08-31T18:00:00Z",
+      "content": "The post-deploy integration suite failed 14 of 80 tests.",
+      "reliability": 0.98
+    },
+    {
+      "id": "E2",
+      "kind": "artifact",
+      "source": "release receipt sha256:abc",
+      "content": "The prior artifact matches the last known-good receipt."
+    },
+    {
+      "id": "E3",
+      "kind": "observation",
+      "source": "operations log",
+      "content": "No rollback rehearsal exists for the new migration."
+    }
+  ],
+  "arguments": [
+    {
+      "id": "A1",
+      "position": "rollback",
+      "claim": "The known-good artifact makes rollback more reversible.",
+      "citedEvidenceIds": ["E1", "E2"]
+    },
+    {
+      "id": "A2",
+      "position": "repair_in_place",
+      "claim": "Rollback has untested migration risk.",
+      "citedEvidenceIds": ["E3"]
+    }
+  ],
+  "constituents": [
+    {
+      "id": "correctness",
+      "label": "Correctness",
+      "question": "Which outcome is best supported by functional evidence?",
+      "evidenceIds": ["E1", "E2"],
+      "argumentIds": ["A1"],
+      "decisionRuleIds": ["rule-1", "rule-2"]
+    },
+    {
+      "id": "reversibility",
+      "label": "Reversibility",
+      "question": "Which outcome has the safest verified recovery path?",
+      "evidenceIds": ["E2", "E3"],
+      "argumentIds": ["A1", "A2"],
+      "decisionRuleIds": ["rule-1", "rule-2"]
+    },
+    {
+      "id": "risk",
+      "label": "Operational risk",
+      "question": "What unsupported risk remains for each outcome?",
+      "evidenceIds": ["E1", "E3"],
+      "argumentIds": ["A2"],
+      "decisionRuleIds": ["rule-1", "rule-2"]
+    }
+  ],
+  "quorum": 2,
+  "maxConcurrency": 3,
+  "timeoutMs": 120000,
+  "maxTokensPerConstituent": 2048,
+  "maxJudgeTokens": 3072
+}
+```
+
+`insufficient_evidence` is a reserved verdict. Do not include it in
+`allowedOutcomes`. The host makes it available to constituents and the judge.
+It produces a held case instead of a binding decision.
+
+## Execution phases
+
+### 1. Record admission
+
+The host validates the input before inference. It rejects duplicate IDs,
+unknown citations, invalid outcome names, incomplete manual assignment
+coverage, and a quorum that exceeds the panel size.
+
+The host creates a canonical case record and SHA-256 record hash.
+
+### 2. Case framing
+
+If the caller omits `constituents`, a tools-free case framer creates 2 through
+6 assignments. Each assignment has a distinct question and an explicit subset
+of evidence, arguments, and decision rules.
+
+The host rejects unknown IDs and incomplete evidence coverage. It retries one
+time with validation codes only. The invalid model output is not added to the
+repair prompt.
+
+### 3. Constituent fan-out
+
+The host runs assignments with bounded concurrency. Each constituent gets a
+fresh context that contains only:
+
+- the exact case question and allowed outcomes;
+- the stated burden;
+- its assignment;
+- its assigned decision rules;
+- its assigned evidence;
+- its assigned arguments.
+
+The constituent gets no tools. It has no mutation authority. It must return a
+public assessment, a recommendation, confidence, cited evidence IDs, claims,
+counterarguments, and uncertainties.
+
+The host rejects unassigned citations, unknown outcomes, identity mismatches,
+and invalid schemas. One strict repair attempt is allowed.
+
+### 4. Quorum
+
+The default quorum is two thirds of the requested panel, rounded up, with a
+minimum of two. A caller can set a stricter quorum.
+
+The tool holds the case if too few findings pass host validation. It does not
+invoke the judge without quorum.
+
+### 5. Judge synthesis
+
+The judge gets the immutable full case record and validated constituent
+findings. The prompt labels findings as analysis rather than evidence.
+
+The judge must:
+
+- apply the burden and decision rules;
+- cite only admitted evidence IDs;
+- consider every validated constituent;
+- accept or reject every constituent finding exactly once;
+- preserve material dissent;
+- select an allowed outcome or `insufficient_evidence`.
+
+The host validates this contract. It holds the case after two invalid judge
+responses.
+
+### 6. Durable receipt
+
+Artifacts are written atomically under:
+
+```text
+.omnius/adjudications/<case-id>/run-<timestamp>/
+  case.json
+  assignments.json
+  findings.json
+  verdict.json
+  receipt.json
+```
+
+`verdict.json` is absent when the case holds before a valid verdict. The
+receipt records hashes, quorum, validation failures, elapsed time, and final
+status.
+
+## CLI display
+
+The CLI opens one live block when record admission starts. It shows:
+
+- case identity and decision question;
+- record size, burden, and allowed outcomes;
+- constituent assignments;
+- separately attributed public assessment streams;
+- host validation results;
+- the judge's public rationale stream;
+- final verdict, citations, status, and receipt path.
+
+The block has a `read mode` row. Select it to expand all retained rows. The
+display retains a bounded amount of text. It strips terminal controls and uses
+the normal secret redactor. It does not display provider hidden reasoning.
+
+## Harness
+
+Run the deterministic impasse harness:
+
+```bash
+pnpm harness:adjudication
+```
+
+The harness does not load a model and does not use a GPU. It verifies parallel
+constituent overlap, streamed public assessments, judge synthesis, and receipt
+persistence. The focused automated tests also cover invalid citations, strict
+repair, partial valid quorum, automatic case framing, and no-judge behavior
+when quorum fails.
+
+The implementation lives in
+`packages/orchestrator/src/adjudication.ts`. The live projection lives in
+`packages/cli/src/tui/adjudication-live-block.ts`.

package/docs/DISCOVERY.json

@@ -70,6 +70,11 @@
         "query": "web search tool exposure agent bound",
         "expand": "workflow.agent-bound-tools"
       },
+      {
+        "intent": "Resolve an evidence-based decision impasse",
+        "query": "adjudicate impartial evidence quorum verdict",
+        "expand": "workflow.evidence-bound-adjudication"
+      },
       {
         "intent": "Debug a stale or unhealthy daemon",
         "query": "daemon version port logs health debug",
@@ -28266,6 +28271,36 @@
         "api.tools"
       ]
     },
+    {
+      "id": "guide.adjudication-uppercase",
+      "kind": "guide",
+      "title": "Evidence-bound adjudication",
+      "summary": "adjudicate resolves a genuine decision impasse. It does not replace normal engineering judgment. It creates a small, tools-free decision environment. It then runs independent constituent assessments and a final judge.",
+      "keywords": [
+        "ADJUDICATION",
+        "md"
+      ],
+      "maturity": "stable",
+      "audiences": [
+        "user",
+        "integrator",
+        "coding-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/ADJUDICATION.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/ADJUDICATION.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
     {
       "id": "guide.agent-memory-index",
       "kind": "guide",
@@ -36048,6 +36083,109 @@
         "packages/cli/src/tui/omnius-directory.ts"
       ]
     },
+    {
+      "id": "tool.adjudicate",
+      "kind": "tool",
+      "title": "Evidence-bound adjudication",
+      "summary": "Resolve one genuine decision impasse through an isolated evidence record, independently scoped constituent review, host-validated citations and quorum, a final judge, and a durable verdict receipt.",
+      "aliases": [
+        "adjudicate",
+        "adjudication",
+        "decision impasse",
+        "impartial decision",
+        "evidence-bound decision"
+      ],
+      "keywords": [
+        "agent-bound",
+        "impasse",
+        "evidence",
+        "constituents",
+        "quorum",
+        "judge",
+        "verdict",
+        "dissent"
+      ],
+      "maturity": "stable",
+      "layer": "orchestration",
+      "audiences": [
+        "coding-agent",
+        "maintainer",
+        "interactive-user"
+      ],
+      "direct_callable": false,
+      "use_when": [
+        "The top-level interactive agent has one exact unresolved decision with at least two materially plausible outcomes",
+        "The admissible evidence supports conflicting conclusions or risk tradeoffs",
+        "The decision changes the next action and benefits from isolated impartial review"
+      ],
+      "avoid_when": [
+        "The question is an ordinary implementation choice, factual lookup, or substitute for gathering missing evidence",
+        "The caller is a child agent, daemon direct-tool client, REST run, or Telegram tool loop"
+      ],
+      "interfaces": [
+        {
+          "type": "tui-agent-tool",
+          "target": "omnius",
+          "description": "Registered only in the top-level interactive agent tool catalog"
+        }
+      ],
+      "references": [
+        {
+          "type": "guide",
+          "target": "docs/ADJUDICATION.md",
+          "relation": "canonical-guide"
+        },
+        {
+          "type": "source",
+          "target": "packages/orchestrator/src/adjudication.ts",
+          "relation": "implementation"
+        },
+        {
+          "type": "source",
+          "target": "packages/cli/src/tui/interactive.ts",
+          "relation": "top-level-registration"
+        },
+        {
+          "type": "source",
+          "target": "packages/cli/src/tui/adjudication-live-block.ts",
+          "relation": "live-projection"
+        }
+      ],
+      "related": [
+        "workflow.evidence-bound-adjudication",
+        "layer.orchestration",
+        "layer.observability",
+        "module.orchestrator",
+        "guide.adjudication-uppercase"
+      ],
+      "verification": [
+        {
+          "check": "Run pnpm harness:adjudication",
+          "expected": "Parallel constituent streams, judge synthesis, and a durable receipt complete without loading a real model"
+        },
+        {
+          "check": "Inspect the top-level and child-agent tool registration tests",
+          "expected": "The top-level tool list includes adjudicate and child-agent lists exclude it"
+        }
+      ],
+      "failure_modes": [
+        {
+          "symptom": "A caller attempts /v1/tools/adjudicate/call",
+          "likely_cause": "Static tool discovery was mistaken for daemon direct-tool exposure",
+          "recovery": "Use the top-level interactive TUI agent"
+        },
+        {
+          "symptom": "The case returns held instead of a verdict",
+          "likely_cause": "Admission, citation validation, quorum, or final verdict validation failed",
+          "recovery": "Inspect the receipt and provide a corrected admissible record; do not infer a decision"
+        }
+      ],
+      "source_of_truth": [
+        "docs/ADJUDICATION.md",
+        "packages/orchestrator/src/adjudication.ts",
+        "packages/cli/src/tui/interactive.ts"
+      ]
+    },
     {
       "id": "tool.agenda",
       "kind": "tool",
@@ -43985,6 +44123,122 @@
         "packages/execution/src/tools/tool-manifest.ts"
       ]
     },
+    {
+      "id": "workflow.evidence-bound-adjudication",
+      "kind": "workflow",
+      "title": "Resolve an evidence-bound decision impasse",
+      "summary": "Admit one exact decision record, isolate constituent review, validate citations and quorum, synthesize a verdict through a final judge, and preserve a durable receipt without granting the panel tools or mutation authority.",
+      "aliases": [
+        "adjudicate impasse",
+        "impartial review",
+        "decision court",
+        "constituent panel"
+      ],
+      "keywords": [
+        "evidence",
+        "arguments",
+        "quorum",
+        "judge",
+        "verdict",
+        "dissent",
+        "receipt"
+      ],
+      "maturity": "stable",
+      "layer": "orchestration",
+      "audiences": [
+        "coding-agent",
+        "maintainer",
+        "interactive-user"
+      ],
+      "prerequisites": [
+        "Top-level interactive TUI agent",
+        "One exact unresolved decision",
+        "At least two allowed outcomes",
+        "Caller-supplied admissible evidence"
+      ],
+      "inputs": [
+        "question",
+        "allowed outcomes",
+        "evidence",
+        "optional arguments, decision rules, burden, constituents, and quorum"
+      ],
+      "outputs": [
+        "validated findings",
+        "verdict or held status",
+        "durable receipt"
+      ],
+      "workflow": [
+        {
+          "step": "1",
+          "action": "Confirm that a genuine impasse exists and submit an immutable record with stable evidence and argument IDs.",
+          "expected": "Host admission succeeds and creates a record hash"
+        },
+        {
+          "step": "2",
+          "action": "Frame or validate distinct constituent assignments with explicit evidence subsets.",
+          "expected": "Every admitted evidence item is covered without unknown IDs"
+        },
+        {
+          "step": "3",
+          "action": "Run tools-free constituent assessments in fresh scoped contexts with bounded concurrency.",
+          "expected": "Public findings cite only assigned evidence"
+        },
+        {
+          "step": "4",
+          "action": "Validate findings and require quorum before invoking the judge.",
+          "expected": "Invalid findings cannot create facts or satisfy quorum"
+        },
+        {
+          "step": "5",
+          "action": "Have the judge apply the burden and rules, preserve material dissent, and select an allowed outcome or insufficient_evidence.",
+          "expected": "A host-validated verdict or held case"
+        },
+        {
+          "step": "6",
+          "action": "Inspect the CLI block and durable receipt before acting on the decision.",
+          "expected": "The decision is traceable to the admitted record, validated findings, and receipt hashes"
+        }
+      ],
+      "avoid_when": [
+        "Using adjudication to replace normal judgment, gather evidence, or let a child agent spawn nested panels",
+        "Inferring a REST, daemon direct-call, or Telegram exposure that is not registered"
+      ],
+      "verification": [
+        {
+          "check": "Run pnpm harness:adjudication",
+          "expected": "The deterministic panel overlaps constituent work, streams attributed assessments, synthesizes a verdict, and persists a receipt"
+        },
+        {
+          "check": "Inspect .omnius/adjudications/<case-id>/<run>/receipt.json",
+          "expected": "Hashes, quorum, validation failures, elapsed time, and final status are present"
+        }
+      ],
+      "failure_modes": [
+        {
+          "symptom": "The case is held before judgment",
+          "likely_cause": "The record, framing, findings, or quorum failed host validation",
+          "recovery": "Use receipt validation codes to correct the admissible record; do not guess an outcome"
+        },
+        {
+          "symptom": "A direct REST call is attempted",
+          "likely_cause": "Agent-bound static discovery was confused with direct registry exposure",
+          "recovery": "Invoke through the top-level interactive TUI agent only"
+        }
+      ],
+      "source_of_truth": [
+        "docs/ADJUDICATION.md",
+        "packages/orchestrator/src/adjudication.ts",
+        "packages/cli/src/tui/interactive.ts",
+        "scripts/adjudication-impasse-harness.mjs"
+      ],
+      "related": [
+        "tool.adjudicate",
+        "layer.orchestration",
+        "layer.observability",
+        "module.orchestrator",
+        "guide.adjudication-uppercase"
+      ]
+    },
     {
       "id": "workflow.extend-omnius",
       "kind": "workflow",

package/docs/DISCOVERY.md

@@ -403,6 +403,7 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 
 | ID | Title | Summary |
 | --- | --- | --- |
+| `guide.adjudication-uppercase` | Evidence-bound adjudication | adjudicate resolves a genuine decision impasse. It does not replace normal engineering judgment. It creates a small, tools-free decision environment. It then runs independent constituent assessments and a final judge. |
 | `guide.agent-memory-index` | Agent Memory Index | Use the Omnius docs skills when an agent needs to explore the documentation corpus instead of loading the whole docs tree. |
 | `guide.agent-memory-index-uppercase` | Agent-Explorable Documentation | Omnius documentation is exposed to agents through project-local AIWG-style bundles under .aiwg/addons/. |
 | `guide.architecture-agent-system-map` | Omnius Agent System Map | Use this page when you need to understand how a user-visible behavior travels through Omnius, where its state lives, and which package owns a change. For a specific task recipe, search the generated catalog first: |
@@ -647,6 +648,7 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 
 | ID | Title | Summary |
 | --- | --- | --- |
+| `tool.adjudicate` | Evidence-bound adjudication | Resolve one genuine decision impasse through an isolated evidence record, independently scoped constituent review, host-validated citations and quorum, a final judge, and a durable verdict receipt. |
 | `tool.agenda` | Agenda | agenda is a directly callable Omnius tool. |
 | `tool.agent` | Agent | agent is a directly callable Omnius tool. |
 | `tool.aiwg-health` | Aiwg Health | aiwg_health is a directly callable Omnius tool. |
@@ -792,6 +794,7 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 | `workflow.daemon-tray-update` | Operate daemon, tray, and updates | Ensure one current daemon owns the service port, start the tray against it, install updates through the real global npm flow, stream progress, restart components, and verify the target runtime. |
 | `workflow.debug-runtime` | Debug an Omnius runtime failure | Diagnose from identity and ownership outward: version, health, port/process, live contract, status/events, state scope, logs/evidence, then the owning module. |
 | `workflow.direct-tool-call` | Call a directly exposed tool | Inspect live metadata, confirm direct-call exposure and safety, submit the exact schema, and verify the tool result. |
+| `workflow.evidence-bound-adjudication` | Resolve an evidence-bound decision impasse | Admit one exact decision record, isolate constituent review, validate citations and quorum, synthesize a verdict through a final judge, and preserve a durable receipt without granting the panel tools or mutation authority. |
 | `workflow.extend-omnius` | Extend or modify Omnius safely | Locate the owning layer/module and canonical registry, change the smallest source boundary, update discovery/docs/contracts, and run targeted plus freshness tests. |
 | `workflow.provider-selection` | Select an inference provider and model | Resolve an explicit provider protocol, credentials, endpoint, and model; verify live reachability and hardware placement for local inference. |
 | `workflow.publish-package` | Build and publish the Omnius package | Follow the repository Minimal Publish SOP: clean all workspaces, rebuild, bundle publish/, inspect a local-cache tarball, patch-bump, publish only from publish/, and verify npm metadata. |

package/docs/agent-memory/INDEX.md

@@ -9,6 +9,10 @@ Omnius documentation is exposed to agents through project-local AIWG-style bundl
 | `omnius-docs` | General Omnius docs entrypoint and feature guides |
 | `omnius-rest-docs` | REST API docs entrypoint and endpoint-family map |
 
+Evidence-bound decision questions route through `omnius-tools-docs` to
+`docs/ADJUDICATION.md`. The catalog entry is `tool.adjudicate`; the operational
+workflow is `workflow.evidence-bound-adjudication`.
+
 ## Agent Use Pattern
 
 1. Run `omnius discover "<need>"` or search `GET /v1/discovery`.

package/docs/discovery/agent-map.json

@@ -29,6 +29,7 @@
       {"intent": "Run a long coding task asynchronously", "query": "long horizon coding REST run poll cancel", "expand": "workflow.async-agent-run"},
       {"intent": "Understand where state is stored", "query": "project global state sessions memory config", "expand": "store.project"},
       {"intent": "Use web search", "query": "web search tool exposure agent bound", "expand": "workflow.agent-bound-tools"},
+      {"intent": "Resolve an evidence-based decision impasse", "query": "adjudicate impartial evidence quorum verdict", "expand": "workflow.evidence-bound-adjudication"},
       {"intent": "Debug a stale or unhealthy daemon", "query": "daemon version port logs health debug", "expand": "workflow.debug-runtime"},
       {"intent": "Add or change Omnius code", "query": "module ownership extend command endpoint tool", "expand": "workflow.extend-omnius"}
     ],
@@ -109,6 +110,7 @@
     {"id":"workflow.stateful-chat","kind":"workflow","title":"Use stateful daemon chat","summary":"Create or select a real chat session, send conversational turns, and load its history without treating control commands such as /quit as chats.","aliases":["chat sessions","history"],"keywords":["session","conversation","history"],"maturity":"stable","layer":"memory","audiences":["integrator","service-agent"],"workflow":[{"step":"1","action":"List or create sessions through the documented chat/session routes.","interface":"GET /v1/chats and chat creation route"},{"step":"2","action":"Send user content through POST /v1/chat with the selected session identity.","interface":"POST /v1/chat"},{"step":"3","action":"Load message history when selecting the session and distinguish UI/control events from conversational turns.","expected":"The selected chat displays its saved conversation"}],"verification":[{"check":"Reload the selected session","expected":"History is restored and control-only commands are absent from the chat list"}],"failure_modes":[{"symptom":"Chats named quit or duplicate Last task summaries appear","likely_cause":"Control/task metadata was projected as a chat session","recovery":"Use the canonical session registry and filter non-conversational control records"}],"source_of_truth":["packages/cli/src/api/chat-session.ts","packages/cli/src/api/session-summary.ts","packages/cli/src/api/web-ui.ts"]},
     {"id":"workflow.direct-tool-call","kind":"workflow","title":"Call a directly exposed tool","summary":"Inspect live metadata, confirm direct-call exposure and safety, submit the exact schema, and verify the tool result.","aliases":["tool REST call"],"keywords":["direct_callable","schema"],"maturity":"stable","layer":"execution","audiences":["integrator","service-agent"],"workflow":[{"step":"1","action":"Inspect the tool metadata and direct_callable flag.","interface":"GET /v1/tools/{name}","expected":"A rest-call interface is explicitly present"},{"step":"2","action":"Validate arguments against the returned parameter schema and call the exact route.","interface":"POST /v1/tools/{name}/call"},{"step":"3","action":"Inspect the structured output and any side effects.","expected":"Tool-specific verified result"}],"avoid_when":["The tool is agent-bound, unavailable, profile-gated, or lacks a rest-call interface"],"verification":[{"check":"Metadata, schema, and result all agree","expected":"No inferred route or unvalidated arguments"}],"failure_modes":[{"symptom":"Direct call returns not found or not callable","likely_cause":"The route was inferred or live exposure changed","recovery":"Re-read GET /v1/tools/{name}; use an agent-bound workflow when no rest-call interface exists"}],"source_of_truth":["packages/cli/src/api/direct-tool-registry.ts","packages/execution/src/tools/tool-manifest.ts"]},
     {"id":"workflow.agent-bound-tools","kind":"workflow","title":"Use agent-bound tools such as web_search","summary":"Offer a non-direct tool to an Omnius agent loop through run/chat instead of inventing a direct REST call.","aliases":["web search","daemon tools"],"keywords":["agent loop","web_search","tool exposure"],"maturity":"stable","layer":"execution","audiences":["integrator","coding-agent"],"workflow":[{"step":"1","action":"Inspect live tool metadata, security classification, availability, and schema.","interface":"GET /v1/tools/web_search"},{"step":"2","action":"Offer the tool through an agent-capable surface and a compatible tool profile.","interface":"POST /v1/run or POST /v1/chat/completions with agent_loop=true"},{"step":"3","action":"Require source/provenance verification appropriate to the research task.","expected":"The agent executes the bound tool and returns evidence"}],"avoid_when":["Calling POST /v1/tools/web_search/call unless live metadata explicitly adds direct exposure"],"verification":[{"check":"Inspect run/chat tool events and returned source evidence","expected":"The intended tool actually ran and its claims are traceable"}],"failure_modes":[{"symptom":"Direct tool URL is missing","likely_cause":"The tool is intentionally agent-bound","recovery":"Use /v1/run or agent-loop chat with the tool offered"}],"source_of_truth":["docs/guides/tools-and-web-search.md","packages/execution/src/tools/web-search.ts"]},
+    {"id":"workflow.evidence-bound-adjudication","kind":"workflow","title":"Resolve an evidence-bound decision impasse","summary":"Admit one exact decision record, isolate constituent review, validate citations and quorum, synthesize a verdict through a final judge, and preserve a durable receipt without granting the panel tools or mutation authority.","aliases":["adjudicate impasse","impartial review","decision court","constituent panel"],"keywords":["evidence","arguments","quorum","judge","verdict","dissent","receipt"],"maturity":"stable","layer":"orchestration","audiences":["coding-agent","maintainer","interactive-user"],"prerequisites":["Top-level interactive TUI agent","One exact unresolved decision","At least two allowed outcomes","Caller-supplied admissible evidence"],"inputs":["question","allowed outcomes","evidence","optional arguments, decision rules, burden, constituents, and quorum"],"outputs":["validated findings","verdict or held status","durable receipt"],"workflow":[{"step":"1","action":"Confirm that a genuine impasse exists and submit an immutable record with stable evidence and argument IDs.","expected":"Host admission succeeds and creates a record hash"},{"step":"2","action":"Frame or validate distinct constituent assignments with explicit evidence subsets.","expected":"Every admitted evidence item is covered without unknown IDs"},{"step":"3","action":"Run tools-free constituent assessments in fresh scoped contexts with bounded concurrency.","expected":"Public findings cite only assigned evidence"},{"step":"4","action":"Validate findings and require quorum before invoking the judge.","expected":"Invalid findings cannot create facts or satisfy quorum"},{"step":"5","action":"Have the judge apply the burden and rules, preserve material dissent, and select an allowed outcome or insufficient_evidence.","expected":"A host-validated verdict or held case"},{"step":"6","action":"Inspect the CLI block and durable receipt before acting on the decision.","expected":"The decision is traceable to the admitted record, validated findings, and receipt hashes"}],"avoid_when":["Using adjudication to replace normal judgment, gather evidence, or let a child agent spawn nested panels","Inferring a REST, daemon direct-call, or Telegram exposure that is not registered"],"verification":[{"check":"Run pnpm harness:adjudication","expected":"The deterministic panel overlaps constituent work, streams attributed assessments, synthesizes a verdict, and persists a receipt"},{"check":"Inspect .omnius/adjudications/<case-id>/<run>/receipt.json","expected":"Hashes, quorum, validation failures, elapsed time, and final status are present"}],"failure_modes":[{"symptom":"The case is held before judgment","likely_cause":"The record, framing, findings, or quorum failed host validation","recovery":"Use receipt validation codes to correct the admissible record; do not guess an outcome"},{"symptom":"A direct REST call is attempted","likely_cause":"Agent-bound static discovery was confused with direct registry exposure","recovery":"Invoke through the top-level interactive TUI agent only"}],"source_of_truth":["docs/ADJUDICATION.md","packages/orchestrator/src/adjudication.ts","packages/cli/src/tui/interactive.ts","scripts/adjudication-impasse-harness.mjs"],"related":["tool.adjudicate","layer.orchestration","layer.observability","module.orchestrator","guide.adjudication-uppercase"]},
     {"id":"workflow.provider-selection","kind":"workflow","title":"Select an inference provider and model","summary":"Resolve an explicit provider protocol, credentials, endpoint, and model; verify live reachability and hardware placement for local inference.","aliases":["BYOI","model selection"],"keywords":["provider","endpoint","protocol"],"maturity":"stable","layer":"inference","audiences":["operator","integrator","coding-agent"],"workflow":[{"step":"1","action":"Discover and expand the provider descriptor; do not infer protocol from a label or API key."},{"step":"2","action":"Configure endpoint/protocol/credential using the documented scope."},{"step":"3","action":"For local model work, perform the required hardware preflight before any token-generating request."},{"step":"4","action":"Verify the selected provider and exact model through live metadata."}],"verification":[{"check":"Live model/provider status matches the intended endpoint, protocol, and hardware","expected":"No silent fallback"}],"failure_modes":[{"symptom":"Model listing works but inference fails or uses the wrong protocol","likely_cause":"Endpoint display label was used instead of the provider descriptor","recovery":"Resolve the stable provider ID/protocol and re-test the exact endpoint before execution"}],"source_of_truth":["packages/backend-vllm/src/providerRegistry.ts","docs/guides/bring-your-own-inference.md"]},
     {"id":"workflow.voice-asr-tts","kind":"workflow","title":"Select and use ASR/TTS engines","summary":"Discover installed and supported ASR/TTS systems, perform managed setup when needed, activate one exact engine/model/device, and use the documented REST or TUI surface.","aliases":["speech","voice engines"],"keywords":["ASR","TTS","VibeVoice","transcribe_cli","LuxTTS"],"maturity":"stable","layer":"media","audiences":["integrator","operator","user"],"workflow":[{"step":"1","action":"List engines/models and inspect status before activation.","interface":"GET /v1/asr/engines; GET /v1/asr/status; voice model routes"},{"step":"2","action":"Run explicit managed setup for missing runtimes/weights and an exact accelerator when required."},{"step":"3","action":"Activate the selected engine/model and verify active status."},{"step":"4","action":"Transcribe or synthesize through the OpenAPI-documented route and validate the output artifact."}],"verification":[{"check":"Status reports the requested active engine/model/device and a small non-live test succeeds","expected":"No interpreter override or fallback to a different engine"}],"failure_modes":[{"symptom":"transcribe_cli is missing although a managed environment exists","likely_cause":"TRANSCRIBE_PYTHON points at an older Whisper environment","recovery":"Use the canonical managed transcribe runtime selection and re-check ASR status"}],"source_of_truth":["packages/execution/src/asr/registry.ts","packages/execution/src/transcribe-python-runtime.ts","packages/cli/src/api/voice-runtime.ts"]},
     {"id":"workflow.daemon-tray-update","kind":"workflow","title":"Operate daemon, tray, and updates","summary":"Ensure one current daemon owns the service port, start the tray against it, install updates through the real global npm flow, stream progress, restart components, and verify the target runtime.","aliases":["update Omnius","indicator update"],"keywords":["npm global","restart","version"],"maturity":"stable","layer":"operations","audiences":["operator","coding-agent"],"workflow":[{"step":"1","action":"Read installed and running identities from /version; diagnose port ownership before restart."},{"step":"2","action":"Start/reclaim the daemon through its managed lifecycle and confirm health."},{"step":"3","action":"Start the indicator and require daemon-online state before enabling service actions."},{"step":"4","action":"Run the update service, stream its live progress, restart the daemon/indicator, and compare /version with the target."}],"verification":[{"check":"Installed package, daemon /version, and indicator version all equal the update target","expected":"Verified target runtime, not merely queued or process-started"}],"failure_modes":[{"symptom":"UI remains on updating/queued","likely_cause":"The update worker was never executed or progress was not connected","recovery":"Inspect update job status/log stream and fail explicitly if no worker owns it"},{"symptom":"Restart verification fails","likely_cause":"Old daemon retained port ownership or new runtime did not become ready","recovery":"Resolve exact port PID, preserve unrelated processes, restart, then verify /health and /version"}],"source_of_truth":["packages/cli/src/update-service.ts","packages/cli/src/update-worker.ts","packages/cli/src/daemon.ts","packages/cli/src/tray.ts"]},