Repository navigation
Added
- AITY suggestions at the vault write boundary. A gallery
ingestwith
suggest: trueruns AITY on the stored photograph — opt-in per photograph,
because the consumer may hold the photographer's consent for some and not
others. AITY only proposes; what the consumer sent is never changed, and
AITY failing never fails the ingest.GET …/w/suggestions?resources=…
returns the proposed title and description per ingested resource (off,
pending,done,failed) to a key that mayupdate; reading never
starts AITY.
@tydal/clientgetssuggestions(resources). See
docs/architecture/VAULT_WRITE_METHODS.md§3.
Upgrading
No migrations and no new configuration. Suggestions run on the existing AITY
pipeline, so they need what AITY already needs: a configured LLM driver and a
queue worker. @tydal/client goes to 1.7.0 (suggestions);
@tydal/org-mcp and @tydal/vault-mcp keep their versions.
Full changes: v1.4.1...v1.5.0