can-you-assist/history/2026-05-28-CYA-Intent-Scope-Gap-Analysis-Post-0005.md

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

Date: 2026-05-28
Repo: can-you-assist
Workplan: CYA-WP-0005 (completed)
Previous Analysis: 2026-05-28 (Post 0004)
Author: Grok

Executive Summary

Since the May 28 analysis (post-0004), the major workplan CYA-WP-0005: Agentic Memory Profiles and phase-memory Interface Optimization has been completed via ralph loop.

Key deliveries:

• Formal Profile 0 baseline (post-0003 local JSON + kinds + activation_context + provenance + retrospection) explicitly documented as the stable foundation.
• Complete profile model: detailed definitions, cya integration plans, and a Capability Matrix for Profiles 1–3 (Reflexion verbal, hierarchical synthesis, procedural/meta-policy evolution).
• First delivered self-improving capability: minimal but working Profile 1 (Reflexion-style verbal reflections/lessons) spike — remember_reflection() + KIND_REFLECTION, optional "capture verbal lesson" step inside cya retrospect, preferential activation, and surfacing in responses / --explain-context.
• Finalized the docs/phase-memory-optimization-suggestions.md handoff artifact for the sister repo.

Overall Assessment: Very strong progress on the most important remaining gap from INTENT.md — the "Personalized Console Helper" that improves over time through user-controlled memory. The memory & longitudinal adaptation gap has moved from "Small-Medium" to "Small". The project now has both the conceptual framework (profiles) and a concrete first implementation (Profile 1 verbal loop) that directly addresses INTENT's vision of longitudinal adaptation via user-steerable memory.

Remaining gaps are now primarily about depth (richer context understanding, deeper phase-memory integration for Profiles 2/3, procedural evolution) rather than missing foundational mechanisms.

Strong Alignments (Updated)

Area	INTENT.md Position	Current Reality (Post-0005)	Assessment
Console-native experience	Foundational	Excellent	Strong match
Safety & mandatory confirmation	Important	Core behavior + memory-aware (reflections can force confirmation)	Exceeded
Explainability & transparency	Strong requirement	Very strong (provenance everywhere, reflections surfaced explicitly, --explain-context)	Strong
Backend agnosticism	Must use llm-connect seam	Clean LLMAdapter Protocol + Fake	Excellent
User-controlled memory	Central principle	Real + now architected with explicit profiles (0 baseline + 1–3 roadmap)	Major improvement
Longitudinal adaptation	Personalized helper that improves over time	cya retrospect + automatic activation + first working self-improvement loop (Profile 1)	Significantly better
Packaging & distribution	Not heavily emphasized	Dev-head install + release process first-class	Major positive shift
Clear boundaries	cya / llm-connect / phase-memory separation	Explicit ports + MemoryVision contract + phase-memory feedback doc	Good
Profile-driven / self-improving behavior	Strong vision in "Personalized Console Helper"	Full model (T03) + first implementation (T05)	New major strength

Key Gaps (Post-0005)

1. Memory & Longitudinal Adaptation — Now a Clear Strength with Clear Next Steps

Previous Status (Post-0004): Small-Medium. Good activation + retrospection loop, but still passive local JSON with limited self-improvement.

Current Status (Post-0005):

• Explicit Profile 0 baseline documented as the shipped foundation.
• Complete Profiles 1–3 model with cya-specific mappings and Capability Matrix (T03).
• Profile 1 (Reflexion verbal) is not just designed — a working spike is shipped: verbal lessons can be captured during cya retrospect, stored with dedicated kind, preferentially activated, and surfaced to the user.
• Strong explainability and user control preserved.

Remaining Sub-Gaps (now much smaller and more targeted):

• Profile 1 is still a minimal spike (capture step + basic activation). Production hardening, better UX, and compaction of reflections would be natural follow-on work.
• Profiles 2 (hierarchical synthesis) and 3 (procedural/meta-policy) remain design + research artifacts. No implementation yet (explicitly registered as debt in 0005).
• Full wiring to phase-memory planners, graph store, and lifecycle rules is still future work (as intended).

Assessment: Large positive movement. The core INTENT vision of a user-controlled assistant that "improves over time" now has both architecture and a concrete first capability. This was the single largest gap for most of the project's history.

2. Depth of Local Context Understanding

INTENT.md envisions rich assistance with code repositories, notes, project structures, and conventions.

Current State:

• Context collector remains intentionally shallow (top-level entries + basic git).
• Memory (especially the new Profile 1 verbal lessons + user-declared retrospection goals) helps significantly with user-taught project conventions and patterns.
• No automatic deep semantic understanding, embeddings, or large-scale repository analysis.

Assessment: Still a medium gap. The memory/profile work makes the user far more effective at bringing rich context into the assistant, but the system itself does not yet deeply understand repositories or notes on its own. This is consistent with original scope boundaries.

3. One-Shot vs Rich Longitudinal Value

INTENT.md: Strong vision of the assistant becoming more useful over time through memory of habits, conventions, and recurring workflows.

Current Reality (Post-0005):

• Users can teach the system via normal use + explicit cya retrospect.
• Directory/project-bound activation + the new verbal reflection mechanism create a real, usable self-improvement loop.
• Profile model provides a clear roadmap for richer future behavior (synthesis, procedural rules).

Assessment: Significantly improved. The basic mechanism for longitudinal, user-controlled adaptation now exists and is demonstrable with Profile 1. Richer automatic pattern learning and procedural evolution (Profiles 2/3) remain the natural next deepening.

4. Packaging & Distribution — Remains Strong

No regression. Still first-class with documented process.

5. Safety & Explainability — Continued Strength

Remains excellent. The new Profile 1 reflections flow through the same rule-based RiskClassifier and are fully visible in --explain-context.

Summary Table (Updated)

Gap Area	Severity (Post-0002)	Severity (Post-0004)	Severity (Post-0005)	Trend	Notes
Memory & Longitudinal Adaptation	Medium	Small-Medium	Small	Major improvement	Profile model + first working self-improvement loop (Profile 1)
Depth of Context Understanding	Medium-Large	Medium	Medium	Stable / slight improvement via user memory	Collector still shallow; user memory helps
Packaging & Distribution	Medium (gap)	Small	Small	Stable	Remains first-class
Safety & Explainability	Positive	Positive	Positive	Stable	Remains a core strength
One-shot vs Rich Longitudinal	Medium	Small	Small	Stable / improved	Real loop exists; richer synthesis is future work

Recommendations

1. Continue the memory evolution roadmap as documented in CYA-WP-0005 and MemoryVision.md:

   • Production-harden Profile 1 (better capture UX, reflection compaction, more surfacing).
   • Begin exploration spikes for Profile 2 (synthesis) when ready.
   • Treat Profile 3 (procedural) as higher-risk / higher-reward and keep strong guardrails.

2. Deepen phase-memory coordination using the finalized docs/phase-memory-optimization-suggestions.md. The 9 categories (especially synthesis planner hooks, procedural support, and dry-run proposal semantics) are now well-scoped asks.

3. Consider whether "Context Depth" becomes a first-class work item. If richer automatic understanding of repositories/notes is desired, it will likely need its own focused slice (separate from the memory/profile work).

4. Keep the seam discipline. The explicit ports, activation model, and safety integration from 0002/0003/0005 remain excellent boundaries. Future work should extend rather than bypass them.

5. Packaging follow-through (unchanged from prior analysis): move the registered debt items (CI gate, PyPI workflow, automation) forward when capacity allows.

Conclusion

CYA-WP-0005 has delivered the single most important conceptual and practical advance since the memory integration work of 0002/0003. The project now has:

• An explicit, documented profile model that directly maps to INTENT's vision of longitudinal adaptation.
• A working, user-visible first self-improving capability (Profile 1 verbal reflections).

The product is now substantially closer to the "Personalized Console Helper" described in INTENT.md than at any previous point. The remaining gaps are about evolving and deepening capabilities that now have clear architectural homes, rather than about missing foundational pieces.

This is a strong position from which to plan the next phase of work.

---

Related Documents

• Previous analysis: history/2026-05-28-CYA-Intent-Scope-Gap-Analysis-Post-0004.md
• Research foundation: history/2026-05-28-CYA-Agentic-Memory-Research-Variations.md
• Memory vision & profile model: MemoryVision.md
• Recent workplan: workplans/CYA-WP-0005-agentic-memory-profiles-and-phase-memory-feedback.md
• Current SCOPE.md (updated as part of this assessment)
• phase-memory feedback: docs/phase-memory-optimization-suggestions.md