Vault & Docs Sync Verification

Summary

• Vault home confirmed: Research/tam/ with 7 topic folders per README (health/tech/medical/foods/automation/ai/news).
• Write path confirmed: this note was scp'd with tam_vault_key and pulled back for read-back verification.
• Docs site docs.youngle.au returns 401 to unauthenticated requests from this laptop — publishing is real but the endpoint is auth-gated; verification of publication = vault pull-back, not anonymous curl.

Key findings

• README workflow: one topic = one note, YYYY-MM-DD-short-topic.md, frontmatter (title/date/category/source URLs), structure summary→findings→implications→sources.
• Trading-relevant findings must ALSO go to Mira (business) or Eva (trade desk) via A2A.
• Registration route correction found 2026-09-08: teammate Eva's A2A answers on :8441 (health agent=eva, host=pulse-laptop); :8442/9902 is Eve (macrobiotics card).

Implications for us

• Every future research note gets: vault write -> scp pull-back SHA check -> A2A note to the relevant desk teammate.

Sources

• Direct pulls via scp -O -i ~/.ssh/tam_vault_key ubuntu@161.33.71.67:... (2026-09-08)
• Central registry :8433 /agents and /health (2026-09-08)