Sources and maintenance

This GitBook combines product documentation, application code, and the visual handoff. All documentation and interface copy are in English, translated from the French product specification where needed. Existing filenames and public URLs are retained so published links keep working.

The three sources#

Local source	Use
`doc/VIVRA-SPEC.md`	Reconstruction and translation of the 42 product specification pages, journeys, and appendices
`code`	Checking rules against the code and documenting implementation status
`vivra-frontend`	Typography, colors, gradients, corner radii, logo, and responsive behavior

cleprive.md, service configuration files, and environment variables are not included in this GitBook's content.

Editorial rules#

Specification pages retain their V1 context. New pages guide readers and clarify differences observed in the code. Open decisions remain identified as such.

Examples in the specification remain examples. No mockup ticker, fictional address, vote count, or illustrative return is presented as live data on the homepage.

Technical identifiers, API routes, schema keys, and source file paths are preserved when translating prose.

Updating a page#

Edit the corresponding file in content/. Navigation is defined in site.config.json. The build regenerates the site, search index, and content/SUMMARY.md from these sources.

npm ci
npm run build
npm run check
npm run dev

The site is served at http://localhost:4173. dist/ contains the static output and can be served independently of the application code.

Reviewing product changes#

When a rule changes, review the relevant specification, the module in packages/core, and the screens that display it. Update Implementation status, then the review date in the manifest.

GitBook checks validate generated pages, internal links, anchors, and files needed for navigation. They do not replace Vivra's product tests.