Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions src/content/spec/SOURCE.json
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
{
"repository": "stackumi/restact",
"commit": "fca00d9b22d59d2ab71c78bba3def15fd2784c0d",
"date": "2026-11-02T23:16:04-06:00"
"commit": "0de8381b102a91ef20657bd18ed26e6b0700a35a",
"date": "2026-11-17T01:45:56-06:00"
}
19 changes: 11 additions & 8 deletions src/content/spec/draft-byrd-restact-presentation-00.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,8 +85,8 @@ A **presentation verb** (informally a *view verb*) is an ordinary REST:ACT verb
exactly like [examples/render-html](https://github.com/stackumi/restactd/tree/main/examples/render-html).

Nothing else is special. A view verb links against only the already-frozen `object` (+ `log`)
interfaces; `wit/world.wit` is unchanged. It runs under the same sandbox, fuel/epoch/memory limits,
and run-as-caller identity as any verb, so a view sees only what the caller may read.
interfaces; `wit/world.wit` is unchanged. It runs under the same sandbox, resource limits and
run-as-caller identity as any verb, so a view sees only what the caller may read.

Naming convention (non-normative, but used by the reference implementations):

Expand All @@ -101,10 +101,11 @@ Naming convention (non-normative, but used by the reference implementations):
# The media type {#media-type}

`application/vnd.restact.ui+json` is a `+json` structured-syntax type: the payload is JSON. A view
verb declares it via `produces`; the host stamps it as the response `Content-Type` and adds
`x-content-type-options: nosniff` (as for any verb output). It is **not** `text/html`, so the host's
HTML-only Content-Security-Policy and `Content-Disposition: attachment` hardening do **not** apply —
the browser never renders the payload; the trusted client fetches and interprets it.
verb declares it via `produces`, and the server sends it as the response `Content-Type`, with the
headers {{RESTACT}} specifies for any verb output (`X-Content-Type-Options: nosniff` and a restrictive
Content-Security-Policy; Security Considerations). The type is not script-capable, so it is served
inline, without `Content-Disposition: attachment`. The browser
never renders the payload; the trusted client fetches and interprets it.

# The component catalog (the trust boundary) {#catalog}

Expand Down Expand Up @@ -139,7 +140,8 @@ registry both speak, they agree.
`target`) against the
registry's path grammar **before** issuing any fetch — for `page.subscribe`, before any event
stream is opened — and MUST resolve a valid object path only against the **same-origin data
plane** (discovery base + `/v1/` + path). This is the sharpened form of the safe-schemes
plane** (the server's base URL + `/v1/` + path; the "Base URL" section of {{RESTACT}}). This is
the sharpened form of the safe-schemes
requirement for path-valued fields: a valid object path is scheme-free by construction, so
external URLs and `data:` URIs are unrepresentable. A facet `target` is never fetched by the
client — it travels only as commit input — but is validated identically before the facet is
Expand Down Expand Up @@ -226,7 +228,8 @@ A host advertises support additively (frozen contract preserved):
and its name is not a reserved accessor/lifecycle name. (`produces` itself already appears in the
descriptor, so a client can key on either signal.)

A client builds its UI **from discovery**: fetch `GET /.well-known/restact`, take every `role == "view"`
A client builds its UI **from discovery**: fetch `GET /.well-known/restact` relative to the server's
base URL, take every `role == "view"`
verb, treat the untemplated ones as navigation and the templated ones as per-object views, and render
each by invoking it and interpreting the returned document. The client needs **no built-in knowledge
of the application's domain** — which is what lets a newly deployed view verb appear with no client
Expand Down
3,472 changes: 1,323 additions & 2,149 deletions src/content/spec/draft-byrd-restact-protocol-00.md

Large diffs are not rendered by default.

41 changes: 36 additions & 5 deletions src/content/spec/registries/README.md
Original file line number Diff line number Diff line change
@@ -1,20 +1,30 @@
# REST:ACT registries

The IANA-style registries requested in the IANA Considerations of the protocol draft
([`../draft-byrd-restact-protocol-00.md`](../draft-byrd-restact-protocol-00.md) §IANA) and of REST:ACT
([`../draft-byrd-restact-protocol-00.md`](../draft-byrd-restact-protocol-00.md) §IANA Considerations) and of REST:ACT
Presentation Verbs ([`../draft-byrd-restact-presentation-00.md`](../draft-byrd-restact-presentation-00.md)
§IANA Considerations), which requests the UI Catalog Node Types registry. They are maintained here
§IANA Considerations), which requests the UI Catalog Node Types registry, and of REST:ACT Connectors
([`../draft-byrd-restact-connectors-00.md`](../draft-byrd-restact-connectors-00.md) §IANA
Considerations), which requests the LLM Providers registry, and of REST:ACT HTTP Verbs
([`../draft-byrd-restact-http-verbs-00.md`](../draft-byrd-restact-http-verbs-00.md) §IANA
Considerations), which requests the Webhook Schemes registry. REST:ACT Objects and Data
([`../draft-byrd-restact-objects-00.md`](../draft-byrd-restact-objects-00.md) §IANA Considerations)
requests no registry of its own and registers its values in these, as do REST:ACT Events
([`../draft-byrd-restact-events-00.md`](../draft-byrd-restact-events-00.md) §IANA Considerations) and the
REST:ACT Model Context Protocol Facet
([`../draft-byrd-restact-mcp-00.md`](../draft-byrd-restact-mcp-00.md) §IANA Considerations). They are maintained here
in the repository ahead of any formal IANA action; on publication these tables become the initial
contents of the corresponding IANA registries.

| Registry | File | Referenced by |
|---|---|---|
| REST:ACT Verb Property Names | [`verb-property-names.md`](verb-property-names.md) | draft §Verb properties; `x-restact-verb.properties` |
| REST:ACT Capability Interfaces | [`capability-interfaces.md`](capability-interfaces.md) | draft §Capability Model; `x-restact-verb.capabilities.interfaces`; the frozen `wit/world.wit` |
| REST:ACT Capability Interfaces | [`capability-interfaces.md`](capability-interfaces.md) | draft §Capability Model; `x-restact-verb.capabilities.interfaces`; the `wit/` package |
| REST:ACT Source Languages | [`source-languages.md`](source-languages.md) | draft §Verb code; `x-restact-verb.sourceMediaType` |
| REST:ACT UI Catalog Node Types | [`ui-catalog-nodes.md`](ui-catalog-nodes.md) | [`../draft-byrd-restact-presentation-00.md`](../draft-byrd-restact-presentation-00.md); `application/vnd.restact.ui+json` documents |
| REST:ACT LLM Providers | [`llm-providers.md`](llm-providers.md) | [ADR-0095](https://github.com/stackumi/restactd/blob/main/spec/decisions/0095-typed-connectors-llm.md); a `kind:"llm"` connector object's `provider` member |
| REST:ACT Feature Tokens | [`feature-tokens.md`](feature-tokens.md) | draft §Conformance, §Discovery; `service.features`; the `featureToken` enum in [`openapi/x-restact-extension.schema.json`](https://github.com/stackumi/restactd/blob/main/openapi/x-restact-extension.schema.json) |
| REST:ACT LLM Providers | [`llm-providers.md`](llm-providers.md) | [draft-byrd-restact-connectors-00](../draft-byrd-restact-connectors-00.md) §IANA Considerations; [ADR-0095](https://github.com/stackumi/restactd/blob/main/spec/decisions/0095-typed-connectors-llm.md); a `kind:"llm"` connector object's `provider` member |
| REST:ACT Webhook Schemes | [`webhook-schemes.md`](webhook-schemes.md) | [draft-byrd-restact-http-verbs-00](../draft-byrd-restact-http-verbs-00.md) §IANA Considerations; the `verify` deployment parameter |
| REST:ACT Feature Tokens | [`feature-tokens.md`](feature-tokens.md) | draft §Conformance and Feature Discovery, §Discovery; `service.features`; the `featureToken` enum in [`openapi/x-restact-extension.schema.json`](https://github.com/stackumi/restactd/blob/main/openapi/x-restact-extension.schema.json) |

## Registration policy

Expand All @@ -30,3 +40,24 @@ by a specification but not in service (a planned interface, a deferred language,
token). On publication the surviving entries become the initial IANA registry contents. User-defined names
outside a registry are permitted where the spec allows them, but MUST NOT reuse a registered name
for a different purpose.

## The Reference cell

Where a registry table has a Reference column, its cell names the document that defines the entry
first. An entry that the core protocol draft defines is cited as `draft §<Heading>`. An entry that
another draft defines links that draft under its docname, as in
`[draft-byrd-restact-presentation-00](../draft-byrd-restact-presentation-00.md) §IANA Considerations`,
or links the draft alone where no one section defines the entry. `<Heading>` is the heading of the
defining section, written in full or shortened to the heading without a trailing parenthetical, or
to the text before its first colon or comma. For example, `draft §Verb code` cites the section
"Verb code: source and executable", and `draft §Deployment history and rollback` cites "Deployment
history and rollback (OPTIONAL, feature `verb-history`)". Two sections of one document are written
`draft §A, §B`. Any ADR that records the decision behind the entry follows, after a semicolon.
A row whose defining section is not written yet cites `none yet (stackumi/restact#<issue>)` in its
place, naming the issue that tracks the section.

A registry file here also holds the entries that extensions register into it, so one table lists
every value, whichever document defines it; the REST:ACT Error Codes registry has no file yet, and
each draft lists the codes it registers.
`.github/scripts/check-xrefs.py` resolves each `§` citation against the drafts' headings. It
fails when one matches no heading or more than one, or when a Reference cell cites no draft section.
Loading
Loading