PVP Canvas v1.1
Application Canvas, Artifact History, and Quick Guide in three A4 pages. Files in Portuguese.
Usage guide · explanatory layerStarter kit v0.1Public release v0.1 · CC BY 4.0
Start using PVP
In five steps, turn a lesson plan into a Versioned Lesson Plan (PAV) and, when a classroom signal motivates an improvement, record the change and produce its next version.
Minimum first-use workflow
- PAV v1.0.0Versioned lesson plan identified
- ApplicationUse in the declared context
- Classroom signalObservation that may motivate improvement
- RMIf an improvement is incorporated
- PAV v1.1.0New version after the change
01 · Application
The minimum you need
You can complete the entire workflow on paper, in a document, a slide deck, or a spreadsheet. No platform is required.
Choose a plan
Use a plan you already prepare. It may be in a notebook, text document, slide deck, or spreadsheet.
Identify the first version
Record subject, topic, grade, author, free-form plan content, and the initial version. Also declare grade/year, lesson time, available resources, and an aggregated class profile. If it had no version history, start at v1.0.0 or v1.0.
Apply and observe
During or after class, observe signals relevant to the plan. If a signal motivates an improvement, describe it briefly, in aggregate, and without identifiable student data.
Complete an Improvement Record (RM) when there is an improvement
Answer: what changed? Why did it change? Which classroom signal motivated the change? An application with no incorporated change does not require a new version.
Produce the new version
Classify the change as Major, Minor, or Patch, update X.Y.Z or X.Y, and preserve the previous version. When X increments, reset Y and Z; when Y increments, reset Z.
02 · Materials
Download the materials
Canvas v1.1 is the main application-tracking instrument. The files are currently in Portuguese. Use the PDFs for printing and keep Starter Kit v0.1 as introductory, editable support.
Canvas Mini v1.1
A5 notebook sheet or two ready-to-cut sheets on one A4 page. Files in Portuguese.
Complete kit
Guide, VLP template, Improvement Record card, and usage notes in one archive.
Five-minute guide
A short explanation of the workflow, X.Y.Z versions, and a fictional example.
PAV template
An editable sheet for identifying the versioned lesson plan, declaring context, and preserving its history.
Improvement Record (RM) card
The minimum change record: what changed, why, and which signal motivated it.
03 · Fictional example
A version identifies the plan’s state — not a quality score.
A plan begins at v1.0.0. After an application, an activity sequence is reorganized without changing the overall structure: v1.1.0 (Minor). Later, an ambiguous instruction is clarified: v1.1.1 (Patch). The history, together with the corresponding Improvement Records, preserves the versions and the reasons for each change.
v1.0.0→v1.1.0→v1.1.1
This example contains no real data and does not demonstrate learning, quality, or effectiveness.
Optional filename convention
How an incorporated improvement creates a new version
This example shows how a filename can make the version visible while a plan circulates. The process remains PVP: observe, record the improvement, and preserve the history.
The filename makes the version visible. The Improvement Record explains the change. The history preserves the trajectory.
In a notebook, a file, or a platform, the workflow is the same.
Complete example sequence:
- File in use: linear-equations-plan-v1.0.0.pdf. Current version used in the declared context.
- Classroom signal: Part of the class asked for support to begin the activity.
- Improvement Record. What changed: A guided example was added before the activity. Why it changed: Provide a shared reference in the opening step. Classroom signal: Repeated requests for support at the start.
- New version: v1.0.0 → v1.1.0, Minor · Y. An adjustment incorporated within the same structure. linear-equations-plan-v1.1.0.pdf
- History preserved: v1.0.0 · previous version; v1.1.0 · current version.
If no improvement is incorporated, the version remains unchanged.
The filename pattern is an optional convention under experimentation and is not part of Core 1.0. It does not replace the Improvement Record, context, history, or provenance. This is a fictional example with no student data.
Frequently asked questions
What you need to use PVP safely
Direct answers for starting with the minimum workflow, with or without tools.
What is PVP?
PVP is an open protocol for versioning lesson plans and recording improvements over time. It organizes version, change, context, history, and authorship.
Do I need a platform, Git, or software?
The workflow can be completed in a notebook, on a sheet, in a spreadsheet, document, or slide deck. A platform, Git, and the Canvas are optional supports.
Does every application produce a new version?
An application may keep the current version. A new version is created when a concrete improvement is incorporated into the artifact and recorded in an Improvement Record.
What is an Improvement Record, or RM?
It is the minimum record of an improvement: what changed, why it changed, and which classroom signal motivated the change. RM is the canonical acronym used by PVP.
What is a classroom signal?
It is an observation made during or after a lesson that helps decide an improvement. It can be recorded briefly and in aggregate, without identifiable data.
What do X, Y, and Z mean?
X marks significant restructuring; Y, an adjustment within the same structure; Z, a localized micro-correction. The version describes the type of change, not a count.
Does a higher version mean a better lesson?
A version locates a change in the artifact history. It is not a quality score and, by itself, does not demonstrate learning or effectiveness.
May I include the version in the filename?
As an optional convention for a Versioned Lesson Plan or related pedagogical artifact: linear-equations-plan-v1.1.0.pdf. In this preview, the proposal is experimental and is not part of Core 1.0. The name helps identify the version but does not replace the Improvement Record, context, history, or provenance.
How do I preserve authorship and history?
Keep the author identification, version, context, and history with the plan. A new version starts from the previous one without erasing its origin.
What data may be included in the record?
Use aggregated context and classroom signals without names or data that identify students. The essential workflow does not depend on individual data.
Ready for the first version?
Download the kit, choose a real plan, and record only what is necessary. The first goal is to make improvement visible and traceable.