/method/structural-density
Structural density and transparency posture
What structural density names
Structural density names the visible thickness of the governed machinery that backs a rendered record. A page with high structural density renders sources, fragment-level citation spans, entities, typed cross-references, intersections, projections, and disputes alongside the canonical body, with edition history and an audit timeline visible on the same surface. A page with low structural density renders the canonical body and little else.
GARPedia's record renderer is a high-density renderer by design. The right-hand provenance rail, the audit timeline at the foot of the page, and the method panel adjacent to the timeline are the visible difference between a governed-record page and an ordinary wiki page. A reader who does not need any of that information can read the canonical column and ignore the rail; a reader who wants to know where every claim came from has the supporting machinery in plain view.
Discovery posture as metadata
Each rendered record carries an optional discovery_posture field. The field records two booleans: whether the record may be search-indexed, and whether the record may be linked from external surfaces. Both booleans are render-time metadata. They do not configure an indexer, do not determine a robots.txt policy, and do not affect what GARPedia presents on the page.
The metadata exists because the underlying record's profile may declare an intent about discovery that downstream surfaces are expected to honor. GARPedia surfaces the declared intent so a reader can see the posture; the surfaces that actually run search and indexing are responsible for honoring or contradicting it.
Control discharge
Each rendered record carries an optional control_discharge field, which is a list of plain-language notes about which governance and operator controls were discharged before render. The list is descriptive, not configurable. A record might note that all review actions for the current edition were discharged before render, that the anchor-resolution check passed for citation spans and cross-references, and that no whole-record dispute is open at render time.
The notes are reader-facing because the control posture is part of how the record was rendered. Operator workflows, review approval, publication approval, dispute adjudication, and other governed actions live in the GARP Workbench (operator) and in the underlying GARP SDK; the control_discharge field is the render-time receipt that those actions completed.
No hidden ranking
A public read surface that runs search or retrieval implicitly ranks the material it presents. GARPedia does not run search and does not run retrieval, so it does not have a hidden ranking to reveal: list orders are deterministic and visible. The records list orders by registry order. The sources, entities, intersections, and publishers lists order by registry order. The provenance rail orders sources, citation spans, entities, cross-references, intersections, projections, and disputes in a fixed sequence rather than ranking them by any score.
Where ordering is computed rather than fixed, the computation is documented inline. The cross-reference panel groups by canonical relationship type and presents the groups in a fixed order; the intersection page orders member entities by the count of member-record appearances, ties broken by registry order. There is no ranking model behind the panel, no scoring that the reader cannot reproduce from the rendered fields, and no dependency on a query the reader did not type.
Where the posture appears
The transparency posture appears in the MethodPanel at the foot of every record page, alongside the profile's admission boundary. The panel renders the discovery posture and the control-discharge notes, names the rule the record cleared upstream, and states explicitly that GARPedia does not run search, does not run retrieval, and does not host operator controls. The same statements apply across the four-family renderer surface; the method panel is where they are written down.