Files
zeekayandHanzo Dev 417eb80eb4 hanzo-research 0.2.4: decision records under /v1/research, actions as the server holds them
The client side of hanzo-inc/cloud 0ce6cf3d5e, proved by filing
kai's apu and jltv examples against apps/research's own handlers.

- Evidence moves under research's prefix: POST /v1/research/evidence,
  /v1/research/evidence/sysml, GET /v1/research/evidence?uri= and
  /v1/research/evidence/dependents. Every call goes through post/get on
  /v1/research; the /v1 sender is gone.
- An Action is {action: <the DDT Action as written>, assignee?}, the shape
  the server reads, and reads back with the server's id, hash, decisionId,
  status, authorizedBy/At, time and by. `hash` is what a person's
  authorization names. The client still neither authorizes nor commits.
- Evaluation and Commitment carry the filing's hash (hash,
  evaluationHash); Decision carries decisionId.

Co-authored-by: Hanzo Dev <[email protected]>
2026-10-16 01:10:40 -07:00
..
2026-07-28 06:03:51 -07:00