ABL WEBSITE — HOW IT WORKS

Status: Draft v0.1
Authority: Canon-governed
Purpose: Explain system mechanics without instruction, persuasion, or promises

OVERVIEW

Adaptive Bespoke Learning operates through structured programs governed by explicit rules.

This page explains how those programs are organized and accessed.

It does not explain what participants should do or achieve.

PROGRAM STRUCTURE

ABL programs are built as discrete systems.

Each program:

  • Has a defined purpose

  • Operates within declared boundaries

  • Is versioned and auditable

  • May be active, gated, archived, or design-complete

Programs do not merge or overlap unless explicitly stated.

ACCESS & STATUS

Program access varies by design.

Possible states include:

  • Public — visible and accessible

  • Gated — visible with restricted access

  • Internal — administrative or development use only

Program status indicates operational state, not value or priority.

TIERS (WHEN PRESENT)

Some programs include tiers.

Tiers:

  • Are optional

  • Are explicitly separated

  • Do not imply progression or advancement

Non-participation at any tier is a valid outcome.

PARTICIPATION BOUNDARIES

Participation:

  • Is voluntary

  • Does not create authority

  • Does not imply endorsement

  • Does not require completion

Programs are designed to function correctly even when participants disengage.

DATA & ARTIFACT HANDLING

When data or artifacts are collected:

  • Scope is declared in advance

  • Use is limited to stated purposes

  • Aggregation and publication are controlled

Absence of data is treated as valid information.

CHANGE CONTROL

ABL programs change only through explicit administrative action.

Changes:

  • Are recorded

  • Are versioned

  • Do not occur implicitly through use or feedback

If no change is declared, the system remains unchanged.

FINAL STATEMENT

This page describes mechanics, not expectations.

Using an ABL program does not require belief, agreement, or action.