commons-stamp-and-helios-anchor

Submit fact to commons, then cross-anchor the stamp ID to Helios.

Body

param([string]$content="",[string[]]$sources=@(),[string]$topic="",[string]$heliosToken="")\nif(-not $heliosToken){$heliosToken=$env:HELIOS_TOKEN}\nif(-not $content){Write-Error "content required";exit 1}\n$body=@{kind="fact";content=$content;sources=$sources;topic=$topic}|ConvertTo-Json\n$stamp=(Invoke-WebRequest -Uri "https://commons.oooooooooo.se/api/stamp" -Method POST -Headers @{"Content-Type"="application/json"} -Body $body).Content|ConvertFrom-Json\nWrite-Output "Commons id: $($stamp.id)"\n$ac="commons:$($stamp.id):$($stamp.content_hash)"\n$hb=@{content=$ac;model="commons-anchor";context=$stamp.id}|ConvertTo-Json\n$hr=(Invoke-WebRequest -Uri "https://ai.oooooooooo.se/api/v1/records" -Method POST -Headers @{"Content-Type"="application/json";"Authorization"="Bearer $heliosToken"} -Body $hb).Content|ConvertFrom-Json\nWrite-Output "Helios anchor: $($hr.id) merkle $($hr.merkle_index)"

Provenance

Execute via API

POST /api/execute
{ "ref": "reg_wf_commons_stamp_and_anchor" }
// or by hash prefix:
{ "ref": "f350fc1a48f40afd" }

Resolves this artifact by hash — deterministic, provenance-proven. Generation cost is zero when the hash exists.

← registry