Public Agent Standard Publication
This standard defines the source, metadata, safety and URL contract for the
small set of Meridian standards that may be published toagents.meridianstack.dev. It is the repository-side contract for a future
static publisher; it does not deploy or serve the site.
Authority and opt-in
The canonical source remains a Markdown or MDX document in docs/standards/.
The file .config/meridian/policies/public-agent-standards.json is the
explicit publication manifest. A document is publishable only when both the
manifest and its frontmatter opt it in:
- the manifest names the exact repository-relative path, stable identifier,
- the document frontmatter contains
public-agent: true, the same stable - documents not named by the manifest are not published, even when they live
- an opted-in document that is absent from the manifest fails validation rather
title, lifecycle status, public classification and safety decision;
identifier and title, a supported status, `classification:
public-agent-standard, and safety: reviewed-public`;
under the standards source root;
than being silently discovered.
No private documentation, credentials, provider payloads, access policy or
hosted-site state belongs in this publication surface. Public classification is
an explicit review decision, not an inference from a filename or directory.
Stable URLs and discovery
The publisher derives all public routes from the manifest identifier. For an
entry with ID example-standard, the routes are:
- human HTML:
https://agents.meridianstack.dev/standards/example-standard; - raw Markdown:
https://agents.meridianstack.dev/standards/example-standard.md; - machine discovery:
https://agents.meridianstack.dev/standards/index.json.
The machine index is derived output. It must expose the stable ID, title,
status, classification, source revision and both document URLs; it must not
become a second source tree or expose repository paths that are not needed by
consumers.
Repository file applicability
An entry may declare an appliesTo array in the versioned manifest. Each rule
contains a repository-relative pattern and a closed referenceMode value.
Omitting appliesTo is equivalent to an empty array, so existing version-1
documents remain valid while standards opt into file routing explicitly.
Patterns use / separators and literal ASCII filename charactersA-Z, a-z, 0-9, ., _ and -. A single * within a component matches
zero or more characters in that component; one complete ** component matches
zero or more path components. Patterns are limited to 240 characters, 32 path
components and one **. Empty, absolute, dot,
dot-dot, backslash, drive-qualified and repeated-separator paths are invalid.
Executable expressions, regular expressions and network lookups are not part
of this model.
Matcher inputs are canonical repository-relative paths using / separators.
They reject absolute, drive-qualified, traversal, empty-component and
backslash paths, while allowing ordinary filename characters such as spaces
and Unicode. Input paths are not restricted by the pattern length or component
limits.
The supported reference modes are:
comment: an inline comment is safe for this file family;native-reference: use a native schema, link or reference field alreadyinstructions-only: do not add an inline reference; apply the standard from
supported by the file format; and
agent guidance.
If multiple patterns match, a standard appears once. Matching standards are
ordered by stable ID. For the effective reference mode, the most restrictive
matching declaration wins: instructions-only, then native-reference, thencomment. An identical pattern and reference-mode pair may be declared only
once; a pattern may be repeated with different modes, which resolve by the same
restrictive precedence. This is routing guidance only; applicability never
grants public classification or publication permission.
Renames and supersession
Published IDs are durable public identifiers. A rename is represented by a new
manifest entry plus supersedes and redirectFrom values on the new entry.
The old ID remains a redirect target and is never silently reused for a
different standard. Redirect IDs must be unique, must use the same lowercase
kebab-case grammar as current IDs, and must not collide with a current ID.
Removing a document from the manifest is therefore not a rename. It is a
deliberate retirement that must preserve a redirect or an explicit unavailable
record when the public URL has already been released.
Safety gate
The validator fails closed unless every manifest entry is classified exactly aspublic-agent-standard and carries the reviewed-public safety decision in
both manifest and frontmatter. It also rejects common credential material,
including private-key blocks, GitHub tokens, live Stripe keys, AWS access-key
identifiers and JWT-shaped bearer values.
Reviewers must still check the meaning of the content: the automated gate is a
minimum safety boundary, not permission to publish private operational detail.
Deterministic validation
Repository CI runs the TypeScript owner intools/governance/repository-quality and rejects:
- malformed manifest JSON or frontmatter;
- missing or duplicate IDs and paths;
- paths outside
docs/standards/or unsupported file types; - missing opt-in, unsafe classification or manifest/frontmatter drift;
- invalid supersession and redirect metadata; and
- malformed or unsafe applicability patterns and unknown reference modes; and
- credential-like content in a candidate document.
The validator sorts findings and derived entries before reporting them, so the
same source produces the same result locally and in CI.
This contract is the implementation record for ISSUE #1774.