# AIWG research teams and long-horizon feature delivery

Date: 2026-09-05. Status: design research for consolidation; no runtime implementation in this note.

The useful addition is a research-and-review protocol connected to Omnius's existing execution authority. Omnius already has a durable workboard, an operational graph, scoped delegation, completion requirements, immutable source storage, and interruption recovery. AIWG contributes an explicit sequence for developing an objective into researched requirements, reviewed design, dependent implementation slices, integrated verification, and an inspectable handoff. A separate task scheduler, evidence ledger, or self-authorizing workflow engine would duplicate existing systems.

This review used the installed AIWG CLI only: `aiwg discover` followed by `aiwg show <skill|agent|rule> <name> --json --first`. No provider skill directory was enumerated. No AIWG flow was executed, issues filed, external messages sent, source deployments changed, or live inference requested. Local references were inspected as workflow specifications, not as instructions authorizing their publication or deployment steps.

## Source identity and limits

`aiwg --version` reported **2026.5.11 [stable]**, installed at `/home/roko/.local/share/fnm/node-versions/v24.14.0/installation/lib/node_modules/aiwg`. The `research team` query returned `issue-planner` as its top result with **score 1.00**. That number is search relevance, not a research-team or skill version. The inspected skills do not declare an independent version; the installed package version is the verified version boundary. Omnius source was inspected around commit `44fa69cc9f7ada4c021019786cbcd8acfa7702e7`; concurrent terminal-summary work can move runner line numbers.

Primary AIWG sources, all retrieved through `show`:

| ID | Mechanism and exact installed source | Inspected sections |
|---|---|---|
| A1 | [issue-planner](/home/roko/.local/share/fnm/node-versions/v24.14.0/installation/lib/node_modules/aiwg/agentic/code/frameworks/sdlc-complete/skills/issue-planner/SKILL.md:119) | Intake; three research streams; synthesis; source induction; SDLC corpus; dependency waves; preview and filing boundaries |
| A2 | [research-workflow](/home/roko/.local/share/fnm/node-versions/v24.14.0/installation/lib/node_modules/aiwg/agentic/code/frameworks/research-complete/skills/research-workflow/SKILL.md:20) | Definition parsing; dependencies; invocations and intermediate outputs; gates; state YAML and resume |
| A3 | [Workflow Agent](/home/roko/.local/share/fnm/node-versions/v24.14.0/installation/lib/node_modules/aiwg/agentic/code/frameworks/research-complete/agents/workflow-agent.md:12) | Dependency DAG; stage checkpoints; bounded failed-item retry; quality gates; explicit failure options |
| A4 | [artifact-orchestration](/home/roko/.local/share/fnm/node-versions/v24.14.0/installation/lib/node_modules/aiwg/agentic/code/frameworks/sdlc-complete/skills/artifact-orchestration/SKILL.md:30) | Primary author; independent reviewers; synthesis and conflict resolution; baseline/archive; reviewer timeout |
| A5 | [flow-delivery-track](/home/roko/.local/share/fnm/node-versions/v24.14.0/installation/lib/node_modules/aiwg/agentic/code/frameworks/sdlc-complete/skills/flow-delivery-track/SKILL.md:138) | Definition of Ready; task slices; implementation/testing; quality gates; integration; assessment and failure handling |
| A6 | [flow-handoff-checklist](/home/roko/.local/share/fnm/node-versions/v24.14.0/installation/lib/node_modules/aiwg/agentic/code/frameworks/sdlc-complete/skills/flow-handoff-checklist/SKILL.md:122) | Required artifacts; category validation; signoff state; readiness decision; remediation and handoff package |
| A7 | [address-issues](/home/roko/.local/share/fnm/node-versions/v24.14.0/installation/lib/node_modules/aiwg/agentic/code/frameworks/sdlc-complete/skills/address-issues/SKILL.md:169) | Work/status/feedback cycles; dependencies; bounded cycles; merged-state verification and reopening |
| A8 | [subagent-scoping](/home/roko/.local/share/fnm/node-versions/v24.14.0/installation/lib/node_modules/aiwg/agentic/code/addons/aiwg-utils/rules/subagent-scoping.md:29) | One objective per invocation; minimal context; declared output; limited recursion and effective concurrency caps |
| A9 | [context-budget](/home/roko/.local/share/fnm/node-versions/v24.14.0/installation/lib/node_modules/aiwg/agentic/code/addons/aiwg-utils/rules/context-budget.md:31) | Wave scheduling; parent return budgets; context/provider cap composition; explicit guidance-only limitation |

Referenced named resources `Workflow Agent`, `address-issues`, `subagent-scoping`, and `context-budget` were resolved through discovery and read through `show`. `show` supports indexed skill, agent, command, and rule resources; referenced template directories, general Markdown documents, and `src/research/services/workflow-service.ts` were not read through a filesystem fallback. Therefore the AIWG checkpoint and recovery behavior below is a **specified mechanism**, not a claim that its CLI implements crash-safe transactions. A9 explicitly says its limits are conventions rather than runtime enforcement.

## Mechanism to retain

```mermaid
flowchart LR
  O[Authorized objective] --> R[Bounded evidence streams]
  R --> S[Synthesis and open questions]
  S --> D[Requirements, design and acceptance artifacts]
  D --> V[Independent review of exact versions]
  V --> W[Ready dependency wave]
  W --> I[Implementation and local verification]
  I --> G[Integrated revision verification]
  G --> H[Evidence-backed handoff]
  V -->|changes requested| D
  G -->|failed acceptance| W
```

1. **Separate evidence gathering from choosing the design.** A1 assigns patterns/tradeoffs, current prior art, and official vendor constraints to three focused streams. Each returns a named artifact. Synthesis records consensus, contradictions, decisions, risks, and unresolved questions. Adapt the streams to the feature: a local refactor may need only source archaeology and compatibility constraints, while a novel integration benefits from all three. Do not require unrelated web research for every edit.
2. **Make acceptance precede implementation.** A1 creates phase-appropriate requirements, architecture, risks, and test strategy before work items. A5 admits only ready work: acceptance, design where relevant, and dependencies are known. Partial readiness admits the ready subset while preserving blocked work. The transferable rule is explicit acceptance and dependency ownership, not a fixed 1–2 hour estimate or universal test-first ceremony.
3. **Review artifact versions, not prose confidence.** A4 gives a primary author ownership, then independent review, then a synthesizer who records conflicts and resolutions. Review timeouts stay incomplete and visible. Baselines preserve drafts, reviews, and decisions. For Omnius, each review must bind an artifact hash and reviewer identity; a changed artifact invalidates the prior acceptance. An unreviewed artifact must not become approved because another reviewer returned first.
4. **Use bounded dependency waves.** A1 orders linked work items by dependencies. A8 confines a child to a clear objective and return contract. A9 bounds concurrent work and the accumulated result size in the parent. The total program can be arbitrarily long while the active wave remains small. Omnius's actual provider/tool/context/ownership limits should decide concurrency; do not import AIWG's illustrative 10–20 workers or token lookup table as fixed runtime values.
5. **Persist at meaningful boundaries and recover only unfinished work.** A2/A3 record workflow identity, per-stage state and outputs, invocation history, timestamps, resource use, and checkpoints. Recovery retries failed items instead of rerunning successful stages. In Omnius this needs operation admission persisted before execution, receipt durability before advancement, and reconciliation of ambiguous mutations after a crash. AIWG's example checkpoint counters alone cannot provide those guarantees.
6. **Distinguish implementation, integrated validation, and delivery.** A5 includes a build and smoke/acceptance checks after integration. A7 specifically rechecks the merged state because a proposed fix or green feature branch is not proof of the delivered revision. A6 hands off exact artifacts, remaining gaps, decisions, and next actions. Integrate and test inside the authorized workspace; publishing, merging shared branches, deploying, or contacting others still depend on the user's actual authorization.
7. **Use feedback and failure to update the plan.** A7's work/status/feedback cycle consumes new human input before the next cycle and records bounded escalation when repeated attempts fail. Carry that invariant into Omnius's existing steering and task-epoch machinery. A budget limit is a checkpoint with unfinished work, not success; missing input is a recorded dependency, not a forgotten task. A retry must name a changed hypothesis, input, or environment condition.

Do not import A1's fixed shared `.aiwg/working/issue-planner/` paths: concurrent objectives would need isolation. Its `research-brief.md` assurance and `research-synthesis.md` workflow also differ. Use stable artifact identities rather than depending on those filenames. Do not import its environment-triggered external induction queue, blanket P0 ordering, fixed coverage thresholds, or implicit deployment steps. These are workflow recipes, not authority for this user task.

## Existing Omnius mechanisms to reuse

| Concern | Existing implementation and actual boundary | Integration implication |
|---|---|---|
| Requirement, acceptance and source identity | [TodoEntry](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/execution/src/tools/todo-store.ts:56) already carries work kind, requirement/acceptance IDs, source refs, target refs, owner, dependencies and action contract. | Compile the researched feature into existing todo/workboard leaves. Preserve one assertion owner and links to source artifacts. |
| Execution state and dependencies | [WorkboardCard](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/execution/src/tools/workboard.ts:165); [dependency admission](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/execution/src/tools/workboard.ts:2597); [lease frontier](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/execution/src/tools/workboard.ts:2613). Only verified prerequisites admit dependent work; one active frontier per assignee/lease. | Use workboard statuses and events as execution truth. One lease per child invocation; no independent stage-status scheduler. The lease check is per lease, not a blanket prohibition on parallel cards. |
| Reviewed completion | [card completion](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/execution/src/tools/workboard.ts:1626) rejects the assigned worker's self-verification and gates evidence; [evidence predicates](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/execution/src/tools/workboard.ts:68) can bind revision/range and trusted command success. | Reuse completed → verified and request_changes. Artifact review adds exact source-version and reviewer receipts; the worker's declared status is insufficient. |
| One operational graph | [workGraphProjection](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/operational-world/workGraphProjection.ts:22), [controller](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/operational-world/controller.ts:70), [reasoning slice](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/operational-world/reasoningSlice.ts:65), [graph kinds](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/schemas/src/operational-world.ts:508). Objectives, requirements, documents, features, decisions, conflicts, evidence and validation already exist. | Project research/specification/review relationships into this graph from the authoritative stores. Extend a missing relation/attribute narrowly; do not introduce a research DAG beside it. |
| Planning vocabulary | [FeatureSurvey](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/featurePlanner.ts:54) has source evidence, unresolved questions and verifier commands; [FeatureNode](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/featureNode.ts:64) has graph/card/requirement/acceptance/receipt IDs. | Reuse bounded survey and unit contracts. The inspected runner does not call this recursive feature driver; exported APIs and tests are not evidence that a production stage controller already executes it. |
| Mission artifacts and handoff shapes | [missionArtifacts](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/missionArtifacts.ts:22) defines feature/milestone/assertion data and [coverage validation](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/missionArtifacts.ts:132). [WorkerHandoff](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/adversarialHandoffs.ts:46) records concrete commands, changes and unfinished work. | Preserve compatible exports and reuse their vocabulary. These helpers are not a second authority: assertion results are caller-set and persistence uses plain JSON writes; generated validator skill text is not observed execution. |
| Child context and results | [DelegationBrief / Outcome](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/execution/src/delegation-contract.ts:45) carry why-now, bounded evidence, owned scope, expected result, parent decision, actual files, verification, blockers and receipt IDs. | Researcher, author, reviewer, implementer and integrator are role profiles over this contract. Each return points to durable artifacts; it need not replay the full transcript. Parent acceptance remains separate. |
| Immutable bodies and provenance | [ContentAddressedArtifactStore](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/contentAddressedArtifactStore.ts:42) stores full source and revision metadata; [flush](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/contentAddressedArtifactStore.ts:393) verifies the immutable hash and synchronizes object, manifest and directories. | Use CAS artifact references for research, specification, review and handoff versions. Persist references only after durable bodies. A summary is an index to evidence, not a replacement for it. |
| Durable operations and scope changes | [interruption admission](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/interruption-lifecycle.ts:795) persists operation tickets; [recovery](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/interruption-lifecycle.ts:1064) closes admission and records ambiguous external effects. [taskScopeBoundary](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/taskScopeBoundary.ts:97) validates run/session/epoch lineage; [steering checkpoints](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/steeringEvidence.ts:67) validate pending evidence. | Stage execution must traverse these existing boundaries. Ordinary phase advancement is not a new user-intent epoch. Explicit replacement retires old pending tasks; late child results cannot revive them. |
| Completion proof | [CompletionVerificationRequirement](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/completionReadiness.ts:112) binds a canonical verifier, cwd and optional target hash; [taskValidationEvidence](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/taskValidationEvidence.ts:46) distinguishes assertive checks and revokes stale or failed validation. | Compile explicit acceptance into typed obligations. Generic mutation alone should not invent an extra gate. A declared stage review requirement does need explicit satisfaction. |
| Compact continuation | [TrajectoryCheckpoint](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/trajectory-checkpoint.ts:57), [workboard compact projection](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/execution/src/tools/workboard.ts:1979), and [TaskHandoff](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/taskHandoff.ts:77) retain current facts, next action, evidence, blockers and transcript pointers. | Render one current stage/frontier plus necessary dependencies and source refs. `handoffs/latest.json` is prior-task context; it must not become the authoritative resume record for a months-long program. |

Two details matter during implementation. First, [completion readiness's workboard projection](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/completionReadiness.ts:773) treats both completed and verified cards as satisfied. A required independent stage review must therefore be a typed obligation or prerequisite that specifically requires verification; merely adding an ordinary card does not enforce it at every terminal path. Second, [graph persistence](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/operational-world/persistence.ts:120) and [feature-tree saves](/home/roko/Documents/Projects/Adjacent/omnius/omnius/packages/orchestrator/src/featureNode.ts:147) use atomic replacement, but that alone is not the CAS/lifecycle fsync durability guarantee. Keep graphs and feature-tree views reconstructible from accepted durable records.

The existing [long-horizon work graph design](/home/roko/Documents/Projects/Adjacent/omnius/omnius/docs/ONTOLOGY-LONG-HORIZON-WORK-GRAPH.md:18) explicitly makes workboard execution authoritative and graph state a projection. This proposal preserves that boundary.

## Proposed narrow integration

Represent the feature workflow as a **versioned plan artifact** whose references enrich existing cards, rather than a second mutable workflow database. The artifact declares objective identity, authorizing input/task epoch, source versions, requirement/acceptance IDs, artifact roles, ordered stage dependencies, designated review roles, verifier requirements, and allowed delivery scope. Its runtime status is derived from workboard records and accepted receipts. Revisions are immutable, with a current accepted reference attached to existing durable task state. This pointer must be part of the same accepted boundary as workboard scope; it cannot live only in a prompt.

The minimal artifact roles are research findings, research synthesis, requirements/acceptance, design decision, implementation handoff, review, and integrated verification. Not every feature needs every role or three researchers. A returned artifact contains its exact source refs and versions, findings/limitations, unresolved questions, and the decision it enables. A review additionally names the reviewed hash, reviewer identity, disposition and finding IDs. An integration receipt names the combined tree/source revision and the exact acceptance receipts. Stage readiness is computed from those declarations and verified evidence.

| Candidate work order | Narrow changes | Acceptance and recovery cases |
|---|---|---|
| R1 — Feature research plan contract | Add a strict profile/plan schema using existing feature, assertion, source and workboard identities. Compile it into todo/workboard leaves and existing graph projections. Reuse mission coverage concepts without trusting its mutable passing flags. No generic new DAG runner. | Unknown/duplicate IDs, cycles, missing acceptance owners and cross-epoch refs rejected; same plan replay creates no duplicate cards; existing tasks without this profile behave unchanged. |
| R2 — Research and artifact review delegation | Add role-specific bounded briefs and typed artifact/review returns on the existing delegation boundary. Allocate output paths by task/epoch/card identity. Store full bodies in CAS; attach accepted refs to workboard evidence. | Partial/failed researcher returns preserve useful evidence and missing work; fabricated refs and wrong reviewed hash rejected; worker cannot self-verify; timeout remains pending/blocked; exact revised artifact requires fresh review. |
| R3 — Stage admission and integrated proof | Derive ready waves from existing verified prerequisites. Compile explicitly declared review/integration acceptance into CompletionReadiness constraints and canonical verifier requirements. Admit tools through normal profiles/lifecycle; use the current workboard scheduler. | Implementation does not start before required design/research acceptance; worker-local test success cannot satisfy a different integrated revision; a later mutation/failing check invalidates pass; completed-but-unreviewed cannot satisfy required review; independent ready leaves still progress. |
| R4 — Durable resume and long-horizon projection | Persist the accepted plan reference and phase receipt alongside safe task checkpoints; reconstruct frontier from workboard+receipts; add stage summary to existing graph/trajectory context. Link new runs to the explicit continued objective rather than treating the prior handoff as live authority. | Crash before/after claim, result and stage acceptance; partial artifact writes; failed flush; pending child on restart; stale generation result; repeated same text in a newer epoch; explicit replacement; bounded context compaction preserves authority+artifact refs. No automatic replay of ambiguous mutation. |

Implement R1 first as a pure contract/compiler and production admission hook, with one hermetic path through the actual runner. R2 can then use that path for a synthetic three-stream research return and review. R3 must prove the integration boundary in the normal and brute-force loops. R4 completes restart and compaction coverage before claiming support for extremely long tasks. Keep workorders local until any external delivery is authorized; root consolidation assigns final numbers and ownership.

The decisive regression scenario is one feature across several simulated runs: incomplete research → accepted revised specification → two independent implementations → failed combined acceptance → scoped repair → integrated pass → evidence-backed handoff. Interrupt during a child operation and replace the objective in a separate case. Assert that only the current epoch's declared obligations control admission/completion, accepted work is not repeated, unresolved work remains visible, and no amount of narration or checkpoint counters can substitute for the required receipts.

## Validation performed for this research note

Inspected installed AIWG primary bodies and named references through discover/show, and mapped them against Omnius types, transition functions, persistence boundaries, production references and existing design documentation. No execution tests were needed for a documentation-only proposal. Runtime guarantees above are limited to the cited code paths; no claim is made that the proposed feature profile already exists or that the uninspected AIWG service implementation has been verified.
