accounting-principles

name

accounting-principles

description

Write or revise a student-facing accounting-principles lesson for Math for Business Operations. Use for lessons 2-4 when the lesson teaches an accounting concept, valuation method, or manual procedure before Excel automation. This skill is for explicit instruction, scaffolded practice, algorithmic phase-4 mastery practice, MCQ exit tickets, and reflection. Do not use for launch lessons, Excel-principles lessons, or project lessons.

Accounting Principles Skill

Assume the repository's base lesson standard in AGENTS.md already applies. This skill adds only the accounting-principles lesson logic.

Goal

An accounting-principles lesson should:

• teach one clear accounting principle, method, or procedure
• make the business reason for the rule visible before and during instruction
• move from high support to low support across phases
• give students repeatable practice until the skill is reliable
• separate procedural fluency from conceptual checking

This is not a launch lesson, workbook-build lesson, or project lesson.

Use This Skill When

Use this skill when the lesson's main job is to:

• teach a new accounting rule, method, or calculation process
• clarify ambiguity that requires a formal accounting treatment
• compare accounting methods and their business consequences
• build manual fluency before any Excel automation starts
• prepare students for later workbook construction

Do Not Use This Skill When

Do not use this skill if the lesson is mainly about:

• launching the unit story or founder problem
• introducing Excel tools, formulas, or workbook conventions
• building a spreadsheet model step by step
• multi-day project production or milestone review

Core Writing Rules

• Teach the core rule directly. Do not make students discover the main procedure on their own.
• Keep one dominant skill target per lesson.
• Make the business purpose visible before the arithmetic gets heavy.
• Follow a concrete-to-representational-to-abstract progression as closely as an e-textbook allows.
• Fade scaffolds across phases 2-4 on purpose.
• Use the same representation long enough for students to gain fluency.
• Keep Excel out of the lesson unless it is only a minor preview and not part of the main task.

Concrete-Representational-Abstract Guidance

Use the CRA principle as a progression rule for accounting-principles lessons:

• early phases should feel as concrete as possible through business story, visible objects, labeled quantities, movement, and before/after state changes
• middle phases should use representational supports such as tables, layers, color coding, callouts, arrows, mini ledgers, and guided layouts
• later phases should become more abstract by reducing explanatory wrappers and moving toward authentic accounting formats

In this course, "abstract" does not mean disconnected from business reality. It means:

• less scaffolding
• fewer visual hints
• more compressed accounting presentation
• stronger alignment to real accounting artifacts and decision contexts

As phases progress, students should move from:

• story and inventory objects
• to structured representations
• to accounting-style forms such as schedules, mini balance sheets, mini income statements, method comparison tables, and clean valuation workspaces

The lesson should not jump straight from story to pure abstraction. Each phase should remove only enough support to prepare students for the next level of formality.

Lesson Pattern

The accounting-principles lesson pattern is:

1. recycle prior knowledge and introduce the new friction point
2. explicit instruction with highly scaffolded practice
3. deeper instruction with reduced scaffolding
4. algorithmic deliberate practice for mastery
5. short MCQ exit ticket on knowledge and understanding
6. reflection and preview

Accounting-Principles Phase Contract

Phase 1: Recycle and Introduce

Purpose: Activate the previous lesson's key idea, then surface the new accounting problem that students cannot yet solve cleanly.

Requirements:

• reconnect to the prior lesson, dataset, or business scenario
• show the exact friction point that makes a new rule or method necessary
• use one short launch move such as prediction, notice-and-wonder, or compare-the-results
• keep the representation highly concrete and story-anchored
• keep the task light enough that students feel the need for instruction

Avoid:

• reteaching the entire previous lesson
• long independent calculation
• introducing multiple new methods at once

Phase 2: Explicit Instruction and Highly Scaffolded Practice

Purpose: Teach the rule, method, or procedure directly and walk students through a first successful attempt.

Requirements:

• name the method or principle clearly
• model the procedure step by step
• explain why each step exists
• use worked examples, guided prompts, and visible intermediate values
• use strong representational supports such as layers, diagrams, highlighted fields, or mini financial connections
• keep students practicing inside a tightly supported structure

Avoid:

• discovery-first instruction
• hidden reasoning
• skipping the business meaning of the numbers

Phase 3: Deepening and Scaffold Fade

Purpose: Extend the same skill under slightly harder conditions and remove some supports.

Requirements:

• add one meaningful complication such as more layers, ambiguity, comparison, or rounding discipline
• keep the skill target the same
• reduce prompts and hints compared with phase 2
• begin shifting toward cleaner accounting-style layouts and more authentic notation
• ask students to explain choices, not only compute answers

Avoid:

• switching to a new skill shape
• adding Excel procedures
• turning the phase into a broad simulation

Phase 4: Algorithmic Deliberate Practice

Purpose: Give students repeatable practice on the same skill shape until they can perform it reliably with minimal scaffolding.

Requirements:

• use the same underlying procedure each round
• vary the numbers or valid permutations algorithmically
• provide automatic checking
• give feedback after submission, not during every step
• include brief reteach guidance tied to the error pattern
• allow a new isomorphic problem immediately after feedback
• define a mastery target such as consecutive correct answers or a threshold score
• present the work in a more abstract, accounting-aligned format with minimal visual support

Avoid:

• workbook construction
• open-ended sandbox play
• broad multi-skill tasks
• heavy reading inside the practice loop

Phase 5: Assessment

Purpose: Check knowledge, recognition, and misconception resistance in a short, aligned exit ticket.

Requirements:

• use a short MCQ exit ticket
• assess definitions, method recognition, reasoning, and common misconceptions
• keep the scope narrow and aligned to the lesson's main target
• separate this check from the longer phase-4 practice loop

Avoid:

• long free-response grading tasks
• repeating the exact phase-4 drill format
• introducing brand new content

Phase 6: Reflection

Purpose: Help students consolidate what the method is for, where they feel confident, and what comes next.

Requirements:

• ask students to reflect on both confidence and understanding
• connect the lesson back to the business problem
• identify what signal tells a student to use this method
• preview the next accounting principle or comparison

Avoid:

• major new instruction
• excessive recap cards or repeated summaries

Phase-4 Component Contract

Every accounting-principles phase-4 component should define:

• the skill target
• the variation schema
• the correctness rules
• the common misconception map
• the feedback tiers
• the reteach snippet
• the mastery rule

Strong phase-4 practice components should also:

• keep the interface stable from round to round
• expose state changes clearly
• offer a New Numbers or equivalent retry path
• allow a worked example only after an attempt
• track progress toward mastery visibly

Component Rules For Accounting Lessons

Prefer components that:

• reveal the accounting logic step by step
• show running totals, assigned costs, remaining units, or other visible state changes
• let students compare methods or outcomes cleanly
• keep one dataset or representation stable across phases 2 and 3
• connect the lesson's numbers to authentic accounting outputs such as mini balance sheets or income statements when that link clarifies why the method matters

Avoid components that:

• bury the accounting logic behind game mechanics
• change the UI shape every phase
• require spreadsheet building before the concept is secure
• overload students with too many controls at once

Success Test

A strong accounting-principles lesson should leave students able to answer:

• What accounting problem does this method solve?
• When should I use this rule or method?
• What steps do I follow to apply it correctly?
• What mistakes am I most likely to make?
• How does this method affect the business story or reported results?