Skip to content

Tax Context History: {client_name} ({tax_year})

Version Summary

  • Current Version: {version_number}
  • Created: {initial_timestamp}
  • Last Modified: {latest_timestamp}
  • Total Changes: {count}

Changelog

Version {version_number} - {timestamp}

Trigger: {trigger_type} - DOCUMENT_ANALYSIS: New or updated document processed - CHATBOT_APPROVED: Preparer approved chatbot-flagged update - PREPARER_MANUAL: Preparer made direct edit - SYSTEM_UPDATE: Automated system update (e.g., tax year rollover)

Source: - Document ID: {doc_id} (if document triggered) - Conversation ID: {conversation_id} (if chatbot triggered) - Preparer ID: {preparer_id} (if manual)

Actor: {AI_ANALYSIS | CHATBOT | PREPARER:{id} | SYSTEM}

Changes:

# Jurisdictions
+ Added: NY (Part-year, Mar 16 - Dec 31)
- Removed: None
~ Modified: NJ from Full-year to Part-year (Jan 1 - Mar 15)

# Skills
+ Added: ny/2024/residency.md
+ Added: ny/2024/nyc-income-tax.md

# Flags
+ Added: [PART_YEAR] Part-year residency NJ→NY March 2024
+ Added: [LOCALITY] NYC resident tax applies

# Document-Derived Values
~ Modified: Primary State from NJ to NY

Rationale: - {explanation of why change was made} - Client statement: "{quote if from conversation}"

Reviewer: {preparer_id or "N/A" for auto-analysis}

Dispute Resolution Reference

To find when a jurisdiction was added: Search for "+ Added: {state}" in changelog

To find what client said about a topic: Search for "Client statement:" or "Client stated"

To verify preparer reviewed a change: Look for "Reviewer:" field - "N/A" means automated, otherwise shows preparer ID

To reconstruct context at a point in time: Use S3 versioning to retrieve tax_context.md as of specific date