Future Trajectory

Roadmap

Weaver's development follows a phased plan: foundations and the safety harness first, then the ADR 007 command-surface reset, then the query, change, and agent-workflow slices built on it. Items marked Planned are not implemented yet; scope and timing may shift.

Foundations: built (daemon, LSP hosting, Tree-sitter, sandbox, Double-Lock, patch application)
Now: the command-surface reset (ADR 007) and introspection slice

Phase Progress

Foundations & safety harness
Built
12
Command-surface reset (ADR 007)
Active
13
Introspection & discoverability
Active
14
Code-reading loop
Planned
15
Sempai query-to-selector slice
Planned
16
Safe change loop
Planned
17
Graph slices & history (Jacquard)
Planned
19
Agent workflow & assurance
Planned
1

Near Term

Phases 12–14: Reset, Introspection, and the Reading Loop

In Progress

Command-Surface Reset

Phase 12

Rebuilding the public grammar around weaver <resource> <verb> per ADR 007: one localized human renderer, one stable --json contract, capability-first routing with providers out of sight, and the prototype observe/act/verify surface retired without compatibility.

  • Contract and grammar decided (ADR 007)
  • Dual renderers on every command
  • Bounded lists with cursors
  • Non-interactive by default
In Progress

Introspection & Discoverability

Phase 13

weaver context --json emits the whole contract as data; capabilities list explains provider selection; help, manpages, and completions generate from the same source with CI drift gates. Errors follow one template: problem, valid alternatives, next command.

Planned

The Code-Reading Loop

Phase 14

definitions get, references list, and diagnostics list in the new grammar, then cards get: compact symbol cards with bounded one-hop relation summaries, detail levels, and cache provenance.

2

Mid Term

Phases 15–17: Query, Change, and Graph Slices

Planned

Sempai Query-to-Selector Slice

Phase 15

The first executable query loop: symbols list with --query, --expr, and --rule inputs, emitting versioned weaver.selector.v1 streams over Rust, Python, and TypeScript through the labelled weaver-syntax-compat-v1 adapter. RFC 0003, plateaus A–D.

Planned

Safe Change Loop

Phase 16

One shared mutation engine behind patches apply, symbols rename, and symbols move: selector-stream intake, stale-source refusal, staged formatting, Double-Lock verification, restart-surviving idempotency, and classified diagnostics deltas. The same selectors that answer questions drive safe change.

Planned

Jacquard: Cards-First Symbol Context

Phase 17

Small, structured "symbol cards" and bounded graph slices exposed as cards get and graph-slices get. Cards carry signature, doc comments, decorators, and LSP-enriched metadata. Graph slices use typed edges (call, import, config) with explicit budgets (max_cards, max_edges, max_estimated_tokens). History diffs over recent commits use probabilistic symbol matching.

cards get graph-slices get Budgeted Traversal JSONL
3

Long Term

Directional — scope and timing subject to change

Interactive Approval Mode

An explicit --interactive flow (or dedicated review command) that presents lock-failure diffs and diagnostics for human approval before writes continue. Non-interactive environments fail closed – prompts are never implicit.

Directional

Project Onboarding

A future weaver project onboard command that orchestrates existing Weaver components to generate a deterministic PROJECT.dna summary artefact from repository metadata and analysis outputs.

Directional

Agent Workflow & Assurance

Phase 19: saved profiles with strict precedence, a durable jobs ledger with --wait and submit-poll-collect recovery, delivery sinks (stdout, file:, webhook:), and structured feedback from agents back to the project.

Phase 19

Editor Integration

Native editor plugins (VS Code, IntelliJ) that surface Weaver's read and verification surfaces in the editor UI. Currently a future goal – Weaver integrates with language servers but does not yet ship its own editor extensions.

Directional

Help Shape the Future

Weaver is open source and the roadmap is driven by what agent builders actually need. Discord is not live yet – GitHub issues are the front door until the public channel opens.