Copyright & reuse
Separate source-code licensing, project-authored content, open media/AI reuse and third-party material. Crawling permission is not copyright permission.
Read rights & reuse →PROJECT IDENTITY / OWNERSHIP / POLICY SURFACES
Say who owns what.
A mature project should make its identity, rights, naming boundaries, collaboration routes and decision model easy to inspect. These pages are Goose house requirements for a serious public project profile — not a claim that every jurisdiction or search platform requires the same pages.
CORE MATURITY SURFACES
Names & marks
Publish the canonical product name, short name, technical identity, module names, legacy names and what trademark status is — and is not — claimed.
Inspect names & marks →Partnership & collaboration
Give research, implementation, integration and commercial enquiries distinct routes. Disclose commercial relationships instead of turning them into implied independent endorsement.
Collaboration routes →Governance
Explain who can make decisions, how evidence changes recommendations, how commercial conflicts are handled and what the current project stage means.
Read governance →Security & corrections
Security reports and factual corrections are different workflows. Keep both visible and bounded.
History & status
Show how the product changed and keep current maturity explicit. A changelog is more useful than a decorative “established” badge.
Project history →Privacy & data use
The site offers optional measurement that starts only after a visitor allows it. This page explains the choice, what we try to learn and what we deliberately avoid collecting or publishing.
Privacy & data use →Media, citation & provenance
Press facts, open-media rights, citation metadata, evidence receipts and release provenance remain separate inspectable surfaces.
CONDITIONAL, NOT DECORATIVE
Do not publish policies you cannot honor.
Terms of service
Required by the Goose maturity profile only when the site actually has accounts, checkout, a paid hosted service, submissions or another contractual user workflow. The current static Goose site does not.
Status / SLA
Add a service-status or support-commitment page only when an availability or response promise exists. A static project site should not invent enterprise support language.
Accessibility statement
Accessibility is an implementation requirement. Publish a separate legal/commitment statement when an applicable duty or explicit public commitment has been established.
Financial & sponsorship disclosure
Disclose a material commercial relationship on the content or recommendation it can affect. Do not create a generic “independence” claim if the project has no evidence to support it.
Maturity is not page count. The profile asks for inspectable responsibilities. One consolidated page can satisfy several jobs when that is clearer; a site should not create thin legal-looking pages merely to resemble a large company.
MACHINE-READABLE CONTRACT
The same boundaries are available to tools.
project/profile.json declares the required semantic surfaces, conditional policies, project-reserved names and the external company route for commercial partnership. The maturity checker verifies the local files exist; it does not certify legal compliance, trademark clearance or live external endpoints.