review-pack.md
HTML wrapper for HTML-only fetchers; content is shown verbatim.
Raw file
Links (extracted)
Clickable list for reviewers; avoids copy/paste line-wrap issues.
# InfraFabric External Review Pack — IF.TTT Homepage Redesign (v0)
**Goal:** Get a second opinion (from humans and LLMs) on a new `infrafabric.io` homepage for **IF.TTT**.
**Single link (HTML wrapper):**
- https://infrafabric.io/static/hosted/review/ifttt-homepage-redesign/2025-12-29/review-pack.html
This pack is intentionally **one file** so reviewers with sandboxed fetchers can still participate.
---
## What You’re Reviewing
We’re redesigning the **root homepage** at `https://infrafabric.io/` to explain IF.TTT with maximum clarity.
- **Tone:** neutral “bank + startup” (striking, calm, forwardable)
- **Style:** OK Computer–inspired minimalism (big negative space; no clutter)
- **Message:** black/white clarity — what’s verified vs what isn’t
- **Call-to-action:** subtle but obvious enough for the right person
IF.TTT is the backbone of the InfraFabric governance stack. This homepage is the top of the funnel.
---
## Non‑Negotiables (Hard Requirements)
### A) The “Big Empty Page” Layout
Homepage must be mostly empty, with a **single central loop**:
- Center typing animation cycles:
- `if.Transparent`
- (replace word) `if.Traceable`
- (replace word) `if.Trust`
- (replace word) `if.TTT`
- then loop
- **Badges are front-and-center** (but not salesy):
- `VERIFIED`
- `QUANTUM READY` (optional; do not claim “quantum-secure”)
- Fixed footer navigation:
- Bottom-left: verticals (links)
- Bottom-right: `Developers | API` (links)
### B) Audience Split
- **Homepage is for PMs / execs / compliance owners**.
- Deep technical detail belongs under `Developers` / `API` pages.
### C) Open Verification Is The Differentiator
The homepage must show **artifacts, not adjectives**:
- Show (or link to) a real trace receipt page.
- Explain offline verification (bundles + verifier tool) in plain language.
- Do not claim “you are compliant.” Say “this supports audits by producing verifiable receipts.”
### D) Bilingual Start
- EN + FR initially.
- Page structure must allow more languages later.
### E) Contact
- Contact details must exist and be easy to find:
- `ds@infrafabric.io`
- `Danny Stocker`
---
## Desired Homepage Flow (v0)
1) Visitor lands on **big empty** page → sees typing loop + badges
2) After first loop completes: a simple “how verification works” stepper appears:
- Source → Hash → Trace Receipt → Offline Bundle (optional) → Verify
3) The stepper can later “collapse” into the header when user scrolls.
---
## Which Verticals + Personas Should The Site Target?
We need a short, defensible set of verticals that *actually buy* this kind of governance:
- Suggest 4–6 verticals max for the homepage footer
- For each vertical, name:
- primary buyer persona
- their “pain” (evidence, audits, disputes, attribution)
- what IF.TTT changes (in one sentence)
**Constraints:** keep it vendor-neutral and non-claimy.
---
## Working References (Current)
These links are included so reviewers can validate what exists today.
### Product
- Home: https://infrafabric.io/
- Governance: https://infrafabric.io/governance/
- Governance (FR): https://infrafabric.io/fr/governance/
- Whitepaper landing: https://infrafabric.io/whitepaper/
### IF.TTT receipt surface (live example)
- Trace receipt page: https://infrafabric.io/static/trace/6qRgcR01kw_qNo63Dbs_ob9n
- Pack (MD): https://infrafabric.io/static/pack/6qRgcR01kw_qNo63Dbs_ob9n.md
- Dossier (download): https://infrafabric.io/static/dossier/6qRgcR01kw_qNo63Dbs_ob9n/download
### Offline verifier (may be blocked by some LLM fetchers)
- iftrace.py (raw): https://infrafabric.io/static/hosted/iftrace.py
- iftrace.py (HTML view): https://infrafabric.io/static/hosted/iftrace.html
### Known access trap (important)
Some sandboxed “web fetchers” can read HTML but may reject binary downloads (e.g., `.tar.gz`) with a 415/400 even when browsers/curl succeed.
For review purposes:
- Prefer `.html` wrappers when available.
- If you can’t download a bundle, review the trace receipt + markdown pack instead.
---
## Quotes Bank (Use These, Or Propose Better Ones)
These are candidate quotes to rotate beneath the typing loop (homepage).
- “Footnotes aren’t decorations. They’re load-bearing walls.”
- “If there’s no trace, it didn’t happen — or shouldn’t be trusted.”
- “We don’t claim trust. We publish receipts.”
- “Open verification is the point.”
Requirement:
- Quotes must be forwardable (boardroom-safe).
- No vendor bashing. Target incentives, not people.
---
## What We Want From You (External Review Output)
### Response metadata (required)
Provide these at the top:
- `llm_name`: provider + model
- `probable_model`: if ambiguous
- `cutoff_date`: YYYY-MM or “unknown”
- `response_date_utc`: ISO8601 UTC
- `web_access_used`: yes/no (if yes, list URLs used)
### 1) Executive feedback (fast)
- 5–10 bullets: what works / what doesn’t
- 3 bullets: who this lands with vs who rejects it
### 2) Scorecard (0–5)
- Message clarity (black/white)
- Trust proof (artifacts > adjectives)
- Aesthetic (minimal, credible)
- CTA correctness (subtle but clear)
- Vertical relevance
- Developer path separation
### 3) Concrete edits
Propose:
- a homepage hero headline (≤12 words)
- a 1‑paragraph explainer (≤90 words)
- the vertical list for bottom-left
- `Developers | API` microcopy (bottom-right)
- 4–8 replacement quotes (if needed)
### 4) Traps to avoid
List 5–10 ways this can go wrong (marketing, legal, trust, UX).
### 5) Patch-style suggestions (preferred)
If you can, give patch suggestions as structured edits or unified diffs against a hypothetical `index.html`.
If you can’t, write precise “replace X with Y” instructions.
---
## Reminder: What IF.TTT Does (Plain English)
IF.TTT is a trace/receipt protocol:
- It binds a source artifact to an output.
- It publishes a no-login receipt surface.
- It can export offline-verifiable bundles.
This is governance people can actually verify — without requesting access to internal systems.