Contents · 9 sections

1   Introduction 2   The three pathways of registration 3   Stage one — review in KoboToolbox 4   Stage two — import to WordPress 5   Stage three — polish and publish 6   Life after publication 7   Edge cases and integrity safeguards 8   What reviewers must never do 9   Conclusion

Introduction

Kente cloth occupies a singular place in the global imagination of African textile heritage. From its origins among the Asante and Ewe weaving traditions of Ghana and Togo, it has travelled the world as a garment of statecraft, a symbol of pan-African solidarity, and a coveted artisanal commodity. With that prominence has come a familiar problem: counterfeits, mislabelled imports, and unverifiable attributions that quietly erode both the livelihoods of master weavers and the cultural integrity of the cloth itself. The Kente Registry was built to address that problem at scale. Operating at KenteRegistry.org, it issues permanent, verifiable identifiers for individual weavers and individual cloths, and it makes those identifiers checkable by anyone with an internet connection.

What follows is a scholarly but readable account of how the Registry actually validates a Kente weaver and a Kente cloth, drawn from the Reviewer’s Manual that governs the work. The process is deliberately small in moving parts and large in safeguards. It runs across three coordinated stations — a field-data tool called KoboToolbox, a WordPress importer, and the public-facing site itself — and it is designed so that nothing destructive can happen by accident.

The three pathways of registration

Every validation begins with a choice the submitter makes at the very top of the registration form. The Registry recognises three distinct pathways, and the pathway determines both the kind of public record that will be created and the prefix carried by the cloth’s or weaver’s permanent identifier. A Weaver Registration produces a Master Weaver profile and is assigned the prefix KR-W. A Cloth Registration produces a Cloth Profile under the prefix KR-D, the D denoting a documented cloth entered into the registry as a primary record. A Cloth Authentication, by contrast, produces a Cloth Profile of the authentication variant and carries the prefix KR-C, the C signalling that the entry is principally concerned with attesting an existing cloth’s chain of custody and provenance.

Whatever the pathway, the identifier itself follows a single, strict format: KR-{prefix}-{year}-{serial}, for example KR-W-2026-15047. Crucially, the serial component is shared across all three prefixes. The registry as a whole therefore advances as a single, strictly sequential ledger, and no two records — regardless of pathway — can ever share a serial. This is more than a tidy convention; it is the structural guarantee that the registry’s growth can be audited and that gaps or duplications would be immediately visible.

Stage one: review and approval in KoboToolbox

Validation begins where the submission lands. KoboToolbox, an open-source data-collection platform widely used in research and humanitarian work, hosts the Registry’s intake form. When a reviewer signs in and opens the data table, every submission appears as a row with its submitter, date, pathway, headline fields, and current status.

The reviewer’s first responsibility is unhurried reading. The manual is explicit that every field must be examined, with particular care given to those that will surface publicly. The display name, for instance, becomes both the post title and the headline on the certificate, and so its spelling, capitalisation, and punctuation are treated as matters of editorial consequence rather than cosmetics. The submitter or weaver name must match the person being credited. Dates and locations — village or town, region, year woven, year registered — must be coherent. Every photograph is opened at full size; blurred, watermarked, or evidently appropriated images are rejected, because the first photograph becomes the hero image of the certificate and must therefore be clean.

Pathway-specific scrutiny then follows. For a KR-D cloth registration the reviewer interrogates designer, original weaver, dimensions, materials, and motif descriptions. For a KR-C authentication the reviewer focuses on the chain of custody and the supporting evidence that anchors the cloth to its claimed origin. For a KR-W weaver registration, biography and lineage carry the weight, since these are the foundations on which a master weaver’s public record will rest.

Where a field is wrong, missing, or sloppy, the reviewer corrects it directly inside Kobo and saves. Kobo retains a revision history, so the original is never lost; rather, every edit becomes part of an auditable trail. Where a submission cannot be brought up to standard from the reviewer’s desk — because it is too incomplete or too dubious — the reviewer marks it Not Approved with an explanatory comment, and the submitter is invited to resubmit. Only when the record is clean does the reviewer set the validation status to Approved. That single action is the gate. Nothing flows downstream automatically; the next station will see the approval the next time it is opened.

There is a deliberate methodological reason for cleaning data in Kobo rather than in WordPress. Kobo preserves the raw submission as evidence and tracks every revision against it, so the audit trail remains honest. Once a submission has crossed into WordPress, the WordPress post becomes the canonical record from that point forward and Kobo settles into its long-term role as a permanent archive of what was first submitted.

Stage two: importing approved submissions into WordPress

The second station is the Import from Kobo screen inside the WordPress admin, reached from Tools in the left-hand menu. It presents a table of every approved Kobo submission with its Kobo ID, pathway, display name, submitter, approval timestamp, and current status. Rows marked Ready are approved but not yet imported. Rows marked as already imported are greyed out and will never be re-imported, ensuring that no fresh KR number is ever burned on a record that already has one.

The reviewer ticks the rows to import — one at a time or several at once — and clicks Import selected. Behind that single click the system performs a sequence of carefully ordered operations. It atomically reserves the next KR serial in the shared sequence, so duplicates and gaps are structurally impossible. It cross-checks against the Supabase backend’s maximum serial as a defence against any stray legacy record colliding with the new one. It creates a Draft post of the appropriate type — Master Weaver or Cloth Profile — and pre-fills the title, the Advanced Custom Fields data, and any uploaded images from the Kobo submission. It stamps the original Kobo identifier onto the new post as the meta value _kr_kobo_id, creating a permanent link back to the source submission. Finally, it adds the Kobo ID to an importer-done list so the same submission can never be imported a second time. The reviewer is then shown a confirmation: Imported 1 record: post 1601 → KR-W-2026-15047, or similar.

The choice to land each record as a Draft rather than a published post is itself part of the validation logic. The KR number is reserved and locked at this point, but the underlying profile remains invisible to the public until a human deliberately publishes it. The Registry’s posture, in other words, is that the issuance of an identifier and the publication of a record are distinct events, and that the latter requires a final human review.

Stage three: polishing the draft and publishing

The third station is the WordPress block editor. The reviewer opens the new Draft from either Master Weavers or Cloth Profiles, where it sits at the top of the list with a Draft status badge, and walks down the post section by section. The title is checked because the certificate’s headline reads from it. The featured image is reviewed and, if necessary, replaced or recropped, since it serves as the hero on both the public profile page and the certificate. The body content is tidied for paragraphing and typography, because this is the narrative that readers will encounter at the public profile URL — /weavers/… for a master weaver, /cloths/… for a cloth.

Attention then turns to the structured data. The Advanced Custom Fields panel, grouped under Certificate fields, holds the discrete attributes that the certificate itself reads: original_weaver, designer, materials, dimensions, year_woven, region, and other_information among them. Each ACF field maps directly to a corresponding line on the certificate, so any change here flows through to the public-facing authentication document. The kr_number_full field is conspicuous here as the one field that must not be touched. It has been set by the importer, it is permanent, and a filter at the system level will refuse any attempt to alter it. The reviewer is instructed to treat it as read-only on principle as well as in practice. Yoast SEO settings, categories, and tags are then completed, and the reviewer uses the Preview function in a new tab to inspect the public profile, opening a second tab to /verify-authenticity/?kr_id=KR-… to view the certificate as the public will see it.

The moment of publication is the moment of validation in the public sense. When the reviewer clicks Publish, the public profile page goes live, the verification certificate at /verify-authenticity/?kr_id=KR-… becomes accessible to anyone with the identifier, search engines may begin to index the page, and the cloth or weaver enters the Registry as a verifiable record.

The issuance of an identifier and the publication of a record are distinct events, and the latter requires a final human review.

— Reviewer’s Manual, Stage Three

Life after publication: corrections without re-issuance

A distinguishing feature of the Registry’s design is that publication is not the end of editorial care. Once a profile is live, any subsequent edit to the WordPress post flows automatically into the certificate within roughly five minutes — the verification endpoint maintains a short cache for performance — without re-importing, re-approving, or re-issuing the KR number. If a master weaver later supplies a fuller biography, or an additional photograph surfaces, the reviewer simply opens the post, makes the change, and clicks Update. The KR number itself is never editable: it is locked at the filter level and refuses writes. The post type is similarly fixed; a Master Weaver cannot be transmuted into a Cloth Profile, and where a re-categorisation is needed a fresh record is created instead.

Edge cases and integrity safeguards

The manual gives unusually close attention to edge cases, and these reveal the Registry’s underlying ethic. When a submission has been approved in Kobo but should not, on reflection, be imported — because a submitter approved their own draft prematurely, or because the cloth was already registered — the preferred remedy is to un-approve it in Kobo, at which point it disappears from the importer table. Where un-approval is impossible, the record can be imported and then trashed without publication; the KR number is then permanently retired as a so-called burnt serial. The Registry tolerates this outcome but does not encourage it, since the integrity of the sequential ledger benefits from minimal waste.

Duplicate submissions for a single cloth are resolved by approving only the canonical entry and rejecting the other in Kobo with a comment that points to it. Factual errors discovered after publication are simply edited in place; the KR number is preserved and the certificate refreshes. Where a published profile is later determined to be fraudulent, the post is moved to Trash, the KR number is retired, and the verification endpoint thereafter returns a not-found response for that identifier — which is itself the correct public signal that authentication has been withdrawn. The original Kobo submission is retained as evidence.

What reviewers must never do

The manual closes with a small set of absolute prohibitions that together describe the Registry’s threat model. The kr_number_full field must never be edited; its permanence is the foundation of every certificate’s trustworthiness. A Kobo submission must never be deleted once imported, because the _kr_kobo_id link back to the source is part of the audit trail. Credentials and API tokens must never be pasted into chats, comments, or public pages; they belong only on the Settings → Kente Importer screen. And bulk editing of Master Weaver or Cloth Profile posts in the WordPress list view is forbidden, because Quick Edit can attempt to write meta fields that the lock will reject, producing harmless but confusing results.

Conclusion

The validation process the Kente Registry has codified is, on its surface, an unremarkable three-step workflow: approve in Kobo, import to WordPress, polish and publish. Read more carefully, it is a layered system of human judgement and structural constraint, in which an atomically reserved sequential identifier, an immutable link to a source submission, a draft-by-default publishing posture, and a deliberately narrow set of editable fields combine to produce certificates that are at once human-verified and machine-auditable. For a textile tradition whose authenticity has too often been asserted without proof, that combination is no small thing. It offers weavers a durable public record of their craft, collectors and institutions a reliable means of authentication, and the broader cultural community a registry whose growth can be inspected, line by sequential line, for as long as the site is online.

---