House of Yakuba Registry · Complete Directory
144HOUSE OF YAKUBA REGISTRY144 BLOODLINE DIRECTORY

UNDER YAH · THE TREE & RIVER COVENANT

144 Tribal Bloodline Yakubas

A protected registry of ancestral continuity—organizing Yakubas, their Trubas, and verified members while preserving the dignity of every bloodline.

Explore 144 seats

◈ Verified stewardship    ◉ Private member records    ⌁ Passport photo intake

144HEREDITARY SEATS
Roots preserve the record.
The river carries it forward.

SPOKEN REGISTRY ORIENTATION

How to use the House of Yakuba Registry

Registry Orientation Transcript

Welcome and purpose

Welcome to the House of Yakuba Registry, the protected directory of the one hundred forty-four Yakuba bloodline fraternities, their Truba family houses, and their verified members. The Registry preserves the record while organizing each person beneath the correct family and bloodline structure.

Public member verification

A visitor, institution, or law-enforcement officer does not need an administrative login to check an issued Registry ID. In the Public ID Confirmation box, enter the final four digits printed on the member's ID and select Verify Member. When one verified record matches, the Registry displays the official photograph, government or commercial name, tribal name when recorded, birthdate, current age, complete Registry ID, and Verified or Active status. Pending and rejected applications do not appear.

Understanding the directory

The directory follows one clear order: Yakuba, then Truba, then member. Begin by choosing one of the one hundred forty-four Yakuba seats. The Registry then displays the Trubas established beneath that Yakuba. Choose a Truba to see the members assigned to that family. HOUSE OF YAKUBA is a Truba beneath TRUBIAN VILLAGE CHOCTAW; it is not the name of the entire directory.

Administrative offices

The Master Administrator has authority across the complete Registry and may establish Assistant and Yakuba office access codes. The Assistant Administrator can assist with records and verification. Each Yakuba Administrator is limited to the Trubas and members belonging to that Yakuba. Select Administrative Login, choose the assigned office, enter the private passcode, and enter the administrative workspace.

Adding Trubas and members

To establish a family unit, open the Trubas section, select the parent Yakuba, enter the Truba number, Truba name, family line, and official website when available, and save the record. To add a member, open Upload Member and enter the government or commercial name, tribal name, birthdate, parent Yakuba, Truba, and location code. Upload a clear passport-style JPG, PNG, or WebP photograph.

Verification and identification

A submitted member begins with Pending status. An authorized steward reviews the information and photograph, confirms the proper Yakuba and Truba placement, and then assigns the Truba and individual member numbers. Approval creates the nine-digit Registry ID using location, Yakuba, Truba, and member identifiers. Only after approval does the record become Verified and available through the public last-four check.

Privacy and stewardship

The public may explore the Yakuba and Truba structure, but the directory does not publicly display every member. A member appears publicly only through a successful individual verification. Registry administrators should enter accurate information, protect photographs and birth records, correct errors promptly, and treat every office as an office of stewardship rather than personal power.

Begin

Start with the audiobook orientation, use the public verification box when confirming an ID, explore the complete directory to understand the family structure, or enter the administrative office to add and verify records. This is the House of Yakuba Registry: preserving the roots, organizing the living record, and carrying the inheritance forward.

144Yakuba seats

6Founding Yakubas

138Reserved placeholders

4ID identifiers

PUBLIC ID CONFIRMATION

Verify a member without logging in

Enter only the final four digits printed on the member's Registry ID. A uniquely matching verified record will display the official registry photograph, name, birthdate and current age.

Member Verification Check

Only records approved as Verified / Active can be confirmed.

YAKUBA → TRUBA → MEMBERS

Complete Registry Directory

Select a Yakuba to see its Trubas. Select a Truba to see its members. Member details remain available to a signed-in administrative office; the public verification box above confirms one verified ID at a time.

THE COMPLETE CIRCLE

Registry of 144 Yakuba Seats

The six established Yakubas appear first. Seats 007–144 remain editable placeholders until each fraternity is formally entered.

● Founding    ○ Reserved

DOCUMENTED PLACEMENT

Yakubas and their family Trubas

Public pages show the cultural structure. Member identity details appear only through a successful last-four verification or an authorized administrative session.

YAK-001 · TRUBIAN VILLAGE CHOCTAW

HOUSE OF YAKUBA

Kuta Gulukwaila / Cuthaugula Coahuila

  • HOUSE OF YAKUBA
  • Wiyot Family Truba
  • Gaddis Lusa-Iyyi Truba
  • Yetti Family Truba
  • Unetlanvhi Family Truba
  • Jones Family Truba
  • Burton Family Truba
  • Smith Family Truba
YAK-002 · TREE & RIVER COVENANT

House of Holitopa Bloodline Trust

Hattak Lusa Holitopa

  • Holitopa Family Tribal Trust
  • Douglas Clan

NINE-DIGIT IDENTITY

Four identifiers.
One continuous record.

The registry number identifies location, Yakuba, Truba and member without revealing a legal name, birth date, age or private information.

HOUSE OF YAKUBA VERIFIED REGISTRY IDENTIFICATION
PHOTO
TRIBAL NAMEIssued after verificationREGISTRY NUMBER01-001-01-01STATUSVERIFIED MEMBER
Tree & River Covenant ◈ 144

PRIVACY BY DESIGN

The public sees the structure.
Authorized stewards see the record.

  • Public: Yakuba names, Truba names and official tribal websites
  • Restricted: member names, birth dates, photographs and documents
  • Age is calculated from birth date and updates automatically
  • No Social Security number is requested or stored