Corezoid Task Data — Lineage and Retention

Corezoid Task Data — Lineage and Retention A data-flow diagram generated by Archify. 01 / Ingress 02 / Execute 03 / Protect 04 / Store 05 / Consume Task Payload · caller JSON · 01 / Ingress · untrusted Task Payload caller JSON untrusted conveyor_api · validate + route · 02 / Execute · auth conveyor_api validate + route auth conveyor_worker · logic execution · 02 / Execute · sharded conveyor_worker logic execution sharded conveyor_crypt · config encryption · 03 / Protect · AES conveyor_crypt config encryption AES Counter Pipeline · per-shard aggregate · 03 / Protect · rollup Counter Pipeline per-shard aggregate rollup Vault Transit · wrapped DEK · 04 / Store · restricted Vault Transit wrapped DEK restricted cp_0..cp_99 · live tasks · 04 / Store · hot cp_0..cp_99 live tasks hot Redis · counters + cache · 04 / Store · volatile Redis counters + cache volatile tasks_archive · archive_cp_* · 05 / Consume · cold tasks_archive archive_cp_* cold Stats Pipeline · aggregation · 05 / Consume · derived Stats Pipeline aggregation derived create task user payload sharded dispatch conv_id rem N process credentials secret wrap key KMS task_data rows system of record node counters metrics increment ephemeral archiver sweep completed only aggregate derived Legend primary data policy / PII async batch data store data flow

Write path

  • • Caller payload becomes task_data, keyed by conv_id
  • • Shard chosen as conv_id rem N (100 in prod)

Secret handling

  • • Process credentials never persist in plaintext
  • • Vault Transit holds the wrapping key, not the data