Skip to content

fix(a2ml): dedupe — keep descriptiles/, retire the 6a2/ copies - #19

Open
hyperpolymath wants to merge 1 commit into
mainfrom
fix/a2ml-dedup-prefer-descriptiles
Open

fix(a2ml): dedupe — keep descriptiles/, retire the 6a2/ copies#19
hyperpolymath wants to merge 1 commit into
mainfrom
fix/a2ml-dedup-prefer-descriptiles

Conversation

@hyperpolymath

Copy link
Copy Markdown
Contributor

Owner ruling 2026-08-27: 6a2/ is retired; descriptiles/ is canonical — it holds the files that describe the repo's state, while contractiles/ holds the contracts being honoured.

Where both directories held a file, the descriptiles copy is kept.

⚠ Every removal is accounted for

The copies differed — they were not duplicates — so this is not a no-op cleanup:

AGENTIC (both real; removed 6a2 34L, kept descriptiles 51L)
ECOSYSTEM (removed 6a2 copy was REAL, 20L; kept descriptiles copy is TEMPLATE RESIDUE, 45L)
META (both real; removed 6a2 27L, kept descriptiles 53L)
NEUROSYM (both real; removed 6a2 21L, kept descriptiles 23L)
PLAYBOOK (both real; removed 6a2 26L, kept descriptiles 137L)
STATE (removed 6a2 copy was REAL, 38L; kept descriptiles copy is TEMPLATE RESIDUE, 64L)

Two of these are a real loss: the removed 6a2 copy held this project's own content, while the kept descriptiles copy is un-instantiated rsr-template-repo residue. That is what the ruling selects for, and it is recorded here rather than dropped silently. The removed content remains in git history at the parent commit.

Estate context

This affects 5 repos: 007, 007-lang, frayed-knot-toolkit, lithoglyph, _pathroot. Measured across all of them, prefer-descriptiles loses real content in 19 file-pairs, drops a second real copy in 29 more, and correctly drops template residue in zero cases.

Related: standards#655, phronesis#92, proof-burrower#75.

Owner ruling 2026-08-27: 6a2/ is retired; descriptiles/ is canonical. descriptiles
holds the files that DESCRIBE the repo's state; contractiles holds the contracts
being honoured. Where both directories held a file, the descriptiles copy is kept.

⚠ EVERY REMOVAL IS ACCOUNTED FOR BELOW. The copies differed - they were not
duplicates - so this is not a no-op cleanup:

AGENTIC (both real; removed 6a2 34L, kept descriptiles 51L)
ECOSYSTEM (removed 6a2 copy was REAL, 20L; kept descriptiles copy is TEMPLATE RESIDUE, 45L)
META (both real; removed 6a2 27L, kept descriptiles 53L)
NEUROSYM (both real; removed 6a2 21L, kept descriptiles 23L)
PLAYBOOK (both real; removed 6a2 26L, kept descriptiles 137L)
STATE (removed 6a2 copy was REAL, 38L; kept descriptiles copy is TEMPLATE RESIDUE, 64L)

Two of these are a real loss: the removed 6a2 copy held this project's own content
while the kept descriptiles copy is un-instantiated rsr-template-repo residue. That
is what the ruling selects for, and it is recorded here rather than dropped
silently. The removed content remains in git history at the parent commit.

Estate-wide this affects 5 repos: 007, 007-lang, frayed-knot-toolkit, lithoglyph,
_pathroot. Measured across all of them: prefer-descriptiles loses real content in
19 file-pairs, drops a second real copy in 29 more, and correctly drops template
residue in ZERO cases.
@sonarqubecloud

Copy link
Copy Markdown

@gitar-bot

gitar-bot Bot commented Aug 27, 2026

Copy link
Copy Markdown

Important

You are using the Gitar free plan. Upgrade to unlock code review, CI analysis, auto-apply, custom automations, and more.

Gitar

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes.

@codacy-production codacy-production Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR consolidates A2ML metadata by retiring the .machine_readable/6a2/ directory and designating .machine_readable/descriptiles/ as the canonical source. Automated analysis shows the PR is up to standards; however, there is a noted regression in documentation quality where project-specific 'REAL' content is sacrificed for 'TEMPLATE RESIDUE' to satisfy structural alignment. There is also a discrepancy between the description, which mentions five repositories, and the single-repository scope of the current diff.

About this PR

  • This PR introduces a regression in documentation quality: project-specific content (specifically in ECOSYSTEM and STATE files) is being replaced by 'template residue' in the descriptiles/ directory. This is a side effect of the deduplication strategy favored by the owner ruling.

Test suggestions

  • Verify that all files listed in the audit (AGENTIC, ECOSYSTEM, META, NEUROSYM, PLAYBOOK, STATE) have been removed from the 6a2/ directory.
  • Verify that the remaining A2ML files in the descriptiles/ directory are syntactically valid and contain the expected (even if template) content.
  • Ensure no references to the retired 6a2/ directory remain in the codebase or automation scripts.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify that all files listed in the audit (AGENTIC, ECOSYSTEM, META, NEUROSYM, PLAYBOOK, STATE) have been removed from the 6a2/ directory.
2. Verify that the remaining A2ML files in the descriptiles/ directory are syntactically valid and contain the expected (even if template) content.
3. Ensure no references to the retired 6a2/ directory remain in the codebase or automation scripts.
Low confidence findings
  • The PR description mentions changes affecting 5 repositories, but the current diff only covers one repository context. Verify if the remaining repositories are being handled separately.

TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant