Scope: medium Risk: medium Spec: partial Type: feature
Summary: ANALYTICS-002: Cost Tracking Per User
Suggestion: needs investigation
Rationale:

Action: Review each blocking factor above. Remove blocked:needs-decision label to route back to triage.

## ⏸ Needs Decision **Blocking factors:** - **Didn't meet auto-approve criteria** — scope=medium, risk=medium, spec=partial --- **Scope:** medium **Risk:** medium **Spec:** partial **Type:** feature **Summary:** ANALYTICS-002: Cost Tracking Per User **Suggestion:** needs investigation **Rationale:** **Action:** Review each blocking factor above. Remove `blocked:needs-decision` label to route back to triage.

Mark commented

2026-05-28 12:21:37 +00:00

Author

Owner

⏸ Needs Decision

What needs to be decided?

Is this issue still relevant? If yes, remove the blocked:needs-decision label to route back to triage.

Blocking factors:

Didn't meet auto-approve criteria — scope=small, risk=low, spec=partial

Scope: small Risk: low Spec: partial Type: feature
Summary: Add per-user cost attribution and aggregation tracking to attribute intent/resource costs to the submitting user identity.
Suggestion: Source user_id from existing intent payload (submitter/requester field), add get_user_cost_summary() to MeshLedger aggregating cost_audit by user, and extend MetabolicTracker with user-level cost tracking. No schema migration needed if user_id is extracted from payload.
Rationale: Small scope because it's purely additive data tracking on existing fields (cost_audit, payload) with no routing/execution changes. Low risk because it touches zero critical paths — just new queries and tracking. Partial spec alignment because resource-metabolism.md covers per-intent cost attribution but doesn't mention per-user rollups; the concept is architecturally consistent but not documented.

To unblock: Remove the blocked:needs-decision label. The triage will apply the appropriate outcome based on your choice above.

## ⏸ Needs Decision **What needs to be decided?** - **Is this issue still relevant?** If yes, remove the `blocked:needs-decision` label to route back to triage. **Blocking factors:** - **Didn't meet auto-approve criteria** — scope=small, risk=low, spec=partial --- **Scope:** small **Risk:** low **Spec:** partial **Type:** feature **Summary:** Add per-user cost attribution and aggregation tracking to attribute intent/resource costs to the submitting user identity. **Suggestion:** Source user_id from existing intent payload (submitter/requester field), add get_user_cost_summary() to MeshLedger aggregating cost_audit by user, and extend MetabolicTracker with user-level cost tracking. No schema migration needed if user_id is extracted from payload. **Rationale:** Small scope because it's purely additive data tracking on existing fields (cost_audit, payload) with no routing/execution changes. Low risk because it touches zero critical paths — just new queries and tracking. Partial spec alignment because resource-metabolism.md covers per-intent cost attribution but doesn't mention per-user rollups; the concept is architecturally consistent but not documented. **To unblock:** Remove the `blocked:needs-decision` label. The triage will apply the appropriate outcome based on your choice above.

Mark added the

blocked:preflight

label

2026-07-31 04:26:45 +00:00

Mark commented

2026-08-11 04:32:36 +00:00

Author

Owner

Approved — removing blocked:needs-decision. Triage failed to auto-approve, but this is low/medium risk, aligned.

Mark

2026-08-11 04:33:16 +00:00