27 lines
880 B
Markdown
27 lines
880 B
Markdown
|
---
|
||
|
|
model: openai/gpt-5.6-sol
|
||
|
|
service: opencode
|
||
|
|
timestamp: 2026-08-19T00:33:28Z
|
||
|
|
git_ref: wkt/tipc_backend_378
|
||
|
|
diff_cmd: git diff HEAD~1..HEAD
|
||
|
|
---
|
||
|
|
|
||
|
|
## Prompt
|
||
|
|
|
||
|
|
The user asked to begin drafting an upstream `/tipc` multiaddr issue
|
||
|
|
similar to the existing WireGuard proposal, then chose to track the
|
||
|
|
draft as an AI planning document.
|
||
|
|
|
||
|
|
## Response
|
||
|
|
|
||
|
|
The generated proposal is intended for `multiformats/multiaddr`:
|
||
|
|
|
||
|
|
> `git diff HEAD~1..HEAD -- ai/tpt-backends/04_tipc_multiaddr_upstream.md ai/tpt-backends/README.md`
|
||
|
|
|
||
|
|
It proposes a code allocated upstream, a fixed 72-bit value holding
|
||
|
|
the service type, instance and scope, and the canonical text form
|
||
|
|
`/tipc/<type>:<instance>:<scope>`. It includes WireGuard composition,
|
||
|
|
security boundaries, the `tipc` versus `cds` naming decision,
|
||
|
|
deployment-management separation, implementation phases, test data
|
||
|
|
and open questions for maintainers.
|