Skip to content

Latest commit

 

History

History
49 lines (33 loc) · 3.67 KB

VALIDATION.md

File metadata and controls

49 lines (33 loc) · 3.67 KB

Validation evidence

Placeholder screenshots were removed on November 15, 2026. Written test results below retain their original dates and scope; historical screenshot references describe earlier captures. Proper Azure and application screenshots are deferred. The illustrated architecture is a source-based explanation, not a live-service screenshot.

Terms used here: DNS turns a service name into the network address used to reach it.

Executed locally

Check Recorded result
Actual extracted TypeScript rules 6 tests passed
Python reference/renderer 13 tests passed
Executed demonstration 8 checks passed
Terraform schema and mock plans Validate passed; 2 tests using simulated cloud responses passed; no apply
Browser Desktop and 390-pixel mobile, tabs/rerun, origin/asset denials passed
Workflow syntax actionlint 1.7.12 passed; no hosted workflow dispatched
Source secret scan Trivy 0.75.0: zero findings in this prepared input

The six actual source tests establish the provider-result mapping. The Python demo replays fictional verdicts; it does not run a malware engine or prove actual Defender delivery. Its eight checks include clean, pending, malicious-verdict and error-verdict cases.

The machine record includes date, commands, counts and source hashes. Screenshots come from the working local code. They are not hand-edited success states or Azure Portal captures.

Reproduce

npm run test:source
python -B -m unittest discover -s tests -v
python -B -m lab demo

Evidence boundaries

  • Actual implementation source/tests are distinct from a compact public renderer or event adapter.
  • Synthetic inputs preserve privacy; they do not establish real provider output quality, identity or employee findings.
  • Mock plans do not prove deployed IAM, DNS, queue delivery, SQL adapter or application hosting.
  • No Azure service start, actual employee operation, live provider request or paid image call occurred for this preparation.
  • Nonproduction screenshot capture remains optional follow-up. Existing accepted operational history is not relabeled as a fresh cloud test.

Troubleshooting documentation review — November 7, 2026

Added a README incident summary and a linked historical lessons guide, checking the account against the maintained source records. Documentation checks covered local links, complete incident fields, identifying-information patterns, whitespace and preservation of the existing four-step walkthrough. Shared incidents link to the relevant project details; unresolved causes remain explicit.

This was an editorial update. Application code, tests, Terraform, images, workflow definitions and cloud settings were not changed. Existing functional test counts and screenshots above retain their original scope and dates; no application suite, live scan, paid image request, recovery rehearsal or GitHub Actions run was executed for this documentation pass.

Tools and utilities documentation review — November 7, 2026

Added a prominent README table naming the relevant tools/services and their jobs. The wording distinguishes actual platform components, operating utilities, selected source adapters, optional preparation and local teaching examples. Relevant step headings name their tools while the four-step order and explanatory sentences remain unchanged.

This editorial pass did not change application code, dependencies, infrastructure, workflows or cloud settings. Existing tests and screenshots retain their original evidence scope; no application suite, live scanner, browser sign-in, paid request or GitHub Actions run was executed for this wording update.