Pinega Web IA Foundation: Master Brand and Programme Boundaries - #21
Merged
Conversation
likern
marked this pull request as ready for review
August 7, 2026 12:01
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements Gate 1 from the accepted
docs/web-content-audit.mdwithout adding a blog, full-text search, paper viewer, Typst HTML pipeline, or new scientific diagrams.The site now presents Pinega as the umbrella database-systems research and engineering programme, Pinega Labs as its working research/engineering and future company identity, and Pinega Engine as the first active implementation programme beneath that master brand.
The working brand line is:
Public information architecture
Primary navigation becomes:
The Blog destination is deliberately deferred until a real blog route and content pipeline exist.
Content contract
Adds a versioned registry under
web/content/for:Native HTML remains the durable body source. The build validates registry/page agreement and derives routes, sitemap entries, and the metadata-rich
site-manifest.jsonfrom this one contract.Content changes
Validation
Final head:
48a7f1d178526ab60154143fd37b9342ad3083e7All applicable final-head gates pass:
31175921576;31175921494.The website gate covers:
The diagram gate confirms that the unchanged shared models and accepted layouts still build and render through Web SVG and Typst/CeTZ.
The final website artifact was downloaded and its
SHA256SUMS.txtmanifest verifies successfully.Review artifacts
Website
Workflow run:
31175921576Artifact:
pinega-website-v0.2-pull_request8992901783;sha256:c03a29fc7fa005c378aa755b5b75937f6ab7e71de70a1a4491ce2b4a936c6e53.Primary review surfaces:
dist/index.html;dist/technology/index.html;dist/research/index.html;dist/docs/index.html;dist/docs/getting-started/index.html;dist/about/index.html;tests/visual/site.visual.spec.ts-snapshots/.Shared diagrams
Workflow run:
31175921494Artifact:
scientific-diagrams-pr-21-48a7f1d17852-attempt-18992823688;sha256:34936b579b2b221589dce357dc1e36f8ca8c22d23e01b14e3a365435ca6b5573.Explicit non-goals
The next milestone after merge is Documentation Reorganisation and Review.