Global Ocean Accounts Partnership Secretariat · GOAP Technical Guidance on Ocean Accounting · circular
After reading this Circular, you will understand how the Technical Guidance on Ocean Accounting is organised, the meta-structure each circular follows, the conventions for versioning, stability classification, and dependency tracking, and the production process for circulars. This Circular is a reference for authors, editors, and users of the Technical Guidance.
None.
This Circular is a meta-circular: it describes how the Technical Guidance itself is organised rather than providing substantive ocean accounting methodology.
The Technical Guidance is organised into seven sections:
Each circular is identified by: TG-[Section].[Number]
The number .0 is reserved for a section-framing circular: one that establishes the vocabulary and the routing the rest of its section depends on, and that carries no method of its own. Section 1 has one, TG-1.0, because the terminology of ocean economy measurement is used by the other twelve circulars in that section. Sections without such a circular begin at .1, and a .0 is not to be created to complete a pattern.
The version number is recorded in the circular’s YAML frontmatter as a separate version field (e.g., version: "0.2.0"). Major increments reflect substantive content changes, whilst minor increments reflect editorial improvements.
Each circular carries a stability badge indicating its relationship to underlying standards. See TG-0.5 Navigating the Technical Guidance for full definitions. Summary:
All circulars follow a standard structure to ensure consistency for readers. This section specifies the template for circular authors.
Every circular begins with machine-readable YAML frontmatter:
Editorial fields only. The block above is what a circular author writes. Each page also carries platform frontmatter — project, visibility, status, content_type, brand, sidebar_category and sidebar.order — which the /new-page skill sets and authors do not hand-edit.
status and circular_status are different fields. status is the platform publish gate (working or published) and governs whether a page is built at all. circular_status is the editorial state (Draft, Completed, Planned) shown in the metadata table. A page can be status: published and circular_status: Draft at the same time — that is the normal state for a circular out for consultation.
Note on badge: See Section 3.3 for stability classification definitions. Note on publication version: The version field reflects the public publication version, not the internal pipeline draft count. Pipeline drafts (e.g., draft-v4, draft-v6) are production artefacts only, and the publication version is confirmed by the Secretariat before a circular moves to Completed status.
The site renders a metadata table automatically from YAML frontmatter (circular_id, version, badge, circular_status, last_updated). Authors do not hand-write the display block in the markdown body.
Required frontmatter fields for the metadata table:
Note on Last Updated: Manually maintained by the author at publication time.
Note on numbering: Acknowledgements is always second-to-last and References always last, numbered consecutively after whatever Guidance content is present. An optional “Limitations and Considerations” section may appear between Guidance Material and Acknowledgements, in which case it becomes Section 4, whilst Acknowledgements and References shift to Sections 5 and 6 respectively.
Section 5 circulars use an adapted structure for country/regional case studies:
Note: This template has not yet been validated against compiled Section 5 drafts. Authors should cross-check against TG-5.x working drafts when available.
Section 0 circulars have unique structures appropriate to their purpose:
Any Section 0 circular not listed above follows the Standard Circular Template.
Each section’s scope is stated in Section 3.1. The tests below say what that scope means when an author is deciding whether a passage belongs in the circular they are writing. They were derived from the Section 1 review of September 2026 and the Section 3 review that followed it, both of which found method distributed across sections that had no rule to test it against.
Two consequences are worth stating explicitly, because both have been breached in practice:
Every circular in Sections 1 to 4 and 6 should carry a short boundary statement, in its :::note[Framework Position] block or immediately after it, naming which account or decision it owns and which circulars own the method it excludes. TG-3.9 is the model.
Page counts refer to rendered PDF A4 pages at approximately 500 words per page. These are guidance targets, not enforced limits.
Format: v0.[Major].[Minor] — the leading 0. marks the consultation edition, which is not adopted guidance
Superseded versions will be archived, with the URL scheme to be confirmed. The current version always appears at the canonical URL.
Table 7.1.1 below summarises the full per-circular review lifecycle for the Second Edition.
Internal production uses an extended triage / director-review / Secretariat-review pipeline. Details are documented in project tooling and are not part of this public-facing circular.
Circulars are published on a monthly cadence following Secretariat review, with publication frequency varying by batch. Priority circulars may be fast-tracked, and updates to existing circulars are published as needed.
Dependencies are tracked in two ways:
prerequisites and enables fields in each circularThe prerequisites field and the prose Requirements section must be kept synchronised. The enables field is machine-readable only and has no prescribed prose counterpart.
See TG-0.5 Navigating the Technical Guidance for the visual dependency graph.
Cross-cutting themes are catalogued in TG-0.5 Navigating the Technical Guidance. Authors should ensure consistency with the treatments described there. Key threads include:
Authors: [To be confirmed]
Reviewers: [To be confirmed]
GOAP. (2024). Discussion Paper: Modular Structure for GOAP Technical Guidance (internal working paper, GOAP Secretariat, not publicly distributed). Global Ocean Accounts Partnership.
United Nations. (2025). System of National Accounts 2025. United Nations.
United Nations. (2021). System of Environmental-Economic Accounting—Ecosystem Accounting. United Nations.
UNECE. (2019). Generic Statistical Business Process Model (GSBPM), Version 5.1.
Cite this report
Structure and Focus of the Technical Guidance (2026) (GOAP Technical Guidance on Ocean Accounting, TG-0.4, v0.10.1). GOAP Secretariat. https://guidance.oceanaccounts.org/circulars/section-0/0-4-structure/
guidance.oceanaccounts.org/circulars/section-0/0-4-structure
© 2026 Global Ocean Accounts Partnership Secretariat · CC BY-NC 4.0 · The report, its PDF and this deck are built from the same source.
Swipe on touch screens. Print gives one landscape page per slide. The address keeps the slide number, so a link opens on the right slide. On a phone in portrait the deck becomes a scrolling document.