Quality assurance
Quality, checked continuously
Woolf does not inspect quality after the fact. Every college, course, resource, and student has a compliance record calculated on the basis of recorded facts. Academic value accrues only after every gate passes.
Two chains, checked end to end
The curriclum must meet quality standards, and the student most provably complete the curriculum. A degree is awardable only when both are satisfied.
Curriculum Compliance
- A college cannot operate until its dean, academic board, and faculty are verified.
- A course is compliant only when every requirement holds. One failed requirement returns it to 0.
- A resource counts only after AI validity checks and human academic review.
Learner Compliance
- Admission requires verified identity and qualification before a college can approve it.
- Learning records count only when they are tied to the actual student.
- Graduation requires full progress and no failed courses. The university approves the award.
The same gates everywhere
The checks are encoded once and applied across colleges, courses, resources, records, and awards. Compliance becomes hard to fake and straightforward to prove.
Verified gates, not trust. Draft or submitted resources are tracked, but count for zero. “Looks finished” is not the same as compliant.
Academic standards for quality curriculum include relevant peer-reviewed literature. Woolf turns each publication into a short quiz, so engagement is shown by a submission, not a PDF view.
AI pre-checks, human verification. Resources pass automated validity and workload checks before academic review. Reviewers spend time on judgment, not triage.
Grades for regular and final assignments give students feedback and map to skills, knowledge, and competencies.
All checks must pass before the Central Administration approves graduation.
The trust layer
Evidence when learning happens
Compliance depends on the data behind it. Woolf captures learning where it happens and ties it to a verified student. A sponsor cannot send a list of grades and receive accredited degrees.
Airlock API
A GraphQL API for syncing content, enrolling students, and submitting grades and submissions.
Airlock SDK
A JavaScript SDK inside the college learning environment. The student signs in, and the SDK records who did what, and when.
Woolf Widget
A floating panel in the college product, giving each student access to their Woolf dashboard, progress, and credentials.
A grade is a claim; the SDK activity stream is proof. API submissions without an SDK activity ID are flagged as a compliance risk, rate-limited, and held for pre-approval.
Content sync is for verification, not consumption. Colleges send content so Woolf can verify workload and return a resource ID. Students learn in the college environment; the ID lets the SDK attribute activity to the verified resource.
Active vs pending. Activity counts only when tied to a verified resource and valid submission. Everything else stays pending.
- Enough verified teachers with the required qualifications
- The required number of graded assignments
- The required number of summative assessments
- Peer-reviewed publications & quality curriculum
- Verified workload at or above the course requirement
When a course becomes compliant, or stops being compliant, that status change is recorded.
A higher quality bar, at scale
The thousandth course is checked the same way as the first.
If a teacher leaves or a publication ages out, the regression is caught immediately, not at an annual audit.
Every decision can be reconstructed from the activity log, so evidence for a credit is queryable.
Why it matters
Rigor in the system of record
For accreditors & regulators
Every credit traces back to attributable evidence and a gate that passed.
For colleges
You get a working QA system, and you cannot accidentally launch a non-compliant course.
For investors
QA enforced in code lets Woolf raise standards as it grows.