docs(whitepaper): v4.0 industry refresh + harness-layer thesis - #168
Open
rmzi wants to merge 2 commits into
Open
docs(whitepaper): v4.0 industry refresh + harness-layer thesis#168rmzi wants to merge 2 commits into
rmzi wants to merge 2 commits into
Conversation
Refreshes the whitepaper against the last ~12 weeks of agentic AI movement: new model tier (Sonnet 5, Opus 5, Fable 5/Mythos 5), the imminent MCP 2026-07-28 spec overhaul, Claude Code's shift to background-default subagents, and EARS notation as prior art for acceptance criteria. Adds a new standalone section, "The Harness Layer: Where PDS Sits Today," naming PDS's current position as a config layer on Claude Code's generic harness, and stating a directional (non-committal) next move toward owning more of the harness layer itself — grounded in 2026's harness-engineering discourse, Gartner's domain-specific-model projections, and Claude Cowork. Expands docs/competitive-analysis.md with the spec-driven-development landscape (GitHub Spec Kit, BMAD-METHOD, AWS Kiro) that had gone unaddressed — BMAD's GitHub-issue-documented cost blowouts now cited as external validation of PDS's lite/med/heavy swarm tiers. Adds docs/adr/0006-harness-layer-thesis.md. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code review is billed via overage credits. To resume reviews, an organization admin can raise the monthly limit at claude.ai/admin-settings/claude-code.
Once credits are available, push a new commit or reopen this pull request to trigger a review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/whitepaper.mdto v4.0 against ~12 weeks of agentic-AI movement: new model tier (Sonnet 5, Opus 5, Fable 5/Mythos 5), the imminent MCP 2026-07-28 spec overhaul, Claude Code's shift to background-default subagents, and EARS notation as prior art for acceptance criteria.docs/competitive-analysis.mdwith the spec-driven-development landscape (GitHub Spec Kit, BMAD-METHOD, AWS Kiro) — BMAD's GitHub-issue-documented cost blowouts now cited as external validation of PDS's lite/med/heavy swarm tiers.docs/adr/0006-harness-layer-thesis.md.Two platform-behavior gaps (background-default subagent backpressure, native auto-PR vs. PDS's human gate) are flagged as known-but-unresolved rather than silently assumed away; follow-up issues filed separately: #164, #165, #166, #167.
Test plan
docs/whitepaper.mdend-to-end; confirm the new section reads consistently with the existing vision-forward register (LLM Independence, Adoption Path Phase 3/4)docs/competitive-analysis.md's new section doesn't duplicate anything already covered elsewhere in the docGenerated with PDS