AICENT-002 -- the rttp URI scheme
V1.2.6 reading
========================================================================

SCOPE

  This is the V1.2.6 reading of AICENT-002. It states what the "rttp" URI
  scheme is and what a client must do with it, and nothing else. The
  normative specification is the Internet-Draft cited at the end of this
  file; where this text and that document differ, the document governs.

WHAT THE SCHEME IS

  An rttp URI names a claim of intent directed at an identified subject.
  The address of that subject is derived by computation from the URI
  authority. No lookup service, registry, or name-resolution system is
  consulted at resolution time.

  The URI is an entry fingerprint. It is not a locator to be resolved.

ADDRESS FORM

  rttp://<intent>.<pillar>.<root>/<action>

    intent   either eight lowercase hexadecimal digits, or a readable
             label
    pillar   operator-chosen label; the processing layer
    root     operator-chosen label; the operator
    action   an optional verb on the intent

  A URI can also be reached from a web page through the prefix that
  browsers reserve for external protocol handlers:

    web+rttp://<intent>.<pillar>.<root>/<action>

  Both forms carry the same authority, the same path and the same derived
  routing label. They are not two schemes.

ROUTING LABEL

  The routing label (the route shard) is a 16-byte value derived from the
  canonical authority. The same authority always yields the same route
  shard. Resolution is a computation, not a query: no DNS, no TTL and no
  registry lookup on the resolution path.

CLIENT REQUIREMENTS

  A client that handles an rttp URI MUST NOT perform a lookup in order to
  use it. It MUST treat the URI as a claim of intent, not as a proof about
  the subject. It MUST NOT render an rttp URI as an IRI. It MUST NOT
  acquire the ability to handle rttp URIs without an explicit action by the
  user. It MUST reject any input whose scheme is neither rttp nor web+rttp.

  Handling an rttp URI is not by itself a statement about the safety of the
  operation that the URI names.

REGISTRATION STATUS

  Scheme:             rttp
  Status:             submitted to IANA, Provisional, pending
  Registered:         no -- the scheme is not registered
  Request ticket:     [IANA #1459939]
  Change controller:  RTTP.COM Organization
  Contact:            ShaoBao Li <lee@rttp.com>

CONFORMANCE

  A published set of deterministic conformance vectors accompanies this
  scheme, replayed by independent implementations that share no code.
  Agreement between implementations is a statement about parsing only, and
  no performance property is claimed.

SPECIFICATION

  draft-li-rttp-intent-addressing
  https://datatracker.ietf.org/doc/draft-li-rttp-intent-addressing/

OTHER READING

  The Aicent Stack narrative (v1.3.0) is preserved, unchanged, at:
  https://rttp.com/AICENT-002/source-v1.3.0.txt

(C) 2026 RTTP.COM Organization