eduKate Singapore

VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Next useful routeCanonical hubHELP

Why English? | Checking a WSQ Digital Certificate Before Sharing It

—

by

eduKate Asia

A WSQ digital certificate is useful because a recipient can verify more than a picture of a certificate. English matters because original file, preview, printed copy, screenshot, integrity, issuer identity, status, accredited, revoked, holder and qualification are not synonyms. Each answers a different trust question.

People searching WSQ certificate, OpenCerts verification, download WSQ e-Cert or how to share a digital certificate often jump directly to forwarding a file. A safer process begins by locating the original digital certificate from the authorised source, opening the official verifier, reading the result, matching the holder to the presenter and deciding what information the recipient actually needs.

SkillsFuture Singapore’s current WSQ digital-certificate page directs employers to verify digital certificates through OpenCerts. OpenCerts explains that verification examines document integrity, issuer identity and document status. Its FAQ also warns that printing discards the cryptographic protections, so a printout should not be treated as the authentic digital object.

Verification is powerful but narrow. A valid digital certificate does not prove that the presenter is the named holder unless identity is matched, that the credential is relevant to every job, or that a receiving organisation must accept it. The reader’s task is to preserve those boundaries while making legitimate sharing easy.

Official sources and the date boundary

The factual floor comes from SkillsFuture Singapore and the OpenCerts verifier documentation. Technology, schemas and interfaces can change. Use the current official verifier and the issuing institution’s instructions; do not upload a credential to an unknown verification site.

These official pages were checked on 22 October 2026. Live interfaces, lists, contact details and procedures can change. Reopen the official source before acting, and keep the publication or update date visible.

Did You Know? A certificate can look perfect in a screenshot yet lose the feature that makes it independently verifiable. OpenCerts says a printout is not authentic because printing discards the cryptographic protections built into the digital document.

Back to contents

1. Locate the original digital certificate

Find the certificate in the authorised account, message or issuing institution route. Preserve the original file rather than rebuilding it from a PDF preview or image.

For the locate the original digital certificate step, remember that verification works only when the right digital object reaches the right verifier. Keep the original OpenCerts file, file name and source, certificate holder, qualification or Statement of Attainment, issuing organisation, issue date, verification result, document integrity, issuer identity, document status, recipient, channel, purpose and privacy decision on one evidence sheet and separate what the certificate displays from what OpenCerts actually verifies.

Credential scene: A learner downloads a screenshot from a messaging app and deletes the original OpenCerts file.

Read the heading, the operative verb and the condition as one unit. A noun without its qualifier is often the beginning of a wrong decision. For a digital credential, preserve the original file, read the verifier result, confirm the presenter’s identity separately and share no more personal information than the recipient needs.

Verification sequence: Return to authorised source; Download original; Keep extension; Store read-only copy. Record the result in words such as integrity, issuer identity and status instead of replacing the official outcome with ‘looks real’.

Boundary: Do not use credentials belonging to another person for practice. Original-source discipline supports research. Verification supports trust in the digital record, but the receiving employer, institution or authority still decides whether the qualification is relevant and acceptable for its purpose.

A four-line working note

  • Return to authorised source
  • Download original
  • Keep extension
  • Store read-only copy

Write a compact note naming the source, the relevant object, the observed wording and the next action. Add one limit sentence so a later reader cannot mistake a possibility for a promise.

Back to contents

2. Separate the file from its visual rendering

The attractive certificate view is a human-readable rendering. The verifiable digital object also contains structured and signed information used by the verifier.

For the separate the file from its visual rendering step, remember that verification works only when the right digital object reaches the right verifier. Keep the original OpenCerts file, file name and source, certificate holder, qualification or Statement of Attainment, issuing organisation, issue date, verification result, document integrity, issuer identity, document status, recipient, channel, purpose and privacy decision on one evidence sheet and separate what the certificate displays from what OpenCerts actually verifies.

Credential scene: A recruiter assumes a high-resolution PDF is more trustworthy than the less familiar original file.

Build a two-column note: exact wording on the left and your plain-English paraphrase on the right. If the paraphrase drops a date, exception or actor, repair it. For a digital credential, preserve the original file, read the verifier result, confirm the presenter’s identity separately and share no more personal information than the recipient needs.

Verification sequence: Name file type; Name preview; Keep original; Explain difference. Record the result in words such as integrity, issuer identity and status instead of replacing the official outcome with ‘looks real’.

Boundary: Visual quality is not authenticity evidence. Interface and data are different in computing. Verification supports trust in the digital record, but the receiving employer, institution or authority still decides whether the qualification is relevant and acceptable for its purpose.

A four-line working note

  • Name file type
  • Name preview
  • Keep original
  • Explain difference

Record the exact source line before paraphrasing it. Then state the applicant, holder or role to which it applies and one fact still awaiting confirmation.

Back to contents

3. Use the official OpenCerts verifier

Open the official verifier directly and load the original file through its stated process. Check the domain before exposing personal information.

For the use the official opencerts verifier step, remember that verification works only when the right digital object reaches the right verifier. Keep the original OpenCerts file, file name and source, certificate holder, qualification or Statement of Attainment, issuing organisation, issue date, verification result, document integrity, issuer identity, document status, recipient, channel, purpose and privacy decision on one evidence sheet and separate what the certificate displays from what OpenCerts actually verifies.

Credential scene: A search advertisement leads to a lookalike certificate-upload site.

Treat the page as a decision instrument rather than promotional prose. Mark what is confirmed, what is conditional and what must be checked elsewhere. For a digital credential, preserve the original file, read the verifier result, confirm the presenter’s identity separately and share no more personal information than the recipient needs.

Verification sequence: Type official domain; Check HTTPS and host; Load locally as instructed; Close unknown site. Record the result in words such as integrity, issuer identity and status instead of replacing the official outcome with ‘looks real’.

Boundary: This guide does not audit third-party platforms. Domain checking supports digital safety. Verification supports trust in the digital record, but the receiving employer, institution or authority still decides whether the qualification is relevant and acceptable for its purpose.

A four-line working note

  • Type official domain
  • Check HTTPS and host
  • Load locally as instructed
  • Close unknown site

Use four labels: evidence, meaning, boundary and action. If any label remains empty, the decision is not yet ready to be treated as closed.

Back to contents

4. Read document integrity

Integrity asks whether the document’s signed data still matches. Even a small alteration should not be hidden by a visually unchanged layout.

For the read document integrity step, remember that verification works only when the right digital object reaches the right verifier. Keep the original OpenCerts file, file name and source, certificate holder, qualification or Statement of Attainment, issuing organisation, issue date, verification result, document integrity, issuer identity, document status, recipient, channel, purpose and privacy decision on one evidence sheet and separate what the certificate displays from what OpenCerts actually verifies.

Credential scene: Someone edits a grade in an image editor while preserving the certificate design.

Follow the source hierarchy. A headline introduces the opportunity; the current official detail page and the applicant-specific record control the decision. For a digital credential, preserve the original file, read the verifier result, confirm the presenter’s identity separately and share no more personal information than the recipient needs.

Verification sequence: Run verifier; Find integrity result; Do not edit original; Record exact outcome. Record the result in words such as integrity, issuer identity and status instead of replacing the official outcome with ‘looks real’.

Boundary: Integrity does not establish whether the holder is the presenter. Checksum thinking transfers to data work. Verification supports trust in the digital record, but the receiving employer, institution or authority still decides whether the qualification is relevant and acceptable for its purpose.

A four-line working note

  • Run verifier
  • Find integrity result
  • Do not edit original
  • Record exact outcome

Draft a one-sentence conclusion and underline every qualifying word from the source that the conclusion must preserve. Repair any missing condition.

Back to contents

5. Read issuer identity

Issuer identity asks whether the digital issuing identity can be connected to the stated organisation through the mechanisms recognised by OpenCerts.

For the read issuer identity step, remember that verification works only when the right digital object reaches the right verifier. Keep the original OpenCerts file, file name and source, certificate holder, qualification or Statement of Attainment, issuing organisation, issue date, verification result, document integrity, issuer identity, document status, recipient, channel, purpose and privacy decision on one evidence sheet and separate what the certificate displays from what OpenCerts actually verifies.

Credential scene: A file displays a familiar training-provider name, but the verifier cannot confirm its issuer identity.

Keep eligibility, suitability and outcome separate. Meeting a stated threshold may permit an application, but it does not promise selection or success. For a digital credential, preserve the original file, read the verifier result, confirm the presenter’s identity separately and share no more personal information than the recipient needs.

Verification sequence: Read issuer name; Read identity result; Check warnings; Contact issuer if needed. Record the result in words such as integrity, issuer identity and status instead of replacing the official outcome with ‘looks real’.

Boundary: A logo alone is not issuer verification. Authorship and provenance matter in sources. Verification supports trust in the digital record, but the receiving employer, institution or authority still decides whether the qualification is relevant and acceptable for its purpose.

A four-line working note

  • Read issuer name
  • Read identity result
  • Check warnings
  • Contact issuer if needed

Name what the source authorises, what it merely describes and what it leaves to a later assessor. Finish with the smallest useful next step.

Back to contents

6. Read document status

Status can indicate whether the document remains issued and has not been revoked according to the verifier’s recognised checks. Read warnings rather than stopping at the certificate image.

For the read document status step, remember that verification works only when the right digital object reaches the right verifier. Keep the original OpenCerts file, file name and source, certificate holder, qualification or Statement of Attainment, issuing organisation, issue date, verification result, document integrity, issuer identity, document status, recipient, channel, purpose and privacy decision on one evidence sheet and separate what the certificate displays from what OpenCerts actually verifies.

Credential scene: A holder shares an old file without noticing a status warning.

Read for who acts, what they must do and when. Passive wording can hide the person responsible for the next step. For a digital credential, preserve the original file, read the verifier result, confirm the presenter’s identity separately and share no more personal information than the recipient needs.

Verification sequence: Find status field; Read warning; Record check time; Ask issuer about conflict. Record the result in words such as integrity, issuer identity and status instead of replacing the official outcome with ‘looks real’.

Boundary: A technical result should be interpreted through the current interface and issuer guidance. Status differs from content in digital systems. Verification supports trust in the digital record, but the receiving employer, institution or authority still decides whether the qualification is relevant and acceptable for its purpose.

A four-line working note

  • Find status field
  • Read warning
  • Record check time
  • Ask issuer about conflict

Create a dated note that another person could reproduce. It should identify the page, field, finding and the official route for resolving uncertainty.

Back to contents

7. Match the holder to the presenter

Compare the certificate holder’s name with appropriate identity evidence through the recipient’s authorised process. Keep this separate from file verification.

For the match the holder to the presenter step, remember that verification works only when the right digital object reaches the right verifier. Keep the original OpenCerts file, file name and source, certificate holder, qualification or Statement of Attainment, issuing organisation, issue date, verification result, document integrity, issuer identity, document status, recipient, channel, purpose and privacy decision on one evidence sheet and separate what the certificate displays from what OpenCerts actually verifies.

Credential scene: A valid certificate file is copied and presented by another person with a similar name.

Preserve the version and date. A saved screenshot can explain what you saw, but the live official page should be reopened before action. For a digital credential, preserve the original file, read the verifier result, confirm the presenter’s identity separately and share no more personal information than the recipient needs.

Verification sequence: Read holder name; Use authorised identity check; Resolve name variants; Avoid excess copies. Record the result in words such as integrity, issuer identity and status instead of replacing the official outcome with ‘looks real’.

Boundary: Do not collect identity documents without a lawful and necessary purpose. Identity matching supports examination administration. Verification supports trust in the digital record, but the receiving employer, institution or authority still decides whether the qualification is relevant and acceptable for its purpose.

A four-line working note

  • Read holder name
  • Use authorised identity check
  • Resolve name variants
  • Avoid excess copies

Write the rule in plain English, but keep its actor, condition and time anchor. A paraphrase that loses any of these has changed the decision.

Back to contents

8. Name the credential precisely

Distinguish a full qualification, module, unit, Statement of Attainment or other award exactly as displayed. Do not upgrade a component into a larger qualification.

For the name the credential precisely step, remember that verification works only when the right digital object reaches the right verifier. Keep the original OpenCerts file, file name and source, certificate holder, qualification or Statement of Attainment, issuing organisation, issue date, verification result, document integrity, issuer identity, document status, recipient, channel, purpose and privacy decision on one evidence sheet and separate what the certificate displays from what OpenCerts actually verifies.

Credential scene: A Statement of Attainment is described on a CV as a full diploma.

Convert the sentence into a checkable question. This turns difficult administrative English into a small task with an answerable evidence need. For a digital credential, preserve the original file, read the verifier result, confirm the presenter’s identity separately and share no more personal information than the recipient needs.

Verification sequence: Copy official title; Copy level if shown; Copy issuing body; Avoid inflated label. Record the result in words such as integrity, issuer identity and status instead of replacing the official outcome with ‘looks real’.

Boundary: The receiving organisation decides relevance. Accurate naming strengthens CVs. Verification supports trust in the digital record, but the receiving employer, institution or authority still decides whether the qualification is relevant and acceptable for its purpose.

A four-line working note

  • Copy official title
  • Copy level if shown
  • Copy issuing body
  • Avoid inflated label

Place the claim beside its evidence and mark the status as confirmed, conditional or unknown. Do not let confident tone replace the missing proof.

Back to contents

9. Check dates without inventing expiry

Record issue date, verification date and any validity information actually stated. Do not call a credential expired merely because training occurred years ago.

For the check dates without inventing expiry step, remember that verification works only when the right digital object reaches the right verifier. Keep the original OpenCerts file, file name and source, certificate holder, qualification or Statement of Attainment, issuing organisation, issue date, verification result, document integrity, issuer identity, document status, recipient, channel, purpose and privacy decision on one evidence sheet and separate what the certificate displays from what OpenCerts actually verifies.

Credential scene: A recruiter assumes every old certificate has automatically expired.

Look for the exception after understanding the rule. Starting with an exception can make a rare pathway look like the ordinary one. For a digital credential, preserve the original file, read the verifier result, confirm the presenter’s identity separately and share no more personal information than the recipient needs.

Verification sequence: Record issue date; Look for stated validity; Check current verifier; Ask relevant authority. Record the result in words such as integrity, issuer identity and status instead of replacing the official outcome with ‘looks real’.

Boundary: Some regulated activities may have separate recency or licence rules. Date logic supports policy reading. Verification supports trust in the digital record, but the receiving employer, institution or authority still decides whether the qualification is relevant and acceptable for its purpose.

A four-line working note

  • Record issue date
  • Look for stated validity
  • Check current verifier
  • Ask relevant authority

Summarise only the decision-relevant wording. Keep a link to the complete source so exceptions and surrounding definitions remain available.

Back to contents

10. Preserve the original file

Keep an untouched archival copy and a sensible filename. Avoid opening and resaving the file through software that may change its structure.

For the preserve the original file step, remember that verification works only when the right digital object reaches the right verifier. Keep the original OpenCerts file, file name and source, certificate holder, qualification or Statement of Attainment, issuing organisation, issue date, verification result, document integrity, issuer identity, document status, recipient, channel, purpose and privacy decision on one evidence sheet and separate what the certificate displays from what OpenCerts actually verifies.

Credential scene: The holder renames the extension or pastes certificate data into a new document.

Compare like with like. Use the same job role, qualification level, applicant category or test type on both sides of the comparison. For a digital credential, preserve the original file, read the verifier result, confirm the presenter’s identity separately and share no more personal information than the recipient needs.

Verification sequence: Keep original bytes; Use safe folder; Back up securely; Work from a copy. Record the result in words such as integrity, issuer identity and status instead of replacing the official outcome with ‘looks real’.

Boundary: Storage security depends on the device and organisation. Version control supports study portfolios. Verification supports trust in the digital record, but the receiving employer, institution or authority still decides whether the qualification is relevant and acceptable for its purpose.

A four-line working note

  • Keep original bytes
  • Use safe folder
  • Back up securely
  • Work from a copy

Turn the paragraph into a checklist question that can be answered from the official record. State who owns the answer and when it should be rechecked.

Back to contents

11. Choose the minimum necessary sharing method

Ask what the recipient needs to verify and use the channel they authorise. A public link can expose personal information to anyone who receives it.

For the choose the minimum necessary sharing method step, remember that verification works only when the right digital object reaches the right verifier. Keep the original OpenCerts file, file name and source, certificate holder, qualification or Statement of Attainment, issuing organisation, issue date, verification result, document integrity, issuer identity, document status, recipient, channel, purpose and privacy decision on one evidence sheet and separate what the certificate displays from what OpenCerts actually verifies.

Credential scene: A learner posts a certificate link containing personal details on a public profile.

Make uncertainty visible. Write ‘not stated on this page’ instead of filling a gap with a confident guess. For a digital credential, preserve the original file, read the verifier result, confirm the presenter’s identity separately and share no more personal information than the recipient needs.

Verification sequence: Name purpose; Name recipient; Choose channel; Limit audience. Record the result in words such as integrity, issuer identity and status instead of replacing the official outcome with ‘looks real’.

Boundary: Privacy decisions depend on context and applicable obligations. Audience awareness improves writing. Verification supports trust in the digital record, but the receiving employer, institution or authority still decides whether the qualification is relevant and acceptable for its purpose.

A four-line working note

  • Name purpose
  • Name recipient
  • Choose channel
  • Limit audience

Record the precise term that changed your interpretation. Explain the before-and-after decision without exaggerating what the source establishes.

Back to contents

12. Explain verification in plain English

A useful message tells the recipient what file is attached, how to open the official verifier and what identity detail may need separate confirmation.

For the explain verification in plain english step, remember that verification works only when the right digital object reaches the right verifier. Keep the original OpenCerts file, file name and source, certificate holder, qualification or Statement of Attainment, issuing organisation, issue date, verification result, document integrity, issuer identity, document status, recipient, channel, purpose and privacy decision on one evidence sheet and separate what the certificate displays from what OpenCerts actually verifies.

Credential scene: An employer receives an unfamiliar extension and assumes the attachment is broken.

Use a closure test. The step is complete only when the official record, required evidence and next action agree. For a digital credential, preserve the original file, read the verifier result, confirm the presenter’s identity separately and share no more personal information than the recipient needs.

Verification sequence: Name file; Link official verifier; State credential; Offer contact. Record the result in words such as integrity, issuer identity and status instead of replacing the official outcome with ‘looks real’.

Boundary: Do not claim the verifier proves more than its result. Reader guidance improves technical communication. Verification supports trust in the digital record, but the receiving employer, institution or authority still decides whether the qualification is relevant and acceptable for its purpose.

A four-line working note

  • Name file
  • Link official verifier
  • State credential
  • Offer contact

Write a closure note only after the source, identity or applicant context and required evidence align. Otherwise log the unresolved question.

Back to contents

13. Handle a warning proportionately

Read which check produced the warning, preserve the file, confirm the source and contact the issuer. Do not accuse a holder or provider solely from an unfamiliar interface state.

For the handle a warning proportionately step, remember that verification works only when the right digital object reaches the right verifier. Keep the original OpenCerts file, file name and source, certificate holder, qualification or Statement of Attainment, issuing organisation, issue date, verification result, document integrity, issuer identity, document status, recipient, channel, purpose and privacy decision on one evidence sheet and separate what the certificate displays from what OpenCerts actually verifies.

Credential scene: A temporary or identity warning is announced publicly as fraud before the issuer is contacted.

Ask one precise question that names the source, field and decision. Specific questions are easier for an institution to answer accurately. For a digital credential, preserve the original file, read the verifier result, confirm the presenter’s identity separately and share no more personal information than the recipient needs.

Verification sequence: Capture exact warning; Check official help; Contact issuer; Record resolution. Record the result in words such as integrity, issuer identity and status instead of replacing the official outcome with ‘looks real’.

Boundary: Suspected fraud or misuse may need the relevant organisation or authority. Proportionate claims support media literacy. Verification supports trust in the digital record, but the receiving employer, institution or authority still decides whether the qualification is relevant and acceptable for its purpose.

A four-line working note

  • Capture exact warning
  • Check official help
  • Contact issuer
  • Record resolution

Phrase the follow-up around one named document and one named field. This gives the official contact a concrete question instead of a general worry.

Back to contents

14. Archive the verification record

Keep the original certificate, authorised sharing record and date of verification. A recipient can rerun verification rather than relying only on your screenshot.

For the archive the verification record step, remember that verification works only when the right digital object reaches the right verifier. Keep the original OpenCerts file, file name and source, certificate holder, qualification or Statement of Attainment, issuing organisation, issue date, verification result, document integrity, issuer identity, document status, recipient, channel, purpose and privacy decision on one evidence sheet and separate what the certificate displays from what OpenCerts actually verifies.

Credential scene: Months later, a screenshot shows valid but no one can locate the original file or checking date.

Archive the final record with its context. A detached sentence may be impossible to interpret after the programme, portal or policy changes. For a digital credential, preserve the original file, read the verifier result, confirm the presenter’s identity separately and share no more personal information than the recipient needs.

Verification sequence: Store original; Log recipient; Log check date; Retain official contact. Record the result in words such as integrity, issuer identity and status instead of replacing the official outcome with ‘looks real’.

Boundary: A screenshot is a record of a view, not a substitute for future verification. Audit trails support professional work. Verification supports trust in the digital record, but the receiving employer, institution or authority still decides whether the qualification is relevant and acceptable for its purpose.

A four-line working note

  • Store original
  • Log recipient
  • Log check date
  • Retain official contact

Archive the final interpretation with its date and source. Add a reminder that later policy or portal changes require a fresh check.

Back to contents

Worked examples

Example 1: Original versus printout

A graduate sends the original OpenCerts file and tells the recruiter to use the official verifier. The graduate does not ask the recruiter to trust a scan of a paper copy.

Reading lesson: Authenticity belongs to the verifiable digital object.

Example 2: Valid file, separate identity check

The verifier confirms integrity, issuer identity and status. The recruiter then follows the organisation’s normal process to match the named holder to the applicant.

Reading lesson: Document verification and person verification are separate.

Example 3: Share only what is needed

A learner sends the certificate through the employer’s application portal rather than posting a public link containing personal information.

Reading lesson: Convenience should not erase audience and privacy boundaries.

Back to contents

Digital-certificate verification studio

Result-language drill

Classify fictional verifier messages under integrity, issuer identity, status or holder matching.

  • Check type
  • Exact result
  • What it establishes
  • Next action

After the exercise, identify the exact word, field or result that changed the decision and explain why it mattered.

Safe-sharing scenario

Choose a channel for a fictional employer, school and public portfolio, then justify the minimum information shared.

  • Purpose
  • Recipient
  • Channel
  • Privacy risk

Finish by naming the missing evidence that would make the next action safer; an empty answer usually means the source was read too quickly.

Back to contents

Advice for students, parents and mentors

For learners and jobseekers

Keep the original certificate file in a secure backup and learn how to explain it to a recipient.

Use the exact credential title on your CV; do not turn a unit or Statement of Attainment into a larger award.

For families

Help organise secure files, but let the certificate holder understand what is being shared and with whom.

Avoid placing identity documents and credentials in open family chats.

For employers and educators

Verify through the official tool and match identity through an authorised process.

Treat warnings as questions to investigate, not instant proof of misconduct.

The goal is not to make a young person afraid of every official page. It is to make careful checking feel normal, achievable and quietly empowering. English becomes useful when it helps someone pause, verify, ask a precise question and choose a proportionate next step.

Back to contents

Frequently asked questions

What is a WSQ digital certificate?

It is a digital credential issued in the WSQ ecosystem that can be independently checked through the supported verification route.

Where should I verify it?

Use the official OpenCerts verifier linked by SkillsFuture Singapore.

Is a printout authentic?

OpenCerts says printing discards the cryptographic protections, so a printout should not be treated as the authentic digital certificate.

What does verification check?

OpenCerts describes checks for document integrity, issuer identity and document status.

Does a valid file prove the presenter is the holder?

No. The recipient should match the named holder through an appropriate identity process.

Can I edit the certificate file?

Keep the original untouched. A change can cause verification to fail.

Can I share it publicly?

Consider personal information, purpose and audience. Use the recipient’s authorised channel where possible.

What if the verifier shows a warning?

Read the exact check, preserve the file, consult official help and contact the issuer.

Does verification prove the credential is suitable for a job?

No. The receiving organisation decides relevance and acceptance.

Why does English matter?

It helps readers separate file, rendering, integrity, issuer, status, holder and purpose instead of collapsing them into ‘real’ or ‘fake’.

Back to contents

Useful next reading

Continue with verified eduKate guides on credentials, course information and functional reading.

Digital-certificate English becomes practical when the original file, official verifier, holder, recipient and privacy decision remain distinct from beginning to end.

Discover more from eduKate Singapore

Subscribe now to keep reading and get access to the full archive.

Continue reading