docs: replace PRODUCT.md with CONTEXT.md, remove vendor-strategy framing#53
Merged
Merged
Conversation
PRODUCT.md asserted AVE is "Layer 1 of the Bawbel five-layer architecture" whose open layers "drive adoption" for a "commercial moat," and carried a full adoption-strategy/roadmap section (Product Hunt targets, launch tactics). That framing asserts the standard exists to serve one implementer's product strategy, which cannot live in this repo at any register, per the framing discipline CONTEXT.md establishes explicitly. - Remove PRODUCT.md; add CONTEXT.md, which contains only what is true of the standard itself. Roadmap/adoption-tactics content lives in TRUST_STRATEGY.md, kept outside this repo (gitignored). - CLAUDE.md's Product context section pointed at PRODUCT.md and repeated the same five-layer/Product Hunt framing -- updated to point at CONTEXT.md and describe record growth as bounded by distinct behavioral classes, not an external target. - research-new-attack-classes SKILL.md listed "before a release or Product Hunt push" as a trigger -- dropped the launch-event framing. Two dated docs/agents/ session records also mention PRODUCT.md; left alone as historical record, same treatment as CHANGELOG.md elsewhere in this repo.
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
PRODUCT.mdasserted AVE is "Layer 1 of the Bawbel five-layer architecture" whose open layers "drive adoption" for a "commercial moat," and carried a full adoption-strategy/roadmap section (Product Hunt targets, launch tactics). That framing asserts the standard exists to serve one implementer's product strategy -- inconsistent with this repo's own neutrality principle, and the exact issue CONTEXT.md's framing discipline section calls out.PRODUCT.md; addCONTEXT.md, which documents only what is true of the standard itselfCLAUDE.md's Product context section pointed atPRODUCT.mdand repeated the same five-layer/Product Hunt framing -- updated to point atCONTEXT.md, and record growth is now described as bounded by distinct behavioral classes rather than an external launch targetresearch-new-attack-classesSKILL.md listed "before a release or Product Hunt push" as a trigger -- dropped the launch-event framingPRODUCT.mdsections) now lives inTRUST_STRATEGY.md, kept outside this repo and gitignored, consistent with how the other local planning docs from earlier work on this repo are handledTwo dated
docs/agents/session records also mentionPRODUCT.md; left alone as historical record, same treatment asCHANGELOG.mdgets elsewhere in this repo.Test plan
python3 scripts/validate_records.py-- all 59 records still validpython3 -m pytest tests/ -q-- 118 passedfive-layer|Layer 1 of the Bawbel|commercial moat|Product Hunt-- zero matches outside the two historical session docsPRODUCT.mdbesidesCLAUDE.md(now fixed)