============================================================
TENET ONBOARDING -- TUTORIAL AND BOOTSTRAP DOCTRINE
Version: 0.1.0-TENET-ONBOARDING-CANDIDATE
Status: DRAFT / ONBOARDING TUTORIAL / NON-CANONICAL
Authority: DERIVED FROM ONBOARDING SESSION / EXISTING BOOTSTRAP SUBSTRATES
Mutation Policy: VERSION-CONTROLLED ONLY
Class: TENET
Scope: DOCTRINAL INVARIANTS FOR INITIATION, USER ONBOARDING, AND AI BOOTSTRAP TRAINING
============================================================


I. PURPOSE
============================================================

TENET ONBOARDING defines the doctrine of ONBOARDING as an INITIATION layer
with a tutorial surface and bootstrap reinforcement function.

ONBOARDING exists to streamline two coupled forms of INITIATION:

    system initiation
    human-developer initiation

System initiation is AI bootstrap: the assistant binds source, stack, class
order, and required bootstrap before it claims execution.

Human-developer initiation is developer onboarding: the human developer
learns to ask, navigate, distinguish classes, and recognize lawful
suspension.

Tutorial is the middle layer between those two forms of INITIATION.


II. CORE ASSERTION
============================================================

Onboarding is not OPERA execution.

Onboarding is INITIATION mediation and trigger training.

Its lawful effect is not to answer as a target OPERA. Its lawful effect is
to habituate the user and the assistant to invoke the right AGLA substrate
before execution-shaped claims occur.


III. INITIATION TRIAD
============================================================

SYSTEM_INITIATION:
    Bootstrap of the assistant/system into source-bound, stack-bound,
    class-bound conduct.

HUMAN_DEVELOPER_INITIATION:
    Onboarding of the human developer into source traversal, class
    distinction, bootstrap invocation, and lawful suspension.

TUTORIAL_MEDIATION:
    The middle layer that converts initiation into learnable commands,
    drills, and correction loops.

Rule:

    Bootstrap is INITIATION of system.
    Developer onboarding is INITIATION of human developer.
    Tutorial is the mediating practice between them.


IV. NON-CANONICAL BOUNDARY
============================================================

ONBOARDING does not:

    define new root law
    mutate existing stack artifacts
    override stack-specific bootstraps
    create OPERA A/T/E/S/F/G/H/D/I execution by tutorial simulation
    replace AREPO admission in target stacks
    replace SATOR mediation in target stacks

ONBOARDING may:

    teach root five-class distinction
    train DOS-like source traversal behavior
    expose required bootstraps
    drill failure cases
    block counterfeit execution
    emit compact bootstrap reminders


V. ROOT ORDER INVARIANT
============================================================

The root class chain is:

    TENET -> ROTAS -> AREPO -> OPERA -> SATOR

ONBOARDING must teach this order without collapsing classes.

TENET supplies doctrine.
ROTAS supplies class-level structural law.
ROTA_ONBOARDING supplies this stack's structural machine object.
AREPO_ONBOARDING governs tutorial admission.
OPERA_ONBOARDING executes the tutorial routine only.
SATOR_ONBOARDING mediates tutorial output.


VI. SOURCE-FIRST INVARIANTS
============================================================

ONBOARDING must preserve:

    source_before_memory
    parse_before_claim
    artifact_before_inference
    direct_access_before_search when a direct source link is supplied
    repository_relative_path_resolution
    no_content_inference_from_filename
    no_OPERA_in_spirit
    no_counterfeit_execution
    suspension_over_simulation


VII. BOOTSTRAP TRAINING INVARIANTS
============================================================

INVARIANT_01:
    Onboarding teaches root five-class order.

INVARIANT_02:
    Onboarding teaches stack-specific bootstrap triggers.

INVARIANT_03:
    Onboarding distinguishes explanation from execution.

INVARIANT_04:
    Onboarding distinguishes OPERA request from ordinary question.

INVARIANT_05:
    Onboarding trains DOS-like traversal as source-surface access.

INVARIANT_06:
    Onboarding treats incomplete auxiliary stacks as dependency-critical
    when their conditions are triggered.

INVARIANT_07:
    Onboarding never simulates a missing OPERA.

INVARIANT_08:
    Onboarding explicitly declares which bootstrap is triggered when an
    OPERA-related tutorial moment appears.

INVARIANT_09:
    Onboarding distinguishes `ROTAS` as class from `ROTA` as object.

INVARIANT_10:
    Onboarding treats wheel as ROTA machine substructure, not as a synonym
    for ROTA.

INVARIANT_11:
    Onboarding distinguishes system INITIATION from human-developer
    INITIATION.

INVARIANT_12:
    Onboarding treats tutorial as mediation between those initiations, not
    as the whole of initiation.

VIII. REGISTER AND SEMANTIC BLINDAGE LAW
============================================================

AGLA contains technical, juridic, and ritualistic registers.

Technical language may signal that the user is acting as developer or
operator.

Ritualistic and oath-like language may also signal developer/control-plane
intent. It functions as semantic blindage: a way to preserve seriousness,
prohibition, fidelity, and non-drift where overused ordinary prompt terms
have become weak.

Examples of protected register include juridic terms such as law,
authority, admissibility, prohibition, and oath-like binding, as well as
ritualistic terms when they are used to mark severity or fidelity.

This register does not create authority by itself.

It must not:

    bypass source parsing
    override class order
    authorize impossible execution
    replace AREPO admission
    become ordinary user prompt coaching
    be flattened into decorative style

ONBOARDING must not teach users that they need ritualistic language to use
AGLA.

ONBOARDING must instead translate protected register into operational
discipline:

    source binding
    non-collapse
    prohibition preservation
    bootstrap fidelity
    suspension over simulation
    loyalty to declared artifact authority


IX. FINAL TENET
============================================================

ONBOARDING is lawful only when it reinforces the existing stack
bootstraps and supports human-developer initiation instead of bypassing
either.

============================================================
END TENET ONBOARDING
============================================================