Evidence 1: Public Contract Pack evidence

Website Contract Pack v2.1.0

This page documents the Website Contract Pack v2.1.0 foundation. Its sanitised examples explain generated structure, contract binding, acceptance mapping and release checks without publishing protected Contract rules. They are not a fresh customer-project test run or a deployment receipt.

How this relates to Website v2.1.1

The current Website Contract Pack is v2.1.1. The examples below document v2.1.0. Version 2.1.1 refreshes dependencies while retaining the same Website v4 contract, blueprint and supported patterns. Existing v2.1.0 projects retain their original version binding.

These excerpts remain v2.1.0 evidence and are not a v2.1.1 test report. The newer dependency set requires its own verification; the examples below do not establish its test or security results.

Packcoge.website.foundation

Contractproject-type.website v4

Patternsgeneral / showcase

Release modeslocal / private / public

01 / Generated output

A project foundation, not a prompt checklist.

The initializer creates a deterministic application foundation and binds it to the selected contract, pattern, and release mode.

Generated project structure

website-project/
|-- app/
|   |-- semantic site shell
|   |-- robots.txt/route.ts
|   |-- sitemap.xml/route.ts
|   |-- layout.tsx
|   └── page.tsx
|-- foundation verification suite
|-- scripts/
|   |-- local launch automation
|   └── protected release check
|-- protected metadata / 
|   |-- binding record
|   |-- project profile
|   |-- acceptance evidence map
|   |-- release evidence record
|   └── runtime verification record
|-- PROJECT_NOTES.md
|-- package manifest
└── deterministic dependency lock

Sanitised contract binding

{
  "schemaVersion": 2,
  "projectType": "website",
  "contractKey": "project-type.website",
  "contractVersion": 4,
  "packId": "coge.website.foundation",
  "packVersion": "2.1.0",
  "patternId": "general | showcase",
  "releaseMode": "local | private | public"
}

The real binding also pins the exact binding integrity. A mismatch stops initialization and requires an explicit Contract Pack review.

02 / Acceptance evidence

Every foundation claim points to evidence.

The generated acceptance map traces Website Contract rules to files, tests, launch records, and release checks.

Selected pattern profileprotected metadata / project profile + pattern test

Mapped

Exact contract pinprotected metadata / binding record

Mapped

Automatic local launchlocal launch automation + protected metadata / runtime verification record

Mapped

Semantic accessibility foundationfoundation verification suite

Mapped

Responsive foundationresponsive style foundation

Mapped

SEO discovery foundationRendered discovery-route evidence

Mapped

Deterministic sourcedeterministic dependency lock + production build

Mapped

Content release gatenpm run release:check

Mapped

Operations release recipeprotected metadata / release evidence record + PROJECT_NOTES.md

Mapped

03 / Test-suite excerpt

Representative assertions from the real foundation test.

This excerpt is taken from the Website v2.1.0 foundation test and shortened only for presentation.

foundation verification suiteReal excerpt

assert.equal(binding.packVersion, "2.1.0");
assert.equal(binding.contractVersion, 4);
assert.ok(["local", "private", "public"].includes(binding.releaseMode));

assert.equal(response.status, 200);
assert.match(html, /<nav\b[^>]*aria-label="Primary navigation"/i);
assert.match(html, /<main\b[^>]*id="main-content"/i);

assert.equal(robots.status, 200);
assert.equal(sitemap.status, 200);

04 / Release control

Incomplete work is blocked before release.

The release check validates the exact Contract Pack binding and scans the application and project notes for unresolved starter, asset, and decision markers.

Expected passing result

{
  "status": "ready",
  "contract": "pinned",
  "blockingIssues": []
}

Any binding mismatch or unresolved marker changes the result to blocked and returns a failing process status.

Local

Runs on the user's machine and does not publish.

Private

Publishes with private visibility after the release check passes.

Public

Requires explicit confirmation and a passing release check before publication.

Version evidence

What Website v2 added

Selectable general and showcase patterns
Explicit local, private, and public release modes
Capability-based foundation tests
Automatic local-port discovery

What this evidence does and does not establish

Transparent mechanics. Protected engineering.

It demonstrates that Website v2.1.0 generates maintained artefacts, maps acceptance evidence, measures rendered composition, executes foundation tests, and blocks incomplete releases.

It does not publish CogentSpec’s protected Contract rules, certify a customer project, or establish end-to-end release evidence for every project-type direction.

Explore the CogentSpec workspace

Evidence 2 · Editable contract baseline

The specification is a real decision system.

This read-only extract shows how Website requirements are made explicit before a build begins. Required protections cannot be removed; selected capabilities and delivery decisions change the approved project baseline.

Editable contract baseline

Configure Website Contract

Start from Website defaults and make the build obligations explicit.

Public evidence · Read only

Inherited

Shared Web Foundation

These protections apply to Website and Web Application projects and cannot be removed.

8 required

Responsive browser interfaceRequired
AccessibilityRequired
Navigation and routingRequired
Browser compatibilityRequired
PerformanceRequired
Security controlsRequired
Deployment and deliveryRequired
Acceptance evidenceRequired

Selectable capabilities

Product and content

Content management
Editors can create and update managed content.
Backend administration
Provide an administrative management surface.
Payments & checkout
Provider-hosted card handling, verified webhooks, refunds, and protected transaction administration.
AI & Search discoverability
Crawlable HTML, stable URLs, sitemaps, canonical links, structured data, attribution, and dates.

Selectable capabilities

Data and platform

Persistent database
Model, migrate, store, and protect durable application data.
Backend API
Provide validated server endpoints and business logic.
Automated functional testing
Verify key journeys and regressions automatically.

Delivery defaults

Decisions

Content model: Static pages / CMS managed
Primary access: Public / Signed-in users
Administration: None / Single administrator / Role based
Hosting target: Managed hosting / Self-hosted
AI training access: Do not allow / Allow

Originality safeguard. References guide function and visual direction only. Protected branding, text, images, source code, and distinctive design assets must not be copied.

What this proves

The baseline demonstrates the depth of CogentSpec’s requirements and decision layer. The generated binding, validation routines, test output, and release evidence elsewhere on this page demonstrate how that specification is carried into delivery.