can-you-assist/history/2026-05-26-CYA-Intent-Scope-Gap-Analysis.md

Gap Analysis: INTENT.md vs SCOPE.md (Post CYA-WP-0001 MVP)

Date: 2026-05-26
Repo: can-you-assist
Workplan: CYA-WP-0001 (completed)
Author: Grok (in ralph loop)

Executive Summary

The original INTENT.md describes an ambitious, long-term vision for a personalized, memory-aware, console-native LLM assistant with strong user control and adaptation over time.

The current SCOPE.md (updated after the MVP slice) and the delivered implementation (T01–T08) are much narrower and more disciplined. This is largely healthy and intentional, but creates several significant gaps against the original intent — particularly around memory and longitudinal value.

Strong Alignments

Area	INTENT.md Position	Current Reality (SCOPE + Implementation)	Assessment
Console-native experience	Foundational	Excellent (Typer + rich, one-shot + explain)	Strong match
Safety & confirmation	Important (explicit confirmation)	Core product behavior (rule-based + mandatory)	Exceeded intent
Explainability & transparency	Strong requirement	Very well delivered (--explain-context, provenance)	Strong match
Backend agnosticism	Must route through llm-connect	Clean LLMAdapter Protocol + Fake (zero bypass)	Excellent
Clear repo boundaries	cya / llm-connect / phase-memory separation	Clearly documented and implemented	Very good
User control	Central principle	Respected (especially memory ports)	Good

Key Gaps

1. Memory & Adaptation (Largest Divergence)

INTENT.md repeatedly positions memory as central to long-term value:

• "keep the memory, history, preferences, and adaptation under the user’s control"
• The tool should "become more useful through memory"
• Support for recurring workflows, project-specific memory, learned patterns, preferences over time
• Explicit relationship to phase-memory as a first-class partner

Current SCOPE / Delivered:

• T05 deliberately implemented the thinnest possible no-op ports only.
• No accumulation of value across sessions.
• Real adaptation, recipes, project profiles, etc. are future work.

Gap Type: Intentional narrowing for the first slice, but this is the biggest deviation from the spirit of the original intent. The memory story is currently the weakest link relative to INTENT.

2. Depth of Local Context Understanding

INTENT.md envisions rich assistance with:

• Code repositories ("where is the CLI entry point?", "suggest a safe first refactoring")
• Local notes and knowledge work
• Project structures and conventions

Current Implementation:

• Context collector is intentionally shallow (top-level entries only, no recursion, minimal git understanding beyond basic status).

Gap Type: Medium to large. The tool currently functions more as a "safe, context-aware command suggester" than a deep repository or knowledge assistant.

3. One-Shot vs Longitudinal Value

INTENT.md:

• Strong emphasis on the assistant learning the user's habits, conventions, aliases, and recurring patterns over time.
• "Personalized console helper"

Current Reality:

• The MVP is almost entirely one-shot (with optional context explanation).
• Very little mechanism yet for the assistant to improve for a specific user or project across uses.

Gap Type: Large. This is one of the core long-term differentiators described in INTENT.

4. Safety Implementation (Positive Gap)

INTENT.md: Safety and confirmation are mentioned but relatively lightly sketched.

Current SCOPE: Genuine rule-based assessment as the primary mechanism, with structured output designed to be fed to the LLM, plus mandatory confirmation. This is more mature and product-like than the original intent.

Assessment: Positive. The current implementation strengthened this area beyond the initial vision (per explicit operator direction during stack review).

5. Test Coverage and Trust

• INTENT implies the tool must be trustworthy for real daily workflows.
• T07 delivered solid safety-invariant and collector tests.
• However, full orchestrator + adapter contract testing and end-to-end scenarios are still relatively light compared to what long-term trust would require.

Summary Table

Dimension	INTENT Ambition	Current SCOPE Reality	Gap Size	Nature
Memory & Adaptation	Central long-term differentiator	Minimal explicit no-op ports only	Large	Intentional narrowing
Depth of context	Repository + notes understanding	Shallow top-level collector	Medium-Large	Scope control
Longitudinal value	Learns workflows over time	Strong one-shot experience	Large	Future work
Safety	Important	Core rigorous product behavior	Positive	Exceeded
Boundaries & seams	Clear separation	Very clearly defined + implemented	Small	Well aligned
Console-native + explainable	Strong	Strongly delivered	Small	Well aligned

Recommendations

1. Keep the narrow SCOPE for the near term — it is healthy and prevents scope creep.

2. Memory Integration Roadmap — The single most important piece of future work to align with INTENT. Consider creating a dedicated MemoryVision.md (or similar) that bridges the current thin ports to the richer phase-memory concepts (profiles, phases, activation planning, etc.).

3. Depth vs Breadth Tradeoff — Decide explicitly whether the next slices should deepen context understanding (better git + file understanding) or prioritize the memory story.

4. Elevate Safety — The current rule-based safety layer is one of the project's strongest differentiators. It may deserve more prominent treatment in both INTENT and SCOPE over time.

5. Test Maturity — As we move beyond the first slice, T07-style safety tests should be complemented by stronger contract and orchestrator tests to support the trust claims in INTENT.

---

Source Documents:

• Original INTENT.md
• Updated SCOPE.md (post CYA-WP-0001)
• CYA-WP-0001-console-native-mvp.md (especially Non-Goals and T05/T08)
• Delivered implementation (src/cya/memory, safety, orchestrator, etc.)

This analysis was generated as part of closing the first ralph-workplan loop.