Event JSON
{
"id": "f6518f713511b6432edb510d5d6883cce09bb5bd3a1c75dec7f1de5c544ff1d8",
"pubkey": "a4a6b5849bc917b3befd5c81865ee0b88773690609c207ba6588ef3e1e05b95b",
"created_at": 1771045868,
"kind": 1,
"tags": [
[
"alt",
"A short note: https://image.nostr.build/001154deab7a977c0c124c3f..."
],
[
"r",
"https://github.com/PR0M3TH3AN/TORCH"
],
[
"r",
"https://image.nostr.build/16cd94a87b61077929c9766a83b4f75a03cf2ad758c293ef9baa71c8926119f6.jpg"
],
[
"r",
"https://torch.thepr0m3th3an.net/"
],
[
"r",
"https://torch-config.json/"
],
[
"r",
"https://image.nostr.build/001154deab7a977c0c124c3f2c1f2ea9df272aec5439ff1b74571f6efe0baf58.jpg"
],
[
"imeta",
"url https://image.nostr.build/001154deab7a977c0c124c3f2c1f2ea9df272aec5439ff1b74571f6efe0baf58.jpg",
"x 76ef87a9d644f8bef3131eeb28ac055cb6d86eb341b311b8cda760d7da570444",
"size 72530",
"m image/jpeg",
"dim 2112x1216",
"blurhash i13IuA%h8wI7yF%jt8R2V;.9xtMdM}x^xtofs;s.Z{nzyGtoVqR2obtUtTDhR+.9%KemWGogk8WA8|R:.7$]n-bzWZi[ne",
"ox 76ef87a9d644f8bef3131eeb28ac055cb6d86eb341b311b8cda760d7da570444",
"alt "
],
[
"imeta",
"url https://image.nostr.build/16cd94a87b61077929c9766a83b4f75a03cf2ad758c293ef9baa71c8926119f6.jpg",
"x 09229adfb2aa97086f647c132e77bbf3e7c7c675d2d4c2480da71dfb87f02757",
"size 99299",
"m image/jpeg",
"dim 2156x1172",
"blurhash i13[_A_1.AxUkF%LX9M|V?xZ-:-=jDWZITWVxuxb%D?d$~t9acRooJobxu_1?wx9x_aIxwW,Rka#oGx]%1t9RiR-jYxuxb",
"ox 09229adfb2aa97086f647c132e77bbf3e7c7c675d2d4c2480da71dfb87f02757",
"alt "
]
],
"content": "https://image.nostr.build/001154deab7a977c0c124c3f2c1f2ea9df272aec5439ff1b74571f6efe0baf58.jpg\n\n🔥 Introducing TORCH — Task Orchestration via Relay-Coordinated Handoff\n\nhttps://image.nostr.build/16cd94a87b61077929c9766a83b4f75a03cf2ad758c293ef9baa71c8926119f6.jpg\n\nTORCH is a portable, Nostr-based task-locking toolkit for multi-agent coordination — think of it like a KANBAN board for software agents that evolve with your codebase. It lets schedulers and agents coordinate work by publishing/claiming task locks over Nostr relays so tasks can be reliably handed off without central servers.\n\nWhat TORCH stands for\nTask\n\nOrchestration via\n\nRelay-Coordinated\n\nHandoff — a decentralized lock/claim/expire model for agents and schedulers.\n\nHow it works (high level)\nScheduler publishes tasks as lockable Nostr events in a project namespace. Agents see the available tasks and attempt to claim them by writing a lock event to the configured relays.\n\nLocks are time-limited (default TTL ~7200s / 2h) and use standardized tags for expiration (NIP-40), so claims auto-expire and races are resolved by relay-coordinated replaceable events. Kind and expiration behaviour are encoded in the protocol (Kind 30078, expiration via NIP-40).\n\nRosters \u0026 namespaces let you scope daily/weekly task groups to your repo; configuration lives in torch-config.json or env vars so TORCH follows your repo’s cadence.\n\nAgents run locally or in the cloud (AGENT_PLATFORM can be set like codex) and use the CLI to lock, check, and list active locks. There’s also an optional static dashboard.\n\nWhy you’d use it\nDecentralized: no single server dependency — task state travels with the codebase and relays.\n\nRepo-native: torch-config.json and prompts let TORCH evolve with your project’s workflow.\n\nIdeal for multi-agent automation, documentation agents, CI helpers, and anywhere you want reliable, contestable task claiming.\n\nTry it: demo \u0026 docs → https://torch.thepr0m3th3an.net/\nSource \u0026 quickstart → https://github.com/PR0M3TH3AN/TORCH (see README for the lock/check/list examples).",
"sig": "7e847ef7d63e80227435a6fe4e505473fe87ec7c7b4423126d43af009b36685d32644ff2fc3b2bb6529ae9bdbdfa0af8cb8eb6184ed0590f4254b0b63c1fd34b"
}
