Why interface
A website can present information without defining how another party should interpret or use it. A publication can distribute material without maintaining a current operational representation of its author. An API can expose functions without offering a legible account of the thing behind them.
A Public Interface joins those concerns without pretending they are the same. It provides a stable place to understand the party, inspect public evidence, retrieve canonical material in useful representations, and determine what forms of contact or action are actually available.
The word public describes discoverability, not authority. Information may be public while actions remain unavailable, authenticated, delegated, or subject to human approval.
What makes it an interface
The defining property is not a particular framework or file format. It is an explicit contract:
- canonical information has a declared source;
- important material has stable addresses;
- human and machine representations remain traceable to the same source;
- current capabilities can be inspected rather than inferred from promotional language;
- claims are connected to evidence and change records;
- unavailable capabilities and permission boundaries are stated plainly.
That contract makes the surface useful to a human reader, a search engine, a language model gathering context, or an agent determining whether it can proceed.
The present boundary
This site currently implements a public read and routing layer. It represents, informs, supplies evidence, supports discovery, and publishes a contact route. It does not authenticate agents, accept delegated authority, execute transactions, or assert that a routed request has been completed.
Those later functions would constitute a separate permissioned action layer. If one is built, it will require its own identity, authorization, revocation, idempotency, state, audit, and failure model. Adding an endpoint is not enough.
Direction, not a promise
The useful long-term question is whether some exchanges can move from discovery through initiation, authorization, execution, completion, and verification with agents acting for the parties involved. That is a design horizon, not a claim about the current deployment.
The public layer should remain durable even if the protocols used by a future action layer change. HTML, Markdown, structured data, feeds, APIs, MCP, signed requests, or later protocols are representations and adapters around the contract; none of them is the contract itself.
This implementation
The architecture record reports what jayweeldreyer.com actually implements, how it is deployed, and how the current version performs. How this site is built explains the engineering rationale. The public reference implementation contains reusable code without Jay’s content or the private production history.