Version Control & Updates

As school documents evolve—curriculum guides get revised, policies are updated, and new resources are added—it’s essential to manage version control within Knobase. This ensures that agents always reference the most current and accurate information, while preserving historical context when needed.

Written By Christopher Lee

Last updated 6 months ago

🧠 Why Version Control Matters

  • ✅ Prevents agents from referencing outdated or conflicting documents

  • ✅ Supports transparency and traceability in school communications

  • ✅ Enables educators to track changes over time

  • ✅ Reduces confusion for students, staff, and parents

🔄 Best Practices for Version Control

1. Use Clear Version Naming

Include version numbers or dates in file names:

  • Y10_Science_Curriculum_v1.pdf

  • HomeworkPolicy_2025_Term1.pdf

  • AssessmentRubric_Updated_March2025.docx

2. Archive Old Versions

Move outdated files to an “Archive” folder:

Curriculum – Year 10 ├── Active │ └── Y10_Science_Curriculum_v2.pdf ├── Archive │ └── Y10_Science_Curriculum_v1.pdf

3. Add Metadata or Notes

Use document descriptions or tags to indicate:

  • What changed

  • Who updated it

  • When it was last reviewed

4. Set Expiry Dates for Time-Sensitive Files

Combine version control with expiry settings to automatically phase out old documents.

5. Notify Relevant Agents

After updating a document:

  • Reconnect the new version to the agent

  • Test the agent’s responses to ensure accuracy

  • Remove or disconnect outdated versions

💡 Example Scenario

You update the Year 10 homework policy to reflect a new submission deadline.

✅ Rename the file: Y10_HomeworkPolicy_v2.pdf
✅ Move the old version to an archive folder
✅ Reconnect the new version to the “Homework Helper” agent
✅ Test the agent with: “What’s the late submission rule for Year 10?”