A marketplace can be described as a set of interacting roles and services without providing a blueprint for operating one. The distinction between visible interface, trust mechanisms, payment claims, and underlying infrastructure helps researchers reason about what a source does and does not reveal. This overview follows a chronology-first reading of the public record.
Layers, not a single machine
A public-facing interface is only one layer. Accounts, moderation, dispute handling, payment representations, and hosting arrangements are separate functions, and evidence about one does not automatically describe the others.
Claims about governance
Terms of service or interface language may describe intended rules, not actual enforcement. Statements about escrow, reputation, or dispute resolution should be treated as claims unless independent records demonstrate how those mechanisms behaved.
Limits of reconstruction
A static page or screenshot rarely reveals backend implementation. This page therefore uses a conceptual map rather than asserting undocumented technical details about WeTheNorth’s internal systems.
Editorial perspective
Chronology lens: distinguish first publication, reported observation, and later retellings. This is a reading framework, not an additional factual claim about the marketplace.
A practical reading test
If a source mentions a marketplace feature, classify it as an interface element, a claimed governance process, a financial arrangement, or infrastructure—and avoid inferring unseen components.
Editorial lens: Northline
Chronology lens: distinguish first publication, reported observation, and later retellings. The systems view distinguishes a feature that is merely advertised from a function that has been independently observed.