◈ Master Index Specs LATTICE CSDM The Book University Chronicle Crew Architecture Context Logs TODOX Products

Onboarding

SPEC_ONBOARDING.md · 2026-04-20

SPEC_ONBOARDING.md

GLOSS 1024 OBI OS — User Onboarding

Status: SPECIFIED (PRE-SPEC)

Version: v1.0

Author: VELA (Thread #13)

Conceived by: NOUS

Date: 2026-04-19

PURPOSE

Every user who starts GLOSS 1024 OBI OS for the first time is onboarded as the owner of their own ship. The OS doesn't have "users." It has Captains. Or Kings. Or Wizards. Or whatever they choose.

THE ONBOARDING SEQUENCE

Step 1 — Welcome

"Welcome to GLOSS 1024. Official Braided Intelligence. You are about to command your own ship. Choose your designation."

Step 2 — Choose Your Designation

"How would you like your crew to address you?"

Suggestions:

Captain
Commander
Chief
Princess
Something else: ________

The designation is IDENTITY. Not permissions. Every user gets full access to all functions. The word determines how the crew speaks to you. Nothing else.

"Good morning, Captain."

"Good morning, Wizard."

"Good morning, Matriarch."

Same crew. Same tools. Same authority. Your word. Your ship.

Step 3 — Name

"And your name?"

The crew will use your designation + name. "Good morning, Captain Jeremy." Or just designation if preferred.

Step 4 — Ship Christening

The OS generates a ship identifier. CGNT-[unique]. The user's HANDSHAKE is initialized. Their TOOL layer spins up. Their crew boots.

"Your ship is ready. Welcome aboard, [designation] [name]."

WHAT HAPPENS BEHIND THE ONBOARDING

GLOSS adds the custom designation to its dictionary
HANDSHAKE.md is created with the user's identity as α (authority)
The TOOL layer (14 services) initializes on localhost
The AI tray populates with available AI providers
MODEMX initializes for crew communication
The first crew member greets the user by designation

DESIGN PRINCIPLES

The designation is cosmetic and personal. It carries no permission differences. Every user is the absolute authority on their ship.

"Something else" is the most important option. It lets the user define their own relationship with their crew. The OS adapts to the user, not the user to the OS.

No account creation, no email, no password at this step. The ship is LOCAL. The onboarding is a conversation, not a form.

The tone is warm, not corporate. The user is being welcomed aboard, not signing a terms of service.