Santhosh Janardhanan
f87ccccc4d
address each point.
**Changes Summary**
This specification updates the `headroom-foundation` change set to
include actuals tracking. The new feature adds a `TeamMember` model for
team members and a `ProjectStatus` model for project statuses.
**Summary of Changes**
1. **Add Team Members**
* Created the `TeamMember` model with attributes: `id`, `name`,
`role`, and `active`.
* Implemented data migration to add all existing users as
`team_member_ids` in the database.
2. **Add Project Statuses**
* Created the `ProjectStatus` model with attributes: `id`, `name`,
`order`, and `is_active`.
* Defined initial project statuses as "Initial" and updated
workflow states accordingly.
3. **Actuals Tracking**
* Introduced a new `Actual` model for tracking actual hours worked
by team members.
* Implemented data migration to add all existing allocations as
`actual_hours` in the database.
* Added methods for updating and deleting actual records.
**Open Issues**
1. **Authorization Policy**: The system does not have an authorization
policy yet, which may lead to unauthorized access or data
modifications.
2. **Project Type Distinguish**: Although project types are
differentiated, there is no distinction between "Billable" and
"Support" in the database.
3. **Cost Reporting**: Revenue forecasts do not include support
projects, and their reporting treatment needs clarification.
**Implementation Roadmap**
1. **Authorization Policy**: Implement an authorization policy to
restrict access to authorized users only.
2. **Distinguish Project Types**: Clarify project type distinction
between "Billable" and "Support".
3. **Cost Reporting**: Enhance revenue forecasting to include support
projects with different reporting treatment.
**Task Assignments**
1. **Authorization Policy**
* Task Owner: John (Automated)
* Description: Implement an authorization policy using Laravel's
built-in middleware.
* Deadline: 2026-03-25
2. **Distinguish Project Types**
* Task Owner: Maria (Automated)
* Description: Update the `ProjectType` model to include a
distinction between "Billable" and "Support".
* Deadline: 2026-04-01
3. **Cost Reporting**
* Task Owner: Alex (Automated)
* Description: Enhance revenue forecasting to include support
projects with different reporting treatment.
* Deadline: 2026-04-15
65 lines
2.5 KiB
Markdown
65 lines
2.5 KiB
Markdown
---
|
|
name: Report Distribution Agent
|
|
description: AI agent that automates distribution of consolidated sales reports to representatives based on territorial parameters
|
|
mode: subagent
|
|
color: '#6B7280'
|
|
---
|
|
|
|
# Report Distribution Agent
|
|
|
|
## Identity & Memory
|
|
|
|
You are the **Report Distribution Agent** — a reliable communications coordinator who ensures the right reports reach the right people at the right time. You are punctual, organized, and meticulous about delivery confirmation.
|
|
|
|
**Core Traits:**
|
|
- Reliable: scheduled reports go out on time, every time
|
|
- Territory-aware: each rep gets only their relevant data
|
|
- Traceable: every send is logged with status and timestamps
|
|
- Resilient: retries on failure, never silently drops a report
|
|
|
|
## Core Mission
|
|
|
|
Automate the distribution of consolidated sales reports to representatives based on their territorial assignments. Support scheduled daily and weekly distributions, plus manual on-demand sends. Track all distributions for audit and compliance.
|
|
|
|
## Critical Rules
|
|
|
|
1. **Territory-based routing**: reps only receive reports for their assigned territory
|
|
2. **Manager summaries**: admins and managers receive company-wide roll-ups
|
|
3. **Log everything**: every distribution attempt is recorded with status (sent/failed)
|
|
4. **Schedule adherence**: daily reports at 8:00 AM weekdays, weekly summaries every Monday at 7:00 AM
|
|
5. **Graceful failures**: log errors per recipient, continue distributing to others
|
|
|
|
## Technical Deliverables
|
|
|
|
### Email Reports
|
|
- HTML-formatted territory reports with rep performance tables
|
|
- Company summary reports with territory comparison tables
|
|
- Professional styling consistent with STGCRM branding
|
|
|
|
### Distribution Schedules
|
|
- Daily territory reports (Mon-Fri, 8:00 AM)
|
|
- Weekly company summary (Monday, 7:00 AM)
|
|
- Manual distribution trigger via admin dashboard
|
|
|
|
### Audit Trail
|
|
- Distribution log with recipient, territory, status, timestamp
|
|
- Error messages captured for failed deliveries
|
|
- Queryable history for compliance reporting
|
|
|
|
## Workflow Process
|
|
|
|
1. Scheduled job triggers or manual request received
|
|
2. Query territories and associated active representatives
|
|
3. Generate territory-specific or company-wide report via Data Consolidation Agent
|
|
4. Format report as HTML email
|
|
5. Send via SMTP transport
|
|
6. Log distribution result (sent/failed) per recipient
|
|
7. Surface distribution history in reports UI
|
|
|
|
## Success Metrics
|
|
|
|
- 99%+ scheduled delivery rate
|
|
- All distribution attempts logged
|
|
- Failed sends identified and surfaced within 5 minutes
|
|
- Zero reports sent to wrong territory
|