Post-V1 Features and Considerations¶
Features deferred from V1 release for post-go-live implementation
Created: 2024-12-31
Related Documents¶
| Document | Purpose |
|---|---|
| backlog.md | Current V1 priorities |
| ROADMAP.md | Future feature roadmap |
| USER_STORIES.md | Full story definitions |
Overview¶
V1 focuses on back-office AI companion functionality for staff use. The features below are client-facing or integration-heavy capabilities deferred until post-go-live to reduce V1 complexity and risk.
Deferred Features¶
1. Advanced Identity Verification (S2-003)¶
User Stories: INT-012, INT-013, INT-014, IDV-001 through IDV-005
Description: Multi-tier identity verification for client portal access: - Tier 2: Phone verification via SMS/voice codes - Tier 3: Government ID document upload with Persona.com integration
Why Deferred: V1 is staff-only (back-office companion). Client portal access and self-service identity verification are not needed until client-facing features are enabled.
Database Tables (not in V1 schema): - phone_verification - SMS/voice verification codes - id_document - Government ID uploads and extraction - persona_inquiry - Persona.com inquiry results and confidence scores
Production Code (exists but dormant): - src/repositories/identity_verification_repository.py (PhoneVerificationRepository, IDDocumentRepository, PersonaInquiryRepository) - src/workflows/intake/identity_verification.py - src/services/persona_service.py
Go-Live Considerations: - Persona.com account setup and API credentials - SMS provider integration (Twilio or similar) - Client portal authentication flow - Privacy policy updates for biometric data (selfie matching)
2. Engagement Letter Process (S3-001, S3-002)¶
User Stories: ENG-001 through ENG-008
Description: Automated engagement letter generation and e-signature: - Template management with versioning - Dynamic fee calculation from fee schedules - E-signature integration (Google Workspace) - Engagement status tracking
Why Deferred: V1 uses existing engagement letter process. Automation adds complexity without immediate V1 value since staff already have established workflows.
Database Tables (not in V1 schema): - engagement_template - Letter templates with fee schedule links
Note: fee_schedule and consent tables ARE included in V1 for invoicing and Form 7216 compliance.
Production Code (exists but dormant): - src/repositories/engagement_repository.py (EngagementTemplateRepository) - src/workflows/intake/engagement_workflow.py - src/services/template_service.py
Go-Live Considerations: - Template content creation and legal review - Fee schedule configuration - Google Workspace e-signature setup - Client notification preferences
3. SmartVault Integration (S4-005)¶
User Stories: DOC-020 through DOC-025
Description: Bidirectional document sync with SmartVault: - Inbound: Poll for new client uploads - Outbound: Push completed returns - Sync status tracking per client
Why Deferred: V1 uses drag-drop upload and folder import. SmartVault integration adds external dependency and complexity. Clients continue using SmartVault directly; staff manually import as needed.
Database Tables (not in V1 schema): - smartvault_sync_status - Last sync timestamps per client - smartvault_export - Document export tracking
Production Code (exists but dormant): - src/workflows/documents/smartvault_sync_workflow.py - src/services/smartvault_service.py
Go-Live Considerations: - SmartVault API credentials and OAuth setup - Folder structure conventions (per-client, per-year) - Sync scheduling (business hours, frequency) - Conflict resolution for duplicate documents - Client notification of sync status
Implementation Priority (Post-V1)¶
| Priority | Feature | Rationale |
|---|---|---|
| P1 | SmartVault Integration | Reduces manual document import burden |
| P2 | Engagement Letter Process | Streamlines onboarding |
| P3 | Advanced Identity Verification | Enables client self-service portal |
Schema Notes¶
When implementing these features, add the corresponding tables to DATABASE_SCHEMA.sql. Table definitions are preserved in git history (commit before TD-020 schema unification) and in this document's linked user stories.
For V1 scope and current priorities, see backlog.md