7.5 KiB
Quickstart: Governance Artifact Truthful Outcomes & Fidelity Semantics
Goal
Deliver the first truthful-artifact slice without widening scope beyond existing governance artifacts and artifact-targeted run detail.
Implementation Phases
Phase 1: Shared Truth Envelope
Goal: Centralize how governance artifacts express truth, degradation, readiness, and next steps.
- Add or extend shared presenter support under existing
app/Supportor domain service namespaces. - Normalize which dimensions are primary vs diagnostic for:
- baseline snapshot fidelity and gaps
- evidence completeness and freshness
- tenant review completeness and publication blockers
- review-pack lifecycle vs provenance
- artifact-targeted run outcome vs artifact result
- Reuse
BadgeCatalog,BadgeRenderer,OperatorOutcomeTaxonomy, andReasonPresenterinstead of page-local label logic. - Add targeted unit tests for any new or remapped badge or presenter semantics.
Phase 2: Artifact Family Integration
Goal: Apply the truth envelope to existing resource lists and detail views.
- Update baseline snapshot list/detail messaging so fidelity/support signals stay diagnostic while false-green capture outcomes are clearly degraded.
- Update evidence snapshot list/detail and evidence overview rows so completeness, freshness, and next-step semantics are explicit.
- Update tenant review list/detail and review register so review existence, completeness, and publication readiness are separated.
- Update review-pack list/detail so file existence is separated from trustworthy stakeholder-output provenance.
- Keep current action surfaces and authorization rules unchanged unless explanation or enablement reasons must reflect truth semantics.
Phase 3: Canonical Run Detail Integration
Goal: Make artifact-targeted operation runs answer whether a trustworthy artifact was produced.
- Extend the operation-run enterprise detail builder for:
baseline_capturetenant.evidence.snapshot.generatetenant.review.composetenant.review_pack.generate
- Show a primary artifact-truth summary before raw JSON/context.
- Reuse related links and reason translation for next-step guidance.
- Preserve diagnostics as a secondary boundary.
Phase 4: RBAC and Regression Coverage
Goal: Prove the slice is truthful and tenant-safe.
- Add positive and negative authorization tests for canonical evidence and review pages.
- Add focused coverage for:
- false-green baseline examples
- partial and stale evidence
- non-publishable reviews
- review-pack provenance and historical availability
- empty-state distinctions for not-created, degraded, and historical-only cases
- artifact-targeted run detail messaging
- Run formatter and affected tests.
- Review the affected list surfaces against
docs/product/standards/list-surface-review-checklist.md.
Curated Manual Validation Set
Validate 12 curated artifact cases before sign-off so the operator can answer from one inspection step whether the artifact exists, whether it is trustworthy, and whether action is required.
- Healthy baseline artifact
- False-green baseline with no trustworthy artifact
- Historical baseline trace that is intentionally non-usable
- Healthy evidence snapshot
- Partial evidence snapshot with missing dimensions
- Stale evidence snapshot with no further action required
- Draft tenant review that is internally useful but not publishable
- Blocked tenant review with explicit next step
- Publishable tenant review
- Historical review pack derived from a formerly publishable review
- Current review pack blocked by regressed source readiness
- Artifact-targeted run that completed but produced a degraded artifact
Completed Validation Checklist
Validated on March 22, 2026 through the focused Spec 158 regression suite plus the canonical authorization and guard checks.
- Healthy baseline artifact
- False-green baseline with no trustworthy artifact
- Historical baseline trace that is intentionally non-usable
- Healthy evidence snapshot
- Partial evidence snapshot with missing dimensions
- Stale evidence snapshot with no further action required
- Draft tenant review that is internally useful but not publishable
- Blocked tenant review with explicit next step
- Publishable tenant review
- Historical review pack derived from a formerly publishable review
- Current review pack blocked by regressed source readiness
- Artifact-targeted run that completed but produced a degraded artifact
List Surface Review Notes
- Baseline snapshot list/detail keeps artifact truth separate from fidelity diagnostics while preserving the existing sortable/searchable structure.
- Evidence overview remains a tenant-safe read-only summary with one drill-down action per row and explicit artifact-truth, freshness, and next-step columns.
- Evidence snapshot, tenant review, review register, and review pack surfaces keep badge-based state rendering, domain-specific empty states, and authorization boundaries intact after the new truth columns were added.
- Canonical evidence and review summaries continue to scope rows, tenant filters, and drill-down links to entitled tenants only.
Likely File Inventory
Modified Files
app/Filament/Resources/BaselineSnapshotResource.php
app/Filament/Resources/EvidenceSnapshotResource.php
app/Filament/Resources/TenantReviewResource.php
app/Filament/Resources/ReviewPackResource.php
app/Filament/Resources/OperationRunResource.php
app/Filament/Pages/Monitoring/EvidenceOverview.php
app/Filament/Pages/Operations/TenantlessOperationRunViewer.php
app/Filament/Pages/Reviews/ReviewRegister.php
app/Support/Badges/OperatorOutcomeTaxonomy.php
app/Support/Badges/BadgeCatalog.php
app/Support/Badges/Domains/*.php
app/Support/ReasonTranslation/*.php
app/Services/TenantReviews/TenantReviewReadinessGate.php
tests/Feature/Evidence/*.php
tests/Feature/TenantReview/*.php
tests/Feature/ReviewPack/*.php
tests/Feature/Monitoring/*.php
tests/Unit/**/*.php
Possible New Helper Files
app/Support/Ui/GovernanceArtifactTruth/*.php
app/Support/Badges/Domains/<new-or-remapped-domain>.php
tests/Unit/Badges/GovernanceArtifactTruthTest.php
Verification Commands
vendor/bin/sail artisan test --compact tests/Feature/Evidence
vendor/bin/sail artisan test --compact tests/Feature/TenantReview
vendor/bin/sail artisan test --compact tests/Feature/ReviewPack
vendor/bin/sail artisan test --compact tests/Feature/Monitoring
vendor/bin/sail bin pint --dirty --format agent
Verification Review Checklist
- Review baseline snapshot, evidence snapshot, tenant review, review-pack, evidence overview, and review register list surfaces against
docs/product/standards/list-surface-review-checklist.md. - Confirm empty-state wording distinguishes not-created, degraded, and historical-only cases where those states can appear.
- Confirm canonical evidence/review list filters and counts remain tenant-safe for both allowed and disallowed tenants.
Rollout Notes
- No migration is required unless implementation reveals a minimal summary/context enrichment need.
- If enrichment is needed, keep it additive to existing
summaryorcontextpayloads and limit it to provenance or usability distinctions that cannot be derived safely at render time. - No deploy-time asset change is expected beyond the existing Filament asset pipeline.
- Historical records must remain readable even if some new truth-envelope inputs are absent.