New footwear, a curated archive, and a manufacturing practice. Each has its own audience and purpose; material knowledge connects all three.
The original site plan gives each business a complete, independent visitor experience. The domains below are recommendations in that plan; ownership and deployment were not checked.
New luxury footwear, including made-to-order pieces. The focus is the product, its material story and the studio that makes it.
piu.comVintage and deadstock fashion, jewellery, accessories and PIU Maison objects. Stylist services extend the collection into a service.
archive.piu.comManufacturing consultancy for other brands, connecting projects with factories, artisans and sourcing expertise.
corpusproduction.comShared founder and material expertise; two consumer experiences and one business service. These are the roles described by the source plan. [1]
The public links explain the relationship in context. Behind the scenes, the proposed model shares selected services while keeping the B2B enquiry journey separate.
New products and orders
↔ Archive discovery
← Corpus production provenance
Resale and stylist requests
↔ Brand discovery
→ Corpus production enquiries
Enquiries and projects
→ PIU manufacturing case study
← Archive material expertise
Footer and About introduce vintage, deadstock and Nadia’s curatorial practice.
Footer and About explain the manufacturing consultancy and factory network behind PIU.
Banner or footer introduces new PIU footwear; the plan proposes one consumer login across both.
Stylist Services directs production enquiries to Corpus; sourcing stories provide another contextual link.
Projects features PIU as the founder’s own manufacturing case study.
About uses the Archive to demonstrate material and cultural knowledge.
Navigation principle: a visitor can complete their task within one site. Cross-links offer useful context without requiring a tour of all three. [1]
The architecture describes data and intended workflows. It does not establish deployed authentication, checkout, payments or database constraints.
PIU products carry materials and images. Orders track fulfilment. Archive listings carry resale details, categories and wishlists; shared payments name both consumer sites.
Pending → Confirmed → In production → Shipped → Delivered
Corpus enquiries can convert into projects. Factories, artisans, shipments and permit records support the production knowledge behind those projects.
New → Responded → Converted or Closed
| Area | Tables / responsibility |
|---|---|
| Brand · 7 | Products, materials, images, orders, collections, journal posts, studio enquiries. |
| Archive · 7 | Listings, listing details, categories, stylist requests, collections, press, wishlists. |
| Corpus · 7 | Projects, factories, enquiries, journal posts, artisan contacts, permits, shipments. |
| Shared · 4 | Users, addresses, payments, newsletter subscribers. |
The important data links: factories underpin product provenance; consumer identity connects orders and wishlists; material references point toward permit paperwork; subscribers record where they came from. These are relationship concepts in the diagram. The permit reference is a text field, and newsletter attribution is not a foreign key. [2]
Use the original design documents as the evidence base. The brief adopts PIU’s monochrome discipline while making the typography and spacing readable on a phone.
Stark. Minimal. Architectural.
Black ink, white ground and grey metadata. The red square belongs only to the loader in the reference; it is not a general brand accent. Photography is specified in greyscale.
Neutral sans-serif, wide-tracked uppercase display and mono labels. One-pixel black rules, square buttons, no shadows. Hover inverts black and white.
Source spacing: 120px desktop gutters, 26px product gaps, 30/70/90/100px vertical rhythm. POS / RSM / RSMI fonts are requested but absent; this brief uses system fallbacks. [3]
A catalogue and typewriter voice: Courier-style mono, an Archivo masthead, hairline organisation and product-led grids. The source shows warm paper, dark ink and white cards.
Wireframe values: #F2F1EF / #121212 / #6E6E6E. Grid expands from two to three to four columns. These document a direction, not finished art. [4]
Oversized Bodoni-style editorial type with restrained sans-serif and mono support. Projects, people and making should supply the substance.
The original spec explicitly leaves colour and copy uncommitted. Purple marks an unresolved backing graphic, not an approved brand colour. The serif here is a system-font specimen. [5]
Recommended shared foundation: common spacing, navigation behaviour, accessibility and component mechanics, with separate typography and art direction for each business. Generated companion palette and typography notes contain guesses; they should not overrule these original references.
The folder has two layers: original material in WEB_DEVELOPMENT_, and the generated WEB_DEVELOPMENT_VAULT companion that explains and cross-references it.
Master catalogue → Original reference → Companion explanation → Relationship index → Build decision
Artwork and image variants, numbered 101–115; visual material for interpretation.
PIU, Archive, Corpus and backend layouts; the principal visual handoff.
The site/link map and database design; the structural starting point.
Packaged reference decks, exported views and extracted files; derivatives of the same work.
Nostra and HealthGoth evaluation material and licence records; not a confirmed final font system.
A type experiment, Corpus logo image and PIU web frame graphic.
PDF, colour and thumbnail scripts, additional to the 33 catalogue assets.
The raw folder contains 36 files. The companion’s 88 claimed edges connect documents, layouts and notes; they do not prove 88 runtime integrations. The five layout bundles expand into 79 indexed files, not separate projects. [6] [7] [12]
The Nadia companion already provides project-specific reading context. Galaxy Core is the wider durable knowledge home; a verified Nadia registration was not located there.
Original designs and architecture are catalogued by the local WEB_DEVELOPMENT_VAULT companion. This brief draws from both, with original sources taking precedence. [6] [8]
Add a Nadia / PIU entry note that points to the existing folders and this brief. Keep heavy source files in place. No registration, move or new vault was performed for this brief. [9] [10]
Glossosphere supplies language and navigation across the vault. SOLARIS and xyz / TecPac are separate sibling projects; no Nadia product or runtime dependency on them was found. [9]
Glossosphere integration is unverified. The companion claims a browser-game connection, while the canonical game record reports its historical source unavailable. A locally served folder does not establish that a game consumes its notes. Keep the vault hub, historical game and separate semantic application distinct. [8] [11]
Reviewed on 7 September 2026 using two Astra agents at medium reasoning: one for Nadia’s source corpus and one for Galaxy relationships. Searches across 8,033 visible Galaxy Markdown paths found no relevant Nadia, PIU or Corpus Production entry. An unrelated Graphify name match was rejected.
The working source is the OneDrive Desktop/Nadia copy. Another Desktop copy has matching raw assets but a different compiled companion. PDF descriptions use existing extraction notes, not a fresh visual review of every print. Live domains, authentication, payments and the game bridge were not tested.
The references are sufficient to describe the vision. These decisions turn that vision into an implementable brief.
Specify Archive orders and fulfilment; the shared payment model names Archive but no Archive order table is shown. [2]
Numbered references above lead here. Local file links require the original Nadia folder and Galaxy vault on this computer. The brief itself works offline and can be shared as one HTML file.
Original source · lines 66–183. Three site maps, six cross-links, shared services and recommended domains.
Original source · lines 65–387. Twenty-five designed tables, lifecycle states and relationship concepts.
Reconstructed reference · lines 22–98. Monochrome system and typography; original r.css and p.js were not supplied.
Annotated wireframes · lines 13–74. Typewriter language, palette, margins and responsive product grids.
Wireframe direction · lines 10–29. Editorial serif; colour, copy and global graphic motion remain open.
Generated catalogue · lines 13–24. Thirty-three source assets; three extra Python helpers found in the raw folder.
Curated note graph · lines 162–176. Eighty-eight claimed document relationships, not application dependencies.
Generated draft · lines 19–29. Research for a future implementation pass. Some statistics and integration claims need correction.
Canonical vault map · lines 15–52. One knowledge home with multiple constellations and separate external repositories.
Canonical governance · lines 17–22. New project notes become constellations; external heavy assets can stay in place.
Canonical recorded status · lines 11–25. Historical game source reported unavailable; distinct from the semantic application.
Generated derivative index · lines 14–21. Five layout bundles and their extracted source/export material.
Some original HTML references depend on relative support files; the extracted layout bundles provide additional context if a raw reference opens incompletely. Galaxy navigation: Open GALAXY in Obsidian (requires Obsidian and the registered vault).