Reconcile FEATURES.md and PROJECT-MAP.md with the current generator - #91
Merged
Conversation
Both files were committed in the 2026-07-06 wrap (#84) from a superseded TangleClaw scaffold, while newer regenerated copies sat untracked in the working tree. Verified which was current against the generator itself (TangleClaw/lib/projects.js): the untracked copies match it, the committed ones do not. FEATURES.md documented the abandoned `file.js:line` pointer format — the generator now mandates stable `file.js#symbolName` anchors, precisely because line pointers rot with nothing re-verifying them — and named its third section "Methodologies / Engines" instead of "Governance / Engines". PROJECT-MAP.md predated the Tangle-Shared doc group (created 2026-07-29, confirmed live via the TangleClaw groups API), so it listed only AI Inference. Also resolves what the reconciliation would otherwise have dropped or carried forward unread: the three auto-stubbed TBD entries and every `<!-- describe -->` placeholder are filled in. The ARCHITECTURE.md stub gets no feature entry — it is a design document, not a feature, and was stubbed only because a PR touched it. FEATURES.md is still sparse: Server / API and Governance / Engines are empty. Nothing was removed to make them so.
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
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
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.
What
FEATURES.md: restore the current scaffold — stablefile.js#symbolNameanchor format, section namedGovernance / Engines.PROJECT-MAP.md: add the missingTangle-Shareddoc group.TBDentries and fill every<!-- describe -->placeholder in both files.### Internal.Why
Both files were committed in the 2026-07-06 wrap (#84) from a superseded TangleClaw scaffold, while newer regenerated copies sat untracked in the working tree — they collided on the next
git pull.Rather than guess which side won, I checked the generator:
TangleClaw/lib/projects.js(FEATURE_INDEX_TEMPLATE) emits exactly the untracked copies. The committed ones are stale in two specific ways:FEATURES.mddocumented thefile.js:linepointer format, which the generator has since abandoned in favor of stablefile.js#symbolNameanchors — the template's own reasoning is that line pointers rot because nothing re-verifies them. A map instructing future sessions to write rotting pointers is worse than no map.PROJECT-MAP.mdpredated theTangle-Sharedgroup (created 2026-07-29, 5 members — confirmed live against the TangleClaw groups API, not inferred from the file).Notes on judgment calls
ARCHITECTURE.mdstub gets no feature entry. It is a design document, not a feature; it was stubbed only because a PR touched the file. Inventing a feature to clear a checkbox would put a wrong entry in the index permanently.FEATURES.mdis still sparse —Server / APIandGovernance / Enginesare empty. That is the pre-existing state, not something this PR removed; the serve endpoint and delegate MCP server have no entries yet. Filling the index properly is separate work and I did not smuggle it in here.Test plan
FEATURE_INDEX_TEMPLATEinTangleClaw/lib/projects.js— headers and section names now match.Tangle-Sharedverified as a real, live group via the TangleClaw API before adding it.<!-- describe -->orTBDmarkers remain in either file.