cal/claude-memory
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity
main
claude-memory/graph/decisions/esb-50-blocks-esb-51-getter-must-run-before-mapping-config-i-65cdb3.md
Cal Corum eea12e4e31 relate: 49d3de63 --CAUSES--> 65cdb31b
2026-02-26 12:58:13 -06:00

1.5 KiB
Raw Permalink Blame History

id type title tags importance confidence created updated relations
65cdb31b-e86f-4465-a321-378e1f704e6f decision ESB-50 blocks ESB-51: getter must run before mapping config is finalized
esb-monorepo
sf-ca
workflow
dependencies
decision
0.6 0.8 2026-02-26T18:57:26.898767+00:00 2026-02-26T18:58:13.456418+00:00
target type direction strength edge_id
ca8d0390-7ff9-4ca7-b033-3656d653c2be RELATED_TO incoming 0.75 8afe2aba-4039-4f34-9c39-02bbe93926b7
target type direction strength edge_id
49d3de63-9123-4d3b-b45b-614927b6afe3 CAUSES incoming 0.85 bfe2c279-396c-4984-9867-a15f0d7895c8

ESB-50 Blocks ESB-51: Dependency Ordering

Decision

ESB-50 (SF-CA getter) must be completed before ESB-51 (object handler config) can be finalized.

Rationale

The existing sf-ca.json mapping was written speculatively and may not match actual Salesforce field names from the Commercial Aquatics instance. Real raw data must be pulled via the ESB-50 getter to confirm:

  • Actual Salesforce API field names for Account and Contact objects
  • Which fields are reliably populated vs. sparse
  • The correct values for db_platform_code and db_source_code for CloudSQL routing

Sequence

  1. Build and test ESB-50 getter against real SF-CA instance
  2. Inspect raw payload to verify field names
  3. Update sf-ca.json mapping in ESB-51 with confirmed field names
  4. Fix copy-paste bug in Contact required_platform_fields