1 Purpose
This document defines reader, rendering, interface, access, or release controls for Standards Reader Information Architecture for Good Taste Awards.
2 Scope
This document applies to the requirements, decisions, records, controls, and outputs expressly identified under Standards Reader Information Architecture. 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-001; 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 |
|---|---|---|
presents | outbound | GTA-REG-001 |
governed_by | outbound | GTA-GOV-001 |
rendered_under | outbound | GTA-PUB-002 |
4 Requirements
GTA-PUB-001-R001 — Reader audiences
The Data and Publication Custodian shall serve public readers, entrants, assessors, operations, reviewers, and technical implementers through confirmed views.
GTA-PUB-001-R002 — Primary navigation
The Data and Publication Custodian shall organize overview, standards, schedules, category guidance, category modules, procedures, forms, data, registries, and governance while identifying explanatory guidance separately from published requirements.
GTA-PUB-001-R003 — Document page
The Data and Publication Custodian shall display identity, title, status, authority, contents, clauses, relationships, and permitted downloads.
GTA-PUB-001-R004 — Clause page
The Data and Publication Custodian shall support stable focused reading and citation without losing document context.
GTA-PUB-001-R005 — Topic pathways
The Data and Publication Custodian shall connect taste, panels, samples, decisions, comments, claims, data, and publication topics.
GTA-PUB-001-R006 — Task pathways
The Data and Publication Custodian shall support entering a product, shipping samples, joining panels, running sessions, deciding stars, and publishing results.
GTA-PUB-001-R007 — Search experience
The Data and Publication Custodian shall prioritize authoritative English content and defined identifiers and distinguish formal results from explanatory guide results.
GTA-PUB-001-R008 — Related content
The Data and Publication Custodian shall show governing, implementing, evidence, validation, and publication relationships.
GTA-PUB-001-R009 — Visibility
The Data and Publication Custodian shall prevent restricted content from appearing through navigation, search, preview, or export.
GTA-PUB-001-R010 — Status communication
The Data and Publication Custodian shall show defined current content and replacement relationships through registered state.
GTA-PUB-001-R011 — Mobile information hierarchy
The Data and Publication Custodian shall preserve title, status, contents, text, tables, and related links on narrow screens.
GTA-PUB-001-R012 — Reader verification
The Data and Publication Custodian shall provide content identity and integrity sufficient for reliable citation.
5 Publication acceptance matrix
| Acceptance ID | Component | Acceptance criterion | Evidence |
|---|---|---|---|
GTA-PUB-001-A01 | Reader audiences | Serve public readers, entrants, assessors, operations, reviewers, and technical implementers through confirmed views. | automated test and reviewer evidence |
GTA-PUB-001-A02 | Primary navigation | Organize overview, standards, schedules, category guidance, category modules, procedures, forms, data, registries, and governance while identifying explanatory guidance separately from published requirements. | automated test and reviewer evidence |
GTA-PUB-001-A03 | Document page | Display identity, title, status, authority, contents, clauses, relationships, and permitted downloads. | automated test and reviewer evidence |
GTA-PUB-001-A04 | Clause page | Support stable focused reading and citation without losing document context. | automated test and reviewer evidence |
GTA-PUB-001-A05 | Topic pathways | Connect taste, panels, samples, decisions, comments, claims, data, and publication topics. | automated test and reviewer evidence |
GTA-PUB-001-A06 | Task pathways | Support entering a product, shipping samples, joining panels, running sessions, deciding stars, and publishing results. | automated test and reviewer evidence |
GTA-PUB-001-A07 | Search experience | Prioritize authoritative English content and defined identifiers and distinguish formal results from explanatory guide results. | automated test and reviewer evidence |
GTA-PUB-001-A08 | Related content | Show governing, implementing, evidence, validation, and publication relationships. | automated test and reviewer evidence |
GTA-PUB-001-A09 | Visibility | Prevent restricted content from appearing through navigation, search, preview, or export. | automated test and reviewer evidence |
GTA-PUB-001-A10 | Status communication | Show defined current content and replacement relationships through registered state. | automated test and reviewer evidence |
GTA-PUB-001-A11 | Mobile information hierarchy | Preserve title, status, contents, text, tables, and related links on narrow screens. | automated test and reviewer evidence |
GTA-PUB-001-A12 | Reader verification | Provide content identity and integrity sufficient for reliable citation. | 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 Standards Reader Information Architecture requires evidence comprising the source hash, projection result, route test, access test, and release authorization. The record for each applicable GTA-PUB-001 requirement shall permit reconstruction without relying on an unrecorded explanation.
Evidence created under GTA-PUB-001 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.