debate-map-v3.1.md
HTML wrapper for HTML-only fetchers; content is shown verbatim.
Raw file
# 654 — if.site Map Debate v3.1 (Assume Stakeholder Is Right)
Date: 2026-02-21
Task: IF-2050
Session: /rook-002 (Codex runtime)
## Debate Prompt
- User concern: the `InfraFabric operating map` still feels weird / over-designed.
- Hypothesis to test: user may be wrong; current direction may be acceptable.
- Required outputs: keep/simplify/replace decision, whether bezier curves help, and whether table should sit under the map.
## Lanes (independent)
1. Design Systems / Enterprise UX
2. Buyer Red-Team / Skeptical Procurement
3. Corporate Comms / Claim-Boundary
4. Visual Direction / Institutional Premium Lens
5. IA / Information-Density
## Lane Findings (condensed)
### L1 — Design Systems / Enterprise UX
- Verdict: `SIMPLIFY`
- High findings:
- Duplicate map render (hero + full section) weakens hierarchy.
- Map carries too many semantics at once (topology + status + dates + evidence).
- Recommendation:
- Keep one map only.
- Add compact decoder table under map.
- Keep full readiness table as separate primary decision section.
### L2 — Buyer Red-Team / Skeptical Procurement
- Verdict: `FAIL` at procurement trust threshold (current state).
- Blockers:
- Evidence links point to module pages, not immutable artifacts.
- Unknown states coerce to preview.
- Compact map hides legend and remains ambiguous.
- Bezier stance:
- Generally negative for conservative buyers.
- Allow only constrained non-critical use, if at all.
- Recommendation:
- Under-map fallback table is mandatory.
### L3 — Corporate Comms / Claims Boundary
- Verdict: complexity should be reduced and state boundaries made explicit.
- Core message:
- Split `verified live` vs `target` semantics in labeling/captioning.
- Avoid language that implies canonical runtime where only surface availability exists.
- Recommendation:
- Add explanatory text and state table directly under map.
### L4 — Visual Direction (Institutional Premium)
- Verdict: map is directionally good, but should look less infographic and more control atlas.
- Bezier stance:
- Only with strict constraints: low curvature, monotone, no loops, no animation.
- Recommendation:
- Keep restrained palette/strokes.
- Add compact evidence table beneath map to increase trust signal.
### L5 — IA / Information Density
- Verdict: page currently duplicates module information too often.
- Recommendation:
- `Map tiny + table primary`.
- Ordering: Hero -> one compact map -> readiness table -> module cards.
## Arbitration
### 1) Is the map trying to do too much?
Yes. Consensus is strong (`5/5`) that the map and surrounding sections currently over-explain and duplicate data.
### 2) Should we use bezier curves?
- Consensus: not as a default for core execution paths.
- Allowed: limited, monotone bezier only for secondary non-critical routing where overlap is unavoidable.
### 3) Should there be a table under the map?
Yes. Strong consensus (`5/5`) for a compact decoder table immediately below map.
### 4) Keep / simplify / replace?
- Final verdict: `SIMPLIFY`, not full replace.
- Keep one map as orientation artifact.
- Remove duplicate map section.
- Make readiness table the primary proof artifact.
## Canonical Next Layout (debate outcome)
1. Hero + claim boundary + 2 CTAs.
2. Single compact control map (only once).
3. `Map decoder` compact table directly under map:
- `From | To | Lane | State | Owner | Evidence`.
4. Full readiness board (primary decision surface).
5. Module cards (secondary details only).
## Implementation Acceptance Gates
1. Single map render on homepage (no second full duplicate map).
2. Decoder table exists immediately under map.
3. Core paths use straight/orthogonal lines; no decorative curvature.
4. Map does not carry full dates/status prose in every node (move to table where possible).
5. Evidence links in table resolve to concrete verifiable artifacts (or clearly labeled explainer when artifact unavailable).
## Black/White Decision
- The user is **not wrong**.
- Current map direction improved but still over-complex for procurement-first reading.
- Action: simplify map, add decoder table, promote table-first proof flow.