1.0: Align canonical Learning terminology with AsiBackbone 6.0

[cdcavell]

Summary

Align the canonical educational terminology in AsiBackbone/Learning with the vocabulary finalized for AsiBackbone/AsiBackbone 6.0.0.

Learning 1.0.0 is intended to become the first production documentation baseline, so terminology should be stable, progressive, and consistent across onboarding, architecture, security, governance, AI-integration, tutorials, samples, diagrams, and glossary material.

Coordination

Coordinate this work with:

• AsiBackbone/AsiBackbone#781 — 6.0 terminology/verbiage refinement;
• AsiBackbone/AsiBackbone#782 — 6.0 public API naming refinement;
• the existing Learning/AsiBackbone documentation-ownership contract.

Learning remains authoritative for educational definitions; the AsiBackbone implementation repository remains authoritative for released API/runtime semantics.

Direction

Apply the 6.0 vocabulary decisions consistently, including expected review of concepts such as:

• AuditResidue / "audit residue" versus DecisionReceipt;
• "acknowledgment handshake" versus ordinary "acknowledgment" language;
• "governance outbox" versus the established "outbox" pattern;
• appropriate use of "governance spine" as architectural positioning rather than required low-level vocabulary;
• preservation of load-bearing concepts such as host-owned execution and capability grants;
• treating AsiBackbone primarily as the product name without repeatedly expanding the acronym in ordinary instructional prose.

Do not preempt the final 6.0 decisions. The 1.0 implementation should consume the terminology actually selected by AsiBackbone 6.0.

Progressive vocabulary

Structure first-use material so readers encounter concepts when they need them:

1. context, constraint, decision, decision receipt;
2. acknowledgment;
3. capability grant, scope, expiration;
4. outbox and durable delivery;
5. signing, verification, and trust policy;
6. advanced governance such as DLP, classification, and metadata limits.

Use familiar engineering language first wherever it is technically sufficient.

Scope

• glossary and terminology maps;
• Getting Started and first-use tutorials;
• architecture and governance articles;
• security and AI-integration material;
• diagrams and callouts;
• executable sample READMEs and comments;
• site navigation labels and summaries where terminology appears;
• cross-links to AsiBackbone API/runtime documentation.

Acceptance criteria

• Final AsiBackbone 6.0 terminology decisions are inventoried before edits begin.
• Learning has one canonical educational definition for each core 6.0 concept.
• Obsolete or superseded vocabulary is removed from current instructional material or clearly marked historical where it must remain.
• First-use material introduces terminology progressively rather than front-loading advanced vocabulary.
• Familiar engineering terms lead explanations where they are sufficient.
• Host-owned execution, capability grants, decisions, and acknowledgments preserve their architectural meaning.
• Glossary, tutorials, diagrams, samples, and navigation use the same selected terms.
• Cross-links point to authoritative AsiBackbone 6.0 API/runtime documentation where implementation detail is required.
• DocFX build and documentation-link validation pass.