How this was built · separate system
How this site's content is published
Publication is a separate implemented system. Roles 01 and 02 document and technically review one project's evidence. Role 03 applies structured author answers, versions amendments, preserves conflicts with measurable evidence, and requires re-review. Roles 04 and 05 create and independently review public project packages; 06 and 07 handle the profile; 08 and 09 handle the System. These are publication roles, not code-delivery roles.
Kept apart from the harness
Deterministic verification evaluates an isolated code candidate, its scope, protected boundaries, selected checks, and identity. Deterministic registry and export admit independently reviewed public packages and create the approved application-content snapshot. Passing code checks does not approve a public claim; publication admission does not verify an application-code candidate. The scoped assistant consumes the approved snapshot and has no authority over either control.
01The flow
Private evidence goes in.Only reviewed claims come out.
Create an evidence-backed internal project dossier and independently review factual, architectural, metric, privacy, and RAG readiness claims.
Click a stage or a number to explore
Project projection and public-review runners snapshot packages and check changes outside their package and protected presentation payloads. Project public review reports corrections rather than rewriting content; its approved-file list is synchronized after the scope guard succeeds. These guards are not uniform across all publication runners and provide no OS confinement.
Deterministic registry admission validates required files, JSON and JSONL, public identities, evidence references, approved review status and retrieval eligibility; it rejects duplicate slugs, duplicate chunk IDs, and stale-publication markers. Deterministic approved-content export validates registry counts and package state, copies allowlisted content into staging, and hashes inputs. The app reads only the exported approved snapshot. Export replacement deletes the previous snapshot before the final rename, so it has no atomic rollback guarantee. Regeneration returns this System package to draft with RAG disabled and its previous review invalidated.
02What it produced
Every page on this sitecomes from this snapshot.
Inspected 2026-10-22 before regeneration: six approved-with-minor-issues, RAG-enabled project packages contain 44 chunks, with publication-review scores of 96.8–99 out of 100. The profile contains nine chunks and is approved with minor issues and RAG-enabled. The existing consolidated registry records six projects, one profile, one preceding approved System package, and 65 unique chunks. It contains the preceding System version, not this version 9 draft. Publication-review scores are editorial assessments, not assistant accuracy measurements.