1 Purpose
This document defines reader, rendering, interface, access, or release controls for Content Rendering and Component Specification within the defined Good Taste Awards standards system.
2 Scope
This document applies to the requirements, decisions, records, controls, and outputs expressly identified under Content Rendering and Component 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.
3 Authority and interpretation
The Data and Publication Custodian owns GTA-PUB-002; 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.
3.1 Registered relationships
| Relationship | Direction | Related document |
|---|---|---|
renders_content_model_of | outbound | GTA-DATA-001 |
governs_outputs_of | inbound | GTA-PUB-004 |
governed_by | outbound | GTA-GOV-001 |
rendered_under | inbound | GTA-PUB-001 |
rendered_under | outbound | GTA-PUB-002 |
rendered_under | inbound | GTA-PUB-003 |
rendered_under | inbound | GTA-PUB-004 |
rendered_under | inbound | GTA-PUB-005 |
4 Requirements
GTA-PUB-002-R001 — Markdown profile
The Data and Publication Custodian shall define permitted headings, paragraphs, lists, tables, quotations, code, links, notes, and metadata.
GTA-PUB-002-R002 — Document header
The Data and Publication Custodian shall render identity, title, version, status, language, visibility, owner, and authority consistently.
GTA-PUB-002-R003 — Heading hierarchy
The Data and Publication Custodian shall preserve clause levels, anchors, numbering, and accessible outline.
GTA-PUB-002-R004 — formal callout
The Data and Publication Custodian shall distinguish requirements, prohibitions, recommendations, permissions, examples, and notes.
GTA-PUB-002-R005 — Definition component
The Data and Publication Custodian shall render preferred term, meaning, aliases, and references.
GTA-PUB-002-R006 — Table component
The Data and Publication Custodian shall preserve headers, captions, relationships, scrolling, stacking, print, and accessible alternatives.
GTA-PUB-002-R007 — Decision component
The Data and Publication Custodian shall render thresholds, conditions, progression, result states, and official phrases without ambiguity.
GTA-PUB-002-R008 — Relationship component
The Data and Publication Custodian shall display governs, implements, records, validates, renders, and replacement links.
GTA-PUB-002-R009 — Code and schema component
The Data and Publication Custodian shall render machine examples safely with copy, wrapping, language, and integrity.
GTA-PUB-002-R010 — Asset component
The Data and Publication Custodian shall control mark, diagram, image, caption, alternative text, and responsive source.
GTA-PUB-002-R011 — Print component
The Data and Publication Custodian shall control page hierarchy, breaks, table continuation, links, and identification.
GTA-PUB-002-R012 — Sanitization
The Data and Publication Custodian shall prevent executable or malformed content from altering the reader or exposing restricted data.
5 Publication acceptance matrix
| Acceptance ID | Component | Acceptance criterion | Evidence |
|---|---|---|---|
GTA-PUB-002-A01 | Markdown profile | Define permitted headings, paragraphs, lists, tables, quotations, code, links, notes, and metadata. | automated test and reviewer evidence |
GTA-PUB-002-A02 | Document header | Render identity, title, version, status, language, visibility, owner, and authority consistently. | automated test and reviewer evidence |
GTA-PUB-002-A03 | Heading hierarchy | Preserve clause levels, anchors, numbering, and accessible outline. | automated test and reviewer evidence |
GTA-PUB-002-A04 | formal callout | Distinguish requirements, prohibitions, recommendations, permissions, examples, and notes. | automated test and reviewer evidence |
GTA-PUB-002-A05 | Definition component | Render preferred term, meaning, aliases, and references. | automated test and reviewer evidence |
GTA-PUB-002-A06 | Table component | Preserve headers, captions, relationships, scrolling, stacking, print, and accessible alternatives. | automated test and reviewer evidence |
GTA-PUB-002-A07 | Decision component | Render thresholds, conditions, progression, result states, and official phrases without ambiguity. | automated test and reviewer evidence |
GTA-PUB-002-A08 | Relationship component | Display governs, implements, records, validates, renders, and replacement links. | automated test and reviewer evidence |
GTA-PUB-002-A09 | Code and schema component | Render machine examples safely with copy, wrapping, language, and integrity. | automated test and reviewer evidence |
GTA-PUB-002-A10 | Asset component | Control mark, diagram, image, caption, alternative text, and responsive source. | automated test and reviewer evidence |
GTA-PUB-002-A11 | Print component | Control page hierarchy, breaks, table continuation, links, and identification. | automated test and reviewer evidence |
GTA-PUB-002-A12 | Sanitization | Prevent executable or malformed content from altering the reader or exposing restricted data. | automated test and reviewer evidence |
Public output shall be generated from active sources and entry-level visibility rules. A split source shall produce an explicit public projection; it shall not be published whole or excluded solely because its source also contains internal fields. Fixed-version routes shall remain immutable. Active routes may resolve only the active version.
7 Conformity and records
Conformity with Content Rendering and Component Specification requires evidence comprising the source hash, projection result, route test, access test, and release authorization. The record for each applicable GTA-PUB-002 requirement shall permit reconstruction without relying on an unrecorded explanation.
Evidence created under GTA-PUB-002 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.