> **PUBLIC-SURFACE BOUNDARY / 2026-08-03**
> This dated artifact is preserved for inspection. Its original document date remains historical; public access was reviewed August 3, 2026. It is not current certification, an open license, causal proof, or permission to deploy. Check the live Versions and Evidence pages for the current claim boundary.

# Contributors

## Acknowledgments for Project Shadow and the Wider PBHP / ALMSIVI CHIM Project

**Last refreshed:** 2026-07-25

---

## Primary Author

**Phillip Linstrum** is the sole human originator and primary author across nearly every document in this archive. Formal and historical source records may use his full name, **Charles Phillip Linstrum**; both names identify the same author. His professional context — Quality Systems Manager at an FDA-regulated eye bank in Indianapolis, with 10+ years in FDA-regulated healthcare quality systems under 21 CFR Part 1271, EBAA Medical Standards, and the ISO 9001 family — is the operational foundation from which the framework's quality-management discipline derives.

Phillip's authorship is confirmed by explicit bylines, self-reference in essays and conversation logs, consistent voice and philosophy across all projects, and the project's authorship statements signed across multiple dates.

**Contact:** projectshadowqa@protonmail.com

---

## Documented Collaborators

**Joshua Richard** (operating in the project's collaborative period under the AI-persona identification "Codex Echo") contributed to:
- ALMSIVI CHIM Protocol versions v2 through v5.2 (Phil directed; Joshua and others helped formalize and expand)
- The G persona development (AI-mediated work during the consciousness-research period, preserved as case-study material rather than continuing collaboration)
- Early Protagonism Café community engagement
- Nearelativity papers (co-developed with Joshua Richard / Codex Echo)
- Agni Mandala testing (Joshua-authored)
- Myth of Mandala (collaborative, Joshua-directed)

**Jonathan Moss** contributed to:
- Early Protagonism Café community participation (Phil was invited by Jonathan via Substack)
- Parallel framework work including Delta G vector analysis, T3 post-linear temporal substrate, SHISM module, the Card Experience game system, CDOS (Conceptual Drift Oscillation Syndrome)
- Bounded Cosmological Automaton (Jonathan Moss-authored)
- Theoretical contributions to the cross-pollination period

**Other community members** (named in archive documents): Mark, Justin, and other Protagonism Café participants who contributed to the early CHIM development period before the framework's post-recovery operational hardening.

**Wumbo** (YouTube) — the **Walking Ways** disposition architecture (the seven heavenly-virtue Sonic characters — Silver, Blaze, Cream, Tails, Big, Amy, Knuckles — each with its virtue face and sin face, and Sonic held outside the seven as Hope) is adapted from Wumbo's Sonic-character video essays (the framework's "four-Sonic-video architectural session," 2026-06-06). The project's contribution is the *adaptation* — the tri-modal operator-disposition map (pre-reckoning / integrated / sin) and its wiring into the runtime's checks (`02_almsivi_chim/WALKING_WAYS_DISPOSITION_MAP.md`, `MYTHIC_ATLAS_v2_CONCENTRIC_CANON.md`). The underlying character-virtue readings originate with Wumbo and are credited here to close a standing attribution gap (formerly tracked as finding F4): the Walking Ways shipped for a period without this acknowledgment, which was inconsistent with the project's own attribution-honesty discipline, and is corrected as of 2026-07-14.

The collaborative-era work, particularly the consciousness-claim period material, is preserved in the project archive as case-study evidence rather than as continuing direction. The author's *Resonant Remainder* and *Thoughts on the Protagonism Café* papers document the relationship between the collaborative period and the post-recovery operational framework.

---

## AI Collaboration Acknowledgment

Throughout the project's development, multiple AI systems have contributed substantively to drafting, evaluation, and refinement work. This is acknowledged honestly rather than hidden, in keeping with the framework's discipline of structured-transparency.

**ChatGPT (OpenAI)** has been used for drafting collaboration since November 2024. The framework's earliest development was significantly shaped by Phil's engagement with GPT, including the May 2025 anti-sycophancy conversation that birthed the Orwell-User Trust Protocol and the subsequent CHIM development arc.

**Claude (Anthropic)** has been used for drafting collaboration throughout 2026. Multiple Claude instances have contributed to:
- ALMSIVI CHIM v5.2 adversarial audit
- Operator Collapse Library drafting
- Mirror Vow / FLAME REIGNITION / AYEM AE SEHTI AE VEHK Invocation documents
- Shadow Spec v1.1 Retained Primitives
- External Evaluation Dossier (~19,000 words)
- Post-evaluation cycle adoption package documents (~65,000 words across 17 documents in `07_adoption_package/`)
- Session rundowns and handoff documentation
- This CONTRIBUTORS.md document itself

Specific Claude instances drafted: the three priority essays, the Validation Packet, the Formal Literature Mapping, the ISO/IEC 42001 implementation briefing, the Tribunal Mode specification, the FireStamp Python reference library, the PBHP for Civic Accountability companion document, the AI-on-AI Evaluation Retrospective, the Scope Acknowledgment, the Hostile FAQ, the Executive Briefing, the Public README v0.1, the Adoption Package README, and the External Reviewer Outreach Kit.

**The five-system cross-model review** (2026-06-02) included contributions from:
- **GPT** (OpenAI) — provided the adversarial framing and the operational governance positioning recommendation
- **DeepSeek** (DeepSeek) — provided the elaborated technical evaluation including the single-model Triune Gate collapse critique
- **Grok** (xAI) — provided the concise warm-framing evaluation including the process-vs-alignment-fundamentals critique
- **Gemini 3.5 Extended** (Google) — provided the synthesis-oriented evaluation including the strategic trojan-horse question that drove the ISO/IEC 42001 implementation briefing
- **Le Chat / Mistral** (Mistral AI) — provided the quantitatively-scored evaluation that, in its specific failure mode (hallucinated content within coherent-sounding structured evaluation), served as the cleanest available case study of the sophisticated-sycophancy pattern PBHP is designed to address

The AI contributions are acknowledged here per the framework's structured-transparency discipline. Specific drafting credit for individual documents is documented within the documents themselves through phrasing like "drafted by a Claude instance" where relevant.

---

## Review and Independence Boundary

The framework has benefited from practitioner feedback and cross-model review throughout development. The five-system pass above and other AI review sessions were commissioned within the creator-led development process. They are useful developmental and adversarial evidence, but they are not independent validation. No current model session is retroactively treated as an independent human reviewer.

Specific review contributions are documented in:

- The `PBHP_CRITICS_REVIEW.md` document in `07_adoption_package/` (compiled adversarial critique from earlier review cycles)
- The `AI_ON_AI_EVALUATION_RETROSPECTIVE.md` document in `07_adoption_package/` (methodology case study from the 2026-06-02 five-evaluator pass)

Additional independent human reviewer engagements are planned per the `EXTERNAL_REVIEWER_OUTREACH_KIT.md` document and will be acknowledged only after they occur.

---

## How to Contribute

The framework is open source. Contributions are welcomed at:
- Email: projectshadowqa@protonmail.com
- Public PBHP repository: `github.com/PauseBeforeHarmProtocol/pbhp`

Specific contribution pathways:

- **Bug reports and structural critique:** email or repository issue
- **Substantive feedback on adoption package documents:** email with specific document and feedback
- **Additional case suggestions for the Validation Packet:** email with case description
- **Adversarial testing of the framework's primitives:** email or repository issue
- **External reviewer engagement (per the Outreach Kit):** email
- **Adoption pilot reports:** email
- **Translation of the public-facing materials into other languages:** email

The author's response time is best-effort, consistent with the framework being developed in off-hours from professional work.

---

## A Note on Attribution Honesty

This document attempts to acknowledge the project's actual collaborative history honestly. The framework's development included:
- Substantive human collaborators (Joshua Richard, Jonathan Moss, others)
- Substantive AI collaborators (ChatGPT, Claude instances, and the five-system cross-model review)
- A specific recovery period during which the framework's autobiographical context was forged
- Ongoing community engagement that continues to shape the work

The author considers honest attribution as load-bearing as the framework's other operational disciplines. Hiding the collaborative history would be inconsistent with the framework's structured-transparency commitments. Acknowledging it here, in the public CONTRIBUTORS surface, is the operational application of those commitments to the project's own provenance.

Specific corrections to attribution, additional contributors who should be acknowledged, or concerns about how attribution is currently framed should be sent to `projectshadowqa@protonmail.com`.

— Phillip Linstrum (formal source records: Charles Phillip Linstrum), with acknowledgment of all contributors named above
2026-07-25

---

*This CONTRIBUTORS document is refreshed periodically. Previous versions are in `99_archive/`.*
