Understanding Wrenfordia's Information Architecture
An explanation of how information is structured, labelled, and connected within Wrenfordia — including key terminology and navigation guidance for new users.
Why Information Architecture Matters
Wrenfordia's usefulness depends on the consistency of how it organises information. The architecture — the way categories, entries, labels, and connections are structured — directly affects how easy it is to find, interpret, and work with what the system holds.
This page describes that architecture in plain terms. It is intended for users who want to understand the logic behind what they see when using the platform, not just the surface of the interface.
The Three Layers of the Architecture
Wrenfordia's information architecture consists of three overlapping layers:
Layer 1 — Classification Categories
The outermost layer is the category structure. Every item of information belongs to at least one category. Categories are defined by the team and represent the primary way in which information is divided for review. They are stable over time, though new categories may be introduced when the volume or type of information requires it.
Categories are the first thing a user encounters when navigating the system. Selecting a category opens the review interface for that section, presenting the items held within it in a consistent format.
Layer 2 — Classification Labels
Within each category, individual entries carry one or more classification labels. Labels are more granular than categories — they describe specific attributes of an entry rather than its broad subject area. A label might describe the format of information, its origin type, its status within the classification process, or a relationship it holds to other entries.
Labels are visible in the review interface alongside each entry. They allow users to filter and compare entries within a category without needing to read each entry in full before deciding whether it is relevant.
Layer 3 — Cross-References
The innermost layer is the cross-reference network. Where an entry in one category relates meaningfully to an entry in another, the system records a cross-reference. These references are bidirectional: following a cross-reference from Category A to Category B will show a return reference from Category B back to the original entry.
Cross-references are not created automatically for all related entries. They are applied selectively, where the connection is substantive rather than superficial. This keeps the cross-reference layer meaningful rather than overwhelming.
Terms Used Throughout the Platform
Entry
A single item of information held within the system. Each entry belongs to at least one category and carries one or more classification labels. Entries are the basic unit of the Wrenfordia architecture.
Category
A defined subject area within which entries are grouped. Categories are determined by the classification framework and represent the primary navigational structure of the system.
Label
A descriptive tag applied to an entry to indicate a specific attribute. Labels are more granular than categories and support filtering and comparison within a category view.
Cross-Reference
A recorded connection between two entries in different categories where a substantive relationship exists. Cross-references allow users to follow related information across category boundaries.
Classification Metadata
Information recorded about how and when an entry was classified. Metadata includes the category assigned, labels applied, the classification date, and any supplementary flags attached during the organisation process.
Access Level
The scope of categories and entries that a given user has been granted permission to review. Access levels are determined on a per-request basis and may differ between users.
Structured Summary
An overview of the entries within a category, presented when the category contains a volume of items that would be difficult to navigate without an initial orientation. Summaries do not replace individual entry review.
Organisation Timestamp
The date and time at which an entry was first classified within the current framework. Where an entry has been reclassified, the most recent timestamp is shown alongside the original for reference.
Supplementary Flag
An indicator applied to entries that could not be fully classified within the current framework — for example, because source information was incomplete. Flagged entries are visible in the interface but marked for additional attention.
Navigating the Interface
Users accessing the Wrenfordia review interface for the first time may find the following guidance useful for orienting themselves quickly.
Start with the category list
The category list provides an overview of all sections accessible at your current access level. Review the category names and any associated structured summaries before opening individual entries. This saves time by helping you identify the sections most relevant to your purpose before diving into the detail.
Use labels to filter before reading
Once inside a category, scan the classification labels attached to each entry before reading them in full. Labels are designed to give you an immediate signal about the nature and status of an entry, allowing you to prioritise your review based on what you are looking for.
Follow cross-references deliberately
Cross-references are useful but can lead you away from your initial focus if followed without intent. It is generally more efficient to complete your review of the current category before following cross-references, rather than following each one as you encounter it.
Note organisation timestamps
Classification metadata includes an organisation timestamp for each entry. Where the currency of information matters to your review, checking this timestamp will tell you how recently the entry was classified or reclassified.
Raise questions through the enquiries page
If you encounter entries that appear miscategorised, find that the information available does not meet your need, or have questions about the architecture that this page does not address, the appropriate channel is the enquiries page. The team will review all submissions and respond where they are able to.
Related pages: System Overview · Capabilities · Platform Details · Enquiries · Privacy Notice · Terms of Use