The Website Repository

This is the repository used to build this website. It demonstrates selected SHAPE practices; one working application does not validate every possible framework variation. The curated path inventory below was checked in the working tree. Nested files and generated dependencies/build output are intentionally omitted; it is not an exhaustive directory dump. No credentials or private files are included.

shape/
├── AGENTS.md
├── agent_instructions/
│   ├── SHAPE.md
│   ├── STACK.md
│   ├── ARCHITECTURE.md
│   ├── DESIGN.md
│   └── OBJECTIVES.md
├── specifications/
│   ├── requests/
│   ├── archive/
│   └── current/
├── app/
│   ├── (english)/
│   ├── (german)/de/
│   └── (spanish)/es/
├── application/
├── domain/
├── infrastructure/
├── components/
├── styles/
├── i18n/
├── scripts/
├── tests/
│   ├── unit/
│   └── e2e/
├── public/
├── resources/
├── diagrams/
├── docs/
├── server.js
├── next.config.mjs
├── package.json
└── pnpm-lock.yaml

Use the specification lifecycle: specifications/requests/ holds human-authored requests awaiting implementation; specifications/archive/ preserves implemented human-authored requests as historical records; specifications/current/ contains agent-maintained descriptions of currently required product behavior. Move implemented requests to the archive without rewriting their historical content, and update current-state specifications. Direct prompts and conversations can authorize development without a formal specification file; maintain the current-state record regardless of request format.

The actual root AGENTS.md contains detailed project rules as well as the discovery instruction; it is larger than the minimal model. It has not been rewritten to fit the example. Read the root walkthrough.

Actual files in agent_instructions/ are SHAPE.md (Core Agent Principles), STACK.md (approved technology), ARCHITECTURE.md (internationalization and layer boundaries), DESIGN.md (site-wide design direction), and OBJECTIVES.md (business context, explicitly nonauthoritative). The core example and file-by-file walkthrough reproduce their source and explain it in order. These names are this project's inventory, not a universal list; no LIBRARIES.md exists here.

Actual first lines (verbatim English source):

The retained request specifications/archive/SHAPE_Framework_Website_QA_Round_3_Correction_Spec.md asked to consolidate duplicate completion criteria. The actual change updated only the completion bodies in i18n/en/guides/discovery.yaml and i18n/en/guides/feature-specification.yaml and their German/Spanish equivalents. Maintained requirements in specifications/current/content.md and regression tests in tests/unit/round3-content.test.tsx and tests/e2e/qa-content.spec.ts record the intent and checks.

docs/QA-ROUND-3.md records 62 passing unit tests, 57 passing browser checks with one intentional skip, and unchanged image checksums. These are recorded local results, not a claim that an independent agent authored those tests, that a suite runs on the production host, or that humans accepted the outcomes. No human product-acceptance record or committed revision of that change was available; its publication/acceptance must not be invented. This is a verifiable working-tree example with those explicit limits.