ai-conversation-impact/tasks/08-value-in-log.md
claude 0543a43816 Initial commit: AI conversation impact methodology and toolkit
CC0-licensed methodology for estimating the environmental and social
costs of AI conversations (20+ categories), plus a reusable toolkit
for automated impact tracking in Claude Code sessions.
2026-03-16 09:46:49 +00:00

1.1 KiB

Task 8: Add value field to impact log

Plan: measure-positive-impact Status: DONE (added annotate-impact.sh for manual value annotation; show-impact.sh displays annotations) Depends on: Task 7 (need the metrics defined first) Deliverable: Updated hook and viewer scripts

What to do

  1. Add optional fields to the impact log JSON schema:

    • value_summary: free-text description of value produced.
    • estimated_reach: number (people affected).
    • counterfactual: enum (none / slower / impossible).
    • net_assessment: enum (clearly-positive / probably-positive / uncertain / probably-negative / clearly-negative).
  2. These fields cannot be filled automatically by the hook — they require human or LLM judgment. Options:

    • Add a post-session prompt (via a Stop hook?) that asks for a brief value assessment.
    • Accept manual annotation via a helper script.
    • Leave them optional; fill in retrospectively.
  3. Update show-impact.sh to display value fields when present.

Done when

  • The log schema supports value data alongside cost data.
  • show-impact.sh displays both.