-
Cold start vs. system-backed work Five paired scenarios were reviewed Public projection · evidence_facts[0]
Observed The pilot evidence set contains five anonymized tasks run once from a prompt-only starting point and once from a system-backed starting point.
Evidence Run metadata lists five paired scenarios; the comparison matrix is retained as the public projection source.
Limit that constrains this row Small sample size.
-
Cold start vs. system-backed work System-backed outputs carried named context Public projection · evidence_facts[1]
Observed The system-backed summaries include inherited decisions, named reusable assets, and explicit limitation language that the cold summaries did not consistently carry.
Evidence Before/after excerpts and metric notes on the proof detail page name reuse, inherited decisions, and explicit limitations as the primary reviewed signal.
Limit that constrains this row Anonymized scenarios only.
-
Cold start vs. system-backed work No productivity number is published Publicly inspectable · evidence_facts[2]
Observed The public case labels the result as a measured pilot and explicitly avoids broad ROI or productivity lift claims.
Evidence Claim status, metric note, and limitations all state that this is pilot evidence rather than a statistical productivity result.
Limit that constrains this row The result supports a launch proof, not a statistical productivity claim.
-
The page built from its own source Four source families are bound to the route Public projection · evidence_facts[0]
Observed The page is backed by route, process, narrative, and code-emission records rather than a standalone marketing brief.
Evidence Run metadata and source artifacts name the structured route record, narrative record, code plan, and process trace.
Limit that constrains this row This is one route, not the whole product.
-
The page built from its own source The source-backed route is published Publicly inspectable · evidence_facts[1]
Observed The demonstration exists as an inspectable public route and is included in the static site build.
Evidence The proof case links to `/how-it-works`; build output includes `/how-it-works/index.html`.
Limit that constrains this row It demonstrates traceability rather than measuring outcome lift.
-
The page built from its own source Numeric lift is held back Publicly inspectable · evidence_facts[2]
Observed The page avoids a numeric improvement claim until the controlled comparison clears its gates.
Evidence The proof case metric identifies claim discipline as the primary gate.
Limit that constrains this row This is one route, not the whole product.
-
Specialist lenses produce different work Eight role samples are published Publicly inspectable · evidence_facts[0]
Observed The public role gallery exposes eight launch-safe roles with a role caption, capability statement, and concrete output sample.
Evidence Homepage persona cards and this proof case both name eight featured roles and one artifact sample per role.
Limit that constrains this row Samples are static in the first launch.
-
Specialist lenses produce different work Four surface types are represented Publicly inspectable · evidence_facts[1]
Observed The gallery covers decision, copy, verification, and visual/motion surfaces rather than only persona descriptions.
Evidence Metric row lists four surface types; visuals include prompt studio, role lens spread, capability matrix, and surface route.
Limit that constrains this row Interactive role calls belong in the hosted-service phase.
-
Specialist lenses produce different work Interactive calls are not claimed Publicly inspectable · evidence_facts[2]
Observed The public case states that static samples ship first and interactive role calls are reserved for the hosted-service phase.
Evidence Limitations section explicitly names static samples and defers interactive role calls.
Limit that constrains this row Samples are static in the first launch.
-
A council run beats one generic lens Five lanes are separated before synthesis Publicly inspectable · evidence_facts[0]
Observed The public projection separates architecture, journey, verification, operations, and business lanes before the synthesized recommendation.
Evidence Council fanout visual, transcript storyboard, and mechanism stage each show five named lanes converging only after lane outputs exist.
Limit that constrains this row This is one sanitized run, not a statistical benchmark.
-
A council run beats one generic lens Color-separation lane board is public Publicly inspectable · evidence_facts[1]
Observed The public persona page now shows five persona lenses as layered color-separation plates that converge into one resolved buyer artifact.
Evidence The `Color-separated proof` board links the same retained corpus source into Hephaestus, Artemis, Cassandra, Mnemosyne, and Argus/HERMES lanes, then resolves them into a decision, limitation, and buyer-action artifact.
Limit that constrains this row The source prompt and lane outputs are not public until redaction is complete.
-
A council run beats one generic lens Cold baseline blends the evidence jobs Publicly inspectable · evidence_facts[2]
Observed The public case describes the cold start as one recommendation where architecture, journey, verification, operations, and business judgments are fused together.
Evidence Before artifact, storyboard step 01, and the T3 proof-row table all name the cold baseline as one blended response without separate source standards.
Limit that constrains this row The run gallery is a redrawn projection, not raw screenshot evidence.
-
A council run beats one generic lens T3 proof rows are visible before the transcript Publicly inspectable · evidence_facts[3]
Observed The public persona page shows a five-row T3 table before asking the reader to accept the broader claim.
Evidence The T3 table lists each lane, the cold-start failure mode, the corpus-backed signal, source class, and buyer decision in one visual review surface.
Limit that constrains this row The capture review board is a publication map, not the underlying private capture set.
-
A council run beats one generic lens Cold baseline review board is public Publicly inspectable · evidence_facts[4]
Observed The public persona page now shows the cold artifact beside the KBPD-backed artifact and lists five baseline checks before the T3 table.
Evidence The `Cold baseline artifact` section includes role boundary, source standard, claim pressure, public proof path, and language gate checks, each with an evidence-row link.
Limit that constrains this row The public page demonstrates reviewability and role separation, not automatic correctness.
-
A council run beats one generic lens Raw screenshots are intentionally withheld Publicly inspectable · evidence_facts[5]
Observed The proof case publishes redrawn mechanisms and explicitly reports zero public source screenshots.
Evidence Metric row `Public source screenshots: 0`; source artifact list marks retained run captures as private evidence; the run gallery labels itself as a public projection.
Limit that constrains this row This is one sanitized run, not a statistical benchmark.
-
A council run beats one generic lens Five-frame sanitized run gallery is public Publicly inspectable · evidence_facts[6]
Observed The public persona page now redraws the retained run as five frames: brief, corpus, lanes, synthesis, and buyer proof path.
Evidence The `Sanitized run gallery` section shows retained signal, public projection, and buyer read for each frame, plus an evidence-row link.
Limit that constrains this row This is one sanitized run, not a statistical benchmark.
-
A council run beats one generic lens Capture review board maps private screens to public proof Publicly inspectable · evidence_facts[7]
Observed The public persona page shows five capture-review rows that connect retained screenshot classes to public frames, redaction boundaries, and exact evidence-row links.
Evidence The `Capture review board` section includes panel launch, architecture lens, journey/verification lenses, operations lens, and business-language gate rows, each with retained signal, public frame, redaction boundary, and an evidence link.
Limit that constrains this row This is one sanitized run, not a statistical benchmark.
-
A council run beats one generic lens Four corpus source classes are represented Publicly inspectable · evidence_facts[8]
Observed The public mechanism shows role roster, prompt archive patterns, prior decisions, and project source as inputs to the run.
Evidence Metric row lists four corpus sources; source artifact list names role registry and prompt archive sources.
Limit that constrains this row This is one sanitized run, not a statistical benchmark.
-
A council run beats one generic lens HERMES and cold-reader gates are named Publicly inspectable · evidence_facts[9]
Observed The public case names the public-language lane and the cold-reader gate as corpus owners before the result becomes buyer-facing copy.
Evidence Corpus ownership cards and the T3 proof-row table identify HERMES, archive discipline, session memory, and cold-reader review as separate responsibilities.
Limit that constrains this row This is one sanitized run, not a statistical benchmark.
-
One brand system, multiple surface moods Three registers are rendered from one system Publicly inspectable · evidence_facts[0]
Observed The public specimen shows warm, neutral, and cool surface registers while keeping the same component skeleton.
Evidence Metric row names three theme registers; visual evidence shows three surfaces sharing one component structure.
Limit that constrains this row This proves visual system survival, not buyer conversion.
-
One brand system, multiple surface moods Design outputs are named source artifacts Public projection · evidence_facts[1]
Observed The case identifies generated design variables, the public specimen route, and motion rules as source artifacts.
Evidence Source artifact list names design outputs, specimen page, and component runtime motion rules.
Limit that constrains this row Accessibility remains a gate per surface class.
-
One brand system, multiple surface moods Accessibility remains a gate Publicly inspectable · evidence_facts[2]
Observed The proof does not claim every visual register is automatically ready for every accessibility context.
Evidence Limitations section states that accessibility remains a gate per surface class.
Limit that constrains this row The seven microsites are artifact-quality checks; they do not prove market lift or user preference.
-
One brand system, multiple surface moods Seven cold/backed specimen pairs are public Publicly inspectable · evidence_facts[3]
Observed The brand-system case links seven public specimen pairs across color, composition, voice, grid, perception, product decision, and typography surfaces.
Evidence The specimen proof matrix and specimen gallery both expose cold and system-backed links for all seven public microsites.
Limit that constrains this row The color, product-decision, and typography values are proxy checks from bounded specimens, not broad benchmark results.
-
One brand system, multiple surface moods Twenty-one specimen values are visible Publicly inspectable · evidence_facts[4]
Observed Each public specimen lists one primary value and two secondary values, for twenty-one visible measured values across the gallery.
Evidence The specimen gallery summary and per-specimen detail panels show the value labels, cold value, backed value, and interpretation.
Limit that constrains this row The retained multi-kit runtime is not public until publication hygiene and dependency validation are complete.
-
One brand system, multiple surface moods Color hierarchy specimen reduces near-value collisions Publicly inspectable · evidence_facts[5]
Observed The color specimen reports near-value collisions moving from 441 in the cold output to 18 in the system-backed output.
Evidence The specimen matrix, gallery selector, and evidence values all show the same 441 -> 18 color hierarchy delta.
Limit that constrains this row This proves visual system survival, not buyer conversion.
-
One brand system, multiple surface moods Product-decision specimen shifts toward outcomes Publicly inspectable · evidence_facts[6]
Observed The product-decision specimen reports outcome/output ratio moving from 0.08 in the cold output to 0.73 in the system-backed output.
Evidence The public product-decision microsite row names the buyer question, the primary value, the cold value, and the backed value.
Limit that constrains this row This proves visual system survival, not buyer conversion.
-
One brand system, multiple surface moods Typography specimen removes hardcoded pixel sizes Publicly inspectable · evidence_facts[7]
Observed The typography specimen reports hardcoded pixel font sizes moving from 11 in the cold output to 0 in the system-backed output.
Evidence The public typography specimen row and gallery detail show the cold/backed value and the bounded interpretation.
Limit that constrains this row This proves visual system survival, not buyer conversion.
-
One brand system, multiple surface moods Retained compositor depth is recorded but bounded Internal retained · evidence_facts[8]
Observed The public case records eight retained UI-kit adapters and 596 retained generated stories as the next publication boundary.
Evidence The system-surface lab and evidence values name the retained adapter count and story count while stating that the full runtime is not public yet.
Limit that constrains this row This proves visual system survival, not buyer conversion.
-
One review frame for many demos Eight proof families are registered Validated by build · evidence_facts[0]
Observed The public registry currently contains eight proof cases spanning comparisons, demos, a case study, a surface trace, and a benchmark placeholder.
Evidence Proof Studio index renders eight cards; validator output reports eight proof cases passed validation and leak scan.
Limit that constrains this row The first registry is curated, not automatically generated.
-
One review frame for many demos Every public case has status and limits Validated by build · evidence_facts[1]
Observed The proof-case validator rejects entries without claim status, limitations, visuals, metrics, source artifacts, and evidence facts.
Evidence `web/scripts/validate-proof-cases.ts` is part of the web prebuild and exits nonzero on missing required fields.
Limit that constrains this row Raw experiment assets require redaction before publication.
-
One review frame for many demos Registry is curated, not automatic Publicly inspectable · evidence_facts[2]
Observed The current registry is intentionally curated and raw experiment assets still require redaction before publication.
Evidence Limitations section states the first registry is curated and raw experiment assets require redaction.
Limit that constrains this row The first registry is curated, not automatically generated.
-
The starter kit runs locally Six local MCP tools are declared Validated by build · evidence_facts[0]
Observed The starter kit local MCP contract exposes health, search, context read, proof index, lint, and diagnostics tools.
Evidence Metric row lists six local tools; source artifacts name the local MCP README, local server, smoke command, and manifest.
Limit that constrains this row The local server works against extracted kit files only.
-
The starter kit runs locally Hosted account is not required for local inspection Publicly inspectable · evidence_facts[1]
Observed The local inspection path reads extracted starter-kit files and does not require hosted authentication.
Evidence Metric row reports zero hosted dependency; limitations distinguish local server behavior from the later hosted service.
Limit that constrains this row Hosted identity, payment operations, service visibility, and plan changes belong to the Phase 2 hosted service.
-
The starter kit runs locally Two smoke paths cover the local server Validated by build · evidence_facts[2]
Observed The proof case records two smoke paths: extracted-package Node smoke and Docker image smoke.
Evidence Metric row names two smoke paths and run metadata names one assembled package plus one Docker MCP image.
Limit that constrains this row Smoke tests prove startup and representative calls, not full hosted account behavior.
-
Controlled benchmark is not public yet No public lift number exists Publicly inspectable · evidence_facts[0]
Observed The benchmark case publishes no numeric lift result and labels the current result as null.
Evidence Metric row says current public number is none; claim status is null result.
Limit that constrains this row No benchmark result exists on the public site yet.
-
Controlled benchmark is not public yet Three benchmark arms are planned Public projection · evidence_facts[1]
Observed The planned benchmark compares project system, generic docs, and competent prompt-only baseline arms.
Evidence Metric row lists three planned arms; after-artifact summary describes separating structured files from generic docs and prompt-only baselines.
Limit that constrains this row The final claim may be narrow or null.
-
Controlled benchmark is not public yet Run artifacts are pending Pending · evidence_facts[2]
Observed The source artifact list marks run artifacts as pending, and the limitations state no public benchmark result exists yet.
Evidence Source artifacts include pending run artifacts; limitations explicitly state the result may be narrow or null.
Limit that constrains this row The result will be published only after the validity gates pass.