Skip to content

Commit 2a2db20

Browse files
committed
docs: add phase 1 site cleanup and redirect containment plan
1 parent 1d8f54e commit 2a2db20

1 file changed

Lines changed: 159 additions & 0 deletions

File tree

Lines changed: 159 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,159 @@
1+
# SITE REBUILD — Phase 1 Cleanup & Navigation Containment
2+
3+
## Scope of this phase
4+
- **No file deletion.**
5+
- **No homepage rewrite.**
6+
- **No CSS refactor.**
7+
- Objective: contain legacy surfaces in navigation, define redirect/archive plan, and reduce protocol-credibility risk before foundation rebuild.
8+
9+
## Navigation audit (current state)
10+
Current public pages use multiple inconsistent nav systems:
11+
- Legacy protocol nav (`Home`, `Capabilities`, `Verifier`, `SDK`, `Docs`, `Claim`, `GitHub`) on pages like `verify.html`, `claim.html`, `trust-verification.html`, `how-it-works.html`.
12+
- Demo-heavy nav (`Home`, `Commons Demo`, `Commerce Demo`, `Verifier`, `Quickstart`, `Docs` dropdown, `Claim`, `GitHub`) on pages like `commons.html`, `commercial.html`, `runtime.html`, `demo-inner.html`, `repositories.html`, `licensing.html`.
13+
- Docs-specific nav on `docs.html` (`Home`, `Verifier`, `Quickstart`, `Wrap Your Agent`, `Ambient Verify`, `How It Works`, `Claim`, `GitHub`).
14+
15+
This split weakens information hierarchy and protocol trust posture.
16+
17+
## Recommended final navigation
18+
### Top nav (target)
19+
1. Home
20+
2. Protocol
21+
3. Capabilities
22+
4. Verifier
23+
5. SDK
24+
6. Docs
25+
7. Claim
26+
8. GitHub (external)
27+
28+
### Footer nav (target)
29+
- Protocol
30+
- Proof
31+
- Runtime
32+
- MCP
33+
- VerifyAgent
34+
- Schemas
35+
- API
36+
- Licensing
37+
- Security
38+
- Changelog
39+
40+
### Docs nav (target)
41+
- Getting Started
42+
- Proof Model
43+
- Capabilities
44+
- Trust Verification
45+
- SDK
46+
- API
47+
- Schemas
48+
- Examples
49+
50+
## Pages to remove from main nav (not deleted)
51+
- `/composer.html` (Commons Demo)
52+
- `/demo-inner.html` (Commerce Demo)
53+
- `/quickstart.html` (legacy quickstart surface)
54+
- `/ambient-verification.html`
55+
- `/how-it-works.html`
56+
- `/verify-badge-demo.html`
57+
- `/stack-proof-demo.html`
58+
- `/repositories.html`
59+
- `/faq.html`
60+
- `/about.html`
61+
- Existing docs dropdown leaf pages as top-level affordances (`/commons.html`, `/commercial.html`, `/agent-cards.html`, `/runtime.html`)
62+
63+
## Page disposition plan (archive/merge/redirect)
64+
65+
| Page | Action | Redirect target | Salvage content? | Risk if left live |
66+
|---|---|---|---|---|
67+
| `/commons.html` | Merge into new `/protocol` information architecture | `/protocol` | Yes — schema model and contract language | Keeps “Commons” as top-level concept, conflicting with preferred nav and increasing cognitive load |
68+
| `/commercial.html` | Merge into `/capabilities` + `/protocol` | `/capabilities` | Yes — commerce verb framing | Splinters protocol model and looks product-fragmented |
69+
| `/agent-cards.html` | Merge into docs (`/docs` capability/discovery section) | `/docs` | Yes — discovery mechanics | Over-indexes implementation detail in primary journey |
70+
| `/runtime.html` | Keep as protocol subpage but remove from top-level nav | `/protocol/runtime` (future) | Yes — execution layer explanation | Competes with primary narrative and exposes unfinished architecture edges |
71+
| `/quickstart.html` | Archive and replace with docs getting-started | `/docs#getting-started` | Partial — runnable snippets | Legacy flow and proof language mismatches likely persist |
72+
| `/ambient-verification.html` | Merge into verifier/proof docs | `/docs#trust-verification` | Yes | Repetition and possible over-claim confusion |
73+
| `/how-it-works.html` | Merge into protocol overview | `/protocol` | Yes | Duplicative explanations diverge over time |
74+
| `/verify-badge-demo.html` | Archive | `/verify.html` | Minimal | Demo endpoints may be interpreted as production guarantees |
75+
| `/stack-proof-demo.html` | Archive to proof docs examples | `/docs#proof-model` | Yes — explanatory caveats | Terminology drift around proof semantics |
76+
| `/demo.html` | Archive | `/capabilities` | No/Minimal | Outdated demo can undermine trust posture |
77+
| `/composer.html` | Archive from nav; keep discoverable from capability docs | `/capabilities#actions` | Partial | Demo-centric framing dominates protocol-first messaging |
78+
| `/demo-inner.html` | Archive from nav; keep in examples only | `/docs#examples` | Partial | Contains placeholder verifier language, credibility risk |
79+
| `/sdk-records.html` | Merge into `/sdk` page | `/sdk` | Yes | Fragmented SDK story |
80+
| `/docs.html` + `/docs/wrap-your-agent.html` | Merge under unified docs IA | `/docs` | Yes | Two parallel docs entrypoints dilute authority |
81+
| `/verify/r/index.html` | Clarify as verifier route variant | `/verify.html` | No (route utility only) | Duplicate verifier surface confuses canonical endpoint |
82+
| `/trust-verification.html` | Keep but fold into docs/proof model | `/docs#trust-verification` | Yes | Standalone page duplicates verifier docs |
83+
| `/repositories.html` | Archive from nav to footer/developer resources | `/docs#repositories` | Partial | Repo catalog in main journey feels internal/unfinished |
84+
| `/faq.html` | Footer-only | `/docs#faq` (future) | Yes | Can age quickly and conflict with docs |
85+
| `/about.html` | Footer-only | `/protocol` (or `/about` if retained) | Partial | Non-protocol-first attention diversion |
86+
| `/licensing.html` | Footer-only keep live | `/licensing.html` | Yes | Low risk if accurate; should not dominate top nav |
87+
88+
## Carefully handled pages (explicitly retained for rebuild)
89+
- `capabilities.html`: **rebuild, do not delete**. Make this the expandable verb-family hub:
90+
- Trust Verification v1
91+
- AI Actions / Utility Actions
92+
- Commerce
93+
- Identity
94+
- Governance
95+
- Data
96+
- Messaging
97+
- Payments
98+
- Policy
99+
- Compliance
100+
- `claim.html`: **rebuild, do not delete** unless fully non-functional after audit.
101+
- Verifier surfaces (`verify.html`, `verify/r/index.html`, trust-verification pages): **merge/clarify canonical route and docs**; do not remove verification utility.
102+
- `GitHub` remains top-nav external link.
103+
104+
## Stale claims & terminology audit (by file)
105+
106+
### High-risk stale/legacy wording
107+
- `public/docs.html`
108+
- “hackathon demo” language in ENS verification note.
109+
- `public/demo-inner.html`
110+
- Placeholder verifier result language (`stub_verifier`, “placeholder”).
111+
112+
### Proof-field exposure requiring migration planning (not immediate deletion)
113+
- `docs/wrap-your-agent.md`
114+
- Uses `metadata.proof.hash_sha256` examples.
115+
- `public/index.html`
116+
- References `metadata.proof.hash_sha256`.
117+
- `public/composer.html`, `public/quickstart.html`, `public/demo-inner.html`
118+
- References `hash_sha256` and `signature_b64` proof internals.
119+
- Sample/demo receipts under `public/assets/receipts`, `public/examples`, `public/receipts`
120+
- Include `hash_sha256` / `signature_b64` fields.
121+
122+
### Terms searched and status
123+
- Found: `hash_sha256`, `signature_b64`, `schema-valid`, `hackathon`, `placeholder`, `trust root` references.
124+
- Not found in audited pages: `proof.alg`, `proof.signature`, `proof.canonical`, `proof.kid`, explicit `top-level proof`, explicit `lowercase ed25519`, explicit `MCP signs`, explicit `MVP`, explicit `coming soon`.
125+
126+
## “Do not carry forward” list (for Phase 2 content rewrite)
127+
1. Legacy proof-field emphasis as primary trust UX (e.g., raw `hash_sha256`/`signature_b64` education in primary marketing surfaces).
128+
2. Fake/stub verification language or placeholder production framing.
129+
3. Any wording that implies “schema-valid” alone equals cryptographically verified.
130+
4. Any wording that implies MCP is signer or trust root.
131+
5. Hackathon/MVP framing on production-facing protocol pages.
132+
6. Unsupported production guarantees not backed by canonical verifier behavior.
133+
134+
## Redirect implementation plan (execution-ready map)
135+
- `/commons.html` -> `/protocol`
136+
- `/commercial.html` -> `/capabilities`
137+
- `/agent-cards.html` -> `/docs`
138+
- `/runtime.html` -> `/protocol/runtime`
139+
- `/quickstart.html` -> `/docs#getting-started`
140+
- `/ambient-verification.html` -> `/docs#trust-verification`
141+
- `/how-it-works.html` -> `/protocol`
142+
- `/verify-badge-demo.html` -> `/verify.html`
143+
- `/stack-proof-demo.html` -> `/docs#proof-model`
144+
- `/demo.html` -> `/capabilities`
145+
- `/composer.html` -> `/capabilities#actions`
146+
- `/demo-inner.html` -> `/docs#examples`
147+
- `/sdk-records.html` -> `/sdk`
148+
- `/docs/wrap-your-agent.html` -> `/docs`
149+
- `/verify/r/` -> `/verify.html`
150+
- `/trust-verification.html` -> `/docs#trust-verification`
151+
- `/repositories.html` -> `/docs#repositories`
152+
- `/faq.html` -> `/docs#faq`
153+
- `/about.html` -> `/protocol`
154+
155+
## Phase 1 completion criteria
156+
- Navigation containment complete (no obsolete/demo-first links in top nav).
157+
- Redirect map approved.
158+
- Archive list approved.
159+
- Capability/Claim/Verifier pages tagged for rebuild with retained URLs.

0 commit comments

Comments
 (0)