Maintainer handover

    A practical guide to taking responsibility for the OPDA knowledge base, its semantic-model toolchain and the services around it. Start with access and a reproducible build, then complete the service and ownership checks before accepting the handover.

    Repository review: . Document status: public operational reference; acceptance remains to be recorded by the receiving owner.

    Handover documents

    Getting started

    Establish ownership, understand the standards boundaries and set up a reproducible local environment.

    Architecture and repository

    Understand the public website, model tooling, participant services and maintained source locations.

    Models and validation

    Change models at their maintained source and select the right validation evidence.

    Release and recovery

    Publish through CI, verify the live release and respond to operational incidents.

    Operations and access

    Transfer account ownership, scheduled automation, Microsoft workspaces and evidence intake.

    Content and NotebookLM

    Maintain resources, marketing materials, notebooks, generated media and source provenance.

    Acceptance and evidence

    Record acceptance, assign open actions and retain the evidence behind this handover.