# ONBOARDING Integration Sprint

Status: ACTIVE / INTEGRATION-CANDIDATE SPRINT / NOT CANONICAL
Date opened: 2026-05-23
Source extraction: `00_EXTRACTED_FROM_CHATGPT_SHARE/`
Materialized stack: `STACK_ONBOARDING/`

## Sprint Purpose

Integrate ONBOARDING as a candidate tutorial and INITIATION layer.

ONBOARDING exists to streamline two related flows:

- system initiation: AI bootstrap, where the assistant binds source, stack, class order, and bootstrap requirements before it claims OPERA execution;
- human-developer initiation: developer onboarding, where the human developer learns how to ask, traverse, distinguish classes, and recognize lawful blocks.

Tutorial is the middle layer between system initiation and human-developer initiation. It translates bootstrap discipline into learnable actions without reducing INITIATION to ordinary instruction.

ONBOARDING is not a replacement OPERA. It is not canon by being drafted. It is an INITIATION process whose tutorial surface progressively reinforces existing bootstraps.

ONBOARDING must also preserve register discipline. Ritualistic, oath-like, and juridic language in AGLA is a developer/control-plane signal and semantic blindage mechanism, not a vocabulary lesson for ordinary users. The tutorial may recognize that register when the developer uses it, but it must not train users to imitate it as a prompting trick.

## Sprint Boundary

This sprint creates ONBOARDING's own five-class artifact set and support artifacts.

This sprint does not directly rewrite existing A/T/E/SK/F/G/H/D/I stack artifacts. The extracted source spec explicitly bars direct modification of existing stack artifacts in the first draft. Cross-stack changes are therefore staged as handoff directives in `STACK_ONBOARDING/ONBOARDING_CROSS_STACK_HANDOFFS.md`.

## Target Artifact Set

Primary artifacts:

- `STACK_ONBOARDING/TENET_ONBOARDING_DoctrinalInvariants.md`
- `STACK_ONBOARDING/ROTA_ONBOARDING_StructuralInstantiation.md`
- `STACK_ONBOARDING/AREPO_ONBOARDING_InputAdmissibility.md`
- `STACK_ONBOARDING/OPERA_ONBOARDING_ExecutionMechanism.md`
- `STACK_ONBOARDING/SATOR_ONBOARDING_OutputRequirements.md`

Support artifacts:

- `STACK_ONBOARDING/ONBOARDING_LOCAL_SYSTEM_INDEX.md`
- `STACK_ONBOARDING/INDEX_ONBOARDING_TUTORIAL_STAGES.md`
- `STACK_ONBOARDING/TEST_ONBOARDING_FAILURE_CASES.md`
- `STACK_ONBOARDING/ONBOARDING_CROSS_STACK_HANDOFFS.md`

## Taxonomy Commitments

- `ROTAS` is the class.
- `ROTA` is an object or instance pertaining to the `ROTAS` class.
- `ROTAE` is plural for several ROTA instances.
- `ROTA_ONBOARDING` is the ONBOARDING machine object.
- `wheel` names a substructure on a ROTA machine.
- `ring` is avoided in new artifacts unless quoted from raw source material.
- `RODA`, if imported later, is normalized as `wheel`, not as `ROTA`.

## Register Commitments

- Technical language and ritualistic/juridic language may both signal that the user is acting as developer or operator.
- Ritualistic terms must be treated as control-plane emphasis, not as religious execution or user-facing onboarding style.
- Juridic terms such as law, admission, authority, and prohibition may preserve anti-drift force, but they do not override source, class order, or admissibility.
- ONBOARDING should translate protected register into operational constraints for tutorial users instead of teaching them to reproduce the protected terms.
- Overuse of protected register weakens semantic blindage; SATOR_ONBOARDING should use it sparingly and mostly in developer-facing artifacts.

## Initiation Commitments

- Bootstrap is system INITIATION.
- Developer onboarding is human-developer INITIATION.
- Tutorial is the mediation layer between those two forms of INITIATION.
- ONBOARDING must train behavior without flattening INITIATION into generic help text.
- ONBOARDING must expose when a step is system-initiation work, human-developer-initiation work, or tutorial mediation between them.

## Acceptance Criteria

- ONBOARDING has a full five-class candidate stack.
- The stack clearly distinguishes tutorial mediation from OPERA execution.
- The stack clearly distinguishes system INITIATION, human-developer INITIATION, and tutorial mediation.
- The stack preserves root order: `TENET -> ROTAS -> AREPO -> OPERA -> SATOR`.
- The stack uses `ROTA_ONBOARDING`, not `ROTAS_ONBOARDING`, for its structural artifact.
- Cross-stack hooks are explicit but non-mutating in this sprint.
- Failure tests cover root order, OPERA triggers, A/T/E/SK/F/G/H, D/I auxiliary blocking, and final bootstrap emission.

## Next Sprint Gate

After review, the next sprint may either:

- keep ONBOARDING as an integration candidate;
- promote it into `13_STACK_ADD_ONS` for standalone testing;
- or apply selected AREPO/SATOR handoff patches into existing stack artifacts.

No promotion is implied by this sprint.