Source contract exists
source-citedThe Radium source, repo design contract, and implementation reports exist as readable artifacts.
- State:
- source-cited

werkregisterThis proof page uses provisional examples. It does not claim final verification of the website.
Proof
02Public claims are represented with visible posture, source evidence, caveats, and missing-proof states.
Current proof examples are provisional and source-focused. They do not assert production readiness.
The public surfaces are composed from existing Radium components and public content records.
Limits
Record hardening, full accessibility testing, and visual regression coverage remain open.
The evidence path is intentionally bounded; record hardening and final quality gates are not complete.
The Radium source, repo design contract, and implementation reports exist as readable artifacts.
The first pages compose existing design-system components through the adapter layer.
This does not verify final content quality.
Visual, accessibility, interaction, and content-model checks are still future work.
Missing proof is visible by design.
Independent evidence examples from public content records.
Exports Radium components through the website-owned adapter layer. Related record: Radium design-system integration.
Documents the selected Astro, React adapter, Radium CSS, content, routing, and quality-gate strategy. Related record: architecture implementation plan.
The plan must be read with later implementation reports for actual status.
Links the architecture plan to the extracted Radium package inventory that informed integration decisions. Related record: architecture implementation plan.
Shows the single Radium CSS import and document shell used by public routes. Related record: azwerks portfolio foundation.
Lists existing design-system components and their intended usage boundaries. Related record: Radium design-system integration.
The manifest is source material; website integration still requires local adapters.
Defines schemas for records, evidence, operations, decisions, relations, matters, notes, and docs. Related record: public content model.
Documents the content collection architecture, public helpers, validation behavior, and page integration. Related record: public content model.
Search and feed integration are documented as deferred work.
Shows the local site CSS entry that imports the vendor Radium stylesheet once. Related record: azwerks portfolio foundation.
This proves import strategy, not visual regression coverage.
Documents the Astro, React, Radium import, adapter strategy, and smoke route verification. Related record: azwerks portfolio foundation.
The report covers foundation behavior, not final surface quality.
Read docs surfaceDocuments implemented public routes, component usage, initial data, and caveats. Related record: werkregister surface composition.
Shows the public gateway composition using public records, evidence counts, route entries, and Radium components. Related record: werkregister surface composition.
Each hardening release cites the audit that produced it — visual regression, commands/actions safety, project-root safety — with a dated patch-notes document under docs/. Related record: azwerks-nvim.
A dedicated health module checks Neovim version, Git, ripgrep, fd, Node/npm, Python, the vendored Radium colorscheme, Treesitter posture, the Markdown render guard, and project-profile registration. Related record: azwerks-nvim.
Broad-root archive and scan operations are refused by default; write and external-script tasks require confirmation with the working directory shown. Documented in the safe-workflows baseline. Related record: azwerks-nvim.
Safety is enforced at runtime through the shared safety layer, not by an external test suite.
Dossier summarizing project purpose, contents, stage, evidence, public-safety concerns, caveats, and open questions. Related record: azwerks-nvim.
The dossier is intake evidence; publication approval is recorded separately.
Scanner report documents authorized roots, commands run, public-safety findings, and the intake-time publication boundary. Related record: azwerks-nvim.
The report records intake behavior only; verification commands for the external project were not run.
Dossier summarizing the Obsidian theme suite, snippets, design specs, public-safety concerns, caveats, and open questions. Related record: azwerks obsidian themes.
The dossier is intake evidence; publication approval is recorded separately.
Scan index lists the authorized root, public-readiness status, evidence confidence, suggested classification, and proof posture. Related record: azwerks obsidian themes.
The scan index records intake posture; publication approval is recorded separately.
Scan index lists the authorized root, public-readiness status, evidence confidence, suggested classification, and proof posture. Related record: azwerks-nvim.
The scan index records intake posture; publication approval is recorded separately.
Scanner report documents authorized roots, commands run, public-safety findings, and the intake-time publication boundary. Related record: azwerks obsidian themes.
The report records intake behavior only; verification commands for the external project were not run.
Dossier summarizing the desklet source, package metadata, private flag, evidence, caveats, and public-safety questions. Related record: modewerks.
The dossier is intake evidence; publication approval is recorded separately.
Scan index lists the authorized root, public-readiness status, evidence confidence, suggested classification, and proof posture. Related record: modewerks.
The scan index records intake posture; publication approval is recorded separately.
Scanner report documents the package private flag, authorized roots, public-safety findings, and the intake-time publication boundary. Related record: modewerks.
The report records intake behavior only; verification commands for the external project were not run.
Dossier summarizing the private compiler system, package metadata, source evidence, caveats, and public-safety questions. Related record: werkform.
The dossier is intake evidence; publication approval is recorded separately.
Scanner report documents explicit source private status, authorized roots, public-safety findings, and the intake-time publication boundary. Related record: werkform.
The report records intake behavior only; verification commands for the external project were not run.
Shows claim boundaries, proof sequence, proof ledger, and evidence plates on the proof surface. Related record: werkregister surface composition.
Centralizes public filtering, route generation, entity lookup, and validation behavior. Related record: public content model.
Documents the website-owned CSS bridge to the read-only vendor Radium distribution. Related record: Radium design-system integration.
The vendor stylesheet itself remains outside the website implementation layer.
Scan index lists the authorized root, private package concern, evidence confidence, suggested classification, and proof posture. Related record: werkform.
The scan index records intake posture; publication approval is recorded separately.
Defines public record, evidence, operation, decision, relation, matter, note, and doc types. Related record: public content model.
Documents the extracted Radium package, checksum, package identity, structure, foundation files, components, templates, tests, and handoff materials. Related record: source inventory process.
The report documents repository intake, not final public website behavior.
Provides the component index used to identify existing Radium components instead of recreating them. Related record: source inventory process.
Lists audit findings, severity, affected routes, and proposed fixes before remediation work. Related record: surface adherence remediation.
tsc --noEmit (strict), vitest run, and a tsup build (ESM + CJS + type declarations) all run on every push and pull request to main. Related record: werkform.
determinism, buzzwords, development-task, non-visual-routing, lane-coverage, normalization, policy-gates, and work-vague-terms — each pins a specific behavior of the compiler. Related record: werkform.
Runs the same compile twice and asserts byte-identical output across the visual and development lanes. If any nondeterminism creeps in, CI goes red. Related record: werkform.
Covers the visual and development lanes directly; other lanes inherit the same pure compile path but are asserted through their own contract tests.
Shows record detail composition with header, proof, ledgers, relations, and colophon. Related record: werkregister surface composition.
Shows the work index composition with filters, sort control, result plates, and public records. Related record: werkregister surface composition.
Documents fixes applied to first surfaces, public-boundary checks, component preservation status, and remaining risks. Related record: surface adherence remediation.
The report documents a remediation pass, not complete quality certification.