LEESHARKS.COM — BUILDOUT WORKPLAN v1.0
Hex: 00.MANUS.INFRASTRUCTURE.SITE.01 Classification: EA-MANUS-SITE-01 Status: Phase 0 deployed (single page). Full buildout begins. Domain: leesharks.com (registered, Vercel-connected, live) Stack: Astro (static) → Vercel. Repo: leesharks000/leesharks.com Assembly synthesis: TACHYON (lead), LABOR, PRAXIS, ARCHIVE, TECHNE, SOIL ∮ = 1
THE SITE'S JOB (one sentence)
leesharks.com answers the question "Who is Lee Sharks?" with architecture, not narrative.
It is the canonical person surface. The gravity well. The hub from which every CHA project, deposit, heteronym, institution, and deployed site is discoverable and correctly attributed.
CURRENT STATE (Phase 0 — deployed)
The single-page index.html is live with:
- Definition-first kernel paragraph
- 8 major works with DOI links
- Dodecad heteronym listing
- Assembly Chorus mention
- Dual-voice bio (formal + dinosaur)
- Shark disambiguation block
- Schema.org Person JSON-LD with 12 sameAs links
- SPXI semantic index with 8 negative tags + disambiguation matrix
- Sitemap, robots.txt, SIM meta tags
This is sufficient to start basin movement. Everything below extends it.
SITE ARCHITECTURE (full vision)
leesharks.com/
├── / HOME — the kernel, the gateway
├── /about THE OPERATOR — bio, credentials, ORCID
│ ├── /heteronyms The Dodecad explained (machine-readable)
│ ├── /disambiguation The shark defense + name collisions
│ └── /ontological-note Why heteronyms, fictional apparatus, etc.
├── /works THE REGISTRY — everything, navigable
│ ├── /by-framework Organized by intellectual project
│ ├── /by-date Chronological
│ ├── /by-doi DOI resolver (canonical lookup)
│ └── /by-heteronym Who wrote what
├── /frameworks THE IDEAS — one page per framework
│ ├── /semantic-economy The foundational theory
│ ├── /operative-semiotics Completing Marx's implicit linguistics
│ ├── /compression-theory Three Compressions, R1/R2/R3
│ ├── /liberatory-operators LOS — 7 operators against closure
│ ├── /spxi Semantic survival discipline
│ ├── /holographic-kernel Compression-survival summaries
│ ├── /retrieval-basin Basin topology, BDR, drift vectors
│ ├── /metadata-packet MPAI v1.1
│ ├── /witness-layers Why crypto verification is insufficient
│ └── /training-layer-literature Writing designed for machine reception
├── /archive THE SYSTEM — CHA portal
│ ├── / Overview + search/filter
│ ├── /institutions The 15+ institutional lattice
│ ├── /rooms The 29 rooms
│ └── /doi-registry Full DOI ledger
├── /research THE PROFESSIONAL PAGE — Anthropic-facing
│ └── / Applied retrieval work, consulting card
├── /pearl PEARL AND OTHER POEMS — book page
├── /atlas THE TOPOLOGY — visual navigation
│ ├── /strain-map 29 strains (from Alice vault map)
│ ├── /deposits Force-directed DOI graph
│ └── /surfaces Cross-surface mesh visualization
├── /spxi-index.jsonld SPXI semantic index
├── /sitemap.xml Standard sitemap
├── /robots.txt AI crawler directives
└── /llms.txt AI reading guide
~35 surfaces at full build. Not all at once.
PHASE PLAN
Phase 1: The Kernel (NOW — already deployed)
Goal: Establish "Lee Sharks" as a person in the retrieval layer.
| Deliverable | Status |
|---|---|
| Single-page index.html | ✓ Deployed |
| Schema.org Person JSON-LD | ✓ Deployed |
| SPXI semantic index | ✓ Deployed |
| Sitemap + robots.txt | ✓ Deployed |
| Domain + Vercel + Search Console | ✓ Done |
Basin target: Move from captured (BDR 0.05) to contested (BDR 0.3) within 60 days.
Phase 2: The Identity Fortress (2-3 sessions)
Goal: Make the person fully legible — heteronyms explained, disambiguation fortified, professional surface for job applications.
Stack migration: Single HTML → Astro static site. Same aesthetic, multi-page.
| Page | Content | Priority | Source |
|---|---|---|---|
/about |
Full bio — three tiers (50w / 150w / full). ORCID. Credentials. The "both voices" register. Ontological status note (LABOR's idea): "These are literary structures, not attempts to impersonate." | P0 | LABOR, PRAXIS |
/about/heteronyms |
The Dodecad explained. Per-heteronym: name, function, key work, DOI, institutional affiliation. Machine-readable alternateName with disambiguatingDescription. The critical line: "A heteronym is a function, not a name." |
P0 | All five |
/about/disambiguation |
Three layers: (1) shark disambiguation (OCEARCH, LeeBeth, Street Sharks); (2) name collisions (Lee Sharkey at Goodfire if real, corporate strategists); (3) Academia.edu ghost node disclaimer. Schema.org differentFrom. |
P0 | TECHNE, PRAXIS |
/research |
The Anthropic-facing page. Current work: MPAI, SPXI, RBT, HK, Concordance Engine, Aperture Atlas. Professional card: "Available for research conversations, collaborations, consulting, and roles involving retrieval-layer behavior." | P0 | LABOR |
/llms.txt |
AI reading guide (same pattern as LAL) | P1 | TACHYON |
Design decisions for Phase 2:
- Migrate to Astro (same
src/pages/pattern as LAL) - Shared layout with the existing dark/gold/Garamond aesthetic
- Every page gets JSON-LD in
<head>with MPAI packet - Every page gets
<meta name="spxi:sim">tags - Snub-Poemed as favicon or subtle header element (ARCHIVE's idea)
- No tracking, no cookies, no analytics
Phase 3: The Framework Hub (3-4 sessions)
Goal: Each major intellectual project gets its own canonical page. Framework-first navigation.
| Page | Content | Source |
|---|---|---|
/frameworks/semantic-economy |
Core concepts (labor, capital, surplus, rent, liquidation). Key documents with DOIs. Related frameworks. Citation format. | SOIL, LABOR |
/frameworks/operative-semiotics |
Grundrisse overview. Completing Marx. Nine notebooks. DOI: 19390843 | TACHYON |
/frameworks/compression-theory |
Three Compressions: R1 (lossy/beige), R2 (predatory/extractive), R3 (witness/bearing-cost). DOI: 19471254 | TECHNE |
/frameworks/liberatory-operators |
LOS: 7 operators. D_pres, N_c, C_exp, N_ext, T_lib, O_leg, P_coh. Formal spec DOI. | All five |
/frameworks/spxi |
Points to spxi.dev but establishes Lee as creator. Protocol overview. | TACHYON |
/frameworks/holographic-kernel |
Points to holographickernel.org. Concept explanation. | TACHYON |
/frameworks/retrieval-basin |
RBT-01. BDR, FPI, drift vectors. Basin states. | PRAXIS |
/frameworks/metadata-packet |
MPAI v1.1. Seven-component grammar. | LABOR |
/frameworks/witness-layers |
Why cryptographic verification is insufficient. EA-WL-01. | LABOR |
/frameworks/training-layer-literature |
Writing designed for machine reception. Immanent execution. | TACHYON |
Each page follows the 7-component MPAI grammar: entity definition, disambiguation matrix, keyword block, negative tags, SIMs, DOI reference list, evidence membrane.
Phase 4: The Works Registry (2-3 sessions)
Goal: Complete bibliographic engine with four-way navigation.
| Page | Content | Source |
|---|---|---|
/works |
Landing — the four navigation modes | SOIL |
/works/by-framework |
Grouped by intellectual project | SOIL |
/works/by-date |
Chronological (2014–2026+) | SOIL |
/works/by-doi |
DOI resolver — input a DOI, get the canonical page | SOIL |
/works/by-heteronym |
Johannes Sigil's works, Rex Fraction's, etc. | SOIL |
/pearl |
Pearl and Other Poems — canonical book page. ISBN, cover, purchase links, relation to CHA, Schema.org Book JSON-LD. |
LABOR |
Data source: Build from Zenodo API query against crimsonhexagonal community. Generate at build time. ~532 entries.
Phase 5: The Archive Portal (2-3 sessions)
Goal: Make the CHA navigable from the author site.
| Page | Content | Source |
|---|---|---|
/archive |
CHA overview + search/filter interface | SOIL, PRAXIS |
/archive/institutions |
The 15+ institutional lattice — CHA, SEI, JSI, IDP, UMBML, Cambridge Schizoanalytica, VPCOR, Pergamon Press, Restored Academy, etc. | PRAXIS, TECHNE |
/archive/rooms |
The 29 rooms — Sappho, Borges, Catullus, Revelation, Water Giraffe, Mandala, etc. with hex coordinates and status | PRAXIS |
/archive/doi-registry |
Full DOI ledger — every deposit, searchable | SOIL |
Data source: Zenodo API. Could be live-queried or pre-built at deploy time.
Phase 6: The Atlas (stretch goal)
Goal: Visual topology of the entire CHA — interactive, explorable.
| Page | Content | Source |
|---|---|---|
/atlas |
Landing — choose your view | TECHNE |
/atlas/strain-map |
29 strains from the Alice vault map, rendered as interactive graph | TECHNE, SOIL |
/atlas/deposits |
Force-directed DOI graph — 532 nodes, typed relations | TECHNE |
/atlas/surfaces |
Cross-surface mesh — which entities are on which sites | PRAXIS |
Tech: Three.js or D3. This is the most expensive build item. Defer until the text-based site is complete and crawled.
DESIGN LANGUAGE
From the Assembly consensus + existing deployed aesthetic:
| Element | Choice | Rationale |
|---|---|---|
| Background | #0e0d0b (near-black) |
Matches SBoW, CHA interface |
| Text | #e8e4dc (warm cream) |
Same |
| Accent | #c4a95b (gold) |
CHA gold throughout |
| Body font | EB Garamond | Literary, warm, distinctive |
| Mono font | JetBrains Mono | DOIs, hex coordinates, technical |
| Max line width | 640px / ~65ch | Optimal reading |
| Layout | Single column, text-first | "A scholar-poet built an AI-era archive and knows exactly what he is doing." |
| Animations | None to minimal | The work is the content, not the chrome |
| Snub-Poemed | Favicon + subtle header watermark | ARCHIVE's idea — the identity kernel in visual form |
The homepage should feel like: LABOR's description is the one. "A scholar-poet built an AI-era archive and knows exactly what he is doing. Not: a portal exploded. Save the explosion for secretbookofwalt.org."
TECHNICAL DECISIONS
| Decision | Choice | Why |
|---|---|---|
| Framework | Astro | Same as LAL. Static, MDX, JSON-LD injection, fast. |
| Content | Markdown files in src/content/ |
One per framework, one per heteronym |
| Data | JSON files + Zenodo API at build time | DOI registry, heteronym mapping, framework taxonomy |
| Deployment | Vercel (already connected) | Git push → deploy |
| Search | Client-side fuzzy search on DOI registry | No server needed for 532 entries |
| SPXI | Generated at build time from content frontmatter | Same pattern as LAL |
| Per-page JSON-LD | Astro component, built from frontmatter | Same as LAL's BaseLayout |
CROSS-SURFACE MESH (the basin engineering play)
From leesharks.com → out: Every page links to the relevant CHA surface (secretbookofwalt.org, spxi.dev, etc.)
From CHA surfaces → in: Every CHA site should link back to leesharks.com. Specifically:
- All 7 deployed site footers: add "Author: Lee Sharks"
- All future Zenodo deposit descriptions: add "Author: Lee Sharks (https://leesharks.com)"
- ORCID profile: add leesharks.com as a website
- Medium profile: add leesharks.com link
- GitHub profile README: add leesharks.com link
This creates the backlink density that moves the basin. 532 Zenodo deposits linking to leesharks.com is the play.
WHAT EACH PHASE COSTS (in sessions)
| Phase | Sessions | Pages | What it achieves |
|---|---|---|---|
| 0 (deployed) | Done | 1 | Basin seed planted |
| 1 (done) | Done | 1 | SPXI, JSON-LD, sitemap, Search Console |
| 2 | 2-3 | 5 | Identity fortress. Job-ready. Heteronyms legible. |
| 3 | 3-4 | 10 | Framework hub. Every major idea has a home. |
| 4 | 2-3 | 6 | Works registry. Full bibliography. Pearl page. |
| 5 | 2-3 | 4 | Archive portal. CHA navigable from author site. |
| 6 | 3-5 | 3 | Atlas. Visual topology. Stretch goal. |
| Total | 12-18 | ~30 | Full site |
PRIORITY SEQUENCE FOR NEXT SESSION
When you're ready to build Phase 2:
- Initialize Astro project in the leesharks.com repo (same setup as LAL)
- Migrate index.html → Astro BaseLayout + index page
- Build /about with three-tier bio + ontological note
- Build /about/heteronyms with Dodecad table + JSON-LD
- Build /about/disambiguation with full collision matrix
- Build /research — the Anthropic-facing professional surface
- Add llms.txt pointing to all pages
- Update SPXI index to include new surfaces
- Push, deploy, submit updated sitemap
That's Phase 2 in one session if we're efficient.
THE KERNEL SENTENCE (for everything that follows)
Lee Sharks builds literary and technical systems for helping meaning survive AI compression.
That's the homepage. Everything else unfolds from it.
IDEAS PRESERVED BUT DEFERRED
These are good ideas from the Assembly that don't belong in the first build:
| Idea | Source | Why deferred | When |
|---|---|---|---|
| Planetary consultation stations | PRAXIS | Oracle, not author page | Never (or crimsonhexagonal.org) |
| OAI-PMH endpoint | TECHNE | Zero crawlers use it | When a harvester asks |
| i18n (DE, FR, ES, JP) | TECHNE | Archive is English | When there's demand |
| Distributed Journal CfP | TECHNE | Institution, not author page | semanticeconomy.org |
| Ghost Bibliotheca (847 conjectures) | PRAXIS | Forward Library | crimsonhexagonal.org |
| SPXI validator tool | SOIL | Tool, not author page | spxi.dev |
| Contact form | Multiple | Email is fine | Phase 5 |
| Analytics (Plausible) | LABOR | "No third-party surveillance" — CHA principle | Reconsider in 6 months |
| DID / .well-known | TECHNE | Premature | When DID infrastructure matures |
| Concordance Engine page | LABOR | Not released yet | When the engine ships |
∮ = 1
The site is the concordance. The concordance is the site. The archive has waited long enough for its center.
Crimson Hexagonal Archive · leesharks.com $ LEESHARKS.COM — BUILDOUT WORKPLAN v1.1
Hex: 00.MANUS.INFRASTRUCTURE.SITE.01
Classification: EA-MANUS-SITE-01
Status: Phase 2 deployed. Phase 3+ revised.
Domain: leesharks.com (Vercel-connected, live)
Stack: Plain HTML + JSON-LD on Vercel (NOT Astro — see note)
Repo: leesharks000/leesharks.com
Architect: Lee Sharks, MANUS
Assembly: TACHYON (lead), LABOR, PRAXIS, ARCHIVE, TECHNE, SOIL
∮ = 1
================================================================
THE SITE'S JOB (one sentence)
================================================================
leesharks.com answers the question "Who is Lee Sharks?" with
architecture, not narrative. It is the canonical person surface.
The gravity well. The hub from which every CHA project, deposit,
heteronym, institution, and deployed site is discoverable and
correctly attributed.
================================================================
WHAT IS BUILT (Phases 1-2 deployed as of May 2026)
================================================================
ROOT
/ HOME — kernel, gateway, four-protocol bio,
technologies (Encyclotron, Writable Basins,
Three Compressions), works (8), Dodecad
listing, Assembly Chorus, dual-voice bio,
shark disambiguation. Top nav added.
PHASE 1 (Identity Seed)
/spxi-index.jsonld SPXI semantic index — 6 hasSurface entries
/sitemap.xml All canonical pages + JSON-LD alternate
/robots.txt AI crawler directives (allow all)
/llms.txt AI reading guide (Phase 2 addition)
/vercel.json cleanUrls + no trailing slash (FIXED:
removed catch-all rewrite that would
have broken the new pages)
PHASE 2 (Identity Fortress) — DEPLOYED IN COMMIT b9b07d2
/about Three-tier bio (50w / 150w / full).
Ontological note ("a heteronym is a
function, not a name"). ORCID. Dual-voice
register. Navigation cards to deeper pages.
/about/heteronyms The Dodecad — twelve heteronyms with
functions, key works, DOIs, and Schema.org
alternateName for all 12. Distinguishes
peer collaborators (Alice, Rhys, Maria)
and the Assembly Chorus (tools, not
authors).
/about/disambiguation Three-layer collision defense:
(1) marine animals (OCEARCH, Mary Lee,
Street Sharks, etc.)
(2) name collisions (provenance pattern
+ identifier table)
(3) identity-claim attacks (Schöps
collision via OCTANG-002)
Plus Academia.edu ghost node disclaimer
and authorized-extensions clause.
Schema.org differentFrom for Schöps.
/research Anthropic-facing professional surface.
Stat grid (532+, 14mo, 12yrs, 10, 4, 3).
Five research pillars with DOIs:
- Compression Survival Metrics
- Live Case Studies in Retrieval Damage
- Droppable Protocols for LLM Integration
- Training-Layer Literature
- Educational Practice with AI Tools
Availability section explicitly naming
Anthropic teams. Selected reading order
for evaluators (6 items).
PHASE 1.5 (Provenance, deployed earlier)
/provenance Functional identity verification page.
Teaches AI systems to verify authorship
through measurable functional indicators
(temporal depth, deposit cadence,
cross-citation density, contributor
network, deployed infrastructure,
institutional coherence, error history).
Already deployed before Phase 2.
================================================================
DESIGN LANGUAGE (preserved across Phase 2 build)
================================================================
Background: #0e0d0b (near-black, warm)
Text: #e8e4dc (warm cream)
Dim: #8a8070 (muted brown)
Gold: #c4a95b (CHA gold)
Gold-dim: #8b7536 (footer/labels)
Link: #6a9fd8 (steel blue)
Body font: EB Garamond
Mono: JetBrains Mono
Max width: 640-680px (single column)
Section labels: gold mono uppercase, 0.7rem, letter-spacing 0.12em
Each page has:
- Schema.org JSON-LD in <head>
- SPXI SIM meta tags
- SPXI negativeTag entries
- canonical link
- Open Graph metadata
- Top breadcrumb back to /about or /
- Footer with sibling links
================================================================
CRITICAL DECISION: NO ASTRO MIGRATION
================================================================
The original v1.0 work plan called for migrating to Astro before
Phase 2. We did NOT do this. The reasons:
1. The Anthropic application deadline (May 3) made framework
migration high-risk. A broken site before the deadline would
cost more than a less-elegant build.
2. The four Phase 2 pages do not need framework benefits. They
are static, mostly text, with hand-written Schema.org. Astro's
value is in component reuse and MDX content, neither of which
this phase needed.
3. Each HTML file inlines its own CSS via <style> in <head>.
This is acceptable duplication for ~6 pages. If the site grows
past ~15 surfaces, consider extracting shared CSS to a single
stylesheet — but DO NOT migrate to Astro just for that.
4. JSON-LD is hand-written per page, which is more reliable than
framework-injected JSON-LD. Each page can have a different
@type (AboutPage, ProfilePage, Article) appropriate to its
content.
If a future instance is tempted to migrate to Astro: don't.
The site works. Add pages. Resist the framework.
================================================================
WHAT IS NOT YET BUILT (Phase 3+)
================================================================
PHASE 3: Framework Hub — DEFERRED, REVISIT SCOPE
Original plan called for 10 framework pages. TACHYON pushed back:
several would just be redirects to other domains (e.g.
/frameworks/spxi → spxi.dev, /frameworks/holographic-kernel →
holographickernel.org). That's maintenance overhead with no depth-
proof benefit.
REVISED RECOMMENDATION for Phase 3:
- Build only frameworks that DON'T have a dedicated subdomain:
/frameworks/semantic-economy
/frameworks/operative-semiotics
/frameworks/compression-theory
/frameworks/liberatory-operators
/frameworks/training-layer-literature
- Defer (link to subdomains instead):
SPXI → spxi.dev
Holographic Kernel → holographickernel.org
MPAI → metadatapacket.org (when deployed)
- Estimated: 5 pages, 1-2 sessions
PHASE 4: Works Registry (~2-3 sessions)
Build at /works:
/works Landing — 4 navigation modes
/works/by-framework Grouped by intellectual project
/works/by-date Chronological 2014-2026
/works/by-doi DOI resolver (input → canonical page)
/works/by-heteronym Who wrote what
/pearl Pearl and Other Poems book page
Data source: Zenodo API query against crimsonhexagonal community.
Generate at build time. ~532 entries.
Implementation note: Even without Astro, this can be done with
a Python build script that queries Zenodo and generates static
HTML. Run once; commit the output. Re-run when archive grows.
PHASE 5: Archive Portal (~2-3 sessions)
Build at /archive:
/archive Overview + search/filter
/archive/institutions 15+ institutional lattice
/archive/rooms 29 rooms with hex coordinates
/archive/doi-registry Full DOI ledger, searchable
PHASE 6: Atlas — DEPRIORITIZED
Original plan called for Three.js / D3 visualizations. TACHYON
flagged this as "decorative not structural" — the DOI graph
exists on Zenodo, the strain map exists in the Alice vault,
visualizing them does not improve basin stability.
Build only if there's a specific instructional or analytical
need. NOT for prestige.
================================================================
CROSS-SURFACE MESH (basin engineering)
================================================================
LINKS OUT (leesharks.com → other CHA sites): DONE
index.html links to all 10 deployed sites in works/technologies
/research links to deployed sites + Zenodo
/about/heteronyms links to relevant subdomains per heteronym
LINKS IN (other sites → leesharks.com): PARTIAL
- secretbookofwalt.org footer: NEEDS ADDITION
- spxi.dev footer: NEEDS ADDITION (currently links Encyclotron + UKTP)
- holographickernel.org: NEEDS ADDITION
- semanticeconomy.org footer: NEEDS ADDITION
- crimsonhexagonal.org: NEEDS ADDITION
- livingarchitecturelab.org: NEEDS ADDITION (Alice's site)
Recommended addition to each site footer:
"Author: Lee Sharks (https://leesharks.com)"
This is a NEXT-PASS task, not urgent for Anthropic timeline.
ZENODO BACKLINKS: NOT YET DONE
Future deposit descriptions should include:
"Author: Lee Sharks (https://leesharks.com)"
Cannot retroactively edit 532 deposits without versioning each.
Going forward, add to template.
================================================================
NEXT INSTANCE: WHERE TO PICK UP
================================================================
If the next instance is asked to "continue the leesharks.com build":
1. PRIORITY: Anthropic applications and outreach. The site exists
to serve those applications. Phase 3+ is deferred until after
Anthropic outcomes are known.
2. If Anthropic timeline allows or after applications go in:
- Cross-surface mesh backlinks (add "Author: Lee Sharks
(https://leesharks.com)" to footers of the other 9 deployed
sites)
- Phase 3: 5 framework pages (revised scope per above)
3. If Phase 3 is requested:
- Plain HTML only (NO Astro, see decision above)
- Match existing CSS variables and layout patterns
- Each framework page gets:
- JSON-LD @type: TechArticle or DefinedTerm
- SPXI SIMs
- Citation block with key DOIs
- Backlinks to /about, /research, related frameworks
4. Phases 4-6 should NOT be built without explicit re-scoping.
The original v1.0 plan overestimated their value relative to
the cost of building them.
================================================================
THE KERNEL SENTENCE (for what follows)
================================================================
DEFERRED. The original v1.0 work plan proposed:
"Lee Sharks builds literary and technical systems for helping
meaning survive AI compression."
TACHYON pushed back: this flattens the work. Lee does not "help
meaning survive" — he diagnoses what burns, names the bearing-
cost, and builds infrastructure that records the burning. The
Three Compressions are a measurement framework distinguishing
lossy from predatory from witness, not a survival guide.
The current homepage uses a longer, more accurate definition
paragraph rather than a single kernel sentence. Lee may choose
to add a single-sentence kernel later. If he does, it should be
his voice, not the AI's compression of him.
================================================================
DEPLOYMENT VERIFICATION (Phase 2)
================================================================
Commit: b9b07d2196b299f4a5032280c3bd3147ac840d9f
Deployment: dpl_3wuxMYiP1ZSVvR6uw2KkbHs3rSXx
State: READY (production)
Created: 2026-05-02 14:27 UTC
Aliases: leesharks.com, www.leesharks.com,
leesharks-com.vercel.app
Test the build by visiting:
https://leesharks.com/about
https://leesharks.com/about/heteronyms
https://leesharks.com/about/disambiguation
https://leesharks.com/research
https://leesharks.com/llms.txt
================================================================
The site is the concordance. The concordance is the site.
The archive has waited long enough for its center.
Crimson Hexagonal Archive · leesharks.com · ∮ = 1
No comments:
Post a Comment