omnius 1.0.646 → 1.0.647

package/docs/ASD-STE100-COMMUNICATION-AUDIT.md

@@ -0,0 +1,233 @@
+# ASD-STE100 Communication Audit
+
+Date: 2026-08-28
+
+## Objective
+
+Use ASD-STE100 Issue 9 for all Omnius natural-language communication.
+Apply the rule to external replies and internal agent messages.
+Preserve exact machine content without a change.
+
+## Standard boundary
+
+[ASD-STE100 Issue 9](https://www.asd-ste100.org/assets/files/ASD-STE100_ISSUE9.pdf) has 53 writing rules.
+It also has an approved-word dictionary and permits necessary technical terms.
+The standard requires consistent technical terms, short sentences, direct verbs, and clear procedures.
+
+Issue 9 limits a procedure sentence to 20 words.
+It limits a descriptive sentence to 25 words.
+It requires one instruction in most procedure sentences.
+It also requires quoted text to remain unchanged.
+
+The [official STE description](https://www.asd-ste100.org/about.html) identifies an approved dictionary and permitted technical terms.
+The [official checker guidance](https://www.asd-ste100.org/ste-software.html) states that software aids are not complete compliance proof.
+
+Therefore, Omnius can enforce structural STE rules automatically.
+A qualified human must confirm full dictionary compliance.
+Omnius must not claim certified compliance from a model or heuristic check.
+
+## 2026 reliability evidence
+
+Current research supports three separate communication layers.
+
+1. Use controlled natural language for human and agent prose.
+2. Use schemas and exact fields for machine messages.
+3. Use code validators for syntax and meaning.
+
+A 2026 protocol review reports weak support for clarification, context alignment, and semantic verification.
+Omnius now names these duties in the common contract.
+Source: [Beyond Message Passing](https://arxiv.org/abs/2604.02369).
+
+A 2026 harness study reports that prompt text alone did not preserve critical guarantees.
+It assigns deterministic guarantees to code, schemas, manifests, and validators.
+Omnius now uses this rule in the common contract.
+Source: [From Prompts to Contracts](https://arxiv.org/abs/2607.08028).
+
+A 2026 structured-output study separates valid syntax from valid meaning.
+It also reports model-specific failure patterns.
+Omnius must validate JSON structure and field meaning.
+Source: [StructHallu-Drift](https://aclanthology.org/2026.surgellm-1.22/).
+
+A 2026 reliability framework treats retries and verification as different recovery operators.
+Omnius must classify a failure before it selects a recovery method.
+Source: [Cost-Aware Adaptive Reliability](https://arxiv.org/abs/2605.09121).
+
+2025 structured-output studies remain directly applicable.
+They show that schema constraints need adapted prompts, examples, and validators.
+Sources: [The Hidden Cost of Structure](https://aclanthology.org/2025.ranlp-1.124/) and [Schema Reinforcement Learning](https://aclanthology.org/2025.acl-long.243/).
+
+## Lossless exception boundary
+
+Do not change these items during STE conversion:
+
+- Code and code blocks
+- JSON, schemas, keys, and enum values
+- Commands, paths, options, and environment keys
+- API routes, headers, status codes, and media types
+- Tool names and tool argument names
+- Model names and provider names
+- Sentinels, tags, placeholders, and parser labels
+- User input and source quotations
+- Logs, errors, traces, and tool output
+- Required literal replies
+
+Use STE for text that introduces or explains these items.
+If STE conflicts with an exact contract, the exact contract has priority.
+
+## Runtime architecture review
+
+| Surface | Previous condition | Current control | Status |
+|---|---|---|---|
+| Small tier | Large duplicated prose with long sentences | Shared common contract and small-tier addition | Updated |
+| Medium tier | Large duplicated prose with long sentences | Shared common contract and medium-tier addition | Updated |
+| Large tier | Large duplicated prose with long sentences | Shared common contract and large-tier addition | Updated |
+| Ollama and compatible providers | No common language envelope | Provider adds one STE policy message | Updated |
+| Anthropic adapter | Independent system translation | Provider policy enters before translation | Updated |
+| Native Ollama stream | Independent message path | Provider policy enters before native transport | Updated |
+| Nexus remote peer | Independent message path | Nexus adds the same policy | Updated |
+| Cascade backend | Delegates to Ollama or Nexus | Inner backend adds the policy | Updated |
+| Web chat | Separate non-tier system prompt | Web prompt starts with the shared policy | Updated |
+| Realtime and phone | Explicit contraction preference | Shared policy and direct spoken rules | Updated |
+| Task templates | Long compound instructions | Eight source templates use short direct rules | Updated |
+| Telegram router | Many inline contracts and exact schemas | Provider policy governs output | Controlled rewrite required |
+| Sub-agent delegation | Separate preambles and exact envelopes | Provider policy governs output | Controlled rewrite required |
+| RALPH runners | Separate JSON-sensitive prompt files | Provider policy governs output | Controlled rewrite required |
+| Memory and compaction | Separate JSON and summary prompts | Provider policy governs output | Controlled rewrite required |
+| CLI dream and emotion prompts | Creative and machine output contracts | Provider policy governs output | Profile-specific review required |
+| Reference contracts | 39 long Markdown contracts | Included under the common policy | Controlled rewrite required |
+| OpenAPI and help text | Human prose in TypeScript literals | Not model-generated | User-interface review required |
+
+The final provider boundary adds the policy before each model request.
+This rule covers inline prompts that still need a controlled source rewrite.
+It also covers new prompts that a feature adds later.
+The policy does not change exact machine content.
+
+## Source inventory
+
+The prompt audit found 83 source Markdown files.
+Generated files under `publish/` are not source files.
+
+- CLI TUI prompts: 7 files
+- Prompt package contracts and templates: 15 files
+- Orchestrator prompts: 22 files
+- Root reference contracts: 39 files
+
+TypeScript also contains direct model prompts and user-interface messages.
+These strings need a separate literal extractor because many strings contain machine data.
+
+## Main defects found
+
+### Tier prompts
+
+The three tier files duplicated nearly all content.
+Many sentences had more than 25 words.
+Several sentences contained more than one instruction.
+The smaller tiers did not have a materially smaller common contract.
+
+The new design keeps one common contract.
+Each tier file now contains only its tier rules.
+This design prevents language drift between tiers.
+
+### Realtime prompt
+
+The previous prompt explicitly permitted contractions.
+This rule directly conflicted with STE.
+The fallback reply also used a contraction.
+
+The new prompt prohibits contractions.
+The fallback now uses two short sentences.
+An exact user-requested reply remains exempt.
+
+### Task templates
+
+The source templates used long labels, questions, vague terms, and compound instructions.
+The revised templates use one direct action in each procedure sentence.
+Exact placeholders and tool names remain unchanged.
+
+### Telegram and tool contracts
+
+Telegram router prompts contain safety, identity, route, and reply policies.
+They also contain exact JSON fields and enum values.
+A broad text conversion can change router behavior.
+
+Tool contracts contain exact JSON, tool names, argument names, and parser sentinels.
+These elements need token-preservation tests before a controlled prose conversion.
+
+### Corrected prompt defect
+
+`packages/cli/prompts/tui/emotion-center.md` had an unclosed parenthesis.
+Its examples also conflicted with its required emoji-and-word output.
+The revised prompt has short instructions and valid examples.
+A test now protects the placeholders and required output format.
+
+## Telegram router failure review
+
+The live failure was not an unavailable model.
+The broker completed the requests with hidden reasoning tokens.
+Omnius then removed the hidden text and received no visible decision contract.
+
+One predicate controlled two different facts.
+It controlled Ollama transport features and Omnius pool ownership.
+The broker discovery correctly disabled the local Omnius pool.
+That result also disabled Ollama transport behavior by mistake.
+
+The affected requests omitted `think:false` and Ollama context options.
+They also used `/v1/chat/completions` instead of the preferred native `/api/chat` route.
+The model used its reply budget for hidden reasoning.
+
+The backend now uses two predicates.
+
+- `isOllamaTransport` controls Ollama request fields and native routes.
+- `useOllamaPool` controls only local runner acquisition and spawn behavior.
+
+Broker-managed endpoints now use native Ollama transport without a local pool slot.
+Regression tests cover unary and streaming requests through `http://localhost:11434`.
+The tests also prove that Omnius does not acquire a local pool slot.
+
+The Telegram bridge had a separate token-count defect.
+It read usage fields from the wrong level of each stream chunk.
+It now reads the `usage` object, which corrects the false `~0 tok` display.
+
+Each model-generation block now has a bottom `read mode` control.
+The control expands all preserved thinking, content, tool-contract, and handling rows.
+The control remains available after the block completes.
+The Telegram chat fast path now streams into its block and closes the block on success or failure.
+
+## Validation policy
+
+The structural check must mask exact machine content.
+It must then inspect only authored prose.
+
+Use these hard checks for core prompts:
+
+- No contraction
+- No semicolon
+- No unresolved placeholder
+- Balanced delimiters outside protected content
+- Maximum 20 words for a procedure sentence
+- Maximum 25 words for a descriptive sentence
+- One instruction in each procedure sentence
+- Exact preservation of machine tokens
+
+Do not use automatic passive-voice detection as a hard failure.
+Do not use an incomplete dictionary as compliance proof.
+
+## Remaining controlled work
+
+Use a token manifest before any broad prompt conversion.
+Record placeholders, schema keys, enum values, tags, sentinels, and tool names.
+Require the same token set after each prose change.
+
+Convert the remaining groups in this order:
+
+1. Telegram router and reflection prose
+2. Sub-agent and delegation prose
+3. Recovery and completion prose
+4. RALPH runner prose
+5. Memory and compaction prose
+6. CLI setup and recovery text
+7. API descriptions and help text
+8. Reference contracts
+
+Run parser and snapshot tests after each group.
+Do not use a repository-wide blind text replacement.

package/docs/DISCOVERY.json

@@ -28394,6 +28394,39 @@
         }
       ]
     },
+    {
+      "id": "guide.asd-ste100-communication-audit-uppercase",
+      "kind": "guide",
+      "title": "ASD-STE100 Communication Audit",
+      "summary": "Use ASD-STE100 Issue 9 for all Omnius natural-language communication. Apply the rule to external replies and internal agent messages. Preserve exact machine content without a change.",
+      "keywords": [
+        "ASD",
+        "STE100",
+        "COMMUNICATION",
+        "AUDIT",
+        "md"
+      ],
+      "maturity": "stable",
+      "audiences": [
+        "user",
+        "integrator",
+        "coding-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/ASD-STE100-COMMUNICATION-AUDIT.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/ASD-STE100-COMMUNICATION-AUDIT.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
     {
       "id": "guide.concept-relational-language",
       "kind": "guide",
@@ -29569,6 +29602,40 @@
         }
       ]
     },
+    {
+      "id": "guide.ontology-long-horizon-work-graph-uppercase",
+      "kind": "guide",
+      "title": "Ontology WorkGraph Review",
+      "summary": "Use an ontological graph to control large and long tasks. Make each work item, relation, claim, and evidence item addressable. Keep one canonical graph across planning, execution, verification, and completion.",
+      "keywords": [
+        "ONTOLOGY",
+        "LONG",
+        "HORIZON",
+        "WORK",
+        "GRAPH",
+        "md"
+      ],
+      "maturity": "stable",
+      "audiences": [
+        "user",
+        "integrator",
+        "coding-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/ONTOLOGY-LONG-HORIZON-WORK-GRAPH.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/ONTOLOGY-LONG-HORIZON-WORK-GRAPH.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
     {
       "id": "guide.opencode-agentic-loop-comparison",
       "kind": "guide",

package/docs/DISCOVERY.md

@@ -407,6 +407,7 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 | `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: |
 | `guide.architecture-overview` | Architecture Overview | Omnius combines a terminal-first agent loop, REST daemon, model routing layer, tool runtime, persistent context, and peer mesh. |
+| `guide.asd-ste100-communication-audit-uppercase` | ASD-STE100 Communication Audit | Use ASD-STE100 Issue 9 for all Omnius natural-language communication. Apply the rule to external replies and internal agent messages. Preserve exact machine content without a change. |
 | `guide.concept-relational-language` | Concept Relational Language (CRL) — Token-Efficient Concept Communication | &gt; Experimental hyper-compressed symbolic notation for mind-mapped logical flow tracking |
 | `guide.context-management-medium-models-proposal` | Context Management for Medium Models (30-40B) — Implementation Proposal | Date: 2026-04-25 Problem: Medium-tier models (~35B params) exhibit excessive repetition at ~35% context fill despite 256K context windows Root Cause: Monolithic context structure + attention degradation + tool schema bloat |
 | `guide.dedup-false-positive-meta-analysis` | Meta-Analysis: False Positive Duplicate Tool Call Detection | Date: 2026-05-14 Scope: packages/orchestrator/src/agenticRunner.ts — proactivePrune() + buildResourceKey() |
@@ -443,6 +444,7 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 | `guide.model-capability-awareness-and-multimodal-memory-root-fix` | Model Capability Awareness And Multimodal Identity Memory Root Fix | Status: planning and integration tracker |
 | `guide.multimodal-identity-memory-implementation` | Multimodal Identity Memory Implementation Tracker | Goal: make voice, text, image, Telegram reply context, CLIP-like embeddings, zettelkasten links, and social profiles converge on one evidence-based identity substrate. |
 | `guide.omnius-self-edit-eval-2026-06-10` | Omnius Self-Edit Evaluation — Uncommitted Changes &amp; Duplicate-Tool-Call Failure Mode | &gt; Eval of the working-tree changes against docs/opencode-agentic-loop-comparison.md. &gt; Subject: an Omnius instance editing its own orchestrator to implement the P0–P10 &gt; learnings. Generated 2026-06-10. |
+| `guide.ontology-long-horizon-work-graph-uppercase` | Ontology WorkGraph Review | Use an ontological graph to control large and long tasks. Make each work item, relation, claim, and evidence item addressable. Keep one canonical graph across planning, execution, verification, and completion. |
 | `guide.opencode-agentic-loop-comparison` | OpenCode → Omnius: Agentic Loop &amp; Sub-Agent Delegation Comparison | &gt; Exhaustive comparison between https://github.com/anomalyco/opencode/tree/dev and &gt; packages/orchestrator/src/agenticRunner.ts (omnius). &gt; Generated 2026-06-10. |
 | `guide.operations-delay-analysis` | Unnecessary Causes of Delays Between Agent Actions | Analysis of packages/orchestrator/src/ (95 files) — identified delay sources ranked by impact. |
 | `guide.operations-delay-fix-review` | Delay Fix Review — Commits Since Delay Analysis | Date: 2026-06-10 Reference: /docs/operations/delay-analysis.md (15 delay sources documented) |

package/docs/ONTOLOGY-LONG-HORIZON-WORK-GRAPH.md

@@ -0,0 +1,329 @@
+# Ontology WorkGraph Review
+
+Date: 2026-08-28
+
+## Objective
+
+Use an ontological graph to control large and long tasks.
+Make each work item, relation, claim, and evidence item addressable.
+Keep one canonical graph across planning, execution, verification, and completion.
+
+## Reference boundary
+
+The [Ontology Workbench](https://robit-man.github.io/ontology/) is the documentation and reference implementation.
+Its [raw source](https://github.com/robit-man/ontology/blob/main/index.html) defines the contracts and behavior.
+
+Use the implementation as a contract reference.
+Do not copy its browser and IndexedDB monolith into Omnius.
+
+## Main conclusion
+
+Omnius already has most required primitives.
+They exist in separate models with different identifiers and completion rules.
+
+Add a canonical `WorkGraph` projection.
+Do not add another independent planner or evidence store.
+
+The graph must join this chain:
+
+```text
+objective
+  -> requirement
+    -> feature
+      -> component or module
+        -> task
+          -> artifact or mutation
+            -> claim
+              -> verification
+                -> evidence
+```
+
+Relations must also represent dependencies, blockers, contradictions, and supersession.
+
+## Useful Ontology Workbench contracts
+
+The reference separates four concerns:
+
+- Type and schema definitions
+- Mutable runtime instances
+- Claims, evidence, and conflicts
+- Objectives, plans, actions, approvals, and executions
+
+The model proposes a revision-bound patch.
+Deterministic code validates and applies the patch.
+The code records an immutable revision receipt.
+
+The reference also uses target-focused evidence collection.
+It scans all target occurrences before it selects evidence.
+It keeps varied semantic roles and document positions.
+It also keeps supporting and contradicting evidence.
+
+These contracts are more valuable than its first chunking algorithm.
+Omnius already has stronger basic chunking, content hashes, staleness checks, and PDF coverage receipts.
+
+## Strong Omnius foundations
+
+### Work decomposition
+
+- `todo-store.ts` has stable identifiers, parents, blockers, owners, dependencies, verifiers, and artifacts.
+- `todoTruth.ts` derives hierarchy, open leaves, dependency state, and parent completion.
+- `featurePlanner.ts` records paths, symbols, tests, evidence, questions, units, and return contracts.
+- `featureNode.ts` provides recursive survey, plan, split, execute, verify, and eviction stages.
+
+### Completion and closure
+
+- `completionLedger.ts` records claims, evidence roles, risks, critiques, unresolved items, and terminal receipts.
+- `deliveryCoverage.ts` has versioned manifests and deterministic coverage evaluation.
+- `integrationClosure.ts` already projects requirements, claims, paths, contracts, evidence, and blockers into a graph.
+- `completion-evidence-gate.ts` requires independent evidence for high-risk claims.
+
+### Evidence and memory
+
+- `evidenceLedger.ts` records content hashes, revisions, ranges, fidelity, mutations, and staleness.
+- `contextMemoryLedger.ts` records authority, trust, temporal validity, relations, and dependency-closed transactions.
+- `evidenceBranch.ts` validates selected ranges against presented windows and original source text.
+- PDF receipts distinguish absence, incomplete coverage, truncation, and omitted pages.
+
+### Retrieval
+
+- Hybrid retrieval combines lexical, vector, and graph candidates.
+- The context assembler supports rank fusion, graph expansion, snippet packing, and request budgets.
+- The memory ledger supports temporal and source-aware retrieval with explicit abstention.
+
+## Critical gaps
+
+### No canonical work identity
+
+Tasks, todos, feature nodes, missions, claims, and memory records use separate identifiers.
+They cannot form one durable requirement-to-evidence path.
+
+### Weak requirement identity
+
+Many requirements and acceptance criteria remain unkeyed prose.
+The integration graph creates one synthetic current-goal requirement.
+Todos do not carry requirement and acceptance identifiers.
+
+### Isolated feature systems
+
+The feature planner, feature tree, and mission artifacts have limited production wiring.
+Their rich contracts do not control the main completion path.
+
+### Advisory completion evidence
+
+The active completion gate records graph gaps but does not stop completion.
+Final reconciliation does not revoke an accepted completion result.
+
+Keep inferred work advisory.
+Make explicit requirements and acceptance paths authoritative.
+
+### No world transaction boundary
+
+`PatchProposal` does not include a base revision or expected source versions.
+It also lacks typed semantic operations and a resulting revision receipt.
+
+Current stale-write controls operate below the proposal contract.
+The system cannot validate one proposal atomically against its observed world.
+
+### No first-class conflict object
+
+Omnius can mark a claim as contradicted.
+It cannot preserve two active incompatible claims in one conflict group.
+
+Add subject, predicate, valid-time, alternatives, authority, confidence, and resolution rationale.
+
+### Incomplete evidence diversity
+
+Several retrieval paths keep one occurrence per file or source.
+Some structured reads select only leading rows or leading text.
+
+This behavior can omit late updates, repeated events, and counterevidence.
+It can also confuse an unobserved fact with an absent fact.
+
+### Fragmented source bindings
+
+Each package uses a different locator and provenance shape.
+Most general records support only line or character ranges.
+
+Add page, sheet, row, heading, table, field, and JSON-path locators.
+
+## Canonical WorkGraph contract
+
+Use these node kinds:
+
+- `objective`
+- `requirement`
+- `feature`
+- `component`
+- `module`
+- `task`
+- `acceptance`
+- `symbol`
+- `artifact`
+- `mutation`
+- `claim`
+- `verification`
+- `evidence`
+- `conflict`
+- `blocker`
+
+Use these core relations:
+
+- `decomposes_to`
+- `part_of`
+- `depends_on`
+- `satisfies`
+- `implements`
+- `modifies`
+- `produces`
+- `verified_by`
+- `evidenced_by`
+- `contradicts`
+- `blocked_by`
+- `supersedes`
+
+Each node and relation must have a stable identifier.
+Each inferred item must record its authority.
+An inferred item remains advisory until code or a user adopts it.
+
+Each action node must define these fields when they apply:
+
+- Target references
+- Inputs
+- Preconditions
+- Expected mutations
+- Side effects
+- Required authority
+- Required approval
+- Risk
+- Verification contract
+
+## Shared evidence contract
+
+Add one `SourceBinding` and `EvidenceRef` schema under `packages/schemas`.
+
+The schema must include these fields:
+
+- Evidence identifier
+- Source identifier and URI
+- Content hash and source revision
+- Observation time and freshness
+- Authority and confidence
+- Typed locator and locator value
+- Supporting or refuting polarity
+- Coverage and truncation status
+- State epoch
+
+Use the same evidence identifier in retrieval, memory, claims, completion, and groundedness.
+Validate each reference against the current source revision.
+
+## Revisioned world reducer
+
+Add a pure reducer under `packages/orchestrator/src/operational-world/`.
+Keep `AgenticRunner`, context systems, and the TUI as consumers.
+
+The model can propose only a `WorldPatch`.
+The patch must include `patchId`, `baseRevision`, and typed operations.
+
+The reducer must do these checks:
+
+1. Verify the base revision.
+2. Validate every runtime schema.
+3. Verify every node, relation, claim, and evidence reference.
+4. Verify expected file hashes and read versions.
+5. Reject duplicate identifiers and dangling relations.
+6. Reject invalid cycles and temporal intervals.
+7. Preserve incompatible claims as a conflict.
+8. Apply operations in a deterministic order.
+9. Emit an immutable patch and revision receipt.
+
+Use `integrationClosure.ts` as the first graph adapter.
+Do not make its bounded display neighborhood the authoritative validation universe.
+
+## Large-document evidence pipeline
+
+Use a source-aware decomposition tree.
+Each child shard must retain its parent and exact locator.
+
+Select shard boundaries by content type:
+
+- Keep prose headings with their paragraphs.
+- Keep JSON paths and array ranges.
+- Repeat table headers for each table shard.
+- Keep PDF page markers.
+- Keep spreadsheet sheet and row markers.
+
+If one extraction fails, subdivide only that shard.
+Preserve the failed shard as unresolved evidence.
+Do not discard it.
+
+For a named target, use this retrieval sequence:
+
+1. Resolve exact target entities.
+2. Scan all target occurrences.
+3. Build section-bounded evidence windows.
+4. Classify each window by semantic role and polarity.
+5. Keep earliest and latest relevant evidence.
+6. Keep early, middle, and late document coverage.
+7. Expand one hop to co-referenced entities.
+8. Include supporting and contradicting evidence.
+9. Trim background evidence before target evidence.
+10. Emit a typed coverage receipt.
+
+Pass one validated `ReasoningSlice` to the reasoner and critic.
+Reject unknown citations and omitted requested targets before model criticism.
+
+## Completion invariant
+
+Use this rule for authoritative work:
+
+> Complete an objective only when every explicit requirement and acceptance path reaches fresh successful evidence after the last relevant mutation.
+
+Do not let a model-created node silently expand the user's required scope.
+Keep each inferred edge advisory until adoption.
+
+## Immediate correctness repairs
+
+Repair these issues before authoritative graph gating:
+
+- Call `verifyUnit` during the feature-node verify stage.
+- Do not mark an exception fallback complete without evidence.
+- Reject missing dependency identifiers and dependency cycles in RALPH plans.
+- Do not serialize independent modules through artificial dependencies.
+- Preserve feature decomposition fields when units become todos.
+- Wire the existing retrieval provider into the production runner.
+- Add free-form lexical retrieval to the context assembler.
+- Remove one-occurrence limits for evidence-mode retrieval.
+
+## Rollout
+
+### Phase 1: Shared identity
+
+Add shared work, relation, source-binding, evidence, conflict, and revision schemas.
+Project current stores into stable graph identifiers.
+
+### Phase 2: Shadow world
+
+Record proposed patches, validation results, revisions, and receipts.
+Compare graph closure with current completion decisions.
+Do not change completion behavior in this phase.
+
+### Phase 3: Retrieval and document evidence
+
+Wire the existing retrieval systems into production context assembly.
+Add evidence diversity, counterevidence, structural locators, and coverage receipts.
+
+### Phase 4: Authoritative explicit closure
+
+Gate only explicit requirement and acceptance paths.
+Keep inferred paths advisory.
+Require fresh evidence after each relevant mutation.
+
+### Phase 5: Parallel long-horizon execution
+
+Schedule ready leaves whose dependency paths are satisfied.
+Assign ownership and authority to each leaf.
+Commit graph patches through the revisioned reducer.
+Reconcile conflicts before dependent work begins.
+
+This design lets Omnius decompose extreme complexity into durable ontological work.
+It also keeps progress, evidence, and completion lossless across long sessions.

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "omnius",
-  "version": "1.0.646",
+  "version": "1.0.647",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "omnius",
-      "version": "1.0.646",
+      "version": "1.0.647",
       "bundleDependencies": [
         "image-to-ascii"
       ],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omnius",
-  "version": "1.0.646",
+  "version": "1.0.647",
   "description": "AI coding agent powered by open-source models (Ollama/vLLM) — interactive TUI with agentic tool-calling loop",
   "type": "module",
   "main": "./dist/library.js",