ahmido
c36cb43741
This PR introduces the Global Surface Information Architecture Contract, detailing rules for decision-first display, metadata separation, and zero-state suppression across UI surfaces. Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #441
3.1 KiB
3.1 KiB
Source Audit Summary
Verification level: repo-verified for file presence, browser-verified where Spec 368 screenshots or browser notes state browser evidence, derived from existing implementation where this package summarizes audit findings.
Primary Inputs
| Source | Availability | Verification Class | Use In Spec 370 |
|---|---|---|---|
specs/368-platform-ui-signal-to-noise-browser-audit/audit.md |
available | repo-verified | Executive summary, page counts, top findings, refactor priority, maturity score |
specs/368-platform-ui-signal-to-noise-browser-audit/findings.md |
available | repo-verified | Detailed bloat and page findings |
specs/368-platform-ui-signal-to-noise-browser-audit/recommendations.md |
available | repo-verified | Global UI rule seed |
specs/368-platform-ui-signal-to-noise-browser-audit/page-scorecard.csv |
available | repo-verified | Surface examples and scoring context |
specs/368-platform-ui-signal-to-noise-browser-audit/page-inventory.csv |
available | repo-verified | Route/surface inventory context |
specs/368-platform-ui-signal-to-noise-browser-audit/spec-candidates.md |
available | repo-verified | Candidate A source |
specs/368-platform-ui-signal-to-noise-browser-audit/artifacts/raw/browser-notes.md |
available | repo-verified | Browser pass context and limitations |
specs/368-platform-ui-signal-to-noise-browser-audit/artifacts/screenshots/ |
available | browser-verified where screenshots captured pages | Examples and before-state evidence |
Audit Baseline
- Audit date: 2026-06-09.
- Pages discovered: 100 repo-verified UI routes.
- Pages browser-audited: 19.
- Screenshots available: 43.
- Blocked or inaccessible pages: 4.
- Overall platform UI maturity score: 3.6/5 across reachable browser-scored pages.
Top Repeating Patterns
- Decision content competes with technical metadata.
- Zero/no-attention metrics remain visible even when the page already states no action is needed.
- Evidence, diagnostics, and operation internals are not always visually separated.
- Provider readiness and required action can require inference from technical table columns.
- Customer/auditor surfaces are mostly safe but can be dense.
- Diagnostic surfaces need stronger first-block guidance.
Source Limitations
| Input | Verification Class | Handling |
|---|---|---|
| Evidence Snapshot detail browser state | not available |
Do not infer customer/auditor evidence-surface quality from the blocked page. |
| Required Permissions browser state | not available |
Keep configuration-surface recommendations generic until fixture/auth access is fixed. |
| System dashboard browser state | not available |
Treat system-surface findings as blocked source evidence, not browser-scored truth. |
| System operations browser state | not available |
Treat system-surface findings as blocked source evidence, not browser-scored truth. |
| Target mock/example per archetype | deferred |
Keep target imagery and archetype mockups for a later approved design/spec package. |
Spec 370 must not invent conclusions for not available inputs. Future specs may promote a deferred item only with fresh source evidence and bounded scope.