Skip to content

Evidence Map — HybridOps.Core

This page maps key platform claims to the proof material that backs them.

Use it as a routing layer between:

  • Narratives on this portal (briefings and showcases).
  • Operational procedures (runbooks and HOWTOs).
  • Execution outputs (timestamped artefacts and logs produced by automation runs).

Evidence locations

Evidence is organised consistently across runs:

  • output/artifacts/… — structured artefacts (plans, JSON, inventories, reports, snapshots).
  • output/logs/… — tool logs (Terraform, Packer, Ansible, CI, etc.).

Depending on the delivery context, evidence may be available via:

  • Release evidence packs published alongside HybridOps.Core releases.
  • Execution outputs produced during local runs in the operator environment.
  • Legacy evidence archive under the output/ tree in the current platform repository (until migration is complete).

1. Intended audience

  • Tech Nation assessors — to verify that stated behaviours are backed by repeatable runs.
  • Hiring managers — to review system design, trade-offs, and delivery discipline.
  • Operators / platform engineers — to locate runbooks, drill reports, and validation outputs.
  • Learners / practitioners — to connect a concept to implementation and observable proof.

This map is aimed at people who need to verify behaviour, not only read descriptions.

Recommended reading pattern

  1. Start with a showcase or briefing to understand the intent and architecture.
  2. Follow the linked runbook/HOWTO to see the operational procedure.
  3. Inspect the referenced artefacts and logs for concrete proof.

2. Quick starting points

These rows connect a key outcome to a narrative and the relevant evidence themes.

Outcome / claim Start with (on this portal) Evidence themes
DR failover to cloud (RTO) Scale workload to cloud DR flows · Cost guardrails
Database read-only + failover Hybrid DR & cost walkthrough · DB failover runbook DR flows
Hybrid connectivity baseline WAN edge & hybrid connectivity Networking
Repeatable image builds Image builds with Packer Images
Delivery platform + GitOps controls CI/CD pipeline overview · Delivery platform & GitOps Delivery
Source of truth automation Source of truth & NetBox automation Source of truth
Documentation and teaching surface Documentation, teaching & community · HybridOps Academy overview Docs

When in doubt, follow the middle column first for context, then move into the themed evidence areas below.

3. Proof archives by theme

Each theme links to:

  • Where to read more on this portal (showcases, runbooks, HOWTOs).
  • Where to find proof outputs (artefact/log paths and evidence packs).

Networking & hybrid connectivity

Hybrid underlay/overlay connectivity, routing governance, and failure-domain validation.

Typical evidence paths

  • output/artifacts/networking/…
  • output/logs/networking/…

Read more

Source of truth & NetBox-driven automation

NetBox as the authoritative source of truth for inventory, IPAM, and topology, plus automation flows that read/write from it.

Typical evidence paths

  • output/artifacts/netbox/…
  • output/logs/netbox/…

Read more

Delivery platform, CI/CD & GitOps

CI/CD pipelines, automation orchestration, and GitOps reconciliation for Kubernetes workloads and platform configuration.

Typical evidence paths

  • output/artifacts/ci/…
  • output/artifacts/ansible-runs/…
  • output/artifacts/terraform/…
  • output/logs/ci/…

Read more

Images, templates & bootstrap

Packer-built templates and first-boot checks used to bootstrap control and workload planes.

Typical evidence paths

  • output/artifacts/packer/…
  • output/logs/packer/…

Read more

DR & hybrid DR flows

On-prem ↔ cloud failover/failback, database promotion patterns, and DR drill orchestration.

Typical evidence paths

  • output/artifacts/dr/…
  • output/logs/dr/…
  • output/artifacts/sql/…

Read more

Cost guardrails & decision service

Cost as a first-class signal for DR and bursting decisions, with decision artefacts emitted by pipelines.

Typical evidence paths

  • output/artifacts/decision/…
  • output/logs/decision/…

Read more

Documentation, teaching & learning

Documentation engine, publication workflow, and Academy mapping.

Typical evidence paths

  • output/artifacts/docs/…
  • output/logs/docs/…

Read more

4. Relationship to Tech Nation submissions

Portfolio PDFs are distilled snapshots of the same work described here.

  • Each portfolio document has a corresponding Markdown source under briefings/gtv/.
  • This evidence map does not introduce new claims; it provides structured navigation and verification paths.

If you are reviewing HybridOps as part of an assessment or hiring process:

  1. Read the relevant portfolio document (or its Markdown source).
  2. Use this evidence map to navigate to the relevant themes and stories.
  3. Follow links into runbooks and evidence outputs until you have sufficient verification.