Public Interface and Export Format Specification

This document defines the machine-readable objects, validation rules, and access boundaries for Public Interface and Export Format Specification for Good Taste Awards.

This document applies to the requirements, decisions, records, controls, and outputs expressly identified under Public Interface and Export Format Specification. Award scope and exclusions are defined by GTA-STD-100; this document shall not create an additional award dimension. Operational prerequisites identified here affect assessment validity and never constitute product certification.

The Data and Publication Custodian owns GTA-DATA-004; the Standards Authority approves it. formal verbs, defined terms, stable requirement identities, policy constants, and generated representations shall be interpreted under GTA-GOV-002, GTA-GOV-005, and the defined registers.

The public interface may be implemented as static resources, an application interface, or both. The implementation form shall not change resource identity, confirmed content, fixed-version immutability, or the distinction between active and version-specific representations.

No public result field may contain a blind code, sample custody detail, assessor identifier, raw response, individual observation, conflict declaration, professional-confirmation ballot, internal reason code, non-public result, or unpublished review evidence.

A resource request shall resolve by stable identity. A collection may filter by document family, document type, topic, category, confirmed star level, or defined term only where that property is public. Filters shall be conjunctive unless the interface explicitly identifies another operator. An unsupported filter shall return an error; it shall not be ignored silently.

Default document ordering shall follow the defined register. Requirement search results shall use deterministic relevance ordering with stable identity as the final tie-breaker. Award-result collections shall use an explicitly declared deterministic order and an opaque continuation cursor. A cursor shall be bound to the collection identity, filter set, ordering rule, and represented release so that a later release cannot silently change an in-progress traversal.

Search shall index authoritative English titles, headings, requirement identifiers, body text confirmed for publication, preferred defined terms, and approved retrieval synonyms. A synonym may improve discovery but shall not replace defined terminology in the displayed result or cited text.

A successful structured response shall identify the resource, represented version, visibility, content integrity value, and canonical relationship. A collection response shall additionally identify applied filters, deterministic order, result count where known, and continuation state where applicable.

Active resources may be revalidated after an confirmed release. Fixed-version resources shall use immutable caching and shall retain the same content integrity value. A withdrawn active route shall not erase its fixed-version record; access to that record shall follow the confirmed status and visibility rule.

A document export shall identify the standards document number, authoritative title, version, status, language, fixed-version route, clause anchors, and content integrity value. Markdown, structured data, reader HTML, print, and citation representations shall be generated from the same confirmed object and shall preserve requirement identity, formal language, tables, notes, and relationship destinations.

A citation shall resolve to a document or stable clause anchor. A citation to an active route shall display the represented version. A citation intended to support an enduring claim shall use the fixed-version route. An export package shall include a manifest and integrity values sufficient to verify that every included resource belongs to the same confirmed release.

Accessibility metadata is part of the representation contract. Reader and export output shall preserve heading order, table header relationships, descriptive labels, alternative text, keyboard-operable destinations, and a text equivalent for any non-text content.

Conformity with Public Interface and Export Format Specification requires evidence comprising the schema result, object identity, relationship check, permission event, and reconstruction test. The record for each applicable GTA-DATA-004 requirement shall permit reconstruction without relying on an unrecorded explanation.

Evidence created under GTA-DATA-004 shall use stable identifiers, immutable event sequence numbers, and machine event timestamps. A correction shall be append-only. A nonconformity shall place the affected object in a non-releasable state until its consequence and confirmed disposition are recorded. Role combination remains subject to the mandatory separation rules.