ARFC-1011: Learning Objectives and Challenge Alignment

Status

Draft Draft Date: 2026-08-08 Last Call Date: — Publication Date: — Version: 0.1

Abstract

A learning objective is something a student is to achieve during a course. Objectives are the answer to “what must this course cover” — and today the platform has no such concept. It records the standards an authority publishes, and it records the work students do, but nothing states what a course is responsible for teaching, so nothing can report whether it did.

This ARFC introduces the learning objective, establishes where objectives come from, and specifies how a challenge is linked to the objectives it provides evidence for. From those two things, coverage becomes computable: an institution can ask which objectives its course actually evidences, and receive an answer built from student work rather than from assertion.

Two principles shape the design. An authority’s standards are a floor, not a ceiling — they establish the minimum a course must cover, and a teacher may add to them but never subtract. And alignment happens at the challenge, never at the lesson or the course, so that coverage above is always the sum of evidence beneath and a gap is findable rather than merely claimed.

This ARFC says what evidence demonstrates. It does not say what evidence is worth; that is ARFC-1012. It also does not describe how objectives are grouped for teaching, which is ARFC-1013.

Table of Contents

  1. Introduction
  2. Motivation
  3. Specification
  4. Version 1 Scope
  5. Security Considerations
  6. Backward Compatibility
  7. References

1. Introduction

Ask a teacher what their course covers and they will describe objectives — the things students should be able to do by the end. Ask the platform the same question and it cannot answer. It knows which standards a particular piece of work has been aligned to, and it knows every score every student has earned, but it holds no statement of what a course set out to achieve.

The gap has a specific cost. Coverage can be reported only from the bottom up — “these challenges touch these standards” — never checked against an intention. Nothing can say that a course claims to teach something it never assesses, because the course makes no claims. And every feature that depends on knowing what a course owes its students, from progress summaries to gap detection to recommending what to teach next, has nothing to stand on.

This ARFC fills that gap with two additions: the objective, which states what a course is responsible for, and the alignment, which states which pieces of student work provide evidence for it.

2. Motivation

Current State

Standards exist and are aligned to work. The platform models standards authorities, their own hierarchies of chapters and parts, individual versioned standards, and the wording of each. A challenge may be aligned to the text of a standard, and coverage for a mission, lesson, or course is the sum of the alignments beneath it. This works and is unaffected by this ARFC.

Objectives do not exist. There is no concept of a thing a course is responsible for teaching. Standards are reference data published by an external body; they are not a teacher’s statement of intent, they are not scoped to a course, and a teacher cannot add to them.

An objective set can already be generated, and is then discarded. A teacher can select a geographic region, a standards authority, a specific standard, and a course duration, and the platform generates a scaffolded set of instructional objectives from that standard’s leaf-level requirements. The result is written into a standalone planning document. Nothing else in the platform can read it — it is not attached to a course, no challenge can be linked to it, and no report can be built from it.

Three defects in that generation path are worth recording, because this ARFC changes them:

Missing Capabilities

No course can state what it covers. Therefore no course can be found to be incomplete.

A teacher cannot add to what an authority requires. Professional judgement about what students need is capped by what a state chose to write down.

Nothing links student work to an intention. A challenge can be aligned to a published standard, but not to what this course is trying to achieve, so a course’s coverage of its own goals cannot be computed.

“Objective met” is undefined. Existing work in this area is explicitly blocked on it: the product definition of what should be counted has never been settled, so no progress or coverage figure can be built.

Design Goals

  1. An objective states an intention, scoped to a course, distinct from a standard published by an authority and distinct from the work that demonstrates it.
  2. Standards form a floor. A teacher may raise the bar and never lower it.
  3. Comprehensiveness is structural. A generated objective set includes every objective the authority identifies. A partial set is not a set.
  4. Alignment happens at the challenge. Coverage above is always derived, never entered.
  5. Ask for as little as possible. Where the platform can propose an alignment from what it already knows, it proposes.
  6. Do not disturb standards alignment. The existing relation continues to work unchanged; objectives sit alongside it.

3. Specification

3.1 Core Principles

An objective belongs to a course, not to a unit or a lesson. This is deliberate and consequential. If objectives lived inside the groupings a teacher arranges lessons into, then rearranging how a course is taught would appear to change what the course covers. Keeping objectives at the course level means restructuring is safe by construction: a teacher may merge groupings, split them, or reorder them freely, and coverage does not move.

The floor only ever rises. An objective that came from an authority may be added to, promoted, or reworded for clarity, but never removed and never demoted below what the authority requires. Every other edit is permitted.

Coverage is built from the bottom up. Alignment is recorded at the individual challenge. A course cannot assert in the abstract that it covers something; either work exists that evidences it, or it does not. This is the property that makes a coverage report answerable to a parent or an auditor.

An alignment claims only what it can support. By default, linking a challenge to an objective asserts that the work provides evidence of correctness and nothing more. Broader claims are made deliberately, and the platform refuses claims a challenge’s form cannot sustain.

Absence of a claim is not a claim. An objective with no alignments is not covered badly; it is not covered at all, and that is a distinct and reportable state.

3.2 Primary Objects

Learning objective — a statement of something a student is to achieve during a course. Belongs to exactly one course. Carries its wording, whether it is required, and where it came from.

Provenance — whether an objective was derived from a standards authority or added by a person. Provenance governs what may subsequently be done to the objective.

Alignment — a link asserting that a particular challenge provides evidence for a particular objective, together with what kind of evidence it provides.

Coverage — for a given objective in a given course, what evidence exists for it. Always derived, never entered.

flowchart TB
    A[Standards authority<br/>publishes requirements] -->|generation| O
    T[Teacher<br/>professional judgement] -->|addition| O
    O[Learning objectives<br/>scoped to one course<br/>required or optional]
    O -.->|aligned to| C[Challenges<br/>the work students do]
    C -->|evidence rolls up| CV[Coverage<br/>derived, never entered]
    O --> CV

3.3 What an Objective Is, and What It Is Not

The platform already has several concepts that sound similar. Keeping them distinct matters, because conflating them is how coverage reports become meaningless.

Concept What it is Who defines it
Standard a requirement published by an external authority a state, board, or national body
Learning objective something a student is to achieve during this course the authority, then extended by the teacher
Lesson one teachable topic the teacher
Mission the primary means by which a student demonstrates mastery of one or more objectives the teacher
Challenge one question or task a student performs the teacher

An objective states what must be achieved. A mission is how a student shows they have achieved it. A single mission may demonstrate several objectives at once, and a single objective may be demonstrated across several missions in different lessons over a whole year. Neither is a renaming of the other.

3.4 Provenance: the Floor and the Extension

Every objective carries its provenance, and provenance determines what may be done to it.

Provenance Origin May be reworded May be promoted to required May be demoted to optional May be deleted
Authority-derived, required generated from a standard the authority requires yes n/a no no
Authority-derived, extension generated from a standard the authority marks as enrichment yes yes yes no
Person-added entered by a teacher or curriculum lead yes yes yes yes

The pattern across that table is a single rule: a teacher may raise the bar but never lower it. Adding objectives, promoting an extension to required, and rewording for clarity all raise or preserve what students owe. Demoting a required standard or deleting an authority-derived objective would lower it, and the platform refuses both.

Rewording deserves a note. Authorities publish text that is frequently unusable in front of students. A teacher may restate an objective in language their students understand; the platform retains the authority’s original wording alongside it, so a coverage report can cite what the authority actually said while a student-facing view shows the teacher’s phrasing. Rewording never severs the link to the standard it came from.

3.5 Required and Optional

Every objective is either required or optional.

A course’s objective set is complete when every required objective is accounted for. Optional objectives are reported, but never block completeness — they are the enrichment a teacher would like to reach, and treating them as obligations would make “this course is ready” a statement no one could trust.

The distinction is what gives completeness meaning. Without it, either every aspiration becomes an obligation, or nothing does.

3.6 Generating an Objective Set from an Authority

A teacher establishes a course’s objectives by choosing a standards authority and the standard their course answers to. The platform generates the objective set from it.

Comprehensiveness is a requirement, not a quality target. The generated set includes every objective the authority identifies within the chosen scope. A set that samples the standard, or that stops at the objectives for which teaching material already exists, understates what the course owes and makes every coverage report quietly wrong. Generation either produces the complete set or reports that it could not.

Three properties correct the current behavior:

Generation produces scope, not sequence. It answers “what must this course cover,” and nothing about the order in which to teach it or how to group it. Standards hierarchies are administrative taxonomies — they collectively specify a whole course’s requirements but are not pedagogically ordered, and treating a standards grouping as a teaching unit produces structure no teacher recognises. Grouping is teacher-authored and is specified in ARFC-1013.

An objective set may also be established by hand, or reused from an existing course. All three paths face the same completeness requirement; provenance does not buy an exemption.

3.7 Alignment: What a Challenge Evidences

An alignment links one challenge to one objective, asserting that the challenge provides evidence for it.

The relationship is many-to-many in both directions. One challenge may evidence several objectives — a word problem requiring two-digit addition evidences both add two-digit numbers and interpret word problems. One objective is normally evidenced by many challenges, sometimes by a great many: good digital citizenship may be evidenced in dozens of places across a year, while Boolean conjunction may be settled thoroughly within a single lesson.

Alignment is recorded at the challenge and nowhere else. A mission’s coverage is the sum of its challenges’ alignments; a lesson’s is the sum of its missions’; a course’s is the sum of its lessons’. There is no way to declare that a lesson covers an objective, because such a declaration could not be checked.

3.8 What an Alignment Asserts

An alignment asserts what kind of evidence the challenge provides for that objective.

By default it asserts correctness only — that the challenge shows whether the student can do the thing correctly. That is the conservative reading, and it is what an author gets without doing anything further.

An author may additionally assert that the challenge evidences:

Assertion Meaning Permitted when
Explanation the student must explain or justify their reasoning about this objective the challenge’s kind admits extended written response
Transfer the challenge applies this objective in a situation unfamiliar to the student always, at the author’s judgement

The platform refuses an explanation assertion the challenge’s form cannot sustain. A multiple-choice question cannot evidence explanation however carefully it is written, and permitting the claim would let a course report an understanding it never observed.

Two clarifications matter.

Assertions are per alignment, not per challenge. An essay about the water cycle evidences explanation for explain the water cycle, and correctness only for spell common words accurately. The same challenge therefore carries different assertions for different objectives.

Some evidence is never asserted, only observed. Whether a student worked fluently, whether they still succeeded weeks later, and how much help surrounded the work are recorded conditions of the attempt (ARFC-1010) — not claims an author makes. Nobody authors a retention challenge; retention is what the record shows when the same objective is evidenced again after time has passed.

3.9 Assistance Refined per Objective

ARFC-1010 establishes contextual assistance as a property of a challenge’s placement in an assignment. One challenge, one tier.

That is right most of the time and wrong in a specific, common case: assistance can differ by objective. A word problem at the end of a unit may be barely assisted with respect to the arithmetic — the student is on their own — while heavily assisted with respect to reading word problems, if the lesson immediately preceding it taught exactly that.

An author may therefore refine the assistance tier on an individual alignment, overriding the placement’s tier for that objective only. Where no refinement is given, the placement’s tier applies. Refinement is available, never required.

3.10 Coverage

An objective’s coverage progresses through states that must be reported distinctly:

State Meaning
Unclaimed nothing in the course’s plan claims this objective
Claimed the plan claims it, but no work yet exists that evidences it
Evidenced challenges exist that evidence it, available to students
Demonstrated at least one student has produced evidence against it

The first two are planning states; a claim is made when a teacher assigns an objective to a grouping, which ARFC-1013 specifies. The third is an authoring state. The fourth is the first that involves a student at all.

The distinction between claimed and evidenced is the one worth having. A course whose plan claims every objective but has authored work for half of them is in a materially different condition from one that has authored everything, and a single “covered” flag conceals which.

Whether any individual student has mastered an objective is a further question entirely, answered in ARFC-1012. Coverage is a property of the course; mastery is a property of a student.

stateDiagram-v2
    [*] --> Unclaimed: objective established
    Unclaimed --> Claimed: assigned to a grouping in the plan
    Claimed --> Evidenced: work authored and aligned
    Evidenced --> Demonstrated: a student produces evidence
    Claimed --> Unclaimed: removed from the plan
    note right of Unclaimed
        A required objective left
        Unclaimed is a planning defect,
        reported as such.
    end note

3.11 Gaps

A gap is a required objective without evidenced coverage. Gaps are reported, not inferred by the reader from an absence.

Two kinds are distinguished, because they call for different work:

A third case is worth surfacing separately: an objective claimed by one grouping while all of its evidencing work sits in another. The objective is covered, but not where the plan says it is taught — which usually means the plan or the alignment is wrong, and is exactly the sort of discrepancy nobody finds by reading.

Optional objectives never produce gaps. They produce an unmet-enrichment report, which no one is obliged to act on.

3.12 Proposed Alignments from Existing Standards Coverage

Institutions already using the platform have aligned challenges to standards. Where an objective was generated from a standard, and a challenge is already aligned to that same standard, the platform proposes the corresponding objective alignment.

A proposal is not an alignment. It is offered for confirmation, because a challenge covering part of a standard does not necessarily evidence every objective derived from it, and only a person can judge that. The author confirms, adjusts, or rejects.

The value is a running start rather than a blank page: a course with years of standards alignment behind it begins with most of its objective coverage proposed rather than with nothing. This mirrors how assistance tiers are proposed in ARFC-1010 — the platform does the work it can and leaves the judgement to the person qualified to make it.

3.13 Objective Lifecycle

stateDiagram-v2
    [*] --> Draft: generated or added
    Draft --> Active: objective set published for the course
    Active --> Reworded: restated in student-facing language
    Reworded --> Active
    Active --> Retired: person-added objective withdrawn
    Retired --> [*]
    note right of Retired
        Available only to person-added
        objectives. An authority-derived
        objective cannot be retired —
        the floor does not fall.
    end note

Retiring an objective never deletes the evidence aligned to it. Historical alignments and the results beneath them remain part of the record, so a grade already reported stays explicable after the objective it referenced is withdrawn.

3.14 API Surface

Method Path operationId Description
POST /v2/courses/{course-eid}/objectives/generate generateCourseObjectivesV2 Generate the complete objective set for a course from a chosen authority and standard
GET /v2/courses/{course-eid}/objectives listCourseObjectivesV2 List a course’s objectives with provenance, required flag, and coverage state
POST /v2/courses/{course-eid}/objectives createCourseObjectiveV2 Add a person-authored objective
PATCH /v2/courses/{course-eid}/objectives/{objective-eid} updateCourseObjectiveV2 Reword, or change the required flag where provenance permits
DELETE /v2/courses/{course-eid}/objectives/{objective-eid} retireCourseObjectiveV2 Retire a person-authored objective
PUT /v2/challenges/{challenge-eid}/objectives/{objective-eid} alignChallengeToObjectiveV2 Create or update an alignment, including its assertions and any assistance refinement
DELETE /v2/challenges/{challenge-eid}/objectives/{objective-eid} unalignChallengeFromObjectiveV2 Remove an alignment
GET /v2/challenges/{challenge-eid}/objective-proposals listChallengeObjectiveProposalsV2 Proposed alignments derived from the challenge’s existing standards coverage
GET /v2/courses/{course-eid}/coverage getCourseObjectiveCoverageV2 Coverage state per objective, with gaps distinguished by kind

A refusal to demote or delete an authority-derived objective is a distinct, explanatory response — it states that provenance forbids the change and which authority requires it, rather than a bare rejection.

3.15 Authorization Model

Establishing and generating an objective set requires curriculum authority over the course. An institution may reserve this to a curriculum lead, in which case instructors see the objective set as read-only.

Adding person-authored objectives may be granted more widely than generation, since adding raises the bar and cannot lower it. An institution that trusts instructors to extend but not to establish can grant exactly that.

No one may lower the floor. Demoting a required authority-derived objective and deleting an authority-derived objective are refused for every caller regardless of privilege. This is not an authorization check that an administrator can pass; it is a property of the objective.

Aligning challenges requires authority over the challenge’s course, matching who may author the work in the first place.

Reading coverage follows course scope. An instructor sees coverage for courses they teach. Coverage reports name no students and require no access to student records — they describe what a course evidences, not who has demonstrated it.

3.16 Absent and Unknown

State Meaning Must not be shown as
No objectives established the course has not been given an objective set fully covered, or zero percent covered
Unclaimed no plan claims this objective a failure to teach it
Claimed, not evidenced work does not yet exist covered
Grade level unknown the authority published none a guessed grade level
Assertion not made the author did not claim explanation or transfer a claim that it is absent

The last row matters most for what follows. An alignment that does not assert explanation is not asserting that the challenge fails to evidence explanation — it is silent. ARFC-1012 must treat silence as unavailable evidence, never as negative evidence.

4. Version 1 Scope

Included

Excluded

5. Security Considerations

Coverage reports are compliance artifacts. A report stating which of an authority’s requirements a course evidences may be relied on by a district, an accreditor, or a regulator. Its integrity therefore matters more than its convenience: every alignment records who made it and when, and a report can be reproduced as it stood at a past date.

The floor must not be circumventable. Because demotion and deletion of authority-derived objectives are refused as a property of the objective rather than as a privilege check, no administrator, integration, or bulk operation can quietly lower what a course owes its students. Any future capability that appears to require lowering the floor should be treated as a design error rather than as a permissions gap.

Rewording must not become misrepresentation. A teacher restating an objective in accessible language is expected and welcome. Retaining the authority’s original wording alongside it means a coverage report can always cite what was actually required, and a reworded objective cannot silently narrow an obligation.

Objectives may be sensitive intellectual property. A carefully constructed objective set represents substantial professional work and may be commercially valuable to the institution that built it. Objectives are scoped to their course and its realm, and are not visible across institutional boundaries.

Coverage requires no student data. Coverage describes a course, not the people in it. Reading it grants no access to student records, and it must not become an indirect channel to them.

6. Backward Compatibility

Standards alignment continues unchanged. The existing relation between a challenge and the text of a standard keeps working exactly as it does today. Objective alignment is a new, parallel relation, not a replacement, and nothing that reads standards coverage is affected.

Nothing exists to migrate. No objectives exist today, so no data is reinterpreted and no report changes value. A course without an objective set behaves precisely as it does now.

Existing standards alignments become an asset rather than a liability. Because objectives generated from a standard retain their link to it, an institution’s accumulated standards alignment produces proposed objective alignments (§3.12). Adopting objectives is therefore not a from-scratch exercise for an established course.

The existing planning documents are superseded, not silently converted. Objective sets generated today land in standalone planning documents that nothing else can read. Those documents are not automatically turned into course objectives: their contents were produced under the defects described in §2 — flattened structure, guessed grade levels, discarded pacing — and importing them wholesale would carry those defects into the record. An explicit, reviewed import is the appropriate path, and is out of scope here.

No objective set means no coverage claim. A course without objectives reports that it has none, and must never be rendered as either fully covered or zero percent covered. The absence of an intention is not a failure to meet one.

7. References

Platform Documentation

Author

ĀYŌDÈ Development Team Codermerlin Academy Architecture