chore(repo): checkpoint current capakraken implementation state

2026-03-29 12:47:12 +02:00
parent beae1a5d6e
commit 47e4d701ff
94 changed files with 4283 additions and 1710 deletions
@@ -6,7 +6,7 @@

 ## Problem

-The bi-weekly chargeability report is currently produced in Excel. Planarchy needs a **live reporting section** in the app that updates in real-time as assignments, resources, and SAH change. The report is not a static file — it is an interactive page that can be **exported** as Excel or PDF on demand.
+The bi-weekly chargeability report is currently produced in Excel. CapaKraken needs a **live reporting section** in the app that updates in real-time as assignments, resources, and SAH change. The report is not a static file — it is an interactive page that can be **exported** as Excel or PDF on demand.

 Core requirements:

@@ -98,7 +98,7 @@ SUM(resource.fte * resource.bdPercentage[month])

 ## Data Requirements

-### What Planarchy needs to have (per resource, per month)
+### What CapaKraken needs to have (per resource, per month)

 | Data Point | Source | Notes |
 |---|---|---|
@@ -114,7 +114,7 @@ SUM(resource.fte * resource.bdPercentage[month])

 ### Forecast Chargeability Derivation

-This is the key insight: **predicted chargeability can be derived from what Planarchy already knows**:
+This is the key insight: **predicted chargeability can be derived from what CapaKraken already knows**:

 ```
 forecastChg(resource, month) =
@@ -133,7 +133,7 @@ This means the chargeability report is a **query over existing assignments + SAH
 For historical data, two options:

 1. **Import from SAP**: bulk import of period data (P-1, P-2, etc.) as snapshots
-2. **Track in-app**: if Planarchy becomes the system of record for time tracking
+2. **Track in-app**: if CapaKraken becomes the system of record for time tracking

 Recommendation: Start with SAP import. Add a `ChargeabilitySnapshot` model for imported actuals.