Skip to content

docs: correct lease vendor namespace segment count #89

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nficano merged 2 commits into from
May 24, 2026
+7 −1
Merged

docs: correct lease vendor namespace segment count #89

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cef65c2
docs: correct lease vendor namespace wording
narutamaaurum May 23, 2026
1f988f6
Merge branch 'main' into docs-85-lease-vendor-segments
nficano May 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion docs/guides/leases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,14 +27,20 @@ patterns. Reserved capability names:
| `cost.budget` | Spend cap; entries are `currency:amount` strings (see §9.6 below). |

Custom capability names MUST use `x-vendor.<vendor>.<cap>` (at least
three dot-separated segments after the `x-vendor.` prefix):
two dot-separated segments after the `x-vendor.` prefix). See the
[vendor extensions guide](./vendor-extensions.md) for the canonical
namespace rules:

```ts
const lease = {
"x-vendor.acme.kafka.publish": ["topic-events-*"],
};
```

For the same namespace shape in another ARCP surface, the tracing
middleware uses `x-vendor.opentelemetry.tracecontext` as its envelope
extension key.

## Example

```ts
Expand Down