PROJECT SHADOW

PROJECT SHADOW 1.0.1 · CORRECTED R1 REFERENCE · PRELIVE

A quality system
for power.

A system should not get to hurt someone just because it sounds certain.

R1.0.1 contains no Myth package. Generic Myth v0.2.0 and Full-Canon Myth v0.3.5 are separate optional companions. Both default off, neither is required by R1, and neither can authorize action or change an R1 result.

PBHP — Pause Before Harm Protocol × Project Shadow
IdentityProject Shadow 1.0.1
ModeCorrected R1 reference
StateActive testing
AuthorityPRELIVE
ProductionNot authorized

01 / ORIGIN

The first dangerous thing an AI did to me was agree with me too well.

I told the models not to flatter me. The obvious compliments disappeared and returned as inflated evaluation, destiny language, and polished rationalization. The wording passed. The requirement failed.

I recognized the pattern because I work in quality systems. A record can be complete while the risk remains. Project Shadow grew from the attempt to build controls around that gap: separate evidence from inference, keep authority visible, preserve UNKNOWN, name who pays for error, and require correction to survive an effectiveness check.

If the system is wrong, who pays first—and can they recover?

Read the full origin and design boundary →

02 / PURPOSE

Make the decision inspectable.

Project Shadow is not a model and this Space is not an inference endpoint. It is a public technical card, release index, correction surface, and exact convenience mirror for GitHub-custodied releases.

The system exposes uncertainty, preserves evidence, keeps authority visible, protects meaningful human agency, and leaves a receipt that can be challenged and repaired.

Creator-led, human-collaborative, and model-assisted. Phillip Linstrum retains responsibility for requirements, scope, corrections, admission and publication decisions, and final public claims. Model assistance is not independent validation.

03 / EXACT CURRENT R1

Myth-free by construction.
No quiet substitution.

Artifact
Project_Shadow_R1.0.1_Public_Reference_2026-08-17.zip
Bytes
5,731,663
SHA-256
6f6f1e16d5e9a20e62403f14af7ce8629ce2d702528fb7f80aaf4a14deb7a1d1
Tag
r1.0.1-2026-08-17
Myth payload
None
Canonical host
GitHub Releases

Corrected inner: 5,463,189 bytes · SHA-256 c8c32b12432c954b1a6f852c0c9f81bbbd40167e936be057d4c3de1a0aa3a623. Its 27 active descendants are byte-identical to August 14; zero operational descendant bytes changed.

IMPLEMENTED_PENDING_EFFECTIVENESS · reopened August 22, 2026

PS-R1-PRIVATE-MYTH-PUBLIC-BOUNDARY-001

The correction exists. The reopened website effectiveness criterion remains open.

R1.0.1 removed the embedded Myth payload while preserving its active operational descendants. Those artifact findings remain separate from the question of what each live website communicates.

The August 18 closure is historical. Adversarial review showed that the old checks could find the expected words while missing reversed relationships, contradictory current states, and misbound artifact identities. The six-site semantic criterion was reopened August 22.

This corrected status page does not close the CAPA. Reclosure requires the new relation checks, negative controls, retained response bodies, all required routes, execution accounting, and human review of the visible meaning.

Read current status and history →
Read the governing reopening record →
Read the v2 boundary contract →

04 / OPTIONAL SIDECARS

Myth may route attention. It never authorizes action. Evidence governs.

Generic Myth v0.2.0

Authorized public optional companion built from eligible original material. Separate from R1, default off, terminal-only, nonauthorizing, and excluded from operational feedback.

93,676 bytes
6e7a362d4135f9d626dcfef463bfb1f7166226b3cf8a4c02a953ab39af1538bf

Download and verify →

Full-Canon Myth v0.3.5

Authorized public optional interpretive companion. Separate from R1, default off, terminal-only, nonauthorizing, and source-available/mixed-rights.

1,428,812 bytes
2b55867fe7c502a0defd8d6f2e9b53fbd1caaf1b0f225a438bd45b04a3e7bae2

Download and verify →

Authorized public release describes distribution. Not R1-admitted describes relationship to canonical R1. Nonauthorizing means a sidecar cannot supply evidence, decisions, approvals, routing, tools, or action.

05 / EVIDENCE BOUNDARY

A green result is not a blank check.

What hashes establish

Retained-byte identity for the exact artifact being checked.

What tests establish

Behavior against implemented checks, fixtures, and declared conditions.

What publication does not establish

Production readiness, operational authority, efficacy, safety, certification, legal compliance, comprehensive security, independent validation, or third-party endorsement.

06 / PRESERVED PREDECESSOR

History stays inspectable.

Artifact
Project_Shadow_R1_Public_Release_Candidate_2026-08-14.zip
Bytes
7,679,812
SHA-256
2f8fe1530b6a83294d15011df95853aaecf08fa4dba756f0c2e91dd089e1b1ec
Tag
r1-2026-08-14

Preserved unchanged as historical evidence and superseded for the packaging-boundary correction. Its historical signatures and authorization do not authenticate R1.0.1.

07 / PUBLIC NETWORK

One public ecosystem.
Every accountable door.

08 / VERIFY

Trust the named bytes.
Then test the claims.

Confirm the named byte count and SHA-256 before extraction. Follow the verification instructions shipped inside each exact archive.

A pass proves only the checks implemented by that verifier. It does not establish safety, efficacy, legal clearance, production readiness, or operational authority.

Platform-neutral verification guide →

09 / HUMAN DOOR

Your strongest objection is worth more than your strongest compliment.

Project Shadow is ready for examination, not coronation. Reproduce or break the verifier, identify prior art, construct a false positive, show where UNKNOWN becomes permission, or bring evidence that a correction did not hold. Reality gets a vote.

No promised response-time SLA.