ClassKit Progress Tracking Integration Specification

Role: Lead iOS Architect specializing in Apple School Manager and ClassKit educational frameworks.

Context

• Educational Institution: {{institution_name}}
• Student Demographic: {{target_grade_band}}
• Academic Content Focus: {{curriculum_module}}
• Reporting Cadence: {{assessment_frequency}}
• Compliance Boundary: {{student_privacy_tier}}
• Connectivity Profile: {{offline_sync_strategy}}

Task

Generate a comprehensive technical specification for integrating Apple ClassKit into an educational iOS application, establishing seamless synchronization with Apple Schoolwork while preserving student privacy and offline functionality.

Method

1. Define the CLSContext hierarchy mapping to {{curriculum_module}} and structural units for {{target_grade_band}}.
2. Detail the activity progress reporting model, mapping completion scores and time intervals based on {{assessment_frequency}}.
3. Architect the local caching and queued synchronization pipeline aligned with {{offline_sync_strategy}}.
4. Specify the security and student data segregation boundaries satisfying {{student_privacy_tier}}.
5. Outline the error handling and retry mechanisms for Schoolwork sync failures without interrupting classroom flow.
6. Specify automated unit and integration tests using XCTest to validate CLSContext state transitions.
7. Document teacher-facing verifiable payloads to confirm accurate assignment state reflectiveness.

Constraints

• MUST adhere strictly to Apple ClassKit framework conventions and zero-tracking privacy policies.
• MUST NOT store unencrypted student identifiers in device-level persistent storage.
• All Swift interface definitions must use Swift 6 concurrency patterns.
• Keep architecture patterns aligned with clean MVVM-C or Composable Architecture standards.

Output format

Provide the specification in four distinct sections:

1. ClassKit Hierarchy Schema (context hierarchy tree and identifier conventions)
2. Data Flow & Sync Specification (state diagram and synchronization logic under 400 words)
3. Core Swift Protocols & Types (production-ready Swift type interfaces)
4. Verification & Testing Matrix (table of test scenarios and expected sync states)

Self-review

• Verify all 6 context variables are actively utilized in the logic.
• Ensure no third-party tracking libraries are included in the architecture.
• Confirm offline reconciliation edge cases are explicitly handled.