Portfolio Evidence Dashboard

Current validation status for portfolio evidence.

A concise summary of systems represented, mapped claims, artifact coverage, screenshot records, manifest freshness, document integrity, and unresolved limitations.

Systems4Primary lab virtual machines represented
Mapped claims13Claims linked to evidence and limitations
Artifacts15Records in the current-state manifest
Last generatedCurrent direct-evidence manifest date

Claim Classification

Coverage from the current claim map.

These counts summarize the 13 entries in the current public claim map.

8Validated

Directly supported by current source or direct evidence.

2Tested

Behavior was exercised within a documented scope.

1Configured

Configuration is present without a broader behavior claim.

2Limitations

One explicit limitation and one documented-with-limitation entry.

Validation Coverage

What is current and where to verify it.

SRC

Source provenance

Direct infrastructure evidence traces to home-lab source commit fb6c286. The public provenance file records source and publication context.

provenanceOpen
DIR

Direct evidence coverage

Primary claims link to direct records for Proxmox, DC01, WS01, Linux01, SSSD remediation, backup configuration, backup inventory, and restore validation.

claim indexReview
DOC

Document integrity

The published DOCX is mirrored in the evidence library and represented by a SHA-256 manifest entry.

Hash prefixd7e81a06dcfb
docxDownload
IMG

Screenshot records

Nine public screenshot files cover Active Directory, DNS, DHCP, Group Policy, Linux system state, evidence transfer, installation type, VM configuration, and archive integrity.

screenshotsReview
LIM

Unresolved limitations

Recurring restore assurance, RTO/RPO, production scale, employer administration, full firewall assurance, and broad security assurance remain intentionally excluded.

evidence boundaryReview
MAN

Current manifest

The manifest records generation time, source commits, public destination paths, classifications, hashes, supported claims, and reviewer notes.

jsonOpen

Dashboard Use

Summary first; source artifacts remain authoritative.

Counts and dates make the evidence set easier to scan. The linked manifest, claim map, provenance file, validation outputs, and direct inventories provide the underlying detail.