The machine before the machine.
Project Shadow is a synthesis and rewrite layer spanning operational governance, philosophical attention, civic accountability, tooling, evaluation, and adoption. The blueprint keeps those workstreams connected without pretending they are the same product.
Open the system reference at this layer.
Follow the mechanism through numbered execution, a worked trace, artifact-bound evidence, adverse results, and validation still required.
Four workstreams
The project is large because it is carrying several related systems with different audiences, evidence, and release rules.
PBHPOperational governance
A deployment-time discipline for exact action, power, harm, dissent, gates, alternatives, and write-ahead receipts.
+
Operational governance
A deployment-time discipline for exact action, power, harm, dissent, gates, alternatives, and write-ahead receipts.
PBHP is the portable public core. It imports structured documentation, deterministic classification, drift review, and corrective/preventive action habits from safety and quality practice without borrowing those domains' authority.
Public adoption materials remain plain-language and operational. They do not require the reader to adopt Shadow's symbolic layer.
PHILOSOPHICALAttention and translation
A literary and philosophical foundation that helps humans remember where to look under pressure.
+
Attention and translation
A literary and philosophical foundation that helps humans remember where to look under pressure.
This layer contributes Care, Clarity, Paradox, Maybe/Therefore, failure archetypes, and a vocabulary for capture and correction. Its firewall is absolute: symbols route attention into checks; evidence and gates decide action.
CIVICAccountability surfaces
The American Repair Manual, The Record, and related civic work apply evidence, correction, and power analysis in public life.
+
Accountability surfaces
The American Repair Manual, The Record, and related civic work apply evidence, correction, and power analysis in public life.
These projects share methods—receipts, source separation, explicit AI Opinion, correction history, least-powerful-first analysis—but remain independent sites and editorial systems rather than navigation branches of Shadow.
INFRASTRUCTURETools, comparisons, adoption, and evaluation
Executable runtime, SIL gauges, protocol codec, standards views, integration contracts, TEVV, behavioral experiments, and an adoption dossier.
+
Tools, comparisons, adoption, and evaluation
Executable runtime, SIL gauges, protocol codec, standards views, integration contracts, TEVV, behavioral experiments, and an adoption dossier.
The infrastructure makes the ideas testable. It also creates a larger burden of version identity, claim control, licensing, reproducibility, and independent challenge.
Repository strata
The historical project map preserves provenance and prevents a later synthesis from erasing where a mechanism came from.
00—02Blueprint, PBHP history, philosophy
00_blueprint defines purpose and audiences; 01_pbhp_history preserves protocol evolution; 02_almsivi_chim holds the philosophical/literary source layer.
+
Blueprint, PBHP history, philosophy
00_blueprint defines purpose and audiences; 01_pbhp_history preserves protocol evolution; 02_almsivi_chim holds the philosophical/literary source layer.
History is operationally important: the public protocol, internal canonical release, ULTRA working specification, and Shadow runtime have not always advanced in lockstep. The blueprint treats version skew as a release risk, not a cosmetic documentation issue.
03—04Framework comparisons and synthesis
03_framework_comparisons studies compatible systems; 04_synthesis records what was absorbed, adapted, cited, rejected, or left unresolved.
+
Framework comparisons and synthesis
03_framework_comparisons studies compatible systems; 04_synthesis records what was absorbed, adapted, cited, rejected, or left unresolved.
A comparison is not an endorsement. Each candidate mechanism receives a provenance, license, compatibility, duplication, authority, and evidence review before it can alter the runtime.
05—07Tools, ecosystem, adoption
05_tools contains executable instruments; 06_ecosystem maps adjacent work; 07_adoption_package translates the system for practitioners and reviewers.
+
Tools, ecosystem, adoption
05_tools contains executable instruments; 06_ecosystem maps adjacent work; 07_adoption_package translates the system for practitioners and reviewers.
The adoption package was described in the recovered overview as an approximately 19,000-word external dossier with a five-evaluator AI assessment and roughly 65,000 words across seventeen post-evaluation documents. Volume is not release readiness; reconciliation and human review remain required.
99Archive
Retired, superseded, duplicated, or provenance-sensitive material remains inspectable without silently steering the active build.
+
Archive
Retired, superseded, duplicated, or provenance-sensitive material remains inspectable without silently steering the active build.
Archiving is a governance act. A removed mechanism should retain its reason, successor, compatibility note, and affected receipt or migration path.
Audience and firewall
A system that says everything to everyone becomes either incomprehensible or misleading.
PRACTITIONEROrganizational adoption
Needs plain controls, roles, schemas, operating examples, failure handling, and bounded claims—not lore prerequisites.
+
Organizational adoption
Needs plain controls, roles, schemas, operating examples, failure handling, and bounded claims—not lore prerequisites.
The adoption path enters through PBHP, SIL, receipts, implementation patterns, and evidence status. Symbolic vocabulary may be omitted entirely without changing the gate contract.
RESEARCHERAcademic and evaluation
Needs artifact identity, preregistration, methods, datasets, scoring, limitations, adverse results, and independent reproduction paths.
+
Academic and evaluation
Needs artifact identity, preregistration, methods, datasets, scoring, limitations, adverse results, and independent reproduction paths.
The research surface should expose nulls and failures at the same resolution as supportive results. A test suite passing its own contracts is not a behavioral validation of the target system.
CONTRIBUTORMechanism and code contribution
Needs clean-room provenance, license compatibility, typed status, tests, change control, and a clear authority boundary.
+
Mechanism and code contribution
Needs clean-room provenance, license compatibility, typed status, tests, change control, and a clear authority boundary.
Contributors should be able to tell whether an idea is a metaphor, proposed check, built function, integration contract, executed experiment, accepted runtime mechanism, or retired artifact.
FIREWALLMyth may route attention; it never authorizes
No character, story, aesthetic, philosophical identity, or personal canon can produce a real-world permission state.
+
Myth may route attention; it never authorizes
No character, story, aesthetic, philosophical identity, or personal canon can produce a real-world permission state.
The required path is symbol → attention → named check → evidence → deterministic gate → receipt. If translation cannot reach a check, it remains interpretation rather than governance.
Project Shadow is an ecosystem with controlled interfaces—not one giant claim wearing a single name.