Auto-attributes (Tower consumer — Phase 1)
Overview
Each protected document is created in neo with structured autoAttributes (source, git or FTP or email context) instead of legacy toolkit tags.
How it works
deposit-fields projects a protect task into attribute codes and storage-path tags. createDocument posts those codes to neo. Git, FTP, and email each fill the codes they own. Tower talks to neo directly. The runtime image does not include bcyip-toolkit.
Key files
src/protocol/utils/deposit-fields.ts— attribute and storage-tag projectionsrc/protocol/bcyip/api.ts— document create and proof downloaddocs/auto-attributes.md— code catalogue
Known issues
- None recorded in the 3.2.0 fragment.
Next steps
- None from this release.