Evidence-led launch decision

Public paid launch remains blocked until the named evidence is complete.

Daskerel is available for controlled review and approved pilots. This page separates implemented capability from production proof, shows who owns every next action, and states exactly what free and paid access includes.

Optional voiceover / Narration

French audio requires a French voice installed in the browser or Windows. Until one is available, Daskerel will show the French transcript rather than read it with an English voice.

Current decision

Public launch

Blocked

Do not accept unrestricted public payments or claim production readiness.

Blocking gates

Each requires named evidence and owner approval before public launch.

Verified controls

Verified means the listed evidence exists; it does not override another blocker.

The DASKEREL UK application passed initial examination, but the GBP 215 Right Start balance is due by 21 September 2026. The mark is not registered. Use DASKEREL™ only and do not claim exclusivity.

Gate register

Blockers, evidence, and owner actions

Owner and legal operations

DASKEREL trade mark application

watchPartial evidence

UKIPO examination letter dated 24 August 2026 says Right Start application UK00004431018 appears to meet the requirements for Classes 9, 35, 41 and 42. The GBP 215 balance is unpaid and due by 21 September 2026; publication, opposition, and registration remain outstanding.

Next owner action: Use DASKEREL™ rather than the registered-mark symbol. Pay the GBP 215 balance through the official UKIPO response route by 21 September 2026 if the owner decides to proceed, retain the receipt, and monitor publication and opposition correspondence.
Evidence required: Certified application, 24 August 2026 examination letter, official balance-payment receipt when paid, publication record, and later registration decision.
Truthful claim now: A pending UK trade mark application that passed initial examination; not a registered trade mark or assurance of exclusivity.

Owner and billing operations

Stripe Tax/VAT live checkout

watchPartial evidencePublic-launch blocker

HMRC approved VAT registration GB 523 5032 29 from 13 July 2026. The live Stripe account has an active GB registration and default invoice VAT ID, while Xero Grow is authorised for MTD with Revolut Business Main GBP and Daskerel Stripe GBP direct feeds connected. Checkout remains paused for product tax codes, digital-link, invoice, refund, reconciliation, and owner readiness approval.

Next owner action: Confirm where the electronic-services fallback applies, assign owner-approved codes to each launch supply, complete payment and digital-link evidence, then set the remaining readiness flags only after owner sign-off.
Evidence required: Restricted HMRC certificate, platform health, Stripe tax check script, billing runbook, invoice samples, owner VAT approval, and checkout guardrails.
Truthful claim now: Prices and paid offers may be reviewed in controlled mode; real-money public checkout is not launch-ready.

Owner and security operations

Google Workspace SSO and MFA

readyVerified evidence

Owner and delegated management sign-in supports Google Workspace SSO with MFA enforced by Workspace policy.

Next owner action: Keep password fallback as controlled local recovery only until production SSO is fully observed.
Evidence required: Service login, SSO callback audit event, Workspace 2-Step Verification setting, and management access report.
Truthful claim now: Management SSO and MFA controls are configured; production observation and break-glass testing remain operating duties.

Operations management

Real lab monitoring evidence

watchPartial evidencePublic-launch blocker

Concurrency routing exists for AWS, Azure, and Google Cloud lab pools, including Africa coverage, but production proof requires load simulation evidence and provider account telemetry.

Next owner action: Run labs:simulate-concurrency, capture provider account pool capacity, cleanup success, budget alarms, and regional failover notes.
Evidence required: Lab demand API, lab concurrency simulator, provider pool JSON, cloud cost alarms, and incident lifecycle records.
Truthful claim now: Lab orchestration is implemented for controlled testing; broad production capacity is not yet evidenced.

Operations, security, and platform engineering

Monitoring and backup evidence

watchPartial evidencePublic-launch blocker

Monitoring, alert, backup, restore-drill, audit-export, and provider smoke evidence must be captured before the next public launch window.

Next owner action: Open /admin/monitoring-backup, complete the evidence board, and attach CloudWatch, AWS Backup, restore, alert, and incident proof to the launch pack.
Evidence required: Monitoring and backup evidence board, AWS backup/DR report, CloudWatch dashboard, backup job history, restore drill notes, and management audit exports.
Truthful claim now: Monitoring and recovery controls exist in the operating design; successful production restore evidence is still required.

Owner, legal, partnerships, and team management

Legal and employer trust pack

watchPartial evidencePublic-launch blocker

Public terms, privacy, refunds, security, employer-use clauses, and operational PDFs are drafted for review.

Next owner action: Have legal/accounting professionals review live commercial wording before launch and before signing employer agreements.
Evidence required: Trust centre, legal pages, employer partnership agreement PDF, IP, confidentiality, data protection, contractor, and employment templates.
Truthful claim now: Draft legal and trust materials are available for review; they are not a substitute for approved live terms or professional advice.

Content quality reviewers

Content freshness and certification currency

readyVerified evidence

Official-source review queues, provider reviews, and freshness badges make currency visible before learner-facing updates are promoted.

Next owner action: Keep a quarterly review cycle and add urgent review when providers publish blueprint, retirement, or exam-code changes.
Evidence required: Content quality queue, provider reviews, certification coverage, review dates, and source URLs.
Truthful claim now: Content currency is tracked through review dates and sources; Daskerel does not claim provider endorsement or guaranteed exam outcomes.

Assessment reviewers and school subject specialists

Mock-assessment validity and anti-guessing review

watchPartial evidence

Generated and authored mock banks now fail automated readiness checks for duplicate prompts, unstable question IDs, invalid answer mappings, weak option rationales, and excessive correct-answer length cues.

Next owner action: Launch with the automated-quality claim only. Complete the deterministic specialist sample queue for every school and authored provider bank before describing those banks as independently reviewed.
Evidence required: Curriculum readiness output, mock-question quality tests, provider route-to-bank tests, reviewer sampling records, corrections, and formal assessment approval.
Truthful claim now: Automated anti-guessing controls are implemented. Independent subject validation is reported separately and only after its evidence is complete.

Learner success and operations management

Learner feedback and improvement loop

readyVerified evidence

Post-lab feedback, course ratings, NPS-style scoring, bug/friction reports, translation issues, and management triage are connected.

Next owner action: Review repeated issues weekly, assign owners, and publish fixes through content and operations queues.
Evidence required: Feedback page, learner feedback dashboard, repeated pages, SLA due dates, owner notes, and improvement status.
Truthful claim now: Feedback and triage workflows are implemented; response performance must be evidenced during the pilot.

Learner success, evidence review, partnerships, and operations management

Career service workflow and review controls

readyVerified evidence

A school-aware learner career dashboard connects role targets, evidence gaps, applications, CV, interview, presentation, writing, and opportunity controls, while a restricted operations view monitors real CV and interview queues.

Next owner action: Pilot the workflow with named learners, measure review turnaround and accessibility friction, and keep employer visibility opt-in and human approval separate from automated drafting.
Evidence required: Career dashboard, career-services operations dashboard, CV and interview queues, opportunity consent controls, automated tests, and the career dashboard readiness report.
Truthful claim now: Career preparation tools support learners but do not guarantee employment, interviews, certification, or employer acceptance.

Owner and operations management

Domain, DNS, and HTTPS

blockedPartial evidencePublic-launch blocker

daskerel.com is the intended canonical website, but its Route 53 or equivalent DNS delegation, production TLS certificate, CloudFront application routing, and legacy-domain redirects are not yet evidenced.

Next owner action: Create and validate the Daskerel DNS and HTTPS configuration, set production NEXT_PUBLIC_APP_BASE_URL to https://daskerel.com, then test root and www routing plus permanent redirects from controlled legacy domains.
Evidence required: Registrar ownership, DNS lookup, TLS certificate, CloudFront/ECS deployment record, redirect tests, and public route smoke checks.
Truthful claim now: The domains are controlled and DNS is delegated; the production application is not publicly deployed or evidenced over HTTPS.

Team management and learner success

Pilot cohort mode

watchPartial evidencePublic-launch blocker

A controlled pilot should validate onboarding, labs, support, reporting, feedback, and employer outcomes before broad launch.

Next owner action: Start with a small named cohort, daily monitoring, weekly owner review, and a clear go/no-go decision.
Evidence required: Pilot cohort page, feedback dashboard, certification report, employer outcome report, and incident/status log.
Truthful claim now: A controlled pilot may proceed within approved limits; pilot readiness is not broad public-launch approval.

Operations management and security operations

Incident and status communication

readyVerified evidence

The platform has an incident lifecycle queue and a public status page pattern for learner-impacting issues.

Next owner action: Publish status changes during incidents and close each incident with cause, mitigation, and follow-up owner.
Evidence required: Incident lifecycle tool, AI operations runbooks, public status page, and management audit trail.
Truthful claim now: Incident workflows and status-page patterns are implemented; service-level performance must be demonstrated in operation.

Commercial transparency

Free access, paid access, and what is not yet for sale

Offer	Free boundary	Paid boundary	Launch state and proof
Public catalogue and learner account	School, pathway, lesson, certification, pricing, trust, and support discovery; account creation and saved free-account state.	Full lessons, protected answers, mock exams, guided labs, evidence workflows, and member-only learning materials require an active entitlement.	Free discovery may be reviewed in controlled environments. Do not accept public payment until the live-checkout gate is verified.Proof: Catalogue routes, access-control tests, Cognito account flow, Stripe entitlement checks, and published pricing terms.
Virtual classes and coaching	Published class information, access rules, accessibility requests, and class-support contact routes.	Specialist tickets, capacity-one coaching, and paid cohorts require the matching approved entitlement, seat, or quote; membership-included sessions must say so explicitly.	Recording-disabled private pilots may run under approved controls. Public paid classes remain blocked pending production and payment evidence.Proof: Class record, seat and entitlement checks, Teams policy, consent/recording decision, attendance reconciliation, and refund rehearsal.
Career, project, writing, and presentation support	Service descriptions, self-help previews, readiness guidance, and basic learner opportunity opt-in where expressly labelled free.	Human review, construction support, enhanced visibility, and specialist preparation are separate paid add-ons unless a named plan explicitly includes them.	Never imply human review, employer introduction, job placement, or regulated advice is included without the matching paid service and available reviewer.Proof: Offer catalogue, Stripe price mapping, entitlement record, reviewer queue, learner consent, and completion record.
Teams and employer cohorts	Employer discovery information and an initial quote request that does not itself create access or a payment obligation.	Named seats, private cohorts, enhanced reporting, and scoped employer services begin only after an approved quote, payment route, and provisioning record.	No cohort is sold or described as active until price, tax, terms, seat count, delivery owner, and support route are approved.Proof: Approved quote, signed terms or statement of work, Stripe/invoice evidence, named-seat provisioning, delivery plan, and employer reporting scope.

Operational ownership

Support and escalation routes

Payment taken but access missing, duplicate charge, invoice/VAT issue, cancellation, or refund request

First owner: Billing operations
Response target: Acknowledge within 4 staffed hours; protect access evidence and payment identifiers.
Escalation: Escalate to the owner immediately for duplicate capture, unresolved paid-access impact, refund failure, or a complaint deadline.

Lab unavailable, cleanup stuck, quota pressure, unexpected spend, or learner environment isolation concern

First owner: Operations management
Response target: Triage active-session impact immediately and create an incident for material learner or cost impact.
Escalation: Escalate to security operations for isolation or credential concerns and to the owner for material spend or prolonged outage.

Suspected data exposure, account compromise, safeguarding concern, or unauthorised paid-content access

First owner: Security operations
Response target: Immediate restricted triage; preserve evidence and avoid copying sensitive content into general support notes.
Escalation: Notify the owner immediately and follow the incident, privacy, safeguarding, and regulatory assessment runbooks.

Accessibility barrier, class joining problem, lesson defect, or learner support issue

First owner: Learner success
Response target: Acknowledge within 1 staffed day, sooner when a live class or paid access is affected.
Escalation: Route billing impact to Billing, platform defects to Operations, and urgent welfare or safeguarding concerns to the restricted owner-led path.

These are operating targets, not contractual service-level guarantees. Use the support route for learner or customer cases and the status page for service-impacting incidents.