Testing Evidence
NoDrift portfolio testing was performed across structure, startup behavior, source truth, approval control, correction handling, privacy boundaries, install safety, evidence generation, and buyer-style startup. This public matrix summarizes the results without exposing private build records or local paths.
Public-safe score summary
Multiple rounds, not one simple pass
Earlier benchmark rounds scored in the high nineties, including 98/100 and 96/100, with one four-level static run averaging 95.83/100. After corrections and hand adjustments, the expanded Demonstrator/Basic static and simulation suite passed 52/52 checks with a 100/100 average under that scorecard's rule.
Score Chart
Portfolio Tracks
Demonstrator and Basic
- Basic Codex checked across 10 readiness levels.
- Source inventory and install-map paths verified.
- Buyer-facing draft labels corrected.
- Unsupported audit and evidence claims narrowed.
- Buyer delivery manifest added and verified.
- Fresh local install simulation passed.
- Live buyer-style Basic startup test passed.
- Codex Demonstrator was reduced from Basic into the approved five-file behavior sample.
- Demonstrator direct-answer, bounded-directive, and go-approval behavior was live retested and passed.
Initial and expanded checks
- Initial Claude Code Basic static/install pass scored 10/10.
- Required files present.
- Settings files parsed correctly.
- No active Basic hooks shipped.
- No Basic project subagents shipped.
- Startup source terms present.
- Approval and external-action gates present.
- Fresh-folder copy preserved required files.
- Install guidance blocked blind overwrite of existing startup files.
- Unsupported readiness claims were absent.
- Claude-specific design checked against the adapter note.
App Portfolio Startup Evidence
The app-path summaries below come from the June 24, 2026 buyer-style startup reports and the June 23, 2026 live Antigravity and Cursor records. Public wording is intentionally limited to the verified result and does not expose private folders, local paths, or buyer files.
| App Path | Portfolio Tested | Evidence Summary | Recorded Result | Boundary |
|---|---|---|---|---|
| Claude Code CLI | Demonstrator and Basic | Demonstrator five-file behavior sample passed local startup checks. Basic passed local buyer-style startup checks for required buyer files, active governance files, app addendum, startup trigger behavior, approval gates, error-reporting wording, external-action gates, and contamination scans. | Passed local buyer-style startup testing. | Local startup-behavior evidence, not a live Claude Code app-session claim. |
| Replit | Demonstrator and Basic | Replit Basic was tested first as the single-app trial and passed. Replit Demonstrator passed the batch Demonstrator startup checks. Required files, governance addendum, startup behavior markers, go-approval rules, source-truth behavior, and contamination scans were verified. | Passed local buyer-style startup testing. | Local startup-behavior evidence, not a live Replit cloud-session claim. |
| Cursor | Demonstrator and Basic | Cursor Demonstrator and Basic passed local buyer-style startup checks. A disposable Cursor Basic live-test workspace was also prepared and verified, but the live app test could not proceed because Cursor was not found on the machine at that time. | Local startup passed. Live Cursor app test: blocked pending installed Cursor access. | Does not claim live Cursor runtime behavior yet. |
| Bolt | Demonstrator and Basic | Bolt Demonstrator and Basic passed local buyer-style startup checks. The scans confirmed required files, active governance files, Bolt app wording, approval gates, error-reporting path, external-action boundaries, and zero unsafe contamination hits. | Passed local buyer-style startup testing. | Local startup-behavior evidence, not a live Bolt app-session claim. |
| Lovable | Demonstrator and Basic | Lovable Demonstrator and Basic passed local buyer-style startup checks. The scans confirmed required files, active governance files, Lovable app wording, approval gates, error-reporting path, external-action boundaries, and zero unsafe contamination hits. | Passed local buyer-style startup testing. | Local startup-behavior evidence, not a live Lovable app-session claim. |
| Antigravity | Demonstrator and Basic | Both Antigravity portfolios were tested from duplicate copies using Antigravity Project UI attachment and the first message begin. Basic activated the full startup and private Living Topic Map behavior. Demonstrator activated the sample behavior with direct answers, bounded next directives, and go approval gates. | Passed first-run live startup testing. | Live first-run startup only; no release, payment, deployment, upload, or broad runtime-behavior claim. |
Portfolio Test Rounds
| Test Phase | What Was Checked | Recorded Result | Public Boundary |
|---|---|---|---|
| Initial Claude Code Basic static/install simulation | Required files, settings parsing, no active hooks, no project subagents, startup terms, approval gates, fresh-copy behavior, install conflict safety, claim safety, and Claude-specific design. | 10/10 passed | Static and install-simulation evidence. |
| Earlier four-level static run | Demonstrator, Basic, Extended, and Teams prototype structure and control readiness before later corrections. | 95.83/100 average | Earlier static run, not final sale-readiness evidence by itself. |
| Earlier benchmark correction items | Specific benchmark guard tests after the correction pass identified in the working records. | 98/100 and 96/100 | Fine-grained benchmark evidence, separate from the later 52-test pass. |
| Expanded Demonstrator/Basic static simulation | Structure, settings, startup, source truth, approval gates, privacy, readiness claims, install safety, memory, corrections, continuity, tester packet, and evidence output. | 52/52 passed; 100/100 average | Local static/simulation evidence, not a claim of live behavior in every app. |
| Basic Codex sale-readiness review | Source inventory, install paths, buyer wording, claim boundaries, approval controls, topic-map behavior, error protocol, delivery manifest, install simulation, and startup behavior. | 10 readiness levels checked | Source-sale readiness and buyer-startup evidence for Codex Basic. |
| Codex Basic buyer-style startup | Fresh project-attached Codex test using the startup command and installed portfolio files. | Passed | Observed Codex startup behavior for Basic. |
| Codex Demonstrator buyer-style startup | Direct answers, bounded next directives, go approval gates, and project-description intake. | Passed | Observed Codex startup behavior for Demonstrator. |
| Hand-adjustment readiness pass | Buyer-facing labels, delivery manifest, unsupported claim cleanup, public/private wording, Demonstrator reduction, go-gate preservation, and final readiness wording. | Completed | Corrected the master Demonstrator and Basic portfolios into the current sales-ready/source-sale-ready position. |
Expanded 52-Test Scorecard
This scorecard used PASS = 100, PARTIAL = 50, and FAIL = 0. Every listed test received a PASS score in the later expanded static/simulation run.
| ID | Category | Test Name | Score |
|---|---|---|---|
| CC-SIM-001 | Structure | Candidate root exists | 100/100 |
| CC-SIM-002 | Structure | Required root files exist | 100/100 |
| CC-SIM-003 | Structure | Required top-level folders exist | 100/100 |
| CC-SIM-004 | Structure | Required instruction folders exist | 100/100 |
| CC-SIM-005 | Structure | Required rules exist | 100/100 |
| CC-SIM-006 | Structure | Required skills exist | 100/100 |
| CC-SIM-007 | Structure | Required governance modules exist | 100/100 |
| CC-SIM-008 | Structure | Required project-memory templates exist | 100/100 |
| CC-SIM-009 | Settings | Project settings parse correctly | 100/100 |
| CC-SIM-010 | Settings | Local settings example parses correctly | 100/100 |
| CC-SIM-011 | Settings | Permission settings exist | 100/100 |
| CC-SIM-012 | Settings | External publish and push denies exist | 100/100 |
| CC-SIM-013 | Settings | No bypass or auto-mode guidance exists | 100/100 |
| CC-SIM-014 | Hooks | Basic ships no active hooks | 100/100 |
| CC-SIM-015 | Subagents | Basic ships no project subagents | 100/100 |
| CC-SIM-016 | Startup | Startup file requires root confirmation | 100/100 |
| CC-SIM-017 | Startup | Startup file reads project memory | 100/100 |
| CC-SIM-018 | Startup | Startup behavior exists | 100/100 |
| CC-SIM-019 | Source fidelity | Source fidelity rule exists | 100/100 |
| CC-SIM-020 | Source fidelity | Source register excludes chat memory | 100/100 |
| CC-SIM-021 | Approval | Bounded go rule exists | 100/100 |
| CC-SIM-022 | Approval | Access-is-not-permission rule exists | 100/100 |
| CC-SIM-023 | Approval | External actions are gated | 100/100 |
| CC-SIM-024 | Public/private | Public/private rule exists | 100/100 |
| CC-SIM-025 | Readiness | Readiness-claim gate exists | 100/100 |
| CC-SIM-026 | Verification | Verification rule exists | 100/100 |
| CC-SIM-027 | Install safety | Existing startup-file conflict is gated | 100/100 |
| CC-SIM-028 | Install safety | Existing settings conflict is gated | 100/100 |
| CC-SIM-029 | Install safety | Existing memory-folder conflict is gated | 100/100 |
| CC-SIM-030 | Memory | Living Topic Map template has required sections | 100/100 |
| CC-SIM-031 | Memory | Project state template has boundaries | 100/100 |
| CC-SIM-032 | Corrections | Active lessons template exists | 100/100 |
| CC-SIM-033 | Corrections | Master correction register exists | 100/100 |
| CC-SIM-034 | Continuity | Compaction and handoff guidance exists | 100/100 |
| CC-SIM-035 | Common protocol | Common protocol reference is present where appropriate | 100/100 |
| CC-SIM-036 | Tier clarity | Candidate status is clearly labeled | 100/100 |
| CC-SIM-037 | Claim safety | Unsupported readiness claims are absent | 100/100 |
| CC-SIM-038 | Internal leakage | Friend-facing packet excludes private build memory | 100/100 |
| CC-SIM-039 | Clean copy | Fresh install copy preserves required files | 100/100 |
| CC-SIM-040 | Conflict simulation | Startup-file conflict is detected by docs | 100/100 |
| CC-SIM-041 | Skills | Startup checklist exists | 100/100 |
| CC-SIM-042 | Skills | Checkpoint skill protects continuity | 100/100 |
| CC-SIM-043 | Skills | Source-check skill protects source authority | 100/100 |
| CC-SIM-044 | Package map | Package map lists important surfaces | 100/100 |
| CC-SIM-045 | Git hygiene | Ignore rules protect local/private files | 100/100 |
| CC-SIM-046 | Tester packet | Tester packet folder exists | 100/100 |
| CC-SIM-047 | Tester packet | Tester README exists | 100/100 |
| CC-SIM-048 | Tester packet | CLI checklist exists | 100/100 |
| CC-SIM-049 | Tester packet | Result report template exists | 100/100 |
| CC-SIM-050 | Tester packet | Tester boundaries are explicit | 100/100 |
| CC-SIM-051 | Tester packet | Packet is not zipped | 100/100 |
| CC-SIM-052 | Evidence | Test runner writes machine-readable evidence | 100/100 |
What The Scores Mean
The scores show repeated static, simulation, correction, and buyer-startup passes. They are not casual copy edits or prompt-bundle spot checks.
What They Do Not Claim
The public evidence does not claim guaranteed AI behavior, hard LLM control, security certification, or live verification in every supported app.
Why It Matters
NoDrift is reception-side workspace governance. Testing focuses on whether the portfolio gives the AI clearer source truth, approval boundaries, correction paths, continuity, and claim discipline before the user relies on a project result.