[AGENT] LT-010: Offline Fallback & Template Registry Integration

[ucguy4u]

Agent

Agent: agent/core-architecture (Framework Agent)

Task Details

Estimate (hours): 4
Priority: P1
Parent: #331

Description

Provide a fallback strategy for custom goal creation when the network is offline or the local LLM fails to run.

Fallback Logic

1. Keyword Matcher: Analyze user prompt strings for keywords matching existing bundled templates (e.g. prompt contains "house" or "flat" → RERA checklist; "doctor" or "operation" → Medical checklist; "college" or "university" → Admission checklist).
2. Template Match recommendation: Prompt user: "You're offline, but we found a similar local template. Would you like to use this instead?".

Critical Agent Gate

Problem: The app will throw errors during custom track creation when offline or when LLM model execution fails.
User / actor: End user experiencing network issues or low-resource device states.
Framework or application layer: Framework (core_data/registry)

Acceptance Criteria

• Offline status detector in blueprint generator use case
• Keyword matching dictionary mapping keywords → template IDs
• Fallback redirection flow returning template recommendations
• Unit tests for keyword matching logic (covering edge cases/synonyms)
• flutter analyze clean

[ucguy4u]

Checked against current main on 2026-06-29 from a fresh worktree based on origin/main (60b1d13). The repository now has bundled LifeTrack templates and a local template registry, but it still does not have the blueprint-generator/custom-track creation use case referenced by this ticket. I could not find an existing offline detector, prompt-to-blueprint pipeline, or fallback recommendation flow to extend.\n\nWhat exists today:\n- bundled template assets and validation in \n- LifeTrack template/domain entities in \n- local persistence/hydration in \n\nWhat is still missing for this issue:\n- the blueprint generator use case that would detect offline/LLM failure\n- the prompt-to-template fallback contract returned to the caller/UI\n- the app/domain entrypoint for custom goal creation where the redirection prompt would actually be surfaced\n\nBecause those seams are not present on main yet, this is not a low-effort close from the current codebase. Skipping for now rather than landing a framework-only partial that would not satisfy the acceptance criteria.

[ucguy4u]

Checked against current main on 2026-06-29 from a fresh worktree based on origin/main (60b1d13). The repository now has bundled LifeTrack templates and a local template registry, but it still does not have the blueprint-generator/custom-track creation use case referenced by this ticket. I could not find an existing offline detector, prompt-to-blueprint pipeline, or fallback recommendation flow to extend.

What exists today:

• bundled template assets and validation in packages/core_data/lib/src/storage/templates/template_registry.dart
• LifeTrack template/domain entities in packages/core_domain/lib/src/entities/life_track_template.dart
• local persistence/hydration in packages/core_data/lib/src/storage/life_track_local_data_source.dart

What is still missing for this issue:

• the blueprint generator use case that would detect offline/LLM failure
• the prompt-to-template fallback contract returned to the caller/UI
• the app/domain entrypoint for custom goal creation where the redirection prompt would actually be surfaced

Because those seams are not present on main yet, this is not a low-effort close from the current codebase. Skipping for now rather than landing a framework-only partial that would not satisfy the acceptance criteria.

[ucguy4u]

Critical Agent Gate

Problem: LifeTrack has bundled templates but no deterministic fallback when custom blueprint generation is unavailable offline or fails locally, so custom-goal setup cannot degrade gracefully.
User / actor: End users creating a custom LifeTrack goal while offline or while the local LLM runtime is unavailable.
Framework or application layer: Mixed, centered on framework-owned template matching plus a small domain use-case contract for callers.
Owning agent: Framework Agent.
Reviewing agents: Brain / AI Agent, QA Automation Agent.
Impacted modules/files: packages/core_domain/lib/src/use_cases/*, packages/core_data/lib/src/storage/templates/*, related tests.
Base branch/worktree: confirmed from latest origin/main: yes (1e213f9b926539513c1f7607d432cc04125e7505).
Open questions: UI prompt wiring is still downstream; this slice will return deterministic fallback recommendations to the caller instead of adding screen code.
Decision: Ready.

Cross-Agent Contract

Provider agent: Framework/template registry layer.
Consumer agent: Brain/custom-goal creation flow.
Interface/API: free-form goal prompt + generation availability/failure state -> fallback recommendation result.
Input shape: prompt text, offline/failure reason, bundled template catalog.
Output shape: recommended template match or explicit no-match result with reason metadata.
State changes: read-only.
Errors: empty prompt, unavailable registry, no keyword match.
Permissions: none beyond local bundled template access.
Privacy/redaction: prompt stays local; no network call in this slice.
Persistence: none.
Versioning/migration: additive only.
Tests required: keyword matching coverage, synonym/normalization coverage, no-match behavior, offline/failure result mapping.

Deterministic Use Cases / Automation Flow

1. Given a prompt like "I need help buying a flat", the fallback returns the bundled real-estate template recommendation.
2. Given a prompt like "doctor operation paperwork", the fallback returns the medical template recommendation.
3. Given a prompt with no known keywords, the fallback returns an explicit no-match result instead of guessing.
4. Callers can distinguish offline/unavailable generation failures from template-match outcomes without invoking a model.