Skip to main content
DigitalSanctum.
Menu
Standards index / Published

Digital Sanctum standards

Digital Sanctum

Design, delivery and editorial governance

These documents explain the principles behind Digital Sanctum’s work and the discipline standards used to design, deliver, review and maintain it. Start with the Design Philosophy for the governing principles, then choose the standard or process for your task. Each document identifies its own scope and adoption state. Publication does not establish adoption or prove that every product or deliverable conforms.

Choose the principles, standard or process for your work

  • Digital Sanctum Design Philosophy

    Nineteen governing principles for design and delivery, including client control, traceable claims, security, review and accountable decisions

    SYS-031 v2.0 · Adopted internally
    Curated public edition of the adopted internal philosophy

  • Website Content Architecture Standard

    Content types, canonical URL families, parent/child relationships, breadcrumbs, page structure and discovery

    SYS-077 v1.0 · Adopted internally
    Canonical public mirror of the adopted standard

  • Journalistic or Web Article Process

    Timely reporting, explainers, practical guides and clearly labelled commentary

    SOP-154 v1.1 · Adopted internally
    Canonical public mirror of the adopted internal version

  • Academic & Research Article Process

    Original experiments and systematic evidence reviews requiring a defined question and method

    SOP-155 v1.1 · Adopted internally
    Canonical public mirror of the adopted internal version

  • Brand Identity & Voice

    Brand purpose, identity, voice and evidence-aware claims

    SOP-004 v1.3 · Adopted internally
    Public brand guidance and visual reference

  • UX and UI Design Standard

    Proposed guidance for clear, accessible interfaces, visual communication and representative product experiences

    v1.4 · Proposed, pending adoption
    Its existing publication and status are unchanged

  • AI Timeline Entry Process

    Dated AI milestones, event identity, primary evidence, practical decisions, review and corrections

    SOP-157 v1.0 · Adopted internally
    Canonical public mirror of the adopted internal version

How the principles and discipline standards work together

The Design Philosophy sets out the governing principles and their limits. Discipline standards and procedures apply those principles to specific work. Its v2.0 adoption establishes the internal principles; this listing does not certify compliance.

What the editorial processes require

Both processes make evidence, uncertainty and responsibility visible. They require a commissioned brief, sources matched to claims, reviewers who did not author the candidate, attributable decisions on the exact version, and a correction path.

The research process adds a prospective method, data and code provenance, analysis and reproducibility limits. The journalistic process distinguishes discovery, disclosure, patching and exploitation, and checks the claimed role of AI. Adopting either process does not approve an article made under it, establish external peer review or grant publication authority.

The content architecture standard supplies the shared classification and navigation rules. It distinguishes a page's canonical home from its discovery links, preserves established URLs unless a reviewed migration is justified, and requires an explicit content map and breadcrumb/discovery checks before release. The editorial and sitemap processes apply that contract rather than maintaining competing rules.

The AI Timeline Entry Process applies those controls to short dated records: it distinguishes event dates from source checks, maps evidence into the existing entry contract and verifies the timeline’s selection, filters and reading behaviour. A milestone does not require a separate full article. Original experiments still follow the research process.

Versions, ownership and changes

Digital Sanctum owns and maintains these documents. The canonical internal records include SYS-031, SYS-077, SOP-154, SOP-155, SOP-157 and SOP-004; each public mirror or curated edition identifies its source version. Proposed changes must be reviewed and accepted in the canonical record before a corresponding mirror is released. Previous versions, decisions and corrections remain traceable.

The UX/UI document follows its own proposal and adoption path. Its presence beside adopted editorial processes does not adopt it by association.

See the reporting process applied

The PHP2Shell, Tailworm and OpenCode security explainer is a separate security explainer. It shows the difference between an evidenced AI connection, an infrastructure-security report and a qualified architectural comparison. Each article requires its own independent review and release decision; adopting a process does not approve an article.

Suggest a correction

Use our contact form and identify the document, version, passage and supporting evidence. We assess whether a correction, clarification or new version is needed, then retain the reason and affected decisions.

Help improve these standards.

Tell us which process, version and passage needs clarification or correction.

Suggest a correction

Digital Sanctum knowledge base

Search Digital Sanctum

Find services, processes, products, case studies, and strategic intelligence in the site index.

Type at least two characters to search the knowledge base.